Why good cash application never forces a match
The easiest way to make receivables reconcile is to hide the difference. Why that is the most expensive mistake in cash application, and what to do instead.
Manoj Tutika5 min read
Working on this yourself? Talk to Mark, our co-founder. We’re here to solve it with you.
On this page
Cash application is matching each incoming payment to the specific invoices it settles. Done well, it never forces a match: when a payment does not add up, the difference stays visible as its own item with a reason, instead of disappearing into a rounding account or the wrong invoice.
If you run finance at a growing company, or you are the founder who still matches payments on a Sunday evening, you know the temptation. The bank shows €4,180. The customer had €4,220 open. It is late, the number is close, and there is an account for small differences. One click and everything is green.
That click is the most expensive one in receivables. This post explains why, and what a good process does with the €40 instead.
What does forcing a match look like?
Take an illustrative payment. Brouwer Logistiek B.V. transfers €4,180.00 with the description "oct invoices". It has three open invoices with you.
- INV-2026-1042 for €1,250.00
- INV-2026-1047 for €1,785.50
- INV-2026-1051 for €1,184.50
Together that is €4,220.00, so the payment is €40.00 short. There are three common ways to make it "close", and two of them are forced.
The rounding account. All three invoices are closed and the €40 goes to a differences account. The books balance. But your revenue and output VAT still assume the customer paid in full, and nobody knows why they did not.
The amount match. Somewhere in the ledger there is another open invoice, INV-2026-1055, for exactly €4,180.00. A rule that matches on amount closes it. The total fits, so it looks done. In reality the three invoices the customer paid stay open, and 1055, which they did not pay, now looks settled.
The visible residue. 1042 and 1047 are closed in full. 1051 is applied for €1,144.50 and €40.00 stays open, with a note. That is the only one of the three that says what actually happened.
Why is a forced match worse than an open one?
An open item is honest. Everyone can see it and someone will ask about it. A forced match looks finished, so nobody does.
The damage shows up later, in places that are hard to trace back.
- The wrong customers get chased. In the amount-match case, the reminder run sends three reminders to a customer who paid, while the one who did not pay hears nothing.
- Disputes get buried. The €40 was a damaged pallet. If it sits on a rounding account, the person who handles that customer never hears about it, and the same problem can happen on the next delivery.
- Revenue and VAT drift. If you agree to the €40 reduction, the correct treatment is usually a credit note, which reduces both revenue and the VAT you owe. Writing it off as a difference skips that. Check the treatment with your accountant.
- The differences account grows. A few euros a week become a balance at year-end that nobody can explain, and your accountant has to unpick it line by line.
What should happen to a difference instead?
Treat every difference as its own small item, with three things attached.
- The amount and the invoice it belongs to. Not spread across invoices to make each one look nearly right.
- The best available reason. From a remittance email, a note in the payment description, an earlier credit note or a dispute already on file. If there is no reason, say so.
- A proposed action. Write off, issue a credit note, ask the customer or wait for a second payment.
Then let a threshold decide who acts. Below an amount you set, for example a few euros of bank charges on a foreign transfer, the difference can be written off automatically with the reason recorded. Above it, a person decides, with everything they need on one screen.
What makes a match trustworthy?
A match is only as good as the evidence behind it. The bank line is where you start, not where the answer is.
For the Brouwer payment, the useful evidence is a remittance email that arrived the same morning: "Paid 1042, 1047 and 1051 in one go. We took off the €40 for the damaged pallet, as agreed with Sanne." With that, the allocation writes itself. Without it, the honest answer is "probably these three, €40 unexplained".
So every match should carry a short explanation that a reviewer can check in seconds and an auditor can read a year later. Something like "Applied to 1042, 1047 and 1051 based on the remittance email of 14 October. €40.00 deducted by the customer for a damaged pallet, credit note proposed."
If a match cannot be explained in a sentence like that, it should not be made yet.
Which decisions should stay with a person?
Software is good at reading the evidence and doing the arithmetic. Some calls belong to someone with authority and context.
- Agreeing a deduction. Whether the €40 for the pallet is fair is a commercial question.
- Write-offs above your threshold. Software can prepare them. A person approves them.
- Changing payment terms or agreeing a payment plan. These affect the customer relationship and your cash.
- The first time a pattern appears. A customer who starts paying through a factoring company, or a new payment provider in the mix. Decide the treatment once, then let it be applied from then on.
How can you test your own process?
You do not need new software to find out whether you force matches. Look at last quarter.
- What is the balance on your payment differences or suspense account, and can anyone explain each line?
- How many customer replies did you get saying "we already paid this"?
- Pick five payments that did not equal a single invoice. Can you see, for each, why it was applied the way it was?
- Were any invoices closed by a payment from a different customer than the one invoiced?
For a payment platform payout, add one more check. Split one payout back into its orders, fees and refunds and see whether the fees landed on a cost account or quietly reduced revenue. Payouts are where netting hides most easily, because the bank only ever sees the total.
If the answers are uncomfortable, the problem is not speed. It is that the process prefers a green screen to a true one.
How does Thred handle the difference?
Thred's agents work on top of the accounting software a business already uses through Thred Layer. They read bank lines together with the remittance emails and documents around them, apply payments where the evidence is clear, raise the difference as its own item with the reason attached, and push the finished entries back to your ledger. You decide the threshold below which they may act on their own. The Collector only follows up on invoices that are genuinely open, so customers who paid are left alone.
If receivables are part of your week and you want them right rather than just reconciled, see what Thred does for businesses, or book a demo on your own bank data.
Frequently asked questions
What is cash application in accounts receivable?
It is the step where each incoming payment is allocated to the specific customer invoices it pays. It keeps the list of open receivables correct, which every reminder, cash forecast and ageing report depends on.
What should I do when a customer pays less than the invoice?
Apply what was paid to the right invoice and leave the difference open with a note. Then find out why. An agreed deduction usually calls for a credit note, a dispute needs a conversation and an error needs a request for the balance.
Is it fine to book small payment differences to a rounding account?
For tiny amounts with a known cause, such as bank charges on a foreign transfer, a write-off within a threshold you set is common practice. Larger or unexplained differences should not be written off, because they can hide disputes and misstate revenue and VAT.
Why do customers get reminders for invoices they already paid?
Usually because their payment was not applied, or was applied to the wrong invoice, before the reminder run. Matching payments daily and never matching on amount alone prevents most of these.
Can I charge interest on late payments from business customers in the EU?
Under the EU Late Payment Directive, businesses can generally claim statutory interest and a fixed compensation for recovery costs on late business-to-business payments. National rules apply, so check the details for your country with your accountant.
Sources
Read next
- How to reconcile a bank account in Xero: match, create, find & match, cash coding and the reconciliation report
- A finance automation playbook for growing SMEs: what to automate first, second and never
- One agent, many ledgers: mapping accounts, VAT codes and journals across Exact Online, Xero and Moneybird
Where Thred comes in
Finance agents running on top of your existing ledger. You set the rules, approve the work and handle the exceptions. No migration.



