Accounting · Receivables and collection discipline

Accounts Receivable Aging: Report, Example, and Collection Workflow

An accounts receivable aging report shows which customers owe money, how much remains unpaid, and how long balances have been outstanding or overdue. It connects the receivables control account to the invoices and customer actions behind the balance. Used well, it supports collection priorities, cash planning, and a cleaner month-end close.

← Accounting hub · Bank Reconciliation · Working Capital

What an AR aging report tells you

A summary report groups balances by customer and bucket. A detail report shows individual invoices, credits, receipts, due dates, and remaining balances. Start with the summary to identify concentrations, then use the detail to determine why an amount is open and what action is appropriate.

An overdue balance can reflect delayed payment, a dispute, incorrect terms, an unapplied receipt, a missing credit, or a posting error. Age alone does not identify the cause or prove that an amount is uncollectible.

Invoice age versus days past due

Invoice age = as-of date − invoice date. Days past due = as-of date − contractual due date. Use calendar days for the example below. Amounts with due dates on or after the as-of date are classified as current under this report’s convention.

Suppose an invoice is issued September 1 and due October 1. At September 30 it is 29 days old but not past due. Calling every 1–30-day-old invoice overdue would overstate collection problems when credit terms have not expired.

Software can use different bucket boundaries and settings. Record the report configuration rather than assuming the column labels mean the same thing in every system.

Worked AR aging example

Original hypothetical report as of September 30, 2026: these balances are after all receipts and credits posted through the cutoff. All items are in one currency. Due-date aging is used, and each customer has one open invoice for simplicity.

The bucket totals are $4,000 current, $3,000 at 1–30, $2,000 at 31–60, $1,000 at 61–90, and $500 at 91+. Overdue receivables are $6,500. Overdue share = $6,500 ÷ $10,500 × 100 = approximately 61.9%. This teaching example has no unapplied credits or customer credit balances; document your denominator when those exist.

Birch’s original invoice was $5,000 and a $2,000 receipt was applied before cutoff. Age the remaining $3,000 by the invoice’s due date. A partial payment does not automatically restart the clock or change the agreed terms.

How to prepare and reconcile the report

1. Set a fixed cutoff: specify entity, date, currency, AR account, aging basis, and transaction inclusion settings.
2. Review the detail: confirm due dates, terms, invoice references, partial receipts, credits, and unusual balances.
3. Tie the subledger: compare the net aging total with the corresponding AR control account at the same date and reporting basis.
4. Explain differences: check direct journal entries, missing customer assignments, unapplied transactions, filters, posting dates, and currency conversion.
5. Resolve supported items: correct misapplications or errors through the appropriate customer workflow and rerun the report.
6. Save the evidence: retain the final aging, GL tie-out, exceptions, and reviewer sign-off.

For the example, assume the matching AR control account has a $10,500 debit balance. The report ties. If a separately reported allowance reduces net receivables on the balance sheet, reconcile gross AR to its control account first, then bridge the allowance separately. Do not compare gross invoice balances directly with a net presentation and call the difference an error.

Turn the aging into a collection workflow

For each significant open item, record the customer contact, underlying reason, last action, promised date, next action, owner, and escalation deadline. Prioritize material exposures, broken promises, disputes, and concentration risk alongside age.

• Atlas, current $4,000: verify delivery and terms; place the expected receipt in the forecast without calling it overdue.
• Birch, $3,000 overdue: confirm the partial payment application and ask for a date for the remainder.
• Cedar, $2,000 overdue: identify whether a dispute or approval issue is blocking payment and assign resolution.
• Desert and Elm: escalate based on evidence, customer history, and approved policy rather than sending identical reminders indefinitely.

Customer commitments are forecast inputs, not guaranteed cash. Keep disputed or uncertain collections visible in cash-planning scenarios. Compare the aging with Accounts Payable Aging to understand collection timing relative to supplier obligations.

Does an aging report require a journal entry?

Running or moving an invoice between aging buckets does not itself create a journal entry. Entries follow underlying transactions or supported accounting adjustments. These simplified accrual-accounting examples omit sales tax and other complications.

After invoicing and the receipt, the open balance is $400. After the return it is $1,000 again, assuming no other activity. Apply the transactions to the correct invoice. See Bank Reconciliation for how the NSF affects cash.

An aging schedule can support a collectibility assessment, but bucket membership alone does not prescribe a loss rate or authorize a write-off. Use the applicable accounting framework, approved estimation approach, customer-specific evidence, and authorized review. This guide does not supply tax write-off rules or universal allowance percentages.

Useful measures and interpretation

• Overdue balance and share: show both dollars and the percentage of the defined AR population.
• Older-bucket exposure: track balances over 60 or 90 days, with consistent boundaries and scope.
• Promises kept: compare receipts with documented commitments after the promised dates have elapsed.
• Collection period: analyze average receivables relative to credit sales using matching periods; it is different from the age of a single invoice.

Use the KPI guide for collection-period formulas and measurement definitions. A falling overdue balance may result from collections, credits, write-offs, or reclassification. Show the movement by cause instead of presenting every decrease as cash collected.

Common errors to avoid

• Aging from invoice date while labeling columns “days past due.”
• Running a historical ledger balance against an aging using today’s cutoff.
• Ignoring unapplied cash or credits that keep paid invoices looking open.
• Netting one customer’s credit against another customer’s debt without a supported basis.
• Removing disputed invoices from management visibility.
• Assuming old balances can be deleted without checking the underlying transaction and approval.

Month-end review checklist

Frequently asked questions

Is current AR overdue?

Not under this report’s convention: current means due today or later. Confirm your software’s treatment of due-today balances.

Why does a paid invoice still appear?

The receipt may be unapplied, assigned to a different customer or invoice, dated after the cutoff, or reversed. Trace the source before creating another payment.

Is AR aging the same as DSO?

No. Aging groups open balances at a point in time. DSO or an average collection-period measure relates receivables to credit sales over a period and can be affected by timing and seasonality.

Continue learning

Review Accounts Payable Aging, Bank Reconciliation, and the Cash Conversion Cycle. Use the Accounting Cycle to connect the supporting schedule to the close, or return to Accounting.

Source and example notes

Intuit: Run an accounts receivable aging report explains summary and detail reports and aging customization. The September schedule, dates, calculations, entries, workflow, and checklist above are original educational illustrations. Report settings and transaction handling vary by system.