The reminder sent to a customer who had already paid
The most expensive mistake in receivables management does not cost you fees. It costs you the customer who got a reminder for a bill she paid three weeks ago.
- The cause
- A missing or wrong payment reference
- Who it hits
- Customers who have paid
- Visible in
- Unreconciled bank entries
- A payment without an unambiguous reference sits unallocated, and the invoice stays open until somebody matches it by hand.
- For as long as it stays open, it counts towards the outstanding balance, pushes DSO up, and can trigger a reminder on a bill that has been paid.
- The price is not the fee, which is easily credited. It is the conversation with a customer who paid on time and was treated as though she had not.
There is an error in receivables management that appears in no metric and is still the most expensive one most companies make. It looks like this: a customer pays on time, the amount lands in the account without a reference, nobody gets round to matching it, and three weeks later the reminder run sends a letter.
The fee can be credited. The letter cannot be taken back.
Why it happens when everything else works
It is rarely carelessness. It happens because matching is the one point in the receivables process where the work cannot be put on a deadline. Reminders can run to a calendar. Formal demands can run to a statutory deadline. But a payment without a reference requires a human being to work out which invoice it belongs to — and that work gets postponed exactly when there is most of it.
Meanwhile the invoice sits open. It appears in the aged debtors report, it pushes DSO up, and it forms part of the basis the reminder run works from. The system is not doing anything wrong. It simply does not know the bill has been paid.
The price is not in the ledger
A mistaken reminder costs nothing in any account. It costs the thing that is hardest to rebuild: the customer’s confidence that you have control of your own book. A customer who paid on time and gets chased anyway learns two things. That your system cannot keep up. And that paying precisely may not matter all that much.
The second is the serious one. A reminder works because it is credible. A systematic reminder flow genuinely shifts payment behaviour — that is well documented. But it works because the recipient assumes the letter is right. Send two letters that were not right, and the third is just post.
It can be fixed in one place
The fix does not sit in the reminder run. It sits upstream, in the matching: an unambiguous reference on the invoice, a payment method that carries the reference with it, and a reconciliation that runs by itself rather than being something somebody gets to when there is time.
If the payment finds its invoice on its own, the whole problem disappears — not as an improved process, but as a category of error that can no longer arise.
AccountabilityNew in the platform
What this rests on
We do not print figures we cannot point to. Where there is a calculation, the assumptions are stated in the text — so you can put in your own figures and see whether it still holds.
- 01A systematic reminder flow markedly increases the share of people who payHallsworth et al., Journal of Public Economics, 2017 — randomised trial with 100,000 participants.