FOUNDER PERSPECTIVE · CONSOLIDATED
Why Receivables Problems Repeat Every Month
Read the flagship perspective →A recurring overdue pattern is usually a signal that the organisation is solving cases without changing the process that created them. The same invoice problem returns under a different customer name because the learning never reaches sales, operations, billing, credit or customer setup.
Resolution is not the same as prevention
A team may successfully collect an invoice after finding a missing PO, correcting a tax detail or securing an acceptance certificate. If the next transaction follows the same flawed process, the business has solved one case but not the control failure.
Look for repeated cause codes
Monthly review should group material delays by cause: documentation, billing error, acceptance, dispute, deduction, customer payment process, credit deterioration, internal approval or another defined category. Repetition becomes visible only when causes are recorded consistently.
Separate one-off exceptions from design defects
An unusual customer event may not justify process change. But the same blocker across customers, teams or months is different. Repeated manual corrections, repeated senior escalations and repeated “special cases” are evidence that a standard process is missing or not being followed.
A recurrence example
If three large customers delay payment because service-entry approval was not initiated on time, collecting those invoices does not close the issue. The preventive action is to define who triggers service-entry, by when, with what evidence and how overdue approvals are surfaced before the invoice becomes late.
Assign owners outside Collections
Root causes often belong to Sales, Operations, Commercial, Billing, Tax, Credit or customer onboarding. A receivables review should therefore create process actions with owners and due dates, not only collection actions against debtors.
Measure whether the cause is shrinking
The best evidence of learning is a falling recurrence rate. Track whether the value and number of invoices affected by the same blocker decline after a corrective action. If not, the action may have been cosmetic or poorly implemented.
What this means for management
Receivables becomes a management system when every difficult case can improve the next transaction. Without that feedback loop, the team can work very hard and still face the same problem every month.
- Require a cause and next event for every material exception.
- Use evidence to decide the escalation route rather than defaulting to more follow-up.
- Feed recurring causes back into credit, sales, operations and billing controls.
Related GGA resources
Continue with the relevant operating material in Revenue Assurance, Revenue Realization, the Knowledge Centre and GGA Research. Company-specific legal, regulatory, insurance or recovery decisions require current evidence and, where appropriate, specialist advice.
- Revenue Assurance - prevent avoidable delay before due date.
- Revenue Realization - manage overdue and exception receivables.
- Knowledge Centre - practical operating guidance.
- Research - evidence and methodology.