AR aging analysis: how to read it and act on it

AR aging analysis sorts your open receivables by how long each invoice has been outstanding, so you can see where collection risk is building and decide which accounts to chase first. It turns one big receivables balance into a ranked list of where cash is stuck and how likely you are to get it back.

The report is the most operational metric in accounts receivable. Where days sales outstanding summarizes how slow collections are overall, the aging analysis tells you exactly which invoices are causing it and what to do next.

What an AR aging report shows

An aging report lists every open invoice and groups it by age. The columns are the aging buckets, the rows are usually customers, and each cell holds the balance that customer owes in that age band.

A typical layout looks like this:

Read across a row to see one customer's risk profile. Read down a column to see how much of your whole book sits in each band.

How to read aging buckets

Each bucket carries a different meaning and a different action.

• Current. Not yet due. Nothing is wrong, but pre-due reminders here prevent invoices from slipping into the past-due columns.
• 1-30 days past due. Recently late. Usually an oversight, a missed invoice, or a slow approval. A prompt nudge collects most of this.
• 31-60 days. A pattern is forming. The customer is either disputing, short of cash, or deprioritizing you. This needs a direct ask, not another soft reminder.
• 61-90 days. At real risk. Escalate to a manager or a firmer notice, and find out what is actually blocking payment.
• 90-plus days. The danger zone. Collection odds drop sharply here, and a chunk of this becomes a write-off if it sits.

The rule of thumb most credit teams use: the probability of collecting in full falls roughly with each bucket an invoice crosses. An invoice at 90-plus days is far less likely to be paid in full than one at 30, which is why moving accounts out of the older bands is the whole point of the exercise.

Spotting risk and root causes

The dollar totals are only half the analysis. The share of your book in each bucket is what tells you whether the ledger is healthy.

Add up each column as a percentage of total receivables. A healthy book keeps the large majority current and the 90-plus band thin, often under 5 percent. When the older buckets swell, you have a problem that a single number like DSO will only confirm later.

Then look for the why. Concentration is the first thing to check: is one or two large accounts driving the 90-plus balance, or is lateness spread across many customers? A few big overdue invoices is a relationship problem you solve with a phone call. Broad slippage is a process problem, usually weak follow-up or unclear terms.

Disputes and deductions are the other common cause. An invoice can age not because the customer is broke but because something is contested. If old balances cluster around the same customers or the same charge types, the issue is unresolved disputes, not unwillingness to pay. Tracking days deductions outstanding alongside aging separates the two.

It also helps to watch the migration rate, the share of balances that roll from one bucket into the next each period. A book can look stable on a single report and still be deteriorating if 20 percent of the current balance is rolling into past-due every month. The migration rate is the leading edge of a rising DSO, visible weeks before the headline number moves. A healthy ledger collects most of what is due before it ages a bucket; a struggling one watches the same dollars slide one column to the right month after month.

Compare the aging against your terms, too. A 30-day-old invoice on net-15 terms is twice as overdue as the same invoice on net-30, but a raw aging report buckets them identically. Reading the buckets relative to each customer's terms, rather than a single calendar, keeps you from treating a serious slip and a routine one the same way.

From analysis to a prioritized action list

The point of aging analysis is not the report, it is the worklist it produces. Sort by impact, not just by age.

A simple way to prioritize:

1. Large balances in the 31-60 band. Highest expected value. They are big, they are slipping, and they are still recoverable. Work these first.
2. Anything new in 61-90. Catch accounts as they cross the line, before they reach the danger zone.
3. 90-plus that is still responsive. Worth a firm, escalated effort while there is a relationship to lean on.
4. Small current balances. Low priority for active chasing; automated reminders handle these.

The mistake teams make is working the report top to bottom alphabetically, or only chasing the oldest invoices because they look the most urgent. The oldest invoices are often the least collectible. The money is usually in the accounts that are sliding now and can still be saved.

Layer customer history on top of the dollar amount. A large balance from a customer who always pays around 10 days late and has never missed needs a light touch, not an escalation. The same balance from an account that has gone quiet, broken a prior promise, or started disputing every invoice is a different risk and deserves to jump the queue. The number on the report is the starting point; the customer's pattern is what tells you how hard to push and how soon.

The limits of a static aging report

A spreadsheet aging report has a built-in flaw: it is out of date the moment you export it. An invoice that was current on Monday is 31 days past due by the next review, but nobody touched it because the report was run last week.

The buckets also hide intent. The report tells you an invoice is 45 days late. It does not tell you the customer already promised to pay Friday, or that the balance is short by exactly the amount of a disputed line. Acting on the snapshot alone means re-chasing customers who already committed and ignoring the disputes that froze the balance in the first place.

And the report does nothing on its own. It surfaces the work, but a person still has to read it, decide, draft the message, send it, and remember to follow up. Between a hundred-line aging report and a small team, most accounts get a generic reminder or no contact at all until they are badly overdue.

Automating aging-driven outreach

This is where an agentic AR system changes the model. Rex does not produce an aging report for someone to work. It treats the aging as a live worklist and acts on it continuously, the moment an invoice crosses a threshold rather than whenever the next review happens.

Rex reads every open invoice against its due date, its history, and any promise to pay or dispute on file, then decides the next-best action per account: a pre-due nudge here, a firm escalation there, nothing at all for the customer who already committed to Friday. It works the whole ledger this way at once, not just the dozen accounts a collector had time for, and it routes the genuine judgment calls, like a large disputed balance or a broken promise, to a person. The aging analysis stops being a weekly snapshot you react to and becomes a process that keeps the older buckets thin on its own.

See how Rex works your aging report end to end, the moment invoices start to slip.