A sale isn't cash until it's paid. The time between those two moments is where a lot of small-business cash flow problems start. A business can show healthy revenue on paper and still struggle to cover payroll, because too much of that revenue is sitting in customers' accounts.
This guide covers how to track what customers owe you, how to tell a normal delay from a real problem, and how to follow up in a way that gets you paid.
What to track
A useful receivables view answers five questions:
- Who owes me, and how much? The current outstanding balance per customer.
- How late is it? Time since the due date, not just since the invoice was issued.
- Have they paid part of it? A partly paid invoice needs different handling from an untouched one.
- Is this normal for them? A customer who always pays in 45 days is not the same risk as one who used to pay in 15 and is now slipping.
- What have I already done about it? A record of reminders and promises, so you don't chase blindly or forget a promise.
Ageing: the simplest useful report
Accountants group unpaid invoices by how overdue they are. A standard layout looks like this:
- Not yet due: issued, but the payment date hasn't arrived.
- 1–30 days overdue: slightly late, often an oversight.
- 31–60 days overdue: worth a direct conversation.
- 61–90 days overdue: a real collection problem.
- Over 90 days overdue: increasingly unlikely to be paid without escalation.
The older a balance, the less likely it is to be paid in full, so the older buckets deserve attention first even if the amounts are smaller.
Watch for these traps
- Unapplied payments. A customer paid, but the money was never matched to an invoice, so the invoice still looks unpaid. Chasing them for it is awkward.
- Overpayments. A customer who paid too much is owed money back. Hiding it inside a negative balance makes other debts look smaller than they are.
- Credit memos. A credit note issued to a customer should reduce what they owe. If it isn't tied to the right invoice, the balance is wrong.
- Partial payments. An invoice paid in instalments isn't "paid" or "unpaid." Track what remains.
How to chase late invoices well
- Remind early and politely. For a few days overdue, a short, friendly note is enough. Most late payments are oversights.
- Be specific. Include the invoice number, amount, due date and how to pay. A message that makes paying easy gets paid faster.
- Escalate the tone gradually. Friendly, then firm, then formal. Each message should be clearly stronger than the last.
- Record promises. If a customer says they'll pay on Friday, write that down with the date, and follow up on Friday.
- Know your last resort. Decide in advance when you'll pause further work or involve a collections process.
Where this gets hard
Getting an accurate picture means matching every payment to the right invoice, accounting for credits and partial payments, and keeping a record of every conversation. Done in a spreadsheet, it stops scaling once you have a few dozen customers.
How Guardian tracks outstanding customer payments
You give Guardian an export of your invoices and an export of the payments you've received, as spreadsheet or CSV files, or a bank or mobile-money statement it can read payments from. Guardian matches payments to invoices, using the invoice reference where it exists and the amount otherwise, and records how each match was made, so you can check it.
From that it builds an ageing report in the standard buckets above, shows credit memos next to the invoices they relate to, reports overpayments as money owed back, and lists the customers with the most overdue money first. All totals are kept per currency, never mixed.
For follow-up, Guardian drafts reminder messages for email or WhatsApp with a suggested tone based on how overdue the balance is, builds a customer statement you can send, and keeps a log of promises and follow-ups.
Guardian prepares the follow-up and keeps the record, but you send the messages and decide when to escalate. It works from the records you provide, so it's only as complete as those exports.
FAQ
Is a customer who's 10 days late a problem? Usually not. A short delay is often an oversight, so a polite reminder is enough. Look for patterns: customers who are late every time, or getting later.
Should I charge late fees? Only if your terms say so. Check your contract and local rules before adding fees.
What if a customer disputes an invoice? Resolve the dispute first and treat the disputed amount separately, so it doesn't get chased as if it were simply unpaid.
Does this replace my accounting software? No. It works from exports of the invoices and payments you already record there.