Accounts Receivable Aging Report: What Each Bucket Means and What to Do
The accounts receivable aging report is not a status update, it's a work queue. Here's what each bucket means, what to do at each stage, and what the report can never tell you.

Run the accounts receivable aging report and the first thing you feel is the size of the number at the bottom. That's the wrong number to stare at. The report's real value isn't the total, it's the way that total splits into buckets by how overdue each invoice is, and each bucket is telling you to do something different.
Most finance teams read it like a status update: here's what we're owed, moving on. Some call it the AR aging report, others just 'the aging report', same document either way. Treated as a status update, it's anxiety with a spreadsheet attached. Treated as a work queue, it tells you which invoices need a gentle reminder, which need a phone call, and which need someone to stop being polite about it.
This walks through what each bucket on an accounts receivable aging report actually means, what to do at each stage, a worked example that reconciles to the dollar, and the things the report will never tell you, however carefully you read it.

Your aging report is a work queue, not a scoreboard
An accounts receivable aging report takes every open invoice and sorts it into a column based on how many days past its due date it sits: current, 1 to 30, 31 to 60, 61 to 90, and 90 plus. That's the entire mechanism. No judgment involved, just a due date compared against today's date.
The reason it's worth more than the total AR figure is that a $200,000 balance sitting entirely in the current bucket is a healthy business. The same $200,000 with half of it past 90 days is a business quietly losing a chunk of it. Same total, completely different problem, and the aging report is the one standard report that shows you which one you're looking at.
Read it as a queue and the next move for each bucket becomes obvious, which is the point of the rest of this piece.
What each aging bucket means, and what to do there
Every accounts receivable aging report breaks down the same five ways, and each bucket calls for a different kind of attention. Some need nothing but visibility. Others need a phone call today.
| Bucket | Days overdue | What it usually means | What to do |
|---|---|---|---|
| Current | Not yet due | Paying on schedule | Nothing to chase. Confirm it was sent and received. |
| 1-30 | 1 to 30 days | Just slipped past terms, usually an oversight | Automatic, on-brand reminder |
| 31-60 | 31 to 60 days | The reminder didn't land, or something's off | A specific note naming the invoice and amount |
| 61-90 | 61 to 90 days | A real collections case now | A phone call and a commitment: a date or a partial payment |
| 90+ | 90 days or more | Likely a dispute, a cash problem, or a lapsed customer | A decision: negotiate, escalate, or write off |
The buckets get more serious as they age, but the jump that matters most is between 31-60 and 61-90. Before that line, most of what you're looking at is a process gap: a reminder that never went out, an email that landed in spam. After it, you're usually looking at either a dispute nobody escalated, or a customer who has decided you aren't the payment they prioritize this month.
A typical business rarely sees its balance spread evenly across the five buckets. Most of it sits current or barely late, and a shrinking share sits further out, which is exactly the shape you want. It's worth checking your own spread against that pattern the same way you'd check your own numbers against the DSO calculator.
That's an illustration of a healthy-shaped report, not a benchmark to hit exactly. What matters is the slope: current and 1-30 should hold most of the weight, and 90+ should be the smallest bar, not a growing one.
How to work an accounts receivable aging report, step by step
Working the report is the same five moves every time, run in bucket order from oldest to newest so the invoices closest to becoming a write-off get looked at first.
- Start at 90+. Pull every invoice in the oldest bucket first and decide, invoice by invoice, whether it's a dispute, a real cash problem, or simply forgotten. That decision changes everything that happens next.
- Resolve disputes before chasing them. Any invoice sitting in 61-90 or 90+ because of a disputed amount needs someone to settle the dispute, not another reminder about a total the customer doesn't agree with.
- Call the 61-90 bucket. A phone call, not another email. The customer already knows the invoice is late, so the goal is a commitment: a date, a partial payment, or an honest reason it's stuck.
- Send a targeted reminder for 31-60. These are usually process gaps rather than disputes, so a specific note referencing the invoice number and amount clears most of them without a call.
- Automate the 1-30 bucket. A polite, on-brand reminder the moment an invoice crosses its due date catches most late payments before they turn into a real problem.
- Recheck current. Nothing to chase yet, but confirm the invoice actually went out and the customer received it. A current invoice that never arrived quietly becomes a 90+ invoice with no warning at all.
A worked example: one customer's balance, broken into buckets
Say a customer, Ferrow Logistics, owes you $23,100 across four open invoices. The aging report doesn't show you one number, it shows you four, each in a different bucket, and the mix changes what you do next.
| Invoice | Amount | Days overdue | Bucket |
|---|---|---|---|
| INV-1042 | $4,200 | 12 | 1-30 |
| INV-1031 | $6,500 | 38 | 31-60 |
| INV-1019 | $2,800 | 74 | 61-90 |
| INV-0987 | $9,600 | 118 | 90+ |
| Total owed | $23,100 | n/a | n/a |
Two of the four invoices are fine where they sit. The 1-30 one just needs the automatic reminder it's probably already getting, and the 31-60 one is due a targeted note. The 61-90 invoice needs a call this week.
The 90+ invoice needs a decision today: is $9,600 a dispute, a cash-strapped customer, or a write-off in progress. Add the four rows and you get the $23,100 the printed statement shows, and now you know which part of that total is actually at risk rather than just late.
What the aging report cannot tell you
An accounts receivable aging report is a snapshot taken at the moment you ran it, not a living view. Run it Monday and a customer who paid Tuesday still shows up overdue until someone reconciles it. Treat the number as true for the day you pulled it, not the day you act on it.
It also has no idea why an invoice is late. A disputed line item, a customer waiting on their own client to pay, an invoice that never arrived, and a customer who has simply decided not to pay, all land in the same bucket if they're the same number of days old. The bucket tells you urgency. It never tells you cause.
| What the report tells you | What it doesn't tell you |
|---|---|
| How much is overdue, and for how long | Why it's overdue |
| Which invoices need attention first | Whether anyone has already called about it |
| Total exposure right now | Whether that exposure is trending up or down |
| That a bucket is full or empty | Whether a payment already happened and just hasn't reconciled yet |
None of that makes the report useless, it makes it a starting point. The report tells you where to look. What happens next, the call, the escalation, the payment plan, is a separate job that has to happen consistently or the buckets refill as fast as you clear them.

Why the buckets pile up even when everyone means well
Chasing invoices is rarely nobody's job. It's usually somebody's fourth job, wedged between the tasks with actual deadlines. An aging report doesn't create urgency on its own, and a bucket someone means to get to on Friday has a way of still being there the next Friday.
According to the Atradius Payment Practices Barometer for North America (2025), 43% of credit-based B2B sales in the US are overdue at any given time. Most of that 43% is not a customer refusing to pay. It's a reminder that didn't go out, or went out once and stopped.
That's exactly the shape of work the invoice chase agent exists for: something that reads the aging report the same way, follows up on every bucket at the right moment, escalates when a customer goes quiet, and stops the second a payment lands, so the buckets get worked every single week instead of whenever someone finds an afternoon free.
See what your slow buckets are costing you
Turn your own receivables and credit sales into a dollar figure before you decide how much attention the aging report deserves. Free, no signup, nothing leaves your browser.
Use the DSO calculatorIf you want to see what the manual version of that work costs across a year, not just this week's overdue calls, the labor cost calculator turns those hours into a dollar figure too. It's the same production discipline behind our shipped work, applied to chasing money instead of chasing tasks.
Frequently asked questions
The bottom line
An accounts receivable aging report isn't a scoreboard to glance at and close. It's a queue with five lanes, and each one is telling you exactly what to do next: watch, remind, call, escalate, or decide.
The mechanics are simple. What's hard is doing it every single week, for every invoice, without letting the oldest ones sit because something more urgent came up. That's a consistency problem, not a strategy problem, and it's exactly what falls apart first when the work depends on someone remembering.
Ready to stop working the aging report by hand?
Bring your aging report to a 30-minute call. We'll show you what an agent that chases every bucket automatically, and stops the second an invoice is paid, would actually do with it.
Book a 30-min callGet one sharp idea on shipping AI, no hype, no spam
The occasional deep-dive on what actually works when you put AI into a real business. Written for owners and operators, not engineers.



