Where the cost actually lands
The money is in the account. That is the fact that makes this feel harmless, and it is why the cost goes uncounted for years.
The damage is on the other side of the ledger. The invoice stays open, so it enters your chasing sequence, so a client who paid three weeks ago receives a polite reminder that they owe you money. Everything that follows — the apology, the screenshot they send, the small recalibration of how organised they think you are — comes from a payment that arrived successfully.
One unidentified receipt, followed through
A R$495 payment received on a static key from a name that matches nothing. Times are one service business's own estimates.
| What happens | When | Cost | Who absorbs it |
|---|---|---|---|
| Receipt sits unallocated | Day 0 | 5 min of trying to place it | You |
| Invoice enters the reminder sequence | Day 14 | 0 — it is automated | Nobody, yet |
| Client receives a reminder for an invoice they paid | Day 14 | Their irritation, unmeasured | The client |
| Client replies with a screenshot | Day 14 | 10 min for them, 10 for you | Both |
| You locate the receipt and allocate it | Day 15 | 10 min | You |
| You apologise | Day 15 | Small and real | The relationship |
| Total | — | ~35 min plus goodwill | Mostly you |
Source: One Brazilian service business's own reconstruction of a specific incident, shared for this page. The goodwill line is deliberately not priced because pricing it would be invention.
Thirty-five minutes for one receipt, against five minutes if it had been resolved on the day it arrived. The multiplier for delay is roughly seven, and it comes almost entirely from involving a second person.
Three worse outcomes than the ordinary one
The invoice gets written off. Six months later, a tidy-up closes old open invoices as bad debt. One of them was paid. The money is in the account, the revenue is not in the accounts, and nobody will ever find it — this is the version that costs the full value of the invoice.
The client is chased twice. The first reminder gets a screenshot; the second, sent because nobody updated anything, gets a much shorter reply. Clients forgive the first and remember the second.
It is allocated to the wrong client. Now two accounts are wrong: one client credited for money they did not send, another still chased for money they did. This is the most expensive outcome and it is the direct product of guessing to clear a row, which is why the template on this site insists on a confidence column.
Objections
- This happens twice a year. It is not a real cost.
- Then it genuinely is not, and you should not buy anything. The arithmetic only gets interesting somewhere above a few a month, which is roughly where a business receiving on a static key lands once it passes fifty or sixty receipts.
- My clients do not mind being reminded.
- Mostly true, and it is worth being precise about what is being claimed. One erroneous reminder costs nothing measurable. The pattern of them, over a year, is what shifts a client's sense of whether you are on top of things — and that is not something they will ever tell you.
- We would catch it at month end anyway.
- You would catch most of them. The write-off case survives month end, because at month end the invoice is only two weeks old and looks like an ordinary late payment. It is the one that gets through, and it is the one that costs the whole invoice.
Questions
How long should I hold an unidentified receipt before refunding?
Should I pause reminders on invoices when unallocated money is sitting there?
How do I stop the write-off case specifically?
Is the goodwill cost real or rhetorical?
The file that prevents most of this
Ten columns, four statuses, and the payer-name lookup that makes next month easier.