We're looking for advice from anyone managing high-volume Accounts Receivable payment applications in Business Central.
We have several large customer accounts that generate approximately 400 sales orders per day, resulting in a significant number of invoices over a relatively short period. When payment is received, our Credit Control team may need to apply a single payment against 1,500+ open customer ledger entries.
Our customer payments are automatically created and posted through the Bank Account Reconciliation process. However, at the time the payment is posted, we do not have the customer's remittance advice, so the payment cannot be applied to the relevant invoices.
Once the remittance advice is received, our Credit Control team manually reviews it and applies the payment to the specific invoices identified by the customer. As a result, the payment application process takes place separately from the payment posting process.
During these large payment application processes, we're experiencing database deadlocks that impact other users, including our warehouse team, who are then unable to ship orders while the locks are in place.
We've investigated the issue and understand Microsoft's guidance to minimise the number of ledger entries processed in a single transaction. However, this isn't operationally practical given the transaction volumes we process.
We're already engaging with our Microsoft partner, but I'd be interested to hear how other organisations manage this scenario.
- Has anyone experienced similar locking or deadlock issues when applying high-volume customer payments?
- Have you found an ISV or custom solution that improves the application process?
- Have you adopted a different approach for allocating payments when remittance advice is received after the payment has been posted?
Any advice or experience would be greatly appreciated.
