AR Aging Report

AR Aging Report is a report that groups outstanding customer receivables by how many days they are past due. It is the main tool for prioritizing collections and measuring AR health. Buckets are usually 30, 60, 90 and over 90 days past due, and the report is read alongside DSO because one shows the concentration and the other shows the trend.

Category: AR Automation SoftwareBest AR Automation Software

The CFO asked how much of the $3.4M in accounts receivable was actually collectible. The aging report showed $2.1M current and $1.3M overdue. What it didn't show: $400K in the 31 to 60 day bucket had been disputed and was unlikely to be collected without a resolution process, and $180K in the 61 to 90 day bucket belonged to a customer in financial difficulty that the account manager had flagged internally but never escalated to finance. The aging report tells you how old the receivables are, not whether they'll be paid. An AR aging report is a snapshot of all outstanding customer invoices, organized by how long they've been outstanding relative to their due date. Standard aging buckets are current (not yet due), 1 to 30 days past due, 31 to 60 days, 61 to 90 days, and 90+ days. Finance teams use it to understand what makes up the AR balance, prioritize collections outreach, judge the health of receivables, and set a bad debt reserve. Every finance team runs some version of it. The difference between a useful aging report and a misleading one is the underlying data: whether disputed invoices are flagged separately, whether unapplied credits have been accounted for, whether aging runs from invoice date or due date, and whether the aging total reconciles to the GL accounts receivable balance. Without those checks, the aging report can paint a picture of receivables that doesn't match what will actually be collected.

How AR aging is calculated

AR aging is calculated by taking each open invoice, counting the days elapsed since either the invoice date or the due date, and placing it in the matching bucket. Which date the aging runs from is a configuration choice with real consequences. Aging from invoice date counts the full payment term window: an invoice on net-30 terms that's 25 days old isn't past due, but it lands in the 1 to 30 day bucket if aging runs from invoice date. Aging from due date reflects true past-due status: an invoice stays current until its due date passes, then moves to the 1 to 30 day bucket. For collections prioritization, age from due date, because it shows which invoices are overdue rather than which are simply recent. The buckets also hide important variation. A $400K invoice that's 45 days past due and a $15K invoice that's 45 days past due both sit in the 31 to 60 day bucket, but the first is a significant cash flow risk that needs immediate escalation and the second is routine. An aging bucket is a categorization tool, not a priority queue. Using it as a priority queue without sorting by balance within each bucket consistently underweights the accounts that matter most. Disputed invoices are the most dangerous category in an aging report. Without a dispute flag, a disputed invoice looks identical to a slow-paying invoice in the same bucket, yet the path to resolution is completely different, and the chance of collecting within the normal payment timeline is zero until the dispute is resolved.

Unapplied credits, invoice-date vs due-date aging

Unapplied credits distort AR aging in a specific way: they reduce the GL accounts receivable balance without reducing the aging report total. A customer credit memo sitting unapplied in the AR system reduces the GL AR balance (because the credit posts when issued) but doesn't reduce the aging (because the open invoices haven't been closed). The aging total then overstates what the customer actually owes net of credits, and it can trigger collections outreach for the full invoice amount while the customer assumes the credit applies and is waiting to hear the net balance. Reconciling the AR aging total to the GL accounts receivable balance is the check that catches this. The difference should be explainable: unapplied payments, unapplied credits, invoices in the AR system but not yet posted to the GL, or timing differences between the AR and GL close. A clean aging-to-GL reconciliation at month-end means both numbers reflect the same underlying balances. An unexplained difference means one or both are wrong. This reconciliation is a standard AR close step, yet it's often skipped where AR and accounting run in separate systems with manual reconciliation. When it's skipped, the aging report becomes an unreliable basis for both collections prioritization and the bad debt reserve estimate.

How platforms handle it

The aggregate view of an AR aging report, totals by bucket, is where analysis starts, not where it ends. The value is in the drill-down: which specific invoices sit in each bucket, which are disputed, which belong to customers on credit hold, which have had recent collections contact, and which carry promise-to-pay commitments. A platform that shows only aggregate aging without invoice-level detail leaves you doing manual follow-up to turn the report into collections work. When you evaluate AR automation software, check the following. Does clicking into an aging bucket show individual invoices, or only customer totals? Can you filter invoices within a bucket by dispute status, collections contact date, or promise-to-pay status? Is the aging data live or batch-refreshed, and if batch, how often does it refresh? Can you export the aging as of a point in time (for example, the last day of the quarter) rather than only as of today? Point-in-time aging is essential for period-end reporting and audit support. Does the platform flag when the aging total and the GL balance differ, or does the finance team have to reconcile them by hand? Platforms that surface the discrepancy automatically and explain it by category (unapplied payments, unapplied credits, timing items) save the time a manual comparison would take.

Questions to ask

Does the aging calculate from invoice date or due date, and does that method reflect actual past-due status?
Are disputed invoices flagged separately in the aging, or do they blend into the standard past-due buckets?
Has the aging total been reconciled against the GL accounts receivable balance, with the difference explained?
Are unapplied credits and unapplied payments identified and factored into the aging interpretation?
Does the aging drill-down show invoice-level detail with dispute status and collections history attached?
Is the bad debt reserve being set using aging-based analysis of historical collection rates by bucket?

Common mistakes

Working the AR aging report as a straight collections priority queue (the 90+ day bucket first, then 61 to 90, then 31 to 60) without accounting for dispute status wastes collections effort. In many organizations, large parts of the past-due buckets are disputed invoices that need resolution, not collections pressure. Prioritizing by bucket and balance, then filtering out disputed invoices, gives a truer picture of where outreach will actually bring cash in. The second mistake is not using the aging to set and validate the bad debt reserve. The reserve should be based on historical collection rates by aging bucket: if 15% of balances that reach 90+ days have historically gone uncollected, the reserve for the current 90+ bucket should reflect that rate. Organizations that set the reserve as a flat percentage of total AR, instead of from an aging-based analysis, carry reserves that don't match the actual risk distribution of the portfolio.

Comparing AR automation

AR tools separate on remittance handling, because a payment with no readable remittance advice becomes manual work no matching engine removes. Once AR Aging Report is settled as a requirement, read the AR Automation Software category guide for how the market splits, then weigh the HighRadius profile against the Versapay profile on that requirement rather than on the feature list. Our HighRadius pricing breakdown records what the vendor publishes and what is quote-based. The HighRadius against Versapay comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the AR automation cash flow calculator so the business case is written down before a vendor writes it for you.

AR Aging Report questions

How is AR aging different from AP aging?

AR aging tracks what customers owe your company, organized by how long each invoice has been outstanding. AP aging tracks what your company owes vendors, organized the same way. Both use aging buckets, but the actions they drive are opposite: AR aging drives collections (getting money in), while AP aging drives payment prioritization (managing money out). Both reports need to be reconciled to the corresponding GL balance, accounts receivable for AR aging and accounts payable for AP aging, to be reliable.

What should we do about invoices in the 90+ day bucket that appear uncollectible?

Invoices in the 90+ day bucket that have exhausted collections outreach should be evaluated for write-off. The decision involves confirming that collection efforts are documented, assessing whether any remaining action (payment plan, external collections, legal) is viable and cost-effective, and checking whether the balance meets the company's write-off policy threshold. Before writing off, request a customer statement reconciliation to confirm the balance is genuinely disputed and unpaid, and not stuck in a payment processing or cash application delay. Once the write-off is decided, it should go through an approval process and be documented for audit.

How often should the AR aging report be reviewed?

Operational collections review of AR aging should happen at least weekly: catching invoices moving into higher-risk buckets before they age further, confirming that recent payment commitments were kept, and escalating accounts that have moved past the threshold for standard collections outreach. Reconciling AR aging to the GL balance should happen at least at month-end as a standard close step. For companies with high invoice volume or significant customer concentration, daily monitoring of the aging for specific customer tiers may be warranted.

Accounts Receivable, Bad Debt Write-Off, and Cash Application come up in the same workflow as AR Aging Report, and the rest of the AR automation cluster is indexed in the finance operations glossary.