An AR aging report is a useful prompt and a poor measure of collectability. This brief sets out what it can show, what it hides, and how to report it.
Bookkeeping Operations
What an accounts receivable aging report can and cannot prove
A research brief on AR aging reports, separating a balance that is old from a customer who will not pay and a ledger that is accurate.
Published · 3 listed sources
Table of contents
Key takeaways
- An aging report shows the age of open invoices, not the likelihood of collection.
- Separate current, past due, and disputed balances before drawing a conclusion.
- Record the customer, the invoice, and the last contact for each aged item.
- A clean aging report can hide a missing invoice or a duplicate credit.
An aging report shows 120,000 dollars over 90 days. The owner treats it as a collection problem and calls the largest customer. The customer says the invoice was never received, and the balance was a billing error.
Defining the age
The age is usually measured from the invoice date or the due date. The two produce different buckets, and the report should say which one it uses.
Write the definition down. A report that changes its reference date cannot be compared month to month.
What the report can show
The report can show the total open balance and its distribution across age buckets. It can show which customers carry the oldest balances.
It can show whether the balance is growing and whether the growth is in current or past-due items. That is a useful signal for the cash conversation.
What the report cannot show
The report cannot show whether the customer will pay. A 90-day balance may be a dispute, a missing invoice, or a customer in difficulty.
It cannot show whether the invoice is valid. A duplicate invoice or a credit that was not applied will appear as an open balance.
It also cannot show whether the balance is accurately stated. The aging report is only as good as the ledger behind it.
Methodology and limits
This brief reviews public guidance on internal control, recordkeeping, and small-business operations, and maps it to a private receivable ledger. The sources support documentation and review discipline; they do not set a collection policy.
We tested the proposed fields against four common cases: a current invoice, a disputed invoice, a missing credit, and a customer on a payment plan. The fields kept those cases distinguishable.
Separate the categories
Classify the aged items: current, past due, disputed, and under arrangement. Each has a different action and a different owner.
A report that only shows buckets forces the reviewer to open every item. The category makes the review faster and the follow-up specific.
Record the last contact
Add the date and channel of the last contact with the customer. A balance with no contact is a balance nobody is working.
The field also protects the team. A customer who says they were never contacted can be checked against the record.
Review the ledger before the aging
Check for duplicate invoices, unapplied credits, and invoices that were never sent. These defects distort the age and the total.
Record the corrections. A clean aging report built on a wrong ledger is more dangerous than a messy one that is accurate.
A worked example
A report shows 20,000 dollars over 90 days. Three invoices account for 15,000; one is disputed, one was never delivered, and one is on a payment plan.
The review corrects the ledger for the undelivered invoice, records the arrangement, and moves the disputed item to a separate list. The collection conversation now focuses on the real balance.
Provisioning
If the client books a provision for doubtful debts, record the basis and the review date. A provision is an estimate, not a write-off.
A provision that is never reviewed becomes a permanent discount on the ledger. The aging report should show the gross balance beside it.
Payment plans
A customer on a payment plan is not a collection failure. Record the arrangement, the dates, and the missed payments.
The aging report should show the arrangement separately so the balance is not counted as a disputed item or as a write-off candidate.
Customer communication
Record the last contact and the next step. A reminder that was sent is not the same as an agreement.
Where a customer disputes an invoice, record the reason and the owner. The dispute is a ledger question as much as a collection one.
A worked example
A report shows 15,000 dollars over 90 days. One customer accounts for 9,000, with a disputed invoice and a missing credit.
The bookkeeper corrects the credit, moves the disputed amount to a separate list, and sends a clear statement. The collection conversation now concerns 6,000 dollars, not 15,000.
Reporting cadence
Review monthly and discuss the over-60 items weekly where the volume justifies it. Keep the definitions and categories stable.
Record the actions and the outcomes. A report that is reviewed but never actioned is a chart.
Limits and appropriate use
This brief is a method note, not an empirical study. It does not establish a collection target or a provision policy. Results depend on the accuracy of the ledger and the honesty of the categories.
Small entities may have few customers, and the report should be read item by item rather than by bucket.
Conclusion
An AR aging report shows the age of open balances. Used with categories, last contact, and a ledger review, it supports collection and cash planning. Used alone, it invites conclusions about customers that the data cannot support.