What is an AR aging report and how do I read it?

An AR aging report lists every open invoice grouped by how long it's been outstanding — current, 1-30, 31-60, 61-90, and 90+ days past due. Read it by tracking the bucket distribution over time, not just the total; a shrinking current bucket and growing 90+ bucket signal a collections problem before it shows up in a blended DSO figure.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 10, 2026Last reviewed September 10, 2026Editorial policy

Part of the accounts receivable and collections guide.

Standard aging buckets	Current, 1-30, 31-60, 61-90, 90+ days past due
What it's grouped by	Customer and invoice, with amount and due date
What to track over time	The bucket distribution trend, not just the total AR balance
Most common data-quality issue	A customer record or credit memo that didn't sync to the report's source system

What's actually on the report

Each row is an open invoice: customer name, invoice number, amount, due date, and days past due, which places it into one of the standard aging buckets. The report totals both by customer (how much a given customer owes across all their open invoices) and by bucket (how much total AR sits in each aging category), which is what makes it useful for two different jobs at once — collections prioritization by customer, and portfolio health assessment by bucket.

Reading it for portfolio health

A single month's snapshot tells you less than the trend across several months. If current and 1-30 hold steady as a share of total AR while 61-90 and 90-plus grow, that's the earliest reliable signal of a developing problem — a specific customer sliding toward non-payment, or a systemic issue like a credit policy that's stopped matching how customers are actually behaving. Because DSO is a single blended number, it can stay roughly flat even while a small, worsening pocket of the portfolio is quietly heading toward write-off.

When the report doesn't tie to the general ledger

The aging report's total should equal the AR balance on the general ledger. When it doesn't, the most common causes, in order, are: a payment applied to the wrong invoice, making one account look overdue and another look paid when neither is accurate; a customer record change (a merged duplicate, an address update) that didn't sync between the system generating invoices and the system the aging report pulls from, orphaning invoices from the correct customer total; and a credit memo or dispute resolved in a support tool but never reflected back in the AR subledger, leaving a balance the customer has already been told they don't owe.

Using it to forecast collections

A simple forecast applies each bucket's typical collection rate to its current balance: current and 1-30 day balances collect at a high rate, historically close to full value for most portfolios; 31-60 somewhat lower; and 90-plus meaningfully lower, reflecting the real risk that a portion never gets collected at all. Applying a company's own historical collection rates per bucket, rather than a generic industry assumption, produces a forecast that's specific to how that company's actual customers behave.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Worked example

Two customers, same total, different risk

Customer A owes $50,000, all of it current (not yet due). Customer B also owes $50,000, but $35,000 of it is over 90 days past due. Both show the same total on a customer-balance summary, but the aging report reveals completely different risk profiles: Customer A is a healthy, on-time account, while Customer B has $35,000 that historically collects at a meaningfully lower rate and may need escalation, a payment plan, or a bad-debt reserve, not just a standard reminder. A report that only showed total balance owed, without the aging breakdown, would treat these two accounts identically — which is exactly why the bucket-level view is the report's whole point.

Frequently Asked Questions

At least weekly for active collections work; many teams pull it daily since invoices move between buckets and payments post continuously throughout the week.

Compare the customer record's ID or key between the invoicing system and the system the aging report pulls from — a mismatch there, rather than the name itself, is usually the actual cause of orphaned invoices.

No — the bucket is a strong signal, but a genuine dispute, a customer mid-negotiation, or a large strategic account often warrants a different decision than the aging bucket alone would suggest.

Sources

Topic

AR & Collections

Accounts receivable is the money customers owe a business for goods or services already delivered on credit — a current asset on the balance sheet until it's collected. AR and collections, as a practi…

Diagnostic

How do I automate accounts receivable without losing customer relationships?

Automate the mechanical middle of the process first — aging, prioritization, payment application — and keep a human in the loop on anything customer-facing until the underlying data is reliable. Most relationship damage comes from an automated reminder firing on stale data: chasing an invoice that's already paid, disputed, or attached to a customer mid-renewal conversation with your sales team.

How-to

How do I reduce days sales outstanding?

Send accurate invoices promptly, offer multiple payment methods, automate payment reminders, follow up systematically on overdue accounts, and review outstanding receivables regularly. Most DSO reduction comes from removing friction and delay in the invoice-to-cash cycle, not from pressuring customers harder.