Receivables glossary

What is an AR aging report?

A time-based view of open customer balances - useful for prioritisation, not a prediction of payment.

In brief

An accounts-receivable aging report groups open customer invoice balances by how long they have been outstanding, commonly into current, 1–30, 31–60, 61–90 and over-90-day buckets. It helps finance prioritise verification and follow-up. The report does not by itself explain disputes, unmatched payments, promises or the likelihood that a customer will pay.

01

How are aging buckets calculated?

Aging begins with a reference date and a consistent age basis, usually the invoice due date for collection work or the invoice date for a different analytical purpose. Every open balance is assigned to the bucket containing its age on that date.

The report should state which basis it uses. Mixing invoice-date and due-date aging produces misleading comparisons, especially when customers have different terms.

  • Current or not due
  • 1–30 days overdue
  • 31–60 days overdue
  • 61–90 days overdue
  • More than 90 days overdue

Apply the report in the AR aging workflow.

02

What does an aging report reveal?

The report shows concentration by customer, entity, currency and age. It can reveal that a small number of old invoices account for most overdue value, or that a newer bucket contains many small operational issues.

It does not reveal the cause automatically. A large old balance may be disputed, partly paid, promised for a date or already paid but not matched. Finance must connect the bucket to record-level context before acting.

  • Value concentration
  • Count of open records
  • Movement between periods
  • Owners and next actions

Start with what is accounts receivable.

03

How should exceptions change the view?

Disputes, credits, unapplied payments and agreed payment plans should remain visible rather than being hidden inside one overdue total. The original invoice, current open amount and exception state answer different questions and should all be retained.

Aging should prioritise the queue, while the state determines the action. A disputed 70-day invoice needs resolution; an ordinary 12-day overdue invoice may need a reminder.

  • Verify delivery.
  • Check matched and unmatched payments.
  • Identify disputes and promised dates.
  • Confirm approved credit notes or adjustments.

Investigate payments through reconciliation.

04

Worked example: read the distribution

Assume a company has $48,000 open: $20,000 current, $12,000 at 1–30 days, $9,000 at 31–60 days, $5,000 at 61–90 days and $2,000 over 90 days. The oldest $2,000 is important, but it is not automatically the only priority.

If the $9,000 middle bucket belongs to one disputed invoice with an approaching resolution date, it may require more immediate ownership than several already-promised older balances. Age supplies sequence; context supplies judgment.

  • Total open: $48,000
  • Overdue: $28,000
  • More than 60 days: $7,000
  • Action order: age plus state, value and commitment

Turn priority into accountable collections.

05

How do teams use aging responsibly?

Review aging on a predictable cadence, compare movement between periods and inspect the records behind material changes. Assign an owner and next action to exceptions, then remove matched payments promptly so the queue stays credible.

Do not publish a collection-performance claim from one snapshot. A measured result needs a consistent definition, baseline, observation period, source and explanation of exclusions.

  • Use one age basis.
  • Retain original and open amounts.
  • Review movement, not only the total.
  • Tie every priority item to an owner.

Use proportionate payment reminders.

Continue in context

net terms.

Common questions

Clear answers without the detour.

What does an AR aging report show?

It shows open customer invoice balances grouped by age at a stated reporting date. Common buckets are current, 1–30, 31–60, 61–90 and over 90 days. The report helps finance see concentration and prioritise review, but it needs record-level context because age alone does not reveal disputes, promises, credits or unmatched payments.

Should aging use the invoice date or due date?

Use the basis that matches the question and label it clearly. Due-date aging is generally more useful for overdue follow-up because it respects agreed payment terms. Invoice-date aging can support other analysis. Do not mix the two bases in one trend without explanation, since a 30-day term changes the apparent age materially even when customer behaviour is identical.

Does the oldest invoice always need the first action?

No. Age is one prioritisation signal. Value, dispute state, payment evidence, customer commitment and the next promised date can change the correct sequence. An older invoice with a documented payment promise may be monitored, while a newer high-value dispute needs immediate ownership. The report should make investigation easier, not replace informed judgment with one bucket.

How should partial payments appear in aging?

Keep the original invoice total and show the remaining open balance after matched payments. The open portion should occupy the appropriate age bucket using the chosen basis. Do not erase the payment history or age the original total as though nothing was received. Any unmatched payment should remain a separate exception until the business has evidence to apply it.

How often should a team review accounts-receivable aging?

The cadence should match invoice volume, terms and collection risk. Many teams use a weekly operating review and a formal month-end view, while lower-volume businesses may need less frequency. Whatever the cadence, use a consistent reference date, inspect material movements, assign owners and reconcile matched payments so stale records do not undermine trust in the report.