Accounts Receivable Aging: Buckets, Example, and Process

Accounts receivable aging groups unpaid customer balances by how long they have been current or past due. It turns one total—“customers owe us $42,000”—into a time-based view that shows which invoices need attention first.

An accounts receivable aging report lists open invoices as of a specific date and places each remaining balance into buckets such as current, 1–30, 31–60, 61–90, and more than 90 days past due. The report supports collection and cash-flow review, but only when invoice balances, due dates, payments, and credits are reconciled first.

Accounts receivable aging at a glance

These ranges are common conventions, not mandatory universal categories. Oracle describes aging buckets as configurable time periods used to review and report open receivables. Choose buckets that fit your payment terms and review rhythm, then keep them consistent enough to compare periods.

How accounts receivable aging works

Each open invoice needs:

• Customer
• Invoice number
• Invoice date
• Due date
• Original amount
• Payments and credits applied
• Remaining balance
• Aging as-of date

The usual calculation is:

Days past due = aging date − invoice due date

If the result is zero or negative, the invoice is current. If the result is positive, place the remaining balance in the matching past-due bucket.

Some accounting systems can age from the invoice date instead. That can be useful for specialized reporting, but it answers a different question. For collection work, aging from the due date usually reflects the payment agreement more clearly.

Worked accounts receivable aging example

Assume the aging date is August 31, 2026.

The total receivable is $8,950, but the total alone hides the risk. The report shows that $2,350 is at least 61 days past due and needs a different response from the $2,400 that is not yet due.

How to prepare an AR aging report

1. Choose the aging date

Use a clear cutoff such as month-end. A report dated August 31 should not include a September 1 payment unless it is explicitly presented as a later update.

2. Reconcile open balances

Before aging, apply settled payments, approved credits, cancellations, and write-offs. Investigate duplicate invoices and unapplied cash.

The invoice reconciliation guide explains this control in detail. Aging incorrect balances only makes bad data look organized.

3. Verify due dates

Check the actual invoice and agreement. Do not assume every invoice is Net 30. A due date may reflect Net 7, Net 15, a milestone, due on receipt, or a custom schedule.

Use the invoice payment terms guide to make future due dates explicit.

4. Age the remaining amount, not the original amount

If a $5,000 invoice received a $3,500 payment, the aging report should show the remaining $1,500 in its appropriate bucket. The original invoice value still belongs in the transaction history, but it is not the current receivable.

5. Review exceptions separately

Flag invoices that are:

• Disputed
• On an agreed installment plan
• Waiting for a PO or vendor setup
• Partly paid
• In collections or legal review
• Credit balances or unapplied cash

Age alone does not explain why an invoice is open. Add a reason and next action without changing the underlying due date.

What an aging schedule tells you

Collection priority

Older balances generally require more attention, but age should not be the only signal. A seven-day-old invoice blocked by a missing vendor form may be easier to resolve today than a 100-day-old invoice already in a formal dispute.

Customer concentration

Group the report by customer as well as bucket. One large customer holding most of the 61–90 day balance creates a different risk from many small, unrelated invoices.

Process problems

Repeated reasons reveal operational issues:

• Missing PO numbers suggest weak pre-invoice checks
• Many partial payments suggest unclear installment terms
• Unapplied cash suggests poor payment references
• Frequent disputes suggest scope or acceptance criteria are vague
• Current invoices becoming 1–30 late suggests reminders start too late

Trend, not certainty

Aging supports judgment; it does not predict exactly when cash will arrive or prove a balance is uncollectible. Use payment history, customer communication, disputes, and local accounting policy alongside the report.

AR aging vs an invoice statement

An aging report is an internal management view organized by time outstanding. A customer statement is a customer-facing account summary of invoices, payments, credits, and balances.

The two may use the same underlying records, but their purposes differ. Do not send an internal aging report with collection notes or risk labels when the customer only needs a clean statement.

How often should you review aging?

Match the review frequency to billing volume and payment terms:

• Weekly: useful for freelancers and small firms with active cash-flow needs
• Twice monthly: useful when most terms are Net 15 or invoices are milestone-based
• Monthly: a common formal reporting cadence, preferably with lighter weekly follow-up
• Daily: appropriate only for high-volume teams with automated transaction feeds

A monthly report does not mean you should wait until month-end to contact a customer whose invoice was rejected for a missing PO.

A practical action matrix

Use the disputed invoice guide when a customer questions validity, and the unpaid invoice reminder templates when the invoice is accepted but late.

Common aging report mistakes

Aging from the wrong date

Document whether the report uses due date or invoice date. Do not switch between methods without explaining the change.

Leaving payments unapplied

Cash received but not matched can overstate customer debt and send the wrong collection message.

Counting cancelled invoices

A cancelled or void invoice should not remain as collectible receivables. Preserve its history, but resolve its balance correctly.

Moving old invoices into current

A promise to pay next week does not make a 90-day-old invoice current. Keep its true age and record the promised date separately.

Treating every old balance as bad debt

Write-off and tax treatment require an approved accounting process. Age is a warning signal, not a write-off instruction.

Weekly AR aging checklist

1. Set and label the report date.
2. Apply payments and credits through the cutoff.
3. Verify due dates and remaining balances.
4. Review the largest and oldest customer balances.
5. Identify disputes and process blockers.
6. Assign one dated next action per material invoice.
7. Compare bucket totals with the prior review.
8. Preserve notes separately from customer-facing documents.

Frequently asked questions