Hi,

We are experiencing long processing times in the Payment Reconciliation Journal when executing the Auto Match functionality, which relies on codeunit 1255 "Match Bank Payments".

Some companies have a large volume of Direct Debit Collection Entries that are no longer relevant for the matching process but must remain stored for historical purposes.

During analysis, we identified that codeunit 1255 always executes the procedure InitializeDirectDebitCollectionEntriesMatchingBuffer, which performs a full table scan on the Direct Debit Collection Entry table. This significantly impacts performance in high-volume scenarios.

Would it be possible to:

• Introduce an event (e.g. OnDisableDirectDebitCollectionEntriesMatch), similar to the existing OnDisable* events, to allow skipping this logic, or
• Provide a way to bypass the DirectDebitCollectionEntriesMatch process entirely when not required?

This would greatly improve performance for customers with large datasets.

We would appreciate your feedback on whether this can be addressed or if there are recommended workarounds.