Two invoices for the same amount can need very different responses: one is not yet due, while another is two months late because of a delivery dispute. Combining them into one customer balance hides the action required. An ageing report organises receivables by time; its practical value comes from connecting each amount with its cause and next action. Here the analysis uses due dates, then turns ageing bands into priorities for contact, correction and follow-up without treating every delay as a lost debt.
Define the age you are measuring
An invoice can be aged from its issue date, or lateness can be measured from its due date. This guide uses days past due. A customer given sixty-day terms is not overdue thirty days after the invoice was issued. Put the reporting date and calculation basis beside the report title and keep them consistent across periods and branches.
A balance remains current until its due date. Overdue bands might then cover one to thirty days, thirty-one to sixty days and more than sixty days. These are illustrative management bands that can be adapted to the sales cycle. They are not, by themselves, a measurement of credit losses or a conclusion that a debt will not be collected.
Clean the balance before contacting customers
Reconcile the report total to the receivables control balance for the same date and scope. Investigate unposted transactions or differences in the branches included. Check unallocated receipts, approved discounts, credit notes and duplicate customer records. Chasing a payment already received wastes time and undermines confidence in the accounts.
Where one transfer covers several invoices, retain its allocation against confirmed payment references. Do not use an assumed allocation merely to remove the oldest invoice from view. If a SAR 15,000 balance includes a disputed SAR 3,000 item, manage resolution of that issue separately from collection of the undisputed portion. The accounting balance should continue to reflect approved supporting documents.
A snapshot at one reporting date
Assume open customer balances total SAR 80,000 after all receipts and approved credits have been allocated. The team sorts the remainder by due date, excluding cancelled invoices and avoiding unsupported deductions for unidentified receipts. All customers in this example are fictional.
| Customer | Remaining balance | Status | Next action |
|---|---|---|---|
| Store A | SAR 30,000 | Not yet due | Confirm invoice received |
| Business B | SAR 25,000 | 1–30 days overdue | Confirm payment date |
| Company C | SAR 15,000 | 31–60 days overdue | Resolve a document query |
| Business D | SAR 10,000 | Over 60 days overdue | Review with finance lead |
Overdue balances total 25,000 plus 15,000 plus 10,000: SAR 50,000. Dividing 50,000 by the SAR 80,000 total gives an overdue share of 62.5%. Balances more than sixty days overdue represent 12.5% of the total. The first measure describes the extent of lateness; the second highlights the oldest portion. Choosing an action also requires the reason for delay and any payment commitment.
Make the report a weekly work list
- Assign one collection owner per customer to avoid conflicting calls.
- Record the latest contact, the cause of delay and any missing document.
- Record an expected payment date, keeping promises distinct from actual receipts.
- Prioritise clear, material and overdue amounts under an agreed internal credit policy.
- Send disputes to the person able to resolve them instead of repeating reminders.
- Review the outcome: cash received, issue resolved or date requiring reassessment.
Aging bands support follow-up. A time band alone does not determine a write-off or a fixed loss percentage. Accounting treatment depends on the applicable reporting framework and the available evidence.
What should you monitor as sales grow?
Compare overdue amounts, their share of total receivables and concentration by customer. Total receipts alone can mislead: collections may rise with sales while old invoices accumulate with one customer. Average collection days can add perspective, but the detailed invoice report reveals cases hidden by an average and points to someone who can take action.
Keep a dated snapshot of each review with its key notes. The following month, ask whether improvement reflects actual payment, changed due dates or an issued credit. Consistent definitions support fair comparisons and prevent a cosmetic improvement in the indicator. ACCA's accounts-receivable role overview also distinguishes payment allocation from collection and dispute work; both need attention in a useful review routine.
During a Wali ERP demonstration, bring a fictional invoice with a partial payment and a clear due date. Use it to discuss customer balances, outstanding amounts and the reports relevant to your workflow. A concrete scenario gives the team a more useful evaluation than a general request to see a dashboard.
Sources & further reading
Visit the original source to explore the concept and its wider context.
General educational content. Appropriate treatment depends on your business and accounting policies; consult your accounting professional when applying it to business records.
