Automated matching is one of those controls that looks trivial in a demo and becomes difficult in production. A payment arrives with a bank reference that does not match the invoice number. A gateway deducts a fee, so the amount is short by a few taka. One transfer settles six invoices. A customer pays twice and then asks for a refund. The software can handle any one of these; the problem is that they happen together.
This guide separates the two matches that finance teams often conflate, then walks through the failures that cause the most manual work and the fixes that keep the ledger clean.
Two matches, not one
- Invoice matching compares a supplier invoice with the purchase order and the goods receipt. It answers: did we order this, did we receive it, and is the price right?
- Payment matching compares a bank or provider payment with one or more invoices. It answers: who paid, how much, for which invoices, and what remains open?
A system can be excellent at the first and poor at the second. Both need an exception queue, an audit trail and a named owner.
Problem 1: Partial payments leave invoices open
Cause: the matcher expects the full invoice amount, so a part payment is treated as unmatched.
Fix: allow allocation against an open invoice with a remaining balance. Decide the business rule for oldest-open versus specified-invoice allocation, and show the remaining balance on the customer or supplier statement. Do not let a part payment silently close an invoice.
Problem 2: Gateway fees create a short payment
Cause: the customer pays the invoice value, the provider deducts a fee, and the bank credit is lower than the invoice.
Fix: record the gross payment, the fee and the net settlement as separate lines. Set a tolerance rule for known fee patterns, and post the fee to its own ledger account. A tolerance is not a licence to ignore differences; it should expire and be reviewed.
Problem 3: One payment covers many invoices
Cause: a corporate customer or distributor pays a lump sum against a statement, with no invoice-level detail.
Fix: capture a remittance advice, parse it where possible, and give the customer a portal to select invoices. If the remittance is missing, park the payment in an unapplied cash account and assign an owner to clear it. Never spread a lump sum across invoices by guesswork.
Problem 4: References are missing, reused or mistyped
Cause: the payment reference is free text, the same number is reused across branches, or the customer types the order number instead of the invoice number.
Fix: issue a unique payment reference per invoice, show it in the payment instructions, and support a lookup by multiple identifiers. Validate the reference at entry. For bank transfers, import the narration and match on a combination of amount, date and reference rather than the reference alone.
Problem 5: Timing differences look like missing payments
Cause: the sale is recorded on Friday, the provider settles on Monday, and the bank statement arrives on Tuesday.
Fix: keep transaction date, settlement date and value date as separate fields. Put pending payments in a clearing account, not in a suspense bucket that nobody owns. Reconcile by settlement date and publish a cut-off calendar for month-end.
Problem 6: Duplicate payments and duplicate credits
Cause: a webhook is retried, a bank file is imported twice, or a manual receipt is entered while the automatic one is still pending.
Fix: use an idempotency key on every payment event, deduplicate on provider transaction ID, and lock the bank statement import by file hash. When a duplicate is found, reverse it through a controlled process rather than deleting the record.
Problem 7: Refunds and chargebacks break the link
Cause: the refund is posted as a new payment, with no reference to the original sale or invoice.
Fix: link every refund and chargeback to the original transaction. Create reversal entries that preserve the audit trail, and route the case to a reason code. A refund without an original reference should be an exception, not a normal entry.
Problem 8: Currency and rounding differences accumulate
Cause: the invoice is in one currency, the settlement in another, and the exchange rate date is inconsistent.
Fix: store the rate and its source on the transaction. Post the difference to an exchange gain or loss account, and set a rounding policy for the base currency. Do not bury the difference in a generic adjustment line.
Problem 9: Manual overrides leave no trail
Cause: a finance user can force a match without a reason, and the override is not visible to the reviewer.
Fix: require a reason code, an approver and a note for every manual match. Report overrides weekly by user and by customer. If one person accounts for most overrides, the process or the master data is the problem.
Diagnostic sequence
- Count unmatched items by age, value and channel. Do not start with the oldest; start with the largest financial exposure.
- Pick five unmatched payments and trace each from bank statement to invoice to ledger.
- Check whether the failure is missing data, a wrong rule or a timing issue.
- Review manual overrides from the last month and the reasons attached.
- Reconcile one full settlement cycle end to end before changing the matcher.
Controls that keep matching healthy
- Separate the person who enters a supplier or customer from the person who approves a bank change.
- Set tolerance limits by value and channel, with an expiry date.
- Assign an owner to unapplied cash and review the ageing every week.
- Keep an audit trail for every allocation, reversal and override.
- Test the exception path, not only the happy path, before go-live.
Metrics
- Automatic match rate by channel.
- Value and age of unapplied cash.
- Duplicate payments detected and recovered.
- Manual overrides per hundred matches.
- Days to close the monthly reconciliation.
Where this fits in our work
Matching sits between payment integration and finance operations. Our Commerce Systems division builds the payment, settlement and reconciliation flow around your existing ledger; the pricing page explains how the scope is set. For the setup side of the same problem, read the payment reconciliation setup guide.
Sources
- Microsoft Learn, Accounts payable invoice matching, accessed 17 November 2026.
- PCI Security Standards Council, accessed 17 November 2026.
- OWASP Application Security Verification Standard, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.