Getting paid faster: a practical guide to invoice aging
Late payment is rarely a client refusing to pay. It's usually an invoice that went out late, a statement that never went out at all, and a follow-up that depended on someone remembering. Here's how to fix the admin instead of chasing harder.
Ask a business owner why cash is tight and you'll usually hear something about clients being slow. Look at the actual ledger and a different story tends to appear: invoices raised a week after the work finished, a handful of payments never allocated against anything, and a debtors list nobody has looked at since month-end.
None of that is a client problem. It's an admin problem — and admin problems are the fixable kind.
What invoice aging actually tells you
Invoice aging is just your unpaid invoices sorted by how long they've been outstanding, usually in buckets: current, 30 days, 60 days, 90 days, and older. Most accounting tools will produce the table. Far fewer people actually read it.
The number that matters isn't the total. It's the shape. A business with R400,000 outstanding that sits almost entirely in "current" is healthy — that's just work recently invoiced. A business with R150,000 outstanding where a third has crossed 90 days has a collections problem, and quite possibly a relationship problem it doesn't know about yet.
Two habits make the aging report meaningful rather than decorative:
- Look at it weekly, not monthly. An invoice that has just tipped into 31 days is a quick phone call. At 91 days it's an awkward negotiation.
- Watch the movement, not the snapshot. If the 60-day bucket is growing week on week, something in your process broke about two months ago.
The four habits that shorten debtor days
1. Invoice the day the work is done
Every day between finishing work and issuing the invoice is a day added to the front of your payment terms, and it's the cheapest day to remove. If invoicing happens in a monthly batch, work completed on the 2nd is already three weeks old before the clock even starts.
2. Put the due date in words
"Payment terms: 30 days" requires the reader to do arithmetic. "Due 23 August 2026" does not. It sounds trivial. It removes a small excuse, and small excuses are what late payment is made of.
3. Send statements, not just invoices
An invoice shows one transaction. A statement shows the relationship — what's outstanding, what's been paid, what's overdue and by how long. Clients with several invoices in flight frequently pay the ones they can see. A monthly statement makes all of them visible at once, and it surfaces disputes early instead of at 90 days.
4. Chase on a schedule, not on a feeling
The most common collections strategy is "remember to follow up when it starts to bother you." That guarantees your most patient clients get chased last and your cash flow depends on your mood. A fixed rhythm — a reminder at due date, one at 7 days, a statement at 30 — takes the emotion out of it, and clients get used to it.
The five-minute weekly check
- Which invoices crossed into a new aging bucket this week?
- Which payments came in that haven't been allocated to an invoice yet?
- Which client has more than one invoice overdue? (That's a conversation, not a reminder.)
Why spreadsheets quietly make this worse
Spreadsheets are excellent at arithmetic and terrible at bookkeeping discipline. The failures are always the same handful:
- Unallocated payments. Money arrives, gets noted somewhere, and never gets matched to a specific invoice — so the aging report is wrong and nobody trusts it.
- Aging that doesn't age. A bucket calculated with a hard-coded date is correct on the day it was written and slowly lies from then on.
- Rounding drift. VAT and cent-rounding applied inconsistently across sheets produces invoices that don't quite reconcile to statements.
- Multi-entity sprawl. The moment there's more than one company, you get more than one spreadsheet, and numbering collisions arrive shortly after.
None of these are exotic. They're what happens when a calculation tool is asked to be a system of record.
What to automate first
You don't need to automate everything, and trying to usually stalls. In order of payback:
- Recurring invoices. Anything billed on a repeating cycle should issue itself. This is pure clerical time back, with no judgement required.
- Aging. Buckets should be computed from today's date, every time you look, without anyone refreshing anything.
- Statement runs. One action per month, per client, in a consistent format.
- Payment allocation. Even semi-automated matching removes the single biggest source of "our numbers are wrong".
Deliberately last: dunning tone. Escalation from friendly nudge to firm demand is a judgement call about a specific relationship. Automate the timing; keep the words yours.
A note on doing this in South Africa
Two local realities are worth designing around. VAT needs to be computed and displayed consistently, ideally server-side rather than in whatever version of a template someone last edited. And payments frequently arrive as EFT with a reference that only loosely matches the invoice number — which means allocation deserves more attention than it usually gets.
None of this requires new discipline from your clients. It requires the invoice to be early, the due date to be obvious, the statement to arrive, and the follow-up to be boringly regular. Do those four things and debtor days fall without a single difficult conversation.