From Invoice to Payment: How to Structure Accounts Receivable Follow-Up

Issuing an invoice isn't getting paid

On a profit-and-loss statement, an issued invoice counts as revenue. In a bank account, it counts for nothing until it's paid. The gap between the two has a precise name: accounts receivable. An SME that manages performance purely on invoiced revenue can look healthy on paper while actually running short on cash.

This isn't a sales-effort problem. It's a process problem: without a clear path from invoicing to collection, every unpaid invoice becomes a one-off case handled by feel, instead of a predictable stage in a tracked cycle.

The cycle in five steps

Invoice issued

The invoice opens the receivable. It's the starting point of the follow-up, not its end — and that's often exactly where tracking stops, for lack of a clearly defined next step.

Due date tracked

Every invoice carries a due date derived from the payment terms agreed with the customer. Without that date tracked individually, there is no objective way to say an invoice is overdue — only an impression.

Reminder sent

Following up shouldn't depend on someone remembering that an invoice is dragging on. A reminder rhythm — before the due date, at the due date, then after a defined delay — turns a one-off gesture into a repeatable process.

Payment received

A payment can be partial, or settle several invoices at once. Tracking needs to reflect both cases without forcing an artificial match between one amount received and a single invoice.

Reconciliation confirmed

The payment received is matched against the invoice or invoices it settles, and any remaining balance stays visible instead of disappearing into a lump-sum entry.

What an ageing balance makes visible

An ageing balance sorts receivables by how long they've been outstanding — under 30 days, 30 to 60, 60 to 90, over 90 — rather than by total amount owed alone. That view changes priority: a small, four-month-old receivable often deserves more attention than a larger, recent one that's still within normal terms.

Without that ageing view, accounts receivable follow-up shrinks to a single question — how much are we owed in total — which says nothing about how urgently to act.

When an amount is blocked or disputed

Not every overdue receivable is a simple oversight. A customer may dispute a line, be waiting on a credit note, or hold back payment pending a commercial disagreement. These cases need to be identifiable separately from a plain delay: they aren't chased the same way, and mixing them up wastes time on both sides.

What a collections team does once a case is blocked depends on your commercial policy and, where relevant, on legal advice suited to your own jurisdiction — not on a generic rule that applies to every SME.

Prioritizing collection without spending your whole week on it

Not every overdue receivable deserves the same effort. A simple framework helps sort them:

• Large amount + significant delay — immediate priority, a direct call rather than an automatic reminder.
• Small amount + slight delay — an automatic reminder is usually enough, no manual intervention needed.
• Recurring customer, good relationship — a personal call before any written reminder, to protect the relationship.
• Declared dispute — taken out of the standard reminder cycle, handled as its own case.

A practical checklist

• Does every invoice carry a due date tracked individually, not just an issue date?
• Does a reminder go out automatically on a defined rhythm, without relying on a manual prompt?
• Is a partial payment visible as such, rather than hidden inside the customer's overall balance?
• Can you read an ageing balance in a few seconds, without rebuilding a spreadsheet?
• Is a disputed case identifiable separately from a plain payment delay?

A "yes" to all five doesn't guarantee getting paid faster. It guarantees knowing, at any moment, who owes you what, since when, and why — which is already half of collections work.