Start with the date and the ageing rule
The worked example is as of 3 Oct 2026. Here, days overdue are calendar days after the due date, and buckets are not yet due, 1–30, 31–60, 61–90 and 91+ days overdue. EX-101 is 15 days overdue and EX-102 is 30 days overdue, so both belong in 1–30. A future-due invoice belongs in not yet due. An invoice due on the report date is not yet overdue in this convention.
Check your accounting report's settings before comparing two exports. Some reports age from invoice dates, others from due dates, and interval boundaries can differ. Also distinguish the report date from the last source update. A report labelled today can still omit a payment awaiting import. Record these settings beside the totals so changes in the method are not mistaken for changes in customer behaviour.
Age the remaining balance, not the original amount
For each record here, remaining balance equals gross invoice amount minus applied credit minus applied payment. EX-101 started at £1,200, has £300 applied and remains open for £900. EX-103 began at £2,000; a £200 credit and £1,800 payment leave £0. Its zero balance contributes nothing to open ageing buckets, although its history remains useful.
A credit reduces what is owed; it is not a cash receipt. A payment allocated to the wrong invoice can make two records misleading even when the customer total appears sensible. Reconciliation means comparing related records, explaining differences and ensuring the correct allocations have been applied. Do not make an unexplained balance disappear in a tracking sheet simply to make its totals match. Ask the authorised accounting owner to resolve it at the source.
Reconcile the example before prioritising
Open balances are £900 + £650 + £800 = £2,350. Overdue is £1,550, all in 1–30 days, and not yet due is £800. The disputed £650 on EX-102 is already included in overdue. A separate disputed view highlights it; it must not be added to the overall balance a second time. The example table and chart are calculated from the same records.
Keep currencies separate before combining customer totals. This example has only GBP; switching language changes number formatting, not currency, tax treatment or economic values. In a real report, compare the included invoice set, exclusions and any currency conversion policy before reconciling it to an accounting balance. A tidy chart without that context can hide missing invoices, duplicated rows or credits that have not been allocated.
Use the status to choose an action
Age tells you how long a balance has been overdue, not why. For EX-101, check the remaining amount and latest contact before choosing a suitable reminder. For EX-102, the next action is an owner review of the dispute while ordinary reminders are paused. EX-104 does not need an overdue message. Grouping invoices by customer helps avoid several uncoordinated messages, but keep each due date, amount and exception visible beneath the customer total.
When the customer says EX-101 is paid, its state becomes awaiting verification; the balance still remains £900. In the separately labelled simulated verified event, the remaining payment is applied and open balances become £1,450, with £650 overdue. A promise or screenshot alone must not produce that change. Always keep the source check, owner and next review date with the action.
A short glossary for the review meeting
Outstanding means still owed, including amounts not yet due. Overdue means an open balance whose due date has passed under the report's convention. Ageing buckets group those balances into day ranges. A dispute is a customer query requiring investigation, not a second balance. A payment promise is an expected date to review, not collected cash. A credit is an adjustment reducing an invoice balance, separately recorded from payment.
Days sales outstanding, often shortened to DSO, is an aggregate measure relating receivables to credit sales over a defined period. A figure is meaningful only alongside its calculation method, sales period and comparable data. These four invoices are not enough to infer DSO, a forecast or a customer's likelihood of paying. Start this review with balances and unresolved tasks, then ask your accounting owner which broader measures fit the business.
The reconciled sample report
- Outstanding
- £2,350
- Overdue
- £1,550
- Not yet due
- £800
Disputed subset: £650 · already included above; never added again.
As of 3 Oct 2026 · GBP · due-date ageing, remaining balances only.
| Invoice | Gross | Applied credit | Applied payment | Remaining |
|---|---|---|---|---|
| EX-101 | £1,200 | £0 | £300 | £900 |
| EX-102 | £650 | £0 | £0 | £650 |
| EX-103 | £2,000 | £200 | £1,800 | £0 |
| EX-104 | £800 | £0 | £0 | £800 |
| Total | £4,650 | £200 | £2,100 | £2,350 |
| Invoice / customer | Due date | Remaining | State / age | Next action / owner | Last update |
|---|---|---|---|---|---|
| EX-101Example A | 18 Sept 2026 | £900 | Part-paid15 days overdue | Review balanceOwner A | 3 Oct 202609:00 UTC · sample snapshot |
| EX-102Example B | 3 Sept 2026 | £650 | Disputed · reminders paused30 days overdue | Resolve queryOwner B | 3 Oct 202609:00 UTC · sample snapshot |
| EX-103Example C | 25 Sept 2026 | £0 | Settled— | Close recordOwner A | 3 Oct 202609:00 UTC · sample snapshot |
| EX-104Example D | 10 Oct 2026 | £800 | Not yet due— | Check contactOwner B | 3 Oct 202609:00 UTC · sample snapshot |
Illustrative workflow · sample data · no messages or payments are processed.