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.
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.
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.
Commercial impact
The Commercial Value Wrapper 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.
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.
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.
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.
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?
- Which accounts require human judgment 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.