Stuut Insights

AR Aging Report Guide

Ben Winter

COO

October 9, 2026

See Stuut in action

Get a personalized demo of Stuut and see how it can help with AR automation.

Get started

TL;DR: Most AR teams treat the aging report as a to-do list. The fastest collectors treat it as a triage tool, routing routine accounts to automation and reserving human attention for the accounts that actually need it. Keeping less than 15% of total AR in the 90+ day bucket is the benchmark. Letting that figure exceed 20% signals elevated write-off risk and requires immediate escalation. This guide covers how to read each aging bucket, prioritize daily collections work, spot high-risk accounts early, and automate the follow-up the report identifies.

‍

An AR aging report tells a Collections Manager exactly which invoices need attention. It doesn't tell them how to find the time to chase all of them. Every day after the due date is an interest-free loan to a customer. Most AR teams treat the aging report as a to-do list. The teams that collect fastest treat it as a triage tool.

This guide shows how to read aging reports, interpret each bucket, prioritize daily collections work, spot high-risk accounts before write-offs, and automate the follow-up work the report identifies.

Core Components of an AR Aging Report

An AR aging report groups receivables into buckets based on the elapsed time since the invoice was due, such as current, 1 to 30 days, 31 to 60 days, 61 to 90 days, and over 90 days, according to Investopedia's guide to accounts receivable aging. The first three columns include identifying information such as invoice number, invoice date, and customer name or number. Key details include customer names, invoice amounts, due dates, and days past due, helping finance teams prioritize collections and monitor cash flow health.

Why AR Aging Reports Are Vital

The aging report answers three questions every morning: Which invoices need attention today? Which customers are trending toward write-off risk? Where should the AR team spend its limited time? Without this report, collections work becomes reactive and random. With it, collections work becomes systematic and targeted.

AR teams at many organizations spend so much time chasing customer payments, navigating portals, and performing manual matching that the organization loses nearly 5 percent of EBITDA, according to Pulse2's Stuut Series A coverage. The aging report identifies the work. The question is whether the AR team has capacity to execute it.

How Finance Teams Use Aging Data

Finance teams use aging data for three core functions. First, liquidity assessment: the report shows how much cash is trapped in receivables and how quickly it's converting to usable funds. Second, credit risk management: accounts trending toward 90+ days signal potential write-offs and may require credit limit adjustments. Third, collections prioritization: the report determines which accounts get contacted today, which get escalated, and which get written off.

A company with $10M in annual revenue and a 60-day average collection period carries roughly $1.64M in receivables at any given time. Reducing that to 45 days frees approximately $410,000 in working capital, an illustrative calculation using standard DSO arithmetic. This is why overdue AR acts as an interest-free loan to clients. The longer invoices sit unpaid, the more working capital the business must finance externally at cost.

Interpreting AR Aging Report Data

Reading an aging report requires understanding three layers: the data fields that populate it, the bucket logic that categorizes invoices, and the totals that show portfolio health. Each layer informs a different decision.

Key Data Fields for Aging Reports

Standard AR aging reports include core fields that identify the transaction and enable prioritization. Invoice number identifies the specific transaction. Invoice date shows when the invoice was issued. Customer name or number links the invoice to the account. Due date establishes when payment was expected. Invoice amount shows the total owed. Days overdue calculates how late the payment is. Aging bucket classification groups the invoice into a time-based category for action.

AR teams calculate the days overdue field automatically using formulas rather than manual entry. In Excel, the DATEDIF function calculates days old: =DATEDIF(A2, TODAY(), "d"), according to Pickl AI's Excel aging formula guide. This field drives the bucket assignment and determines which collection action applies.

Categorizing Invoices by Age

Finance teams typically group invoices in 30-day intervals with standard columns of current, less than 30 days, 31 to 60 days, 61 to 90 days, and over 90 days, consistent with the standard aging schedule format used across accounting practice. AR teams use IF statements in Excel to allocate each invoice's balance into the correct aging bucket based on the days overdue value.

Tracking Total Outstanding Receivables

The report totals show portfolio health at a glance. Total AR is the sum of all unpaid invoices. Current AR is the amount not yet due. Overdue AR is the sum of all past-due buckets. The percentage of total AR in each bucket reveals collection effectiveness and risk concentration.

Mastering AR Aging Intervals

Each aging bucket represents a different stage of delinquency and requires a different collection response. The bucket is not just a reporting category. It's a triage decision.

Aging Bucket What It Means Recommended Action Escalation Trigger Current (0 days) Invoice not yet due Routine monitoring, confirm receipt None 1-30 Days Recently overdue, payment likely overlooked or deprioritized Send gentle reminder No response after follow-up reminders sent 10 to 14 days apart 31-60 Days Payment slipping, needs attention Escalate to phone contact to surface the real issue No payment commitment confirmed after direct contact 61-90 Days Serious delinquency, collection window narrowing Escalate to AR manager, contact customer decision-maker by phone No response from customer decision-maker after direct contact 90+ Days High write-off risk, immediate action Executive review, external collections Invoice reaches 90 days past due without an active payment plan

‍

Tracking Recently Invoiced Receivables

Current receivables are invoices not yet due. These require routine monitoring but no active collection effort. The goal is to confirm the customer received the invoice and has everything needed to process payment on time. A quick confirmation email or portal check prevents most current invoices from aging into the 1 to 30 day bucket.

1 to 30 Days: Managing Initial Delinquency

The 1 to 30 day bucket is where most overdue invoices land. These accounts need a gentle nudge, not aggressive follow-up. Send a standard payment reminder to keep the invoice top of mind. Automation can handle this without manual intervention.

A well-structured dunning workflow starts with a pre-due reminder a few days before the invoice date, then sends a first reminder on or shortly after the due date for unpaid invoices. The tone is helpful, not accusatory. The goal is to remove friction and make payment easy.

Addressing Invoices 31 to 60 Days Late

Add phone contact and copy the customer's account manager at 31 to 60 days. Silence at this stage usually means the invoice has slipped through or the customer is deprioritizing payment. A phone call surfaces the real issue faster than another email. Standard practice includes a firmer notice around the 10 to 15 day mark and an escalation to phone contact at 30 days.

61 to 90 Days: Escalation Tactics

The 61 to 90 day bucket requires AR manager escalation. Escalate to a decision-maker at the customer's company instead of chasing the same contact repeatedly. The AP clerk who hasn't responded to three emails isn't going to respond to a fourth. The controller or VP of Finance will.

At 60 days, escalating to direct management contact with the debtor moves the conversation past the AP clerk who has ignored previous outreach. A formal demand or referral to internal legal or external collections between 60 and 90 days applies when earlier outreach hasn't produced a payment commitment.

Resolving Accounts 90 Days Past Due

The 90+ day bucket is where cash goes to die. Accounts sitting here need immediate, structured intervention, not another reminder email. Standard escalation moves the account to external action: referral to a commercial collections agency, credit bureau reporting, small claims court for smaller balances, or formal legal proceedings for larger ones. Companies that establish clear escalation protocols, including internal follow-up at 30 days and collection agency placement at 60 to 75 days, typically recover significantly more than those that wait.

Spotting High-Risk Trends in AR

The aging report reveals trends before they become write-offs. A single invoice in the 90+ bucket is a problem. A pattern of invoices from the same customer aging into 90+ days is a crisis. The report shows both.

Step-by-Step Aging Report Review

Review new entries in the 30-day bucket: Every morning, review new entries in the 30-day bucket and begin proactive outreach before invoices age further. This prevents small issues from becoming big problems.
Identify accounts trending toward 90+ days: Look for customers with multiple invoices aging into higher buckets. One late invoice is a clerical issue. Three late invoices from the same customer is a payment behavior problem.
Check for concentration risk: If one customer represents 20% of total AR and that customer's invoices are aging, the entire portfolio is at risk. Diversification matters in AR just as it does in revenue.
Monitor the 90+ day percentage: Finance teams typically target less than 15% of total AR in the 90+ day bucket, and exceeding 20% signals elevated write-off risk.

Identifying Risky Payment Behaviors

Certain patterns signal high-risk accounts before they hit the 90+ day bucket. Customers who consistently pay at 45 days when terms are net 30 are training the AR team to accept late payment. Customers who short-pay invoices without explanation are testing whether the AR team will chase the difference. Customers who go silent after multiple contact attempts are signaling cash flow problems or deprioritization.

Using aging buckets as a daily workflow tool shifts collections work from reactive to proactive. Every morning, the collections team reviews new entries in the 30-day bucket and begins proactive outreach before invoices age further.

How to Triage Daily Collections Work

The aging report identifies accounts that need attention. Triage determines which accounts get contacted by a human and which get automated.

Strategy for High-Value AR Accounts

High-value accounts get white-glove service. Organizations typically prioritize their top strategic accounts by revenue or relationship importance, and these accounts receive personal phone calls rather than automated emails. The Collections Manager owns these relationships and handles all communication directly. Automation supports these accounts by confirming invoice receipt and sending pre-due reminders, but a human handles any overdue follow-up.

Define explicit actions for each bucket: 1 to 30 days gets an automated reminder, 31 to 60 days gets a phone call plus account manager CC, 61 to 90 days gets AR manager escalation, and 90+ days gets executive review. This framework ensures high-value accounts receive appropriate attention without consuming all available capacity. Stuut supports this by escalating based on complexity and confidence, so human attention goes where it's actually needed rather than being spread across the full portfolio.

Oldest Invoices by Bucket

Prioritize by balancing invoice value against age risk. A $50,000 invoice at 35 days is more urgent than a $500 invoice at 65 days. The aging report sorts by bucket, but the daily collections list sorts by value within each bucket.

Collections managers should prioritize by balancing invoice value against age risk, and at 60 days, escalate to direct management contact with the debtor. This ensures the highest-value, highest-risk invoices get attention first.

Customer Payment History

Payment history predicts future behavior. A customer who always pays on the 15th after two reminders doesn't need aggressive follow-up on day 5. A customer with a history of short-pays needs invoice-level detail in every communication. A customer who responds to SMS but ignores email needs a different channel mix.

Stuut is designed to remember interactions and learn each customer's payment patterns, communication preferences, and history to personalize every touchpoint, helping unify intelligence across the AR process, according to Stuut's platform overview. This eliminates the need for AR teams to manually track these patterns in spreadsheets.

Tailoring Follow-Ups for Specific Clients

Different customers require different communication strategies. A manufacturing customer with a formal AP department needs invoices submitted through a portal with PO numbers. A small business customer needs a text message with a payment link. A strategic account needs a phone call from the Collections Manager, not an automated email.

Stuut handles proactive outreach autonomously, including sending reminders, confirming invoice receipt, answering balance questions, and logging promise-to-pay dates. The platform escalates work that requires human judgment, such as complex disputes and payment plan negotiations, based on complexity and confidence rather than a fixed aging threshold. This preserves relationship management for high-value and complex accounts while automating routine volume.

Automating AR Aging Reports and Collections

The aging report identifies what needs to be done. Automation does it. The report surfaces the 300 accounts the AR team doesn't have time to contact. Stuut contacts them.

Upgrading Manual AR Aging Processes

The manual process: Export aging report from ERP to Excel, sort by bucket and value, send reminder emails one by one, make collection calls, log into customer portals to submit invoices, manually match payments to invoices, research short-pays, and document everything in spreadsheets the ERP can't handle. These manual, repetitive tasks consume 60 to 70% of AR staff time, according to Ardent Partners research cited by SINGOA.

The automated process: Review Stuut exception dashboard, see which accounts need human attention (AI has already contacted routine accounts overnight), handle escalated accounts requiring judgment, and review AI communication logs for quality. The AR team shifted from chasing routine payments to managing complex disputes and white-glove service for strategic accounts.

Workflow Step Manual (Excel + ERP) Stuut (Automated) Report generation Export from ERP, sort in Excel Real-time dashboard, no export Prioritization Manual triage by value and age AI triages by risk and value Outreach 30-50 calls/emails per day AI contacts routine accounts overnight Payment matching Manual matching in ERP 95%+ automated match rate Escalation AR team identifies and escalates AI escalates only what requires judgment

‍

Automating Routine AR Aging Follow-Ups

Stuut is designed to handle workflows independently, delivering 40% cash flow increases and 37% faster DSO while eliminating 70% of manual tasks, according to Stuut's Series A announcement. The platform deploys in 3 to 4 days versus 3 to 6 months for traditional software because it works differently. Legacy AR platforms are deterministic, meaning a rules engine executes only the paths that have been configured, so every dunning sequence, approval hierarchy, matching rule, and exception path must be encoded before go-live. Stuut uses a probabilistic approach, meaning the agent infers the right action from patterns in the data, the policies it has been given, and the contracts it can read, including cases no one configured in advance. Going live is a matter of connecting to the ERP rather than authoring behavior up front.

Bishop Lifting reduced overdue receivables by 35% and unlocked $3M in working capital by rolling Stuut out across 45 branches, with AI agents handling 91% of outbound communications, as Bishop Lifting's case study details. PerkinElmer reduced overdue invoices from 50% to 15% in one year with $300M collected, and EZG Manufacturing collected $11.67M automatically while reducing DSO by 5 days.

Criteria Excel Template Stuut Portfolio size Under 100 accounts 100+ accounts Invoice volume Under 500 invoices/month 500+ invoices/month Team capacity AR team has time for manual follow-up AR team can't cover all accounts DSO trend DSO stable or decreasing DSO increasing or flat

‍

Stuut is designed to cover the accounts the AR team doesn't have time to reach. Every account gets contacted on schedule rather than only the ones that fit into the day, and coverage holds as invoice volume grows without adding headcount. Work that requires judgment escalates with the full communication history attached, so the analyst steps in with context instead of starting cold. This human-in-the-loop model addresses control concerns: Finance leadership defines the policy and escalation thresholds, and the agent operates within them.

Book a demo with the team to see Stuut execute collections from aging data autonomously.

FAQs

How Often Should Organizations Review Their AR Aging Report?

Review the aging report daily to identify new entries in the 30-day bucket and begin proactive outreach before invoices age further. Weekly reviews work for portfolios under 50 accounts, but organizations with larger, faster-moving portfolios may find more frequent review necessary to catch new entries in the 30-day bucket before they age further.

What Is a Healthy Accounts Receivable Aging Report?

A healthy aging report shows less than 15% of total AR in the 90+ day bucket, with the majority of receivables in current and 1 to 30 day buckets. Exceeding 20% in the 90+ day bucket signals elevated write-off risk and requires immediate escalation protocols.

What's the Difference Between DSO and AR Aging?

DSO (Days Sales Outstanding) measures the average number of days it takes to collect payment after a sale, while an AR aging report shows the distribution of unpaid invoices by how long they've been outstanding. DSO is a single metric. The aging report is a detailed breakdown that informs daily collections work.

Can Aging Buckets Be Customized for a Business?

Yes, aging buckets can be customized to match business payment terms and collection cycles. Standard buckets are current, 1 to 30, 31 to 60, 61 to 90, and 90+ days, but businesses with longer payment terms often adjust buckets accordingly to align with their cycles.

Key Terms Glossary

Accounts receivable aging report: A report that groups unpaid invoices by how long they've been outstanding, typically in 30-day buckets (current, 1 to 30, 31 to 60, 61 to 90, 90+ days). Finance teams use it to prioritize collections and assess cash flow health.

Aging bucket: A time-based category that groups invoices by days overdue. Standard buckets are current (not yet due), 1 to 30 days, 31 to 60 days, 61 to 90 days, and 90+ days past due.

Days Sales Outstanding (DSO): The average number of days it takes to collect payment after a sale. Calculated as (Accounts Receivable / Total Credit Sales) × Number of Days.

Dunning: The process of communicating with customers to collect overdue payments. Dunning typically escalates from gentle reminders to formal demands as invoices age.

Cash application: The process of matching incoming payments to open invoices in the ERP. Manual cash application is time-consuming and error-prone. Automated platforms use AI to match payments without manual intervention.

Write-off: An unpaid invoice that the business no longer expects to collect and removes from accounts receivable. Invoices in the 90+ day bucket have the highest write-off risk.

Ben Winter

COO

Ben brings over a decade of go-to-market and operations expertise to building AR automation that actually works. He was VP Marketing at Fairmarkit (where he met Tarek) and GTM executive at Waldo before co-founding Stuut. He focuses on operations, product, and marketing—ensuring the platform integrates seamlessly with existing ERP systems and delivers results in days rather than months.

How to calculate DSO and the importance of tracking it

Tarek Alaruri

Mar 10, 2026