AR aging buckets explained: 30/60/90 and what to do with them

Total accounts receivable is a single number that hides everything worth knowing. Two companies can both report $2,000,000 of AR: one where 90% is not yet due, and one where a third of it is more than 60 days late. The aging report exists to tell those two apart, and the buckets are how it does it.

AR aging bucket

A band of days used to group open receivables by how long each invoice has been outstanding past its due date. The conventional bands are current (not yet due), 1–30, 31–60, 61–90 and 90+ days past due, and each band carries a different probability of being collected.

Why 30, 60 and 90 days?

The bands are conventional rather than statistical. Thirty-day steps line up with monthly close, with net-30 terms, and with the natural rhythm of a customer's own payment run — an invoice that misses one AP cycle typically slips a whole month, not four days. They also map onto escalation stages: reminder, statement, credit hold, third party.

That convention breaks in two situations. If your terms are net 45 or net 60, a 30-day grid straddles the boundary between "not yet due" and "late" inside a single bucket. And if your escalation ladder fires at 7, 14 and 30 days, a first bucket 30 days wide hides the accounts you were about to escalate. In both cases, design buckets around your ladder — 1–15, 16–30, 31–60, 61–90, 90+ works well — and keep them stable so the trend stays readable.

A real aging distribution

Here is a $2,000,000 ledger for a distributor on net-30 terms, monthly credit sales of $1,300,000, aged by days past due date.

Before reading anything into the mix, check it against terms. With $1,300,000 of monthly credit sales, DSO here is ($2,000,000 ÷ $1,300,000) × 30 = 46.2 days on net-30 terms, so customers are running about 16 days beyond terms. The bucket mix now tells you where those 16 days live — and the answer is the 1–30 bucket, not the tail. Recover the DSO figure first; it frames everything below.

Weighted average days overdue

The mix is five numbers. Sometimes you need one. Weighted average days overdue collapses the distribution by assigning each bucket a representative day count — its midpoint — and weighting by balance.

Midpoints used: current = 0, 1–30 = 15, 31–60 = 45, 61–90 = 75, 90+ = 120

Weighted days =    420,000 × 15 =  6,300,000
                +  186,000 × 45 =  8,370,000
                +   94,000 × 75 =  7,050,000
                +   60,000 × 120 = 7,200,000
                = 28,920,000 dollar-days

Now pick a denominator, and this is where teams talk past each other.

Across the whole ledger:  28,920,000 ÷ 2,000,000 = 14.5 days
Across overdue balances:  28,920,000 ÷   760,000 = 38.1 days

Both are legitimate. The whole-ledger figure (14.5 days) answers how late is our receivables book on average, and it moves whenever sales volume moves. The overdue-only figure (38.1 days) answers when something is late, how late is it, and it isolates collection difficulty from sales volume. Use the overdue-only version to judge the collections function, publish the definition next to the number, and never switch mid-year.

Turning buckets into a bad debt reserve

The aging method for reserves applies an expected loss rate to each bucket. Loss rates should come from your own history — take the invoices that entered each bucket two or three years ago and measure what fraction was eventually written off. Failing that, start with rates like these and correct them annually.

Two observations. The 61–90 and 90+ buckets together are $154,000 — 7.7% of the ledger — but they carry $38,100 of reserve, which is 65.9% of the total. That ratio is the argument for where a collector's Tuesday should go.

Second, compare against the flat percentage-of-sales method: 0.4% of $15,600,000 of annual credit sales gives $62,400, close to the $57,800 the aging method produced. They often land near each other in a stable year, which is why people default to the simpler one. The difference shows up when the mix deteriorates: shift $100,000 from current into 90+ and the aging reserve rises by $39,500 while the sales-based reserve does not move at all. The bad debt reserve calculator runs both methods side by side.

Working the report by value, not by date

The default aging report sorts oldest first. It feels rigorous and it is a bad use of your best collector. Sorting by age puts a $1,200 invoice that is 95 days old ahead of a $214,000 invoice that is 22 days overdue. Sort by amount, either overall or within each bucket.

Five calls cover $491,000 of the $760,000 overdue. Note that the largest single exposure sits in the youngest overdue bucket, which an age-sorted report would show on page four. Work value first, then age, then set a de minimis threshold — below perhaps $500, an automated reminder ladder is cheaper than a human, and the rest of the DSO lever list applies.

Five things that make an aging report lie

• Aged by invoice date instead of due date. On net-30 terms this shifts every balance a full term to the right: an invoice 15 days overdue appears in the 31–60 bucket, and invoices that are not due at all appear in 1–30. Check which basis your report uses before you interpret a single number. Most ERPs offer both, and the default is not always the one you want.
• Unapplied cash. A $40,000 receipt sitting unmatched leaves a $40,000 invoice ageing in 31–60 while the money is already in your bank. Unapplied cash over five days old belongs on a daily report, not in the month-end clean-up.
• Unapplied credit memos. These net against the current bucket and quietly reduce the overdue percentage. If the aging total reconciles to the GL but the current bucket looks too big, look for credits with no invoice attached.
• Disputes mixed in with slow payers. A queried invoice is not ageing, it is waiting. Flag disputes and report them as a separate line, because chasing them harder does nothing and the fix lives in billing.
• Partial payments and invoice-level versus balance-level aging. A $100,000 invoice with $90,000 paid should age $10,000, not $100,000. Some reports age the whole invoice at its original date. That single behaviour can double your apparent tail.

What to watch weekly

The aging report is a monthly artefact, but three numbers derived from it are worth watching weekly, because they move before DSO does: overdue value by bucket, count of disputed invoices with their total value, and unapplied cash older than five days. Add collection effectiveness index monthly — it grades the collections team without punishing them for a sales spike, which the aging mix cannot do on its own.

Getting the buckets right in your ERP

Standard aging reports are usually the fastest thing to get and the hardest thing to trust: fixed buckets, aging basis buried in a preference, credit memos handled inconsistently, and multi-subsidiary consolidation that silently changes the answer. Rebuilding it properly means a saved search per bucket or a formula field per band, and it breaks the first time somebody adds a payment term. Running the AR aging report in NetSuite walks the specifics.

Ask ERPray "show our AR aged by due date in 15-day buckets, excluding disputed invoices, with the top 10 overdue customers by value" and you get the answer computed live from your own account, with the query shown underneath so you can verify the aging basis instead of hoping. Read-only by default.