The Accounts Receivable Aging Report: How to Read It, Analyze It, and Automate It in 2026

TL;DR: What Is an Accounts Receivable Aging Report?
An accounts receivable aging report is a schedule that groups every unpaid customer invoice into time buckets based on how long it has been outstanding — typically Current, 1–30, 31–60, 61–90, and 90+ days past due. Finance teams use it to see which customers owe money, how overdue each balance is, how much of the receivable portfolio is at risk of becoming bad debt, and where collection effort should be focused next. CFOs analyze AR aging because it is the earliest reliable warning signal for cash flow problems, credit deterioration, and revenue that has been booked but will never be collected. The limitation of the traditional aging report is that it is backward-looking and usually stale by the time it is circulated — modern AR platforms replace the monthly Excel aging schedule with a live dashboard that not only shows aging buckets but automatically triggers collection action against them.
Almost every finance team produces an accounts receivable aging report. Far fewer actually use it to change what happens next.
The typical pattern looks like this: someone on the AR team exports an open-items listing from the ERP on the first working day of the month, pastes it into a spreadsheet, applies a set of formulas that bucket invoices by days outstanding, colour-codes the worst offenders, and circulates the file to the controller and the CFO. By the time the report lands in an inbox, it describes a receivable position that is already several days out of date — and nothing in the file tells anyone which of the 400 overdue invoices to chase first.
This guide covers what an AR aging report actually contains, how to read and analyze it properly, the metrics that turn it from a static listing into a decision tool, and how finance teams are replacing the manual aging schedule with automated accounts receivable reporting that drives collection action in real time.
What an Accounts Receivable Aging Report Contains
At its simplest, an aging report answers one question: how much do our customers owe us, and how late are they?
A standard aging schedule contains one row per customer (or per invoice, in a detail report) and one column per aging bucket:
| Customer | Current | 1–30 Days | 31–60 Days | 61–90 Days | 90+ Days | Total Outstanding |
|---|---|---|---|---|---|---|
| Customer A | $82,000 | $24,000 | $0 | $0 | $0 | $106,000 |
| Customer B | $15,000 | $31,000 | $28,000 | $12,000 | $0 | $86,000 |
| Customer C | $0 | $0 | $9,500 | $18,000 | $47,000 | $74,500 |
| Customer D | $140,000 | $0 | $0 | $0 | $0 | $140,000 |
| Total | $237,000 | $55,000 | $37,500 | $30,000 | $47,000 | $406,500 |
The buckets are defined relative to the invoice due date, not the invoice date — a distinction that trips up a surprising number of teams. An invoice issued 45 days ago on 60-day terms is not overdue; it belongs in “Current.” Bucketing from invoice date instead of due date inflates your apparent delinquency and makes the report useless for credit decisions.
Summary vs. Detail Aging Reports
Most ERPs produce two versions, and they answer different questions:
- The aging summary shows one line per customer with totals per bucket. It is the right view for portfolio-level analysis: concentration risk, overall portfolio health, and bad debt provisioning.
- The aging detail shows every individual open invoice, with invoice number, date, due date, days outstanding, and remaining balance. It is the right view for collections work, because the collector needs to reference specific invoice numbers on a call.
A common failure is giving collectors the summary report. Telling a collector that “Customer C owes $74,500” is not actionable; telling them that invoices INV-4471, INV-4502, and INV-4588 totalling $47,000 have been sitting past 90 days is.
How to Read an Accounts Receivable Aging Report
Reading the report well means looking past the totals. Four things matter more than the bottom-right number.
1. The Shape of the Distribution
A healthy receivable portfolio is heavily weighted toward “Current,” with a thin and rapidly decaying tail. In the example above, $237,000 of $406,500 (58%) is current — which is mediocre. Best-in-class B2B portfolios typically run 75–85% current.
More important than the absolute percentage is the slope. If each successive bucket is materially smaller than the last, your collection process is working: invoices that slip do get recovered. If the 90+ bucket is larger than the 61–90 bucket, you have a structural problem — balances are entering the oldest bucket and never leaving it. That is the signature of receivables that are disputed, forgotten, or uncollectible rather than merely late.
2. Concentration Risk
Look at how much of the overdue balance sits with a single customer. In the table above, Customer C accounts for $47,000 of the $47,000 in the 90+ bucket — 100% concentration. That is a single-customer credit event, not a collections process problem, and it requires a completely different response: a credit hold, a payment plan, or escalation to legal, rather than another reminder email.
Portfolio-level metrics hide this. A CFO looking only at “11.6% of AR is 90+ days” would reasonably conclude the collections team needs to work harder. The concentration view shows the real issue.
3. Movement Between Periods
A single aging report is a snapshot. The insight lives in the comparison. Placing this month’s aging next to last month’s reveals roll rates — the percentage of each bucket that rolls forward into the next bucket rather than being collected.
If 40% of your 31–60 balance rolls into 61–90 every month, you can forecast your bad debt exposure with reasonable accuracy months in advance. Roll rate analysis is the single most underused technique in AR aging analysis, and it is nearly impossible to do when each month’s report is a separate static spreadsheet.
4. Disputed vs. Genuinely Late
Not every overdue invoice is a collections problem. A meaningful share of aged balances are invoices the customer is not paying because something is wrong: a pricing discrepancy, a missing PO reference, an invoice that never reached the right portal, or a short payment against an unapproved deduction.
Standard ERP aging reports have no field for this. The invoice looks identical to a genuine slow-pay. Teams that do not separate the two send payment reminders to customers who are waiting on a credit note — which damages the relationship and wastes collector time. If short payments and deductions are a recurring pattern in your aging, deduction management is a distinct workflow that needs to sit alongside collections, not inside it.
Why Do CFOs Analyze the Aging of Accounts Receivable?
CFOs care about AR aging for reasons that go well beyond chasing late payers.
It is the earliest warning signal for cash flow. Revenue recognition tells you what you earned. The aging report tells you what you are actually going to collect and roughly when. A portfolio drifting rightward across buckets predicts a cash shortfall one to two quarters before it appears in the bank balance — enough lead time to draw on a facility, slow discretionary spend, or tighten credit terms.
It drives the bad debt provision. Under both IFRS 9 and ASC 326, expected credit loss models are commonly built on an aging matrix: a loss rate applied to each bucket, calibrated on historical roll rates. The aging report is the input to a number that lands directly in the P&L, which makes its accuracy an audit matter, not just an operations matter. The mechanics of that calculation are covered in bad debt expense and the allowance for doubtful accounts.
It reveals credit policy failures. If new customers consistently appear in the 61–90 bucket within their first two invoices, the problem is not collections — it is that credit is being extended without adequate assessment. Aging analysis is often the evidence that triggers a credit policy review.
It quantifies the cost of working capital tied up in receivables. Every dollar sitting in the 90+ bucket is a dollar funded by the company’s cost of capital. At a 10% cost of capital, $500,000 permanently parked in aged receivables costs $50,000 a year in financing — a number that usually exceeds the cost of fixing the underlying process. Peakflo’s savings calculator models this trade-off directly.
The Metrics That Turn Aging Into Analysis
The aging report itself is raw material. These four metrics convert it into something a finance leader can act on.
Days Sales Outstanding (DSO)
DSO measures the average number of days it takes to collect revenue after a sale.
DSO = (Average Accounts Receivable / Total Credit Sales) x Number of Days in PeriodDSO is the headline receivables metric, but it is heavily distorted by sales seasonality — a strong final month inflates closing AR and makes DSO look worse even if collection performance improved. Read it as a trend over four or more quarters, never as a single-month figure. For a practical playbook on moving this number, see how to reduce DSO by 25%.
Accounts Receivable Turnover Ratio
AR Turnover Ratio = Net Credit Sales / Average Accounts ReceivableThis tells you how many times per year the receivable book is collected and replaced. A ratio of 8 means the portfolio turns roughly every 45 days. It is the same underlying relationship as DSO expressed differently, and it is the version most commonly used in external benchmarking and lender covenants.
Collection Effectiveness Index (CEI)
CEI = [(Beginning AR + Credit Sales - Ending Total AR) / (Beginning AR + Credit Sales - Ending Current AR)] x 100CEI is the metric most worth adding if you only track DSO today. Where DSO is contaminated by sales volume, CEI isolates how much of what was available to collect actually got collected — expressed as a percentage where 100% is perfect. A team whose DSO worsened because sales grew 30% can still demonstrate a CEI of 92% and prove that collection execution improved. Best-in-class is generally considered above 80%.
Average Days Delinquent (ADD)
ADD = DSO - Best Possible DSOADD strips out the portion of DSO that is simply your payment terms and isolates the portion that is genuine lateness. If your terms are Net 45 and your DSO is 61, your ADD is 16 days — and that 16 days, not the 61, is the number your collections process controls.
Why the Manual Aging Report Breaks Down
The aging report concept is sound. The way most teams produce it is not.
It is stale on arrival. A month-end export reflects a single point in time. Payments received on the second of the month do not appear until the following cycle, so collectors routinely chase invoices that have already been paid — one of the fastest ways to erode customer goodwill.
It does not reflect cash that has arrived but is not applied. If remittances are sitting unmatched because cash application is manual, invoices show as open when the money is already in the bank. The aging report is only as accurate as the cash application process feeding it — see remittance advice and unapplied cash for why matching breaks.
It fragments across entities and ERPs. Businesses running multiple ERPs after acquisition or geographic expansion cannot produce a single consolidated aging without manual normalisation of customer master data. The same customer appears three times under three different IDs, and concentration risk becomes invisible.
It ends where the work begins. The report identifies the problem and then stops. Someone still has to decide who to contact, in what order, through which channel, with what message — and then actually do it. That gap between the report and the action is where DSO is won or lost. Aging is also only one stage of a longer flow — see the order-to-cash process for where else cash gets stuck.
From Static Aging Schedule to Live AR Dashboard
Modern AR platforms treat aging not as a monthly report but as a continuously updating state that automation acts on.
Real-time bucketing. Aging recalculates as invoices are issued and payments are applied, so the view is accurate at the moment a collector opens it. Automated reconciliation and cash application closes the gap between cash arriving and invoices closing.
Consolidated across systems. Direct integrations with NetSuite, Xero, QuickBooks and SAP normalise customer records across entities so the aging reflects the true group-level exposure per customer.
Segmented by root cause. Overdue balances are tagged as genuine slow-pay, disputed, short-paid, or undelivered — so the invoices waiting on a credit note are routed to resolution rather than to a reminder sequence.
Connected to action. This is the decisive difference. Aging buckets become triggers: a balance entering 1–30 days fires an automated payment reminder; a balance crossing 60 days routes to an owner in the finance CRM; high-value balances past 90 days are escalated to AI voice agents that place outbound calls, capture promise-to-pay commitments, and write them back against the invoice automatically.
The report stops being a document that describes the past and becomes the control surface for collections.
How to Build an Aging Analysis Process That Actually Reduces DSO
Step 1: Fix the data before the report. Confirm buckets run from due date, clear unapplied cash, and deduplicate customer records across entities. An aging report built on bad data produces confidently wrong decisions.
Step 2: Separate disputed balances from genuine lateness. Tag every overdue invoice by root cause and route disputes to resolution rather than to a reminder sequence.
Step 3: Add CEI and ADD alongside DSO. These are the metrics your team can actually influence, and they survive scrutiny when sales volume swings.
Step 4: Measure roll rates between periods. Month-over-month bucket movement is the leading indicator that a single snapshot cannot give you.
Step 5: Wire aging buckets to automated action. Reminders for early-stage balances, owner escalation for mid-stage, voice outreach for high-value aged balances. This is the step that converts visibility into collected cash.
Our Verdict: The Aging Report Is Only Worth What You Do With It
Most finance functions already produce an aging report. Very few use it as a control surface. The gap between those two states is where the value sits, and it is almost entirely a question of data currency and connected action rather than analytical sophistication.
Three things separate teams that get value from AR aging from teams that merely circulate it. First, the data must be current — an aging built on an unapplied-cash backlog reports invoices as open that are already settled, and every decision downstream inherits that error. Second, overdue balances must be segmented by root cause, because a disputed invoice and a slow-paying customer require completely different responses and only one of them belongs in a collections queue. Third, the buckets must trigger something automatically; a report that identifies a problem and then stops has converted analysis into a to-do list nobody owns.
The reporting discipline also has an external dimension. Expected credit loss frameworks published by the IFRS Foundation and the Financial Accounting Standards Board both require provisions to reflect current and forward-looking conditions rather than historical averages alone, which makes aging accuracy an audit matter. Professional bodies including the Chartered Institute of Credit Management and the National Association of Credit Management publish credit and collections benchmarking that is useful for calibrating bucket loss rates against sector norms rather than inventing them internally.
Conclusion
The accounts receivable aging report remains one of the most valuable artefacts in finance — but only when it is current, accurate, segmented by root cause, and connected to the action it implies. A monthly spreadsheet that describes last month’s receivable position is a record. A live aging view that automatically triggers the right outreach on the right invoice is a collections engine.
Request a demo to see how Peakflo’s accounts receivable automation turns real-time aging analytics into automated collections, or explore AR reporting to see the dashboards replacing manual aging schedules.
Frequently Asked Questions
What is an accounts receivable aging report?
An accounts receivable aging report is a schedule that lists all unpaid customer invoices grouped into time buckets based on how many days past due they are — typically Current, 1–30, 31–60, 61–90, and 90+ days. It shows which customers owe money, how overdue each balance is, and how much of the receivable portfolio is at risk of becoming uncollectible.
How do I read an accounts receivable aging report?
Start with the distribution rather than the total: a healthy portfolio has 75–85% of balances in “Current” with each successive bucket materially smaller than the last. Then check concentration — whether one customer accounts for most of the overdue balance — and compare against the prior month to see how much of each bucket is rolling forward instead of being collected.
What is the difference between an aging summary and an aging detail report?
The aging summary shows one line per customer with bucket totals and is used for portfolio analysis, credit decisions, and bad debt provisioning. The aging detail lists every individual open invoice with its number, due date, and days outstanding, and is the version collectors need because it lets them reference specific invoices during customer conversations.
Why do CFOs analyze the aging of accounts receivable?
CFOs analyze AR aging because it is the earliest reliable predictor of cash flow problems, the primary input to the expected credit loss provision under IFRS 9 and ASC 326, the clearest evidence of whether credit policy is working, and a direct measure of how much working capital is tied up in uncollected revenue.
How are accounts receivable aging buckets calculated?
Buckets are calculated from the invoice due date, not the invoice date. An invoice issued 45 days ago on Net 60 terms is still current. Calculating from invoice date is a common error that inflates apparent delinquency and makes the report unusable for credit and provisioning decisions.
Can accounts receivable aging reports be automated?
Yes. Modern AR platforms recalculate aging continuously as invoices are issued and payments are applied, consolidate balances across multiple ERPs and entities, tag overdue invoices by root cause, and use the buckets as triggers for automated reminders, owner escalation, and AI voice agent outreach — replacing the monthly Excel export entirely.
What is a good percentage of receivables over 90 days?
As a general benchmark, healthy B2B portfolios keep balances over 90 days below 5% of total receivables. Above 10% usually indicates either a structural collections problem or unresolved disputes sitting in the oldest bucket. The trend and the concentration matter more than the absolute figure.
How often should an accounts receivable aging report be produced?
Monthly production is the common minimum, but it is too infrequent to drive collections. Teams working from a live aging view that recalculates as invoices are issued and payments applied avoid the most damaging failure of periodic reporting, which is chasing customers for invoices that were already paid earlier in the cycle.
What is a roll rate in AR aging analysis?
A roll rate is the percentage of balances in one aging bucket that move into the next bucket instead of being collected. Comparing consecutive months reveals these rates, which are the most reliable internal basis for forecasting bad debt exposure and for calibrating the loss percentages used in an expected credit loss provision.
Why does unapplied cash distort the aging report?
When payments are received but not yet matched to specific invoices, those invoices continue to appear open in the aging. This overstates receivables, inflates DSO, corrupts the bad debt provision built on the aging matrix, and triggers payment reminders to customers who have already paid.