Martin Winkels

Current Challenge

Currently, generating a credit note for a posted invoice is causing significant system slowdowns and freezing. This is particularly acute when handling invoices composed of 31 to 60 Sales Orders (SOs),with in total thousands of Sales Order Lines. The high volume of transactional data being processed in a synchronous, real-time fashion strains system resources, impacting both user productivity and system stability.

Proposed Solution: Batch Job for Credit Note Generation

To address these performance and usability issues, we propose implementing a batch job functionality for the credit note generation process. This enhancement would allow users to initiate credit note creation as a scheduled background task, similar to the existing "run in batch mode" feature for invoice generation.

Key Features:

• Asynchronous Processing: The system will queue credit note requests and process them in batches in the background, alleviating immediate processing load on the user session and UI.
• Batch Submission Interface: Introduce an option(e.g., a "Batch" button) the credit note generation form, enabling users to choose between synchronous and asynchronous execution based on their needs.
• Progress Tracking: Users will have access to batch job status and results, with notifications upon completion or failure.
• Scalability: The batch process will handle large datasets efficiently, breaking big jobs into manageable sub-tasks to prevent timeouts and reduce memory consumption.
• Configurable Scheduling: Credit note batches can be scheduled during off-peak hours or according to predefined intervals, further minimizing impact on system performance during business hours.

Business and Technical Benefits:

• Significant reduction in UI freezes and wait times, improving end-user experience and productivity.
• Enhanced stability and performance for other critical business functions by offloading heavy operations.
• Flexibility and control for finance or operations teams to handle high-volume credit note processing without manual intervention.
• Auditability and transparency with logs and monitoring tools integrated into the batch framework.

We noticed, that the new feature of automated Foreign currency postings during Ledger Settlement does not work, if we want to settle transactions in different Currencies.

Example:

Invoice of 100 USD is paid through payment run with USD.

Our Bank is an EUR Bank and transfers the USD to the Vendor but translates the 100USD into 90 EUR and sents us the 90 EUR confirmation

now on the clearing account we have:

1. Payment 100 USD -> 95 EUR
2. Bankconfirmation 90 EUR

these ledger settlements cant be settled without a manual posting

Description:

We have observed that the new automated foreign currency posting feature during Ledger Settlement does not currently support scenarios where transactions are settled in different currencies.

Scenario:

For example, consider the following process:

• An invoice of 100 USD is paid via our payment run, also in USD.
• Our bank account is denominated in EUR. When transferring the payment to the vendor, the bank converts 100 USD to 90 EUR and provides a 90 EUR payment confirmation.

This results in the following entries on the clearing account:

• Payment: 100 USD (converted to 95 EUR in our system)
• Bank confirmation: 90 EUR

Current Issue:

Currently, these entries cannot be fully settled automatically in the ledger, as the system does not post the realized foreign exchange gain or loss. Manual postings are required to clear the differences arising from currency conversion.

Suggestion:

We propose an enhancement to enable automatic posting of realized FX gains or losses during ledger settlements where transaction and settlement currencies differ. This would streamline the process, reduce manual work, and ensure accurate financial reporting.