An aging report is useful only when it changes what someone does next. A long list of balances grouped into 30-day bands can look precise while hiding the facts that matter: whether the invoice arrived, whether it is approved, whether it is disputed, and who owns the next contact.
A weekly review keeps collection work proportional. Recent invoices need routing checks, older invoices need a specific obstacle and commitment date, and high-risk balances need a documented escalation decision.
Build the report from reliable dates
Use the contractual due date rather than the issue date to calculate days overdue. Keep open credits, deposits, partial payments, and disputed amounts visible so the balance represents what is actually collectible.
Reconcile the report to the billing ledger before the meeting. Duplicate invoices and unapplied cash create false collection work and damage customer confidence.
Segment by action, not only age
Current invoices should be checked for successful delivery and correct routing. The first overdue band should have a named follow-up owner. Older balances should show the blocker, the customer commitment, and the planned escalation date.
Separate administrative delays from genuine disputes and financial distress. Each condition needs a different response and should not be hidden under the same “past due” label.
Run a short weekly meeting
Start with the largest and fastest-aging exposures, then review new exceptions. For each invoice, record one next action, one owner, and one date. Notes such as “follow up” are not decisions.
Track promises to pay separately. When a commitment date passes, the item should return to the review automatically rather than waiting for someone to remember it.
Measure whether the process is improving
Watch total overdue balance, the share over 60 days, disputes without an owner, and promises missed. A rising current balance can be healthy growth; a rising old balance usually signals a control problem.
Compare trends over several weeks instead of reacting to one customer payment. The purpose is to identify recurring routing, approval, or service issues that can be prevented upstream.
Pre-send control checklist
- Aging is calculated from due dates.
- Cash, credits, deposits, and write-offs are applied before review.
- Disputed and undisputed balances are separated.
- Every overdue item has a named owner.
- Every open action has a date.
- Promises to pay are recorded and monitored.
- Large or old balances receive explicit escalation decisions.
- Invoice delivery and approval status are visible.
- Weekly totals are compared with prior periods.
- Root causes are fed back into invoicing and customer setup.
Decision table
| Stage | Control question | Required action or evidence |
|---|---|---|
| Current | Was it delivered and routed correctly? | Confirm receipt and approval path |
| 1-30 days overdue | Is there an administrative blocker? | Obtain a payment date or missing requirement |
| 31-60 days overdue | Is the balance disputed or at risk? | Resolve the blocker and set escalation |
| 61+ days overdue | What recovery action is proportionate? | Management decision with evidence |
Primary sources
BillingFixPro reviewed the following government guidance for the recordkeeping and financial-control principles used on this page: