Accounts Receivable Analysis: KPIs, Aging, and Cadence

Accounts receivable analysis is the practice of reviewing invoice-level data to judge how fast customers pay, where cash is stuck, and which accounts carry risk. If you do nothing else this week, run an aging report and check your DSO alongside the dollar concentration sitting in the 61+ and 90+ buckets. That single step usually reveals more about your cash position than a month of revenue forecasting.

TL;DR:

Regularly analyzing the aging report, especially the 61+ and 90+ buckets, reveals potential liquidity issues and guides cash management strategies.

Monitoring trends such as rising DSO and bad-debt ratios helps identify systemic issues or deteriorating customer payment behaviors early.

Building tailored aging buckets based on actual customer payment terms prevents misclassification of accounts and improves collection prioritization.

Automating routine processes like aging runs, dunning sequences, and payment matching reduces manual effort and increases collection efficiency.

Assigning clear ownership for AR review and escalation thresholds ensures timely collections and effective covenant management.

Why Perform Accounts Receivable Analysis in the First Place?
What Are the Key AR KPIs and How Do You Calculate Them?
How Do You Build an AR Aging Report Without the Common Traps?
How Should You Use Trend and Cohort Analysis to Find Root Causes?
What Should an AR Dashboard Include and What Should Automation Handle?
How Often Should You Run AR Analysis, and Who Owns It?
What's the 30/60/90-Day Playbook for Cutting DSO?
How Does Automated Data Normalization Change AR and Diligence Work?
What Does a Missed AR Signal Actually Cost in a Deal?
Sources

Why Perform Accounts Receivable Analysis in the First Place?

Accounts receivable is often the largest non-cash asset on a small or mid-sized company's balance sheet, and it behaves unpredictably. A slow quarter in collections can crimp payroll funding, trip a debt covenant tied to a current ratio, or force a founder to draw on a credit line they'd rather leave untouched. Accounts receivable analysis exists to catch that slide before it becomes a liquidity emergency.

The analysis also feeds decisions well outside the finance department. Sales wants to extend terms to close a big account; credit policy needs data on how that customer segment actually pays, not just how they promise to pay. Run the review often enough and it doubles as an early-warning system, flagging deterioration weeks before a customer formally defaults.

Specific outcomes a solid analysis should drive:

Tightening or loosening credit limits for specific customer segments
Deciding whether a sales team can offer extended terms without hurting cash flow
Triggering a covenant review before a lender does it for you
Flagging which accounts need a collections call this week, not next month

What Are the Key AR KPIs and How Do You Calculate Them?

Five numbers do most of the work in accounts receivable management. Each one answers a slightly different question, and none of them tell the whole story alone.

Days Sales Outstanding (DSO): Average AR ÷ (Annual Credit Sales ÷ 365). If average AR is $500,000 and annual credit sales are $6 million, DSO comes out to roughly 30 days. A rising DSO trend, even a small one, usually means either collections are slipping or a large customer has slowed down.
AR turnover ratio: Net Credit Sales ÷ Average AR. Turnover of 8 means you collect the full receivables balance about eight times a year. It complements DSO because it's easier to compare across companies of different sizes, while DSO ties more directly to daily cash planning.
Collection Effectiveness Index (CEI): (Beginning AR + Credit Sales − Ending Total AR) ÷ (Beginning AR + Credit Sales − Ending Current AR) × 100. A CEI near 100% means you're collecting nearly everything that comes due; anything drifting toward 80% signals collections aren't keeping pace with new invoicing.
Bad-debt ratio: Bad Debt Write-offs ÷ Total Credit Sales. This is your reality check on credit policy. A ratio creeping upward often means underwriting standards loosened somewhere upstream.
AR-to-sales ratio: Total AR ÷ Total Sales, tracked over time to catch receivables growing faster than revenue, a classic sign of quality-of-earnings trouble.

Quick reference: ERP dashboards often calculate two related figures the same way: Net Overdue % equals Overdue Amount divided by Total Receivables, times 100, and AR Collection % equals Collected Amount divided by Total Starting AR, times 100. Both numbers are worth pulling into any dashboard you build alongside DSO and CEI.

How Do You Build an AR Aging Report Without the Common Traps?

Aging analysis sorts every open invoice into time buckets, usually current, 1 to 30 days, 31 to 60, 61 to 90, and 90 plus. You can build it two ways: invoice-date aging (counts from the day the invoice was issued) or due-date aging (counts from when payment was actually owed). Due-date aging is the more honest view for collections prioritization, since it accounts for varying payment terms across customers instead of treating every invoice as if it were net-30.

Standard 30-day buckets work fine for companies with uniform terms. If a meaningful share of your book runs net-60 or net-90, rigid 30/60/90 buckets can mislead your team into escalating accounts that are actually current under their contract. Build your bucket sizes around your actual payment-term mix, not a default template.

Watch for three recurring pitfalls:

Unapplied credits sitting in a suspense account, which inflate gross AR and distort every ratio downstream
Month-end billing spikes that push a disproportionate share of invoices into the "current" bucket right when you pull the report
Customers with individually negotiated terms getting aged against your standard schedule instead of their actual due date

Pro Tip: Pull your aging report on the same day of the month, every month. Comparing a report run on the 1st against one run on the 28th will make your DSO trend look far more volatile than it actually is.

Once the buckets are clean, use the 61+ and 90+ columns to build your daily or weekly call list, largest dollar exposure first.

How Should You Use Trend and Cohort Analysis to Find Root Causes?

A single aging snapshot tells you how much is late. Trend analysis tells you why. Plotting rolling 90-day DSO against prior periods exposes inflection points, and once you see one, you can usually trace it back to a specific cause: a new sales rep offering unauthorized terms, a seasonal dip in a customer's industry, or early signs of financial distress at a key account.

Hands plotting AR trend graph on paper

AR analytics reframes the entire question: instead of asking how much is outstanding, you start asking which customers and invoices will actually affect cash over the next 60 days. That shift only happens when you segment.

Break the portfolio down by:

Invoice month, to catch billing-cycle distortions before they get blamed on collections
Customer or account, to separate one slow payer from a systemic trend
Product line or sales channel, since some offerings naturally attract slower-paying buyers
Sales rep or region, to catch a pattern in who's negotiating unauthorized terms

Combining ratio, aging, and trend views beats relying on any single method. A rising bad-debt ratio paired with a cohort breakdown showing it's concentrated in one sales channel is a policy fix, not a collections problem.

What Should an AR Dashboard Include and What Should Automation Handle?

A dashboard earns its place on someone's desktop by answering three questions at a glance: how much is overdue, which accounts are highest risk, and how is each collector performing. Beyond that, it's noise.

Build your dashboard around these tiles:

Aging by dollar value, not invoice count, since ten small overdue invoices matter less than one large one
High-risk cohort view, flagging customers whose DSO trend has broken from their historical pattern
Collector or account-owner performance, tracked against a target CEI
Net Overdue % and AR Collection %, calculated the way most ERP systems already do it

Automation earns its keep on the repetitive work: scheduled aging runs, prioritized dunning sequences, payment auto-application, and predictive alerts all reduce manual hours and shrink the lag between a payment slipping and someone noticing. None of it works, though, without clean subledger data, meaning invoice-level records with terms, payment dates, and unapplied credits properly matched. Before buying a tool, ask the vendor how it handles partial payments, credit memos, and multi-invoice remittances; those three cases break more AR automation projects than anything else.

How Often Should You Run AR Analysis, and Who Owns It?

Cadence should scale with volume and risk, not calendar convenience. Weekly aging review is the standard for high-volume AR teams, with monthly as the floor for smaller portfolios where invoice counts are low enough that nothing moves fast.

Ownership needs to be explicit or the report becomes shelfware:

An AR lead pulls and distributes the aging report and owns the day-to-day collector queue
The controller reviews trend metrics (DSO, CEI, bad-debt ratio) monthly and flags covenant risk
Sales leadership gets pulled in whenever a credit-limit change is on the table

Set escalation thresholds in advance: an invoice crossing 60 days past due triggers a collector call, 90 days triggers a credit-limit freeze, and any single account exceeding a set dollar exposure goes straight to the controller for a policy decision instead of sitting in a queue.

What's the 30/60/90-Day Playbook for Cutting DSO?

This week: Run the aging report, reconcile every unapplied credit sitting in suspense, and call the largest overdue accounts first, dollar value beats invoice count every time.
Within 30 days: Turn on automated payment reminders, offer a second payment method for customers citing processing friction as an excuse, and start enforcing credit limits you've been quietly ignoring.
Within 60 to 90 days: Escalate chronic late payers to a collections agency or factoring arrangement, revisit credit policy for the segment driving your bad-debt ratio, and consider invoice financing if DSO gains are slower than your cash needs.

Pro Tip: Track your 90-day playbook against a single number: the percentage of AR sitting in the 61+ bucket. If that percentage isn't shrinking after 60 days of effort, the problem is policy, not collections effort.

How Does Automated Data Normalization Change AR and Diligence Work?

Manual AR review in Excel works until the volume of source documents outpaces the analyst's time, which happens faster than most finance teams expect. Add-back was built around that exact bottleneck for financial due diligence, ingesting bank statements, general ledgers, and payment detail, then normalizing it into a single structured view within roughly 60 minutes rather than the weeks a manual quality-of-earnings review typically takes.

The overlap with AR analysis is direct:

Automated normalization catches unapplied credits and misposted receipts that hide in a manual pull for days
Anomaly detection flags invoices aging abnormally against a customer's own historical pattern, not just a generic bucket
Working-capital analysis ties AR trends directly into cash-flow and deal-screening decisions

Teams evaluating an acquisition or lending exposure benefit most from this kind of automated financial due diligence when receivables data spans multiple systems or years of inconsistent formatting, exactly where spreadsheets start to buckle.

What Does a Missed AR Signal Actually Cost in a Deal?

Reviewing target companies for acquisition screening turns up the same pattern repeatedly: a healthy revenue line sitting on top of receivables that have quietly drifted from 35 to 70 days DSO over eighteen months, hidden by a bad-debt reserve nobody revisited. One deal I looked at almost closed at a valuation that assumed full collectability on a customer concentration that was already 120 days past due. Catching that in financial due diligence changed the offer by a meaningful margin.

The lesson isn't complicated: ratios without trend context miss the story, and trend context without governance just becomes an ignored chart. Combine both, and put a human owner on the escalation, or the analysis is decoration.

— Klara

Sources

For deeper formula validation and downloadable templates, start with AccountingTools' breakdown of AR analysis techniques, Zenskar's aging report template guide, and QuickLaunchAnalytics' overview of DSO and AR KPIs. For SMB-focused collections tactics, Zivvy's accounts receivable playbook is worth a read.