What an AR aging report includes, how aging buckets work, how to calculate one, and how finance teams use it to decide which invoices to collect first.
Dadhich Rami 
An accounts receivable aging report lists every unpaid customer invoice and groups the balances by how long they have been outstanding or past due, usually as current, 1–30, 31–60, 61–90, and over 90 days. Finance and collections teams use it to find overdue invoices, decide which accounts to contact first, watch for credit risk, estimate bad debt, and forecast incoming cash.
If your business sells on credit, the balance sheet tells you how much customers owe. It does not tell you whether that money is two days old or two quarters old. The aging report answers that question, and the answer changes what your team does next.
This matters more than it might seem. In Atradius's 2026 survey of US businesses, 55% of suppliers said their B2B customers were delaying invoice payments, and late payments affected an average of 22% of B2B receivables. The same survey found that most overdue invoices were settled within a month of the due date. That is exactly the pattern an aging report helps you manage: catching balances while they are still young and easy to collect.
This guide covers what an aging report contains, how the buckets work, how to calculate one by hand, how to read a real example, and how to turn the report into a collections plan. It also covers the report's limits, because an aging report on its own can point you in the wrong direction.
An accounts receivable aging report, also called an AR aging schedule, is a breakdown of your open receivables by age. Each customer appears on a row, and their unpaid balance is split across columns that represent time periods.
The total of all the columns equals your accounts receivable balance on the report date. What the report adds is timing. Two customers can each owe $10,000, but if one balance is current and the other is 95 days past due, they need completely different handling.
"Aging report" and "aging schedule" are used interchangeably in most finance teams. Accountants tend to say schedule when the breakdown supports a month-end calculation, such as the allowance for doubtful accounts. Collections teams tend to say report. The data is the same.
A summary aging report shows one row per customer with totals by bucket. A detailed report goes down to the invoice level. Most accounting systems and ERPs can produce both. A useful detailed report includes:
| Field | Why it matters |
|---|---|
| Customer name and account number | Groups invoices so you can see total exposure per customer. |
| Invoice number | Lets collectors reference the exact document when they contact the customer. |
| Invoice date | The starting point for measuring days outstanding. |
| Payment terms and due date | The starting point for measuring days past due. |
| Original amount, amount paid, open balance | Shows partial payments and short pays, not just the invoice total. |
| Days outstanding or days past due | The number used to place the balance in a bucket. |
| Aging bucket | The column the open balance falls into on the report date. |
| Status and notes | Disputes, promises to pay, and last contact date, so the team knows what has already happened. |
The last field is the one most often missing from basic reports, and it is the one collectors rely on most. A balance marked as disputed needs a different conversation than a balance with a promise to pay on Friday.
Buckets are the time periods that make up the report's columns. The most common structure uses 30-day intervals, but the first thing to confirm is what the report measures from.
Aged by invoice date means each bucket shows how long ago the invoice was issued. A 20-day-old invoice lands in 0–30 days even if it is not due for another 40 days.
Aged by due date means each bucket shows how long the invoice has been late. Anything not yet due sits in a "current" column. This version is more useful for collections because it separates on-time balances from late ones.
Here is how the same invoice moves through due-date buckets on Net 30 terms:
| Bucket | What it usually means | Typical action |
|---|---|---|
| Current | Within terms. Nothing is late yet. | Confirm the invoice was received and has no errors. |
| 1–30 days past due | Often a missed payment run, approval delay, or unmatched remittance. | A reminder and a check on invoice status with the customer's AP team. |
| 31–60 days past due | Something is blocking payment: a dispute, a missing PO, or a cash problem. | Direct contact with a named person and a request for a payment date. |
| 61–90 days past due | Real risk. The longer this runs, the harder it gets to collect. | Escalate internally, involve the account owner, review credit terms. |
| Over 90 days past due | Serious risk of loss. | Formal demand, payment plan, credit hold decision, or third-party collection. |
Businesses with long payment terms, such as construction or equipment rental, sometimes add buckets like 91–120 and 120+ so the oldest balances do not disappear into one column. Pick a structure that fits your terms and keep it consistent so month-to-month comparisons mean something.
Your accounting system will normally build the report for you, but knowing the calculation helps you spot errors and explain the numbers to others. For each open invoice:
Worked example
Invoice amount: $10,000, no payments received
Invoice date: July 1. Terms: Net 30. Due date: July 31. Report date: September 15.
Days outstanding (from invoice date): 76 days
Days past due (from due date): 46 days, so the balance goes in the 31–60 days past due bucket
Notice that the same invoice would sit in the 61–90 column on an invoice-date report and the 31–60 column on a due-date report. When two people disagree about how old a balance is, this is usually why.
Step 5 is the one people skip. If the aging total does not match the general ledger, something is wrong: an unapplied payment, a credit memo that was never matched, or a manual journal entry. Fix the difference before anyone uses the report to make decisions.
Here is a summary aging report for a distributor on Net 30 terms, aged by due date, as of September 30.
| Customer | Current | 1–30 | 31–60 | 61–90 | 90+ | Total ($) |
|---|---|---|---|---|---|---|
| ABC Traders | 3,000 | 1,200 | - | - | - | 4,200 |
| Blue Sky Supplies | 2,000 | 2,800 | 2,000 | - | - | 6,800 |
| Greenfield Retail | - | 1,500 | - | 1,000 | 1,000 | 3,500 |
| Nova Tech | 5,000 | - | - | - | - | 5,000 |
| Stellar Logistics | 1,500 | - | 1,200 | - | 2,000 | 4,700 |
| Total | 11,500 | 5,500 | 3,200 | 1,000 | 3,000 | 24,200 |
| % of total AR | 47.5% | 22.7% | 13.2% | 4.1% | 12.4% | 100% |
Start with the shape, not the biggest number. Nova Tech has the largest single balance, $5,000, but all of it is current. It needs nothing today.
The two accounts that need attention are Stellar Logistics and Greenfield Retail. Stellar has $2,000 over 90 days while it keeps buying on credit, which suggests either a dispute on an old invoice or a habit of paying newer invoices first. Greenfield has balances spread across 1–30, 61–90, and 90+, a pattern that often means the customer is paying partially or selectively.
Blue Sky Supplies is the account to watch. Nothing is critical yet, but $4,800 has slipped past due, and if next month's report shows the $2,000 moving into 61–90, the trend becomes a problem.
Overall, 52.5% of this AR is past due. That is well above the 22% average share of late B2B receivables Atradius reported for US companies in 2026, which in a real business would be a signal to review both collections workflow and credit terms.
An aging report becomes useful the moment it drives a daily worklist. A simple way to rank accounts is to weigh age against dollar value:
With the accounts ranked, a practical weekly routine looks like this:
For a fuller look at collection workflows, see our guide to B2B collections.
The aging report is a snapshot. These metrics turn it into a trend you can manage:
| Metric | How to calculate it | What it tells you |
|---|---|---|
| Past-due percentage | Past-due AR ÷ total AR × 100 | How much of your AR is late. 52.5% in the example above. |
| 90+ percentage | AR over 90 days ÷ total AR × 100 | How much is at serious risk. 12.4% in the example. |
| Days sales outstanding (DSO) | (AR ÷ net credit sales) × days in period | How long, on average, it takes to turn a credit sale into cash. |
| Collection effectiveness index (CEI) | (Beginning AR + credit sales − ending AR) ÷ (beginning AR + credit sales − ending current AR) × 100 | How much of the collectible balance your team actually collected in the period. |
| Bucket migration | Compare each bucket with the prior month | Whether balances are aging faster than they are being collected. |
DSO and the aging report can disagree. A few very large current invoices can pull DSO down while the 90+ bucket quietly grows. Tracking both keeps one from hiding the other.
Under US GAAP (ASC 326, the CECL standard), companies must estimate expected credit losses on receivables, and an aging schedule is one of the most common ways to do it for trade receivables. The method applies a higher loss rate to each older bucket. Rates should come from your own collection history, adjusted for current conditions. The rates below are illustrative only.
| Bucket | Balance ($) | Illustrative loss rate | Estimated loss ($) |
|---|---|---|---|
| Current | 11,500 | 1% | 115 |
| 1–30 | 5,500 | 3% | 165 |
| 31–60 | 3,200 | 10% | 320 |
| 61–90 | 1,000 | 25% | 250 |
| 90+ | 3,000 | 50% | 1,500 |
| Total | 24,200 | - | 2,350 |
In this example, the 90+ bucket holds 12.4% of the balance but 64% of the estimated loss. That is why moving even a small amount out of the oldest bucket has an outsized effect. For the accounting entries, see allowance for doubtful accounts and the aging of accounts receivable method.
The aging report is the data: balances by customer and bucket on a given date. Aging analysis is what you do with it. Analysis means comparing reports over time, looking for customers whose balances are shifting older, checking whether a particular sales region or product line produces more late invoices, and deciding whether credit terms or the collection process need to change.
A team that only produces the report sees where things stand. A team that analyzes it sees where things are heading.
Many teams still build or adjust aging reports in spreadsheets exported from the ERP. The report is only as accurate as the data behind it, and these problems come up again and again:
An aging report tells you how old a balance is. It does not tell you:
A 75-day balance from a long-standing customer with a documented pricing dispute is a very different problem from a 75-day balance from a new customer who has stopped answering. Aging data works best alongside payment history, dispute status, credit information, and collection notes. Keep the report as the starting point, not the full picture.
Most of the problems above come from the report and the underlying activity living in different places. AR automation software addresses this by keeping invoices, payments, and collection activity in one system. Depending on the tool, that can mean applying incoming payments to invoices automatically, flagging balances as they cross into older buckets, triggering reminder workflows by bucket, and recording disputes and promises to pay against the invoice they relate to.
The practical result is an aging view that reflects what has actually happened, without someone rebuilding a spreadsheet first.
Quick Receivable is one example. It is an accounts receivable automation platform built on Salesforce, so aging data and collection activity sit in the same CRM that sales and account teams already use. That helps when an overdue balance needs the account owner involved. You can see how it handles aging specifically on our AR aging report software page.
An accounts receivable aging report is simple to produce and easy to misread. Used well, it tells your team which balances to collect first, which customers are changing their payment behavior, how much bad debt to reserve, and how much cash you can realistically expect next month.
A practical checklist to take away:
40%
DSO reduction70%
less manual work95%
cash match accuracyFind out exactly how much time and money your AR team can save with Quick Receivable. No commitment, no setup required.
AI-powered Accounts Receivable Automation on Salesforce, built to accelerate collections, automate workflows, and improve cash flow.