An accounts receivable aging report is a financial report that lists every unpaid customer invoice and groups it into date ranges based on how overdue each balance is. It gives finance teams a snapshot of total receivables exposure, broken down by customer and by age, so leadership can read collection risk at a glance.
A standard aging report sorts every open invoice into these buckets, and each one carries a different signal:
- Current. Not yet due. Confirm receipt only.
- 1 to 30 days past due. The early-warning zone. Watch for repeat offenders.
- 31 to 60 days past due. A specific blocker is usually holding payment. Diagnose, do not just remind.
- 61 to 90 days past due. Real collection risk, with recovery odds falling each week.
- 90+ days past due. The write-off and bad-debt-reserve threshold. Some businesses add a 120+ bucket for chronic delinquencies.
Table of Contents
What Accounts Receivable Aging Report tells you, and what it hides
The aging report tells you who owes money and how late they are. It does not tell you why they have not paid. That gap between “how old” and “why stuck” is where cash goes to die.
Most finance teams run the report, sort by dollar amount, and start calling the biggest balances first. The calls go out. The tone escalates. And the invoice that sat in someone’s AP queue because of a wrong PO number stays stuck for another 30 days. This guide teaches you how to read the report, then read past it to the operational blocker behind every overdue line. It is the single most referenced document in any collections conversation, and on its own it is only half the picture.
The formula and a worked example
The aging calculation starts at the invoice due date, not the invoice date. Subtract the due date from today’s date. The result is the number of days past due, and that number determines the bucket.
Say you invoiced a customer on April 1 with Net 30 terms. The due date is May 1. On June 15, that invoice is 45 days past due and lands in the 31 to 60 bucket. If you mistakenly calculate from the invoice date instead of the due date, you get 75 days and place it in the 61 to 90 bucket. That single error distorts collection priority and bad-debt estimates at the same time.
| Customer | Invoice # | Due date | Amount | Current | 1-30 | 31-60 | 61-90 | 90+ |
|---|---|---|---|---|---|---|---|---|
| Acme Logistics | 1042 | May 1 | $18,000 | $18,000 | ||||
| Acme Logistics | 1078 | June 5 | $6,500 | $6,500 | ||||
| Redline Mfg | 1019 | Mar 10 | $42,000 | $42,000 | ||||
| Coastal Health | 1055 | May 20 | $11,200 | $11,200 |
Read the table left to right for each customer. Acme Logistics has two open invoices across two buckets. Redline Mfg has one invoice sitting at 90+ days. The dollar concentration in a single bucket and a single customer tells you where collection risk clusters.
How to read each aging bucket and what it signals
The buckets are not just time slices. Each one carries a different operational signal, and treating them the same flattens real information into noise.
Current and 1 to 30 days past due
Current invoices need no action beyond confirming they were received. The 1 to 30 bucket is your early-warning zone. A large share of invoices here is normal. The signal to watch is repeat offenders: the same customer showing up in this bucket month after month. That pattern points to a process issue on their side or yours, not a credit problem.
31 to 60 days past due
At this stage, something specific is blocking payment. A missing approval, a disputed line item, an invoice routed to the wrong AP contact. Dollars in this bucket deserve a diagnosis, not just a reminder. Sending a second copy of the invoice solves nothing if the original was rejected for a PO mismatch.
61 to 90 days and beyond
Invoices at 61+ days represent real collection risk. The probability of full recovery drops with every week. At 90+ days, you face a decision: escalate formally, negotiate a partial settlement, or reserve for bad debt. The 90+ bucket is also where gaming shows up, but more on that below.
The point is straightforward. Each bucket answers a different question. Current asks “did they get it?” The 31 to 60 bucket asks “what went wrong?” And 90+ asks “can we still recover this?”
Common mistakes that distort the report
The aging report is only as honest as the data feeding it. Three errors show up repeatedly in finance teams that rely on the report without questioning it.
Using invoice date instead of due date
This is the most common mechanical error. If your system ages from invoice date, every invoice looks older than it is. A Net 60 invoice dated January 1 and due March 1 appears 60 days old on the report the day it is issued. Collection teams chase invoices that are not even due yet. The fix is a one-time configuration change in your ERP or accounting system.
Ignoring unapplied credits and disputes
A customer disputes a $5,000 line on a $50,000 invoice. The full $50,000 shows as overdue. Your team escalates on the full amount. The customer, who was ready to pay the undisputed $45,000, now digs in on the whole thing. Unapplied credits create the same distortion. The report shows a balance that does not reflect reality, and collection actions based on that balance damage the relationship.
Treating age as the only sort dimension
This is the habit that costs the most cash. Finance teams sort by age, then by dollar amount, and start calling. The assumption is that old plus large equals urgent. But a $200,000 invoice at 35 days past due because of a missing approval signature is a different problem than a $200,000 invoice at 35 days because the customer is insolvent. Age tells you the symptom. It does not tell you the disease.
Turn the report into action: sort by reason, not just age
Here is the shift that separates teams who run aging reports from teams who actually collect. After you pull the report, add a column. Call it “blocker” or “reason code.” For every overdue invoice, identify the specific operational cause.
Common blocker categories
- Wrong PO number. The invoice references a PO the customer’s AP system does not recognize. Payment will not release until the PO matches.
- Disputed line item. The customer contests a charge or a rate. The dispute freezes the entire invoice in most AP workflows.
- Missing receiving confirmation. The customer’s system requires a goods-received note before AP processes payment. If delivery was not logged, the invoice sits.
- Wrong AP contact. The invoice went to a general inbox or a person who left the company. Nobody with authority to approve has seen it.
- Approval bottleneck. The invoice is approved at one level but waiting on a second signature from someone on vacation or buried in a queue.
Once you tag each overdue invoice by reason, the action plan changes completely. PO mismatches need a corrected invoice, not a reminder. Disputes need a conversation about the contested line, not a demand for full payment. Wrong-contact issues need a five-minute phone call to the right person.
Prioritize by fixability, not just size
A $12,000 invoice stuck on a PO mismatch is a 15-minute fix. A $120,000 invoice tied to a contract dispute requires legal review. If your team spends the morning on the $120,000 dispute and ignores the $12,000 PO fix, you left easy money on the table. Sort the tagged invoices by how quickly the blocker can be resolved. Fix the fast ones first. That approach moves more cash per hour of effort than chasing the biggest numbers.
The relationship cost of tone-deaf escalation
A loyal customer who pays $500,000 a year and has one invoice stuck at 45 days because of a receiving confirmation issue does not deserve the same escalation tone as a customer with three invoices at 90+ days and no communication. But a report sorted only by age and amount treats them identically.
Aggressive collection language sent to a relationship account creates a cost that never shows up on the aging report. The customer pays the invoice and then quietly shifts new business to a competitor. You collected $30,000 and lost $500,000 in future revenue. The report went green. The business went backward.
The fix is context. Before sending any collection communication, check the account history and the blocker reason. A well-structured AR workflow drafts the right message based on the reason code and the relationship tier, then queues it for a human to review before it reaches the customer. The human decides. The system handles the drafting and routing.
DSO and the aging report: two views of the same cash
Days sales outstanding (DSO) tells you the average number of days it takes to collect after a sale. The aging report shows you the specific invoices driving that number. They are two views of the same thing, and reading one without the other gives you an incomplete picture.
What good DSO looks like
A useful benchmark: good DSO runs at about 1.5x your payment terms. On Net 30, that means roughly 45 days. Enterprise reality often sits at 65+ days because approval chains and procurement workflows add lag that has nothing to do with willingness to pay. As a general reference point, Investopedia notes a DSO under 45 days is considered good for most businesses, though the right target always depends on your terms and industry.
Read DSO inside the full cash conversion cycle. DSO alone does not tell you whether your cash runway is healthy or eroding. Founders and owner-operators often describe DSO as “days to get paid.” That framing is fine. The metric is the same regardless of what you call it.
How DSO gets gamed and how the aging report shows it
DSO becomes a vanity metric when it is managed for optics instead of cash. Two common moves inflate the appearance of collection health without moving real money.
First, “refreshing” an old invoice. A 90-day invoice gets re-issued with a new date. It drops from the 90+ bucket into Current. DSO improves on paper. Cash stays trapped. Second, aggressive write-offs. Writing off stubborn balances clears the 90+ bucket and lowers DSO. The income statement takes the hit, but the AR report looks clean for the board deck.
A report sorted by age and dollar amount cannot catch either move. The buckets reset, the totals shift, and the story changes without a single dollar arriving in the bank account. A report sorted by reason exposes both patterns. The refreshed invoice still carries the original blocker. The written-off balance still had an unresolved dispute. Reason codes create an audit trail that age buckets alone cannot provide.
This is why reducing DSO requires fixing the causes behind overdue invoices, not just managing the metric. The sibling guide on how to reduce your DSO covers that playbook in full.
How clearing overdue accounts extends cash runway
Every dollar sitting in an aging bucket is a dollar your business cannot deploy. It cannot cover payroll or fund inventory. The aging report quantifies that trapped cash. Acting on the report converts it from a status document into a cash-recovery tool.
This is not a small problem. In Intuit QuickBooks’ 2025 US Small Business Late Payments Report, over half of small businesses were owed money on unpaid invoices, an average of $17,500 each, and those most affected were 1.4x more likely to report cash flow problems. The aging report is where that trapped cash becomes visible and recoverable.
Consider a business with $400,000 in receivables past 30 days. Tagging each invoice by blocker reason reveals that $180,000 is stuck on administrative errors: wrong PO numbers and invoices sent to departed employees. Those are fixable within days, not weeks. Resolving them pulls $180,000 into the operating account and extends cash runway by the equivalent number of operating days that money covers. That recovered cash flows straight into your Live Cash Runway.
The remaining $220,000 breaks down into active disputes, slow-paying enterprise accounts with long approval chains, and a small segment of genuine credit risk. Each category needs a different response. Disputes need negotiation. Enterprise accounts need patience and relationship management. Credit risk accounts need formal escalation or reserve decisions.
The aging report, read through the reason lens, gives you the sequencing. Fix the administrative errors this week. Open dispute conversations next week. Adjust credit terms for chronic risk accounts at the next review cycle.
Reading past the buckets with operational context
The limitation of a static aging report is structural. The report lives in your accounting system. The reasons invoices are stuck live somewhere else: in your order management system, your delivery records, your email threads, your customer’s AP portal.
Bridging that gap manually means pulling up the ERP, cross-referencing the delivery log, checking email for dispute notes, and calling the customer to ask what happened. For five overdue invoices, that process is manageable. For 500, it breaks down.
Reading the report against operational truth is what a live ontology makes possible. Truzer connects the systems receivables live in (ERP, billing, order and delivery records) and surfaces why a specific invoice is stuck so finance can fix the cause instead of sending another reminder. It drafts the right next step and queues it for a human to approve. The ontology is the digital twin. Same thing. The broader accounts receivable management process sits on top of that same live model.
The principle holds regardless of what tools you use. An aging report that only answers “how old” forces your team into a guessing game about “why.” Adding the reason layer turns guessing into diagnosis. Diagnosis leads to action. Action moves cash. For teams evaluating tooling, the sibling guide on AR automation software covers what separates a tool that just sends reminders from one that knows the operational context.
The report is a starting line, not a finish line
An accounts receivable aging report does exactly what it was designed to do: sort unpaid invoices by time. That is valuable. It shows exposure, flags risk, and gives leadership a snapshot of collection health.
Where teams lose cash is in treating that snapshot as the whole picture. The buckets tell you who is late. The reason behind each stuck invoice tells you what to do about it. One is a report. The other is a collection strategy.
Pull the report weekly. Tag every overdue invoice with a blocker reason. Sort by fixability. Match your tone to the relationship. And track whether your DSO improvements come from real cash arriving or from cosmetic adjustments to the buckets. That discipline turns the aging report from a status document into the most direct path between your receivables and your bank account.
Try Truzer or Book a call
