← Back to blog

Accounts Receivable Aging Report: How to Read One (and What It's Telling You)

July 15, 2026

An accounts receivable aging report groups unpaid invoices by how long they've been outstanding — typically current, 1–30, 31–60, 61–90, and 90+ days — so you can see not just how much you're owed, but how overdue it is and where collection risk is concentrated.

It's one of the most useful reports finance produces and one of the least read outside finance, mostly because the raw version is a wall of invoice numbers rather than a story.

What each bucket actually means

Current. Invoices not yet past their due date. This is expected AR and not a concern on its own.

1–30 days past due. Mildly late. Often just a slow-paying customer or an invoice that got stuck in someone's approval queue — normal in most businesses.

31–60 days past due. Worth a follow-up if it isn't already happening. At this point it's no longer "probably fine," it's a specific invoice that needs a specific person chasing it.

61–90 days past due. This is where collection risk starts becoming real. A customer this late is either having cash flow trouble of their own or disputing something about the invoice — either way, it needs a direct conversation, not another automated reminder.

90+ days past due. The bucket most likely to become a bad debt write-off. Every invoice here should have a clear next step and a named owner, not just a balance.

What healthy looks like

There's no universal benchmark, but the general shape to look for is a heavy concentration in "current" and a sharp drop-off after 30 days. A rough distribution like 70% current, 20% in 1–30, and single digits everywhere past that is common for businesses with reasonable collections discipline. What you don't want is a flat or growing distribution across the older buckets — that's a sign invoices are aging instead of resolving.

The trend matters more than the snapshot

A single aging report tells you today's exposure. Watching it month over month tells you whether collections are improving or slipping. If the 90+ bucket has been quietly growing for three months straight, that's a materially different story than a one-time spike from a single large invoice — and it's a distinction a raw export won't show you unless someone's actively comparing periods.

Turning it into something a non-finance exec can act on

The report itself is built for finance. What a CEO or board member actually needs is the summary version: total AR, what percentage is current vs. at-risk, which specific accounts make up the bulk of the 60+ balance, and whether that's trending better or worse than last period. That reframing — from a ledger to a narrative — is usually the missing step between "we have this data" and "leadership actually uses it."

FAQ

What's a good DSO (days sales outstanding) benchmark? It varies heavily by industry, but many B2B companies target 30–45 days. The more useful number is usually your own trend over time rather than an external benchmark.

How often should an AR aging report be reviewed? Monthly at minimum for leadership visibility; weekly internally within finance/collections if overdue balances are a recurring issue.

Is a large 90+ balance always bad? Not always — a single disputed enterprise invoice can distort the bucket without reflecting a broader problem. The context (which accounts, why) matters as much as the total.

Where this gets easier

An AR aging export is exactly the kind of spreadsheet ReportSync is built to turn into something shareable: upload it and get the current-vs-at-risk breakdown, period-over-period trend charts, and an AI-written summary highlighting which buckets moved and why — as a live link or a PDF/PPTX for your next update. Free to try on two real reports.

The numbers in an AR aging report don't change by looking at them differently. But how quickly someone notices a problem often does.