An accounts receivable aging report, or AR aging report, lists open customer receivables at a defined reporting date and groups them by how long they have been outstanding or overdue. It helps finance teams inspect customer balances, prioritize follow-up, identify unapplied payments and disputed invoices, and assess whether the reported AR balance is supported.
An aging report is only useful when its population agrees with the AR subledger and its dates, terms, credits, and allocations are correct. Formatting open items into buckets does not by itself establish that the report is complete or that an old balance is collectible.
What an AR aging report should contain
| Field | Why it matters |
|---|---|
| Reporting or as-of date | Defines the population and the date on which age is calculated |
| Customer and legal entity | Separates balances with different counterparties, currencies, and ownership |
| Invoice or document number | Provides the open-item reference used for application and investigation |
| Invoice and due dates | Support age calculations and distinguish time outstanding from time overdue |
| Payment terms | Explain the due date and expose incorrect customer-master settings |
| Original and open amount | Shows partial payments, credits, and the remaining customer obligation |
| Currency and reporting amount | Prevents unlike currencies from being added without an approved conversion basis |
| Bucket and days overdue | Supports prioritization and policy-based review |
| Dispute, promise, or collection status | Adds operational context without changing the accounting balance |
| Owner and next action | Makes older or unusual items actionable rather than merely visible |
How AR aging is calculated
A report must state whether it ages from the invoice date or from the due date. Aging from the invoice date shows how long the receivable has existed. Aging from the due date shows how long it has been overdue under the recorded payment terms. Both views can be useful, but switching the basis between reports makes trends and thresholds unreliable.
A common overdue calculation is the reporting date minus the due date, with items not yet due presented in a current bucket. Bucket labels such as current, 1–30, 31–60, 61–90, and over 90 days are common examples, not a mandatory universal design. The organisation should define buckets that align with its billing cycles, collection process, close controls, and reporting policy.
AR aging report example
The following simplified example uses days overdue. The amounts and customer names are illustrative and do not represent an Aetherix client.
| Open item | Open amount | Days overdue | Bucket | Operational note |
|---|---|---|---|---|
| Customer A — Invoice 1042 | 15,000 | Not yet due | Current | No exception |
| Customer B — Invoice 2088 | 9,500 | 18 | 1–30 | Payment promised |
| Customer C — Invoice 3151 | 6,000 | 47 | 31–60 | Service item disputed |
| Customer D — Invoice 4770 | 11,000 | 76 | 61–90 | Receipt found but not applied |
| Customer E — Credit note 119 | (2,000) | 65 | Credit | Must be linked to the related invoice |
| Total | 39,500 | — | — | Must agree to the underlying open-item population |
Customer D illustrates why aging cannot be interpreted without cash-application evidence. If the bank receipt belongs to that invoice, collection follow-up is not the immediate task; cash application is. Customer E shows why credits should remain visible and connected to the relevant customer items rather than being hidden from the report.
How to validate an AR aging report
- Freeze the reporting date. Confirm that invoices, receipts, credits, and adjustments after the as-of date are excluded or separately identified.
- Reconcile the total to the subledger. The sum of customer open items should agree with the AR subledger balance for the same entities, currencies, and date.
- Reconcile the subledger to the GL. Investigate direct GL journals, failed batches, currency revaluation, or timing that prevents agreement with the control account.
- Test dates and terms. Sample invoice dates, due dates, and customer payment terms against source documents and approved master data.
- Review cash and credits. Identify receipts or credit notes that have not been applied, were applied to the wrong customer, or sit in suspense.
- Investigate old and unusual items. Look beyond age to disputes, duplicate invoices, negative balances, promises, payment plans, and balances with no recent activity.
- Document action and review. Assign ownership and evidence to material exceptions, then retain preparer and reviewer sign-off with the close workpaper.
Common AR aging errors
| Error | Effect on the report | Investigation |
|---|---|---|
| Incorrect payment terms | Items appear current or overdue by the wrong number of days | Compare customer master and contract or invoice terms |
| Unapplied cash | Paid invoices remain open and overdue | Trace bank receipts and remittance to customer open items |
| Credits not allocated | Gross receivables are overstated and negative balances remain separate | Validate approval and link credit notes to the intended invoices |
| Backdated or future-dated invoices | Age and cutoff are distorted | Check transaction, service, issue, and posting dates |
| Duplicate invoices | Customer and total AR are overstated | Compare document numbers, source orders, amounts, and billing records |
| Wrong customer account | One customer is overstated while another has a credit or unexplained receipt | Review payer, invoice, and parent-child account relationships |
| Mixed currencies | Bucket totals may combine amounts on inconsistent bases | Retain transaction currency and use the approved reporting conversion |
| Closed items included | Aging total exceeds the real open-item population | Check report parameters and clearing status as of the reporting date |
AR aging and accounting estimates
Age is one input to credit-risk and collectibility review, not an automatic accounting conclusion. Dispute status, customer circumstances, security, subsequent receipts, historical experience, forward-looking information, and the applicable accounting framework may also be relevant. The aging report should preserve accurate source data and exception evidence; the organization's qualified finance team applies its approved policy to provisions, allowances, or write-offs.
AR aging versus collection reporting
An accounting aging report establishes the open balance and age at a point in time. A collection view may add promises to pay, contact history, dispute ownership, and next actions. Those operational fields are useful, but they should not silently change invoice amounts, dates, or clearing status. Keeping the accounting population stable allows the collection process to be measured against a reliable baseline.
Where the report fits in reconciliation operations
The aging report is one output of accounts-receivable reconciliation. It connects billing, bank receipts, remittance advice, customer credits, the AR subledger, and the general ledger. Aetherix can assemble these records, identify inconsistent dates or open items, and route exceptions while the client's authorized finance team retains accounting-policy decisions. For related source-to-ledger controls, see ledger reconciliation services.
Frequently asked questions
What does an AR aging report show?
It shows open customer receivables at an as-of date, normally with invoice references, due dates, open amounts, currencies, and age buckets. Better reports also retain dispute, collection, and ownership context.
Should AR be aged from invoice date or due date?
Either basis can be useful if it is clearly defined and consistently applied. Invoice date measures time outstanding; due date measures time overdue under the recorded payment terms.
Why does the aging report not match the general ledger?
Common causes include direct GL journals, failed or late subledger batches, currency revaluation, report-date differences, excluded customers, unapplied receipts, and incorrect report parameters. The difference should be reconciled rather than assigned to an aging bucket.