Observable condition
Invoices are issued, due dates pass, and follow-up happens unevenly. One customer gets a reminder quickly, another waits because the responsible person was busy, absent or working from a private list.
The working pattern is easy to recognise. Someone in finance keeps a spreadsheet, a notebook or a set of flagged emails showing who needs chasing. At month end, or when cash feels tight, they work through it. In a busy week the list waits. When they take leave, it waits longer, because nobody else knows exactly where each account stands: who promised to pay on Friday, who queried a line item, who has already received two reminders. Customers notice the inconsistency too. Some receive a polite reminder the day after the due date; others hear nothing for weeks and then receive a firm call.
Realisation
Collection effort is not only a finance activity; it is a timed operating process. When the next action is known in advance, relying on memory introduces unnecessary variation into cash conversion.
Almost everything needed to decide the next step already exists in the business's systems: the invoice amount, the due date, the customer and whether payment has arrived. What is missing is the rule that turns those facts into an action at the right time, and the record that shows what happened. Without it, the timing of cash coming in depends partly on customer behaviour and partly on how full one person's week happens to be. Only the first of those is outside the business's control.
Identification
This is an accounts-receivable follow-up workflow problem. The invoice exists and the due date is known, but the system has not converted that information into consistent next actions and escalation.
Diagnosis
Typical causes include disconnected invoicing and communication tools, no reminder rules, unclear exception ownership, and manual tracking of promises to pay. Xero’s invoicing documentation, for example, includes configurable automatic invoice reminders and visibility into reminder status. The broader operating principle is that predictable follow-up can be systematised while exceptions remain with finance staff.
Looking more closely at that example is useful because it shows how ordinary the capability has become. Xero describes letting a business choose how often payment reminders are emailed, and send them before or after the due date. It describes seeing the status of pending and paid invoices at a glance, receiving notifications when customers view or pay an invoice, and seeing when reminders were sent. Other accounting platforms offer comparable features. The point is not the product; it is that the information and mechanisms for consistent follow-up are frequently already present.
So why does memory still run the process? Usually for one of four reasons:
- Configuration never happened: reminders were available but never set up, or were switched off after a complaint and never redesigned.
- Exceptions live outside the system: disputes, promises to pay and agreed payment plans are recorded in email or private notes, so automated reminders cannot respect them.
- Payment status lags: if bank reconciliation is slow, automated reminders risk chasing customers who have already paid, so staff prefer to check manually.
- Ownership is personal: accounts are informally “owned” by whoever usually deals with them, with no shared view of where each stands.
The last two causes connect to neighbouring patterns, such as why sending an invoice requires so much work, and to the reconciliation effort described in the cost of manual payment matching.
Commercial impact
The commercial value at stake is cash conversion, revenue leakage, finance capacity and margin. Inconsistent chasing delays visibility into genuine disputes, weakens escalation discipline and uses finance capacity on repetitive reminders.
- Cash timing: money owed arrives later than it needs to, which affects working capital and the ability to plan.
- Late discovery of disputes: a customer who is not paying because of a genuine query may not be identified until the account is well overdue, by which point resolution is harder.
- Finance capacity: skilled staff spend time composing routine reminders rather than handling the accounts that need judgement.
- Customer relationships: uneven treatment, or reminders sent after payment, can irritate customers who have done nothing wrong.
- Continuity risk: when the person holding the list is unavailable, collection slows across the whole book.
The financial consequence is explored in the cash-flow cost of inconsistent payment follow-up. Any estimate for a particular business should come from its own debtor ageing, collection history and finance time records rather than from borrowed figures.
Common misidentification
The pattern is often treated purely as a customer-payment problem. Some customers will pay late regardless of process quality, but an inconsistent internal follow-up mechanism makes it harder to distinguish external delay from internal inaction.
A second misidentification is to treat automation as the whole answer. Switching on reminders without bringing disputes, payment plans and reconciliation status into the same workflow can produce reminders that are consistent but wrong, which damages trust and leads staff to switch them off again.
Possibility
A stronger model creates a collection sequence tied to invoice status, due date, customer segment and exception state. Routine reminders happen consistently, while disputes, broken promises or high-risk accounts are surfaced for human action.
In practice, every overdue account has a visible next step and a date. Anyone in the finance team can open an account and see what has been sent, what the customer said and what was agreed. Reminders stop automatically when payment is matched. The people with the most experience spend their time on the accounts where a conversation will make a difference.
Intervention
Map the current reminder cadence, define automated and manual stages, connect payment status to the workflow, and create a visible exception queue. Ensure customers are not contacted after payment because systems failed to reconcile status.
- Write down the current cadence as it actually happens, including who does what and from which list.
- Define stages: for example, a courtesy reminder, a firmer reminder, a personal call and an escalation, with the timing for each.
- Decide which stages are automated and which require a person.
- Record disputes, promises to pay and payment plans where the workflow can see them, so reminders pause appropriately.
- Make sure payment matching is timely enough for reminders to be trusted.
- Give the exception queue a named owner and review it on a fixed rhythm.
Practical diagnostic questions
- How is the next follow-up date determined?
- Can another team member see the collection history?
- What stops reminders once payment is received?
- Where are promises to pay and disputes recorded?
- Which accounts require human judgement rather than automation?
- How are disputes separated from simple overdue balances?
Bottom line
If cash collection depends on someone remembering who to chase, the business has placed a time-sensitive financial process inside personal memory. A controlled workflow can make routine follow-up consistent and make exceptions more visible.
Sources and further reading
- Easy Online Invoicing Software (last verified 10 October 2026)
- Invoice App For Small Business (last verified 10 October 2026)
Related Mellorca reading
- When Finance Teams Become Data Clean-Up Teams
- The Signs That Your Business Needs an Operating System, Not Another App
- When Service Quality Depends on Who Picks Up the Ticket