Late Payments Nobody Follows Up: The Cost of Slow Collections

The sale is complete but the cash is still outside the business

An invoice can be accurate, sent on time and still become an operating problem if nobody owns the collection process. Finance checks overdue balances when time allows. Account managers hesitate to chase valued customers. Statements go out irregularly. Promised payment dates are stored in inboxes or memory.

The result is not always a bad debt. Often it is slower cash conversion: the business waits longer for money it has already earned while continuing to fund its own obligations.

Picture a Johannesburg engineering services firm with forty customers on 30-day terms. The bookkeeper sends reminders when month-end work allows, which in a busy month means not at all. One large customer always pays, eventually, so nobody chases them. A smaller customer promised payment "next Friday" in a phone call that was never logged. By the time the owner looks at the age analysis, several balances have drifted past 60 days, and nobody can say which were disputes, which were forgotten and which were simply never followed up.

Why inconsistent collections becomes normal

Collections can feel relational rather than operational. Teams worry about irritating customers, responsibilities between sales and finance are unclear, and small overdue amounts appear harmless. The workload also grows as the ledger grows, so manual chasing is often deferred precisely when it becomes more important.

Xero's South African guidance on chasing outstanding invoices recommends staged follow-up, regular tracking of outstanding invoices and automated reminders, and stresses acting quickly once an invoice becomes overdue. Its guidance on accounts-receivable financing notes that cash tied up in receivables limits the ability to cover operating costs, pay suppliers and invest in growth. Xero is a vendor source, but these recommendations describe a process any business can measure independently.

A further reason is structural. Sales often holds the context (who agreed what, which customer is under strain) while finance holds the ledger. When those two records do not meet, follow-up depends on someone remembering to ask. That pattern is described in when cash collection depends on someone remembering to follow up.

Warning signs

• The age analysis is reviewed only at month-end, or only when the bank balance is low.
• Nobody can say when a specific overdue customer was last contacted.
• Reminders differ in tone and timing depending on who sends them.
• Disputed invoices sit in the same overdue list as invoices nobody has chased.
• The business uses its overdraft while material balances are past due.

How the pain becomes money

• Working-capital pressure: the business funds payroll and suppliers while earned cash remains outstanding.
• Financing cost: overdrafts, credit facilities or owner funds may bridge a gap that faster collection could reduce.
• Collections labour: finance staff repeatedly review ledgers, send reminders and reconstruct prior conversations.
• Bad-debt exposure: problems can age before the business escalates or changes credit decisions.
• Planning uncertainty: cash forecasts become less dependable when payment behaviour is not actively managed.

The commercial signal: if the business cannot show who owns each material overdue invoice, the last contact date and the next committed action, collections is reactive rather than controlled.

Calculate the financing effect carefully

Do not describe all overdue receivables as lost revenue. Most are timing problems until evidence says otherwise.

Average receivables tied up by extra delay = average daily credit sales × avoidable extra collection days

Indicative annual financing cost = average avoidable receivables balance × relevant annual financing rate

Add collections labour separately. If two finance employees each spend four hours a week on avoidable manual chasing, quantify those hours using actual loaded labour cost. Keep permanent bad debt separate from delayed cash.

As an illustration only: a business with average credit sales of R50,000 per working day that could realistically shorten collection by ten days would release around R500,000 of working capital. Whether that matters depends on what the business is paying to fund the gap. If it sits in an overdraft, the saving is the interest on that balance. If it is owner money, the cost is what that money could otherwise have done. Use your own sales, ageing and funding data rather than these figures.

Automation helps consistency, not judgement

Automated reminders can make routine follow-up reliable, but they should not blindly chase disputed invoices, strategic accounts or customers with agreed payment plans. Good automation handles predictable stages and surfaces exceptions for people.

Xero's guidance on reducing payment delays suggests reminders on the due date and then at 7, 14 and 30 days overdue, alongside clear payment terms, prompt invoicing and easy payment options. A practical design separates the stages:

The same Xero guide treats invoices older than 90 days as seriously delinquent and outlines escalation through statements, calls, late fees communicated upfront, stopping work, debt collection and, as a last resort, legal action. It also notes the three-year prescription period for debts in South Africa, which is a reason not to let old balances drift without a decision.

The trade-off is relationship risk. Automated reminders sent to a customer who has already paid, or who is mid-dispute, damage trust. That is why automation should depend on accurate payment matching (see the cost of manual payment matching) and a reliable flag for disputes and payment plans.

When this becomes commercially urgent

Priority rises when overdue balances grow faster than sales, debtor days worsen, finance spends significant time chasing routine payments, promised payment dates are not tracked, or the business borrows while a material amount of collectible cash sits overdue.

What good looks like

Payment terms are clear before work begins. Invoices are accurate and prompt, which matters because late invoicing delays the collection clock before it starts. The ledger is reviewed on a defined cadence. Reminders are consistent. Material overdue accounts have owners and next actions. Disputes are separated from simple non-payment. Management can see ageing, concentration and collection trends before cash pressure becomes urgent.

What to do first

If nothing structured exists today, start small. Pull this week's age analysis, pick the ten largest overdue balances and give each one an owner, a last-contact date and a next action. Agree a single reminder schedule and switch on automated reminders for routine invoices only. Then review the list weekly for a month. That alone usually shows whether the problem is customer behaviour, internal follow-up or invoice quality.

Practical next actions

1. Segment receivables by current, 1–30, 31–60, 61–90 and older overdue bands.
2. Assign an owner and next action to every material overdue balance.
3. Standardise reminder timing and escalation rules.
4. Automate routine reminders while routing disputes and exceptions to people.
5. Track promised payment dates and whether customers keep them.
6. Measure debtor days, collection labour and financing cost over time.
7. Feed recurring disputes back into sales, delivery and billing processes.

Bottom line

Late payment is partly a customer behaviour problem and partly an operating-system problem. The business cannot control every debtor, but it can control whether overdue cash is visible, owned and followed up consistently. That discipline reduces avoidable financing pressure without pretending every overdue invoice is recoverable.

Sources and further reading

• Accounts Receivable Financing (last verified 10 October 2026)
• How to Handle Unpaid Invoices (last verified 10 October 2026)
• How to reduce late payments and get paid faster (last verified 10 October 2026)

Related Mellorca reading

• The Payroll Cost of a Slow, Spreadsheet-Heavy Month-End
• Paying the Same Supplier Invoice Twice: The Direct Cost of Weak Controls
• Paying for Cloud Resources Nobody Uses