What Is an Accounts Receivable Aging Report? (And How to Actually Read One)
Most people read an aging report by looking at the total and then the 90+ column. That order hides the two patterns worth acting on. Here is what the report is, how the buckets work, and how to read it in the order that produces decisions.
On this page
Key takeaways
- An aging report groups every unpaid invoice by how long it has been outstanding — the standard brackets are current, 1–30, 31–60, 61–90 and 90+ days.
- Age is measured from the due date, not the invoice date. Getting this wrong makes a compliant book look delinquent.
- Read it in this order: movement between buckets, then concentration, then the 90+ column, then the total. The total is the least actionable number on the page.
- A static aging report is out of date the day it is produced, which is why it drives reporting well and daily action badly.
- The report tells you *what* is old. It cannot tell you *why* — and the two dominant causes, cash and documentation, need opposite responses.
The accounts receivable aging report is the most widely produced document in finance that almost nobody is taught to read. Every accounting system will generate one, every auditor asks for it, every bank wants it with the facility review — and in most businesses it is looked at exactly the way it should not be: total at the bottom, glance at the 90-plus column, close the file.
Read properly it is the closest thing receivables has to a diagnostic. It will tell you whether your collections process is working, which customers are quietly becoming a problem, and — by what it cannot explain — where to look next.
What the report is
An accounts receivable aging report, also called an aged debtors or aged receivables report, lists every unpaid customer invoice grouped by how long it has been outstanding. Rows are customers; columns are age brackets; each cell is the amount that customer owes in that bracket.
The standard brackets are current, 1–30, 31–60, 61–90 and over 90 days. They are conventional rather than mandated — auditors, banks and provisioning policies are all built around them, which is reason enough not to invent your own.
| Customer | Current | 1–30 | 31–60 | 61–90 | 90+ | Total |
|---|---|---|---|---|---|---|
| Al Fahad Trading | 120,000 | 45,000 | 0 | 0 | 0 | 165,000 |
| Gulf Contracting | 0 | 30,000 | 85,000 | 60,000 | 40,000 | 215,000 |
| Marina Supplies | 80,000 | 0 | 0 | 0 | 0 | 80,000 |
| Desert Steel | 15,000 | 12,000 | 0 | 0 | 95,000 | 122,000 |
| Total | 215,000 | 87,000 | 85,000 | 60,000 | 135,000 | 582,000 |
Four customers, four completely different stories — and none of them is visible from the AED 582,000 total.
Look at those four rows rather than the total. Al Fahad is a healthy account trading normally. Marina Supplies owes nothing overdue at all. Gulf Contracting is deteriorating across every bracket — the classic profile of a customer with a cash problem. Desert Steel is the interesting one: current and 1–30 look fine, and then there is AED 95,000 sitting in 90+ with nothing in between.
How the buckets are calculated
One detail determines whether the report means anything: age is counted from the due date, not the invoice date.
On 60-day terms, an invoice raised 45 days ago is not 45 days old for aging purposes — it is current, and it is not late. Systems that age from the invoice date make every customer on extended terms look delinquent, which sounds like a technicality until it reaches a bank covenant conversation or a bad-debt provision.
| Bucket | Meaning | Typical interpretation |
|---|---|---|
| Current | Not yet due | Working capital doing its job. Not a collections concern. |
| 1–30 | Up to a month past due | Usually process friction: approval cycles, payment runs, a missed reference. |
| 31–60 | One to two months past due | The customer has now skipped at least one payment run. Needs a specific commitment. |
| 61–90 | Two to three months past due | Escalation territory. Chasing at the same level has already failed twice. |
| 90+ | Over three months past due | Recovery rather than collection. Provisioning and credit-stop decisions live here. |
A second detail: aging should be recalculated continuously, not stored. If the bucket is written to the record when the invoice is imported, then yesterday's 30-day invoice is still labelled 30 days old today, and invoices stop crossing the 90-day boundary on schedule — they cross it whenever somebody refreshes the report. Deriving the bucket from the due date on demand means there is only ever one version of the truth, and it is today's.
How to read one, in order
The instinct is to read from the total upwards. That is exactly backwards, because the total is the number with the least information in it — it moves with sales volume, so it can rise in a month where collections improved.
1. Movement between buckets
Compare this month's report against last month's, bucket by bucket. The question is not "how much is overdue" but "which direction is money flowing between brackets". Money moving down the brackets — from 31–60 into 1–30 and out — is a working process. Money accumulating in 61–90 while 1–30 stays flat means invoices are entering the overdue population faster than the team is clearing them, and headcount or process is the constraint.
This is the single most diagnostic view of the report and it is invisible in any single snapshot, which is why a report produced only at month end can be read for compliance but not for management.
2. Concentration
Sort by total and look at the top five customers as a share of the ledger. One customer at 30% of receivables is a materially more dangerous position than ten at 3% with worse aging profiles, because the downside is correlated: if that name fails, it takes a third of the book.
3. The 90+ column, customer by customer
Now look at the oldest bracket, but per customer rather than in aggregate, and classify each balance. Is it disputed, stranded on documentation, or genuinely unpaid? Those three require a commercial conversation, a reconciliation, and an escalation respectively — and lumping them together as "bad debt risk" is how a recoverable balance gets provisioned and a genuinely bad one gets chased for another six months.
4. The total, last
Finally, the total — and mainly as an input to days sales outstanding, where it becomes comparable across periods by being expressed relative to sales rather than in absolute terms.
What the aging report cannot tell you
This is the limit worth being explicit about, because it explains why teams with immaculate aging reports still collect badly.
The report tells you an invoice is 74 days overdue. It does not tell you that a collector spoke to the customer on Tuesday, that the customer committed to paying AED 40,000 on the 25th, that they made the same commitment last month and broke it, or that nobody has contacted this account in six weeks. It describes the state of the ledger and says nothing about the state of the work.
| The aging report answers | It cannot answer |
|---|---|
| Which invoices are old | Who is responsible for chasing them |
| How much is in each bucket | What the customer said last time |
| Which customers owe the most | What they committed to, and whether they kept it |
| Where the 90+ exposure sits | Which accounts have had no contact at all |
That gap is why aging tends to be produced by an accounting system while the chasing is managed somewhere else entirely — historically a spreadsheet and an inbox. The useful version of the report is one where each aged invoice carries its own follow-up history, so the report is a work list rather than a snapshot. That connection is what invoice aging software exists to make, and the follow-up side of it is covered under collections management software.
A practical review cadence
The report serves three audiences with genuinely different needs, and trying to serve all three with one monthly document is why it usually serves none of them well.
| Level | Frequency | Looking for |
|---|---|---|
| Collector | Daily | Their own accounts, prioritised by value and age — a work list for today |
| Finance manager | Weekly | Bucket movement, escalations due, accounts with no recent contact |
| CFO / owner | Monthly | DSO trend, concentration, 90+ exposure and the provision |
A collector reading a monthly report is working from data up to four weeks stale on accounts that change daily.
None of this requires new software to start — the reading order and the cadence are free. What is genuinely hard to sustain manually is the daily level, because a report rebuilt by hand cannot be current enough to be a work list. For where the aging report fits in the receivables process as a whole, see what accounts receivable management covers, and for the credit decisions upstream of it, the credit control process.