12 AR Metrics Every Controller Should Report Monthly

Most AR reports have too many metrics or the wrong ones. A CFO reading it takes 30 seconds, glances at DSO, and moves on. The controller wanted to show the story, but the deck did not tell it.

Here is the working set of 12 metrics that answers what a CFO actually wants to know, and how to compute each one so the number is honest.

What are the 12 metrics that belong on the report?

Every metric answers a specific question. If it does not, drop it.

Each of these deserves a definition, because AR metrics are notorious for being computed differently in different companies.

How do you compute DSO variants correctly?

Standard DSO is the one everyone reports. Two variants tell you more.

• Standard DSO. Total AR at period end divided by total credit sales for the period, times number of days in the period. Simple, useful for trend, easily distorted by monthly billing lumpiness.
• Best Possible DSO. Current AR divided by total credit sales, times number of days. This is the DSO you would achieve if every customer paid exactly on terms. The gap between DSO and BPDSO is the operational drag.
• Delinquent DSO. Past-due AR divided by total credit sales, times number of days. Isolates the impact of late-paying accounts, ignoring current-bucket noise.

Reporting all three surfaces different problems. Rising DSO with stable BPDSO means collections is slipping. Rising BPDSO means your terms are creeping longer. Rising Delinquent DSO with stable percentage-current means fewer accounts are going late but they are going more late.

Why does Collection Effectiveness Index matter more than DSO?

CEI measures how effective you were at collecting the receivables you were actually able to collect in the period. It normalizes for billing lumpiness, seasonality, and mix in a way DSO does not.

The formula: (beginning receivables + monthly credit sales - ending total receivables) divided by (beginning receivables + monthly credit sales - ending current receivables), times 100.

Read it this way: the numerator is what you actually collected of what was outstanding at the start plus what became due during the period. The denominator is what you could have collected, in a world where you got every dollar that was not still legitimately in its current-bucket window. A CEI of 85% means you collected 85% of what was collectible.

CEI is boring, which is exactly why it works. It does not swing when your billing mix changes, so it is a fair measure of collections performance over time.

How should aging be reported?

Aging by cohort, not just as a snapshot.

A single monthly snapshot of aging buckets tells you where dollars sit today. It does not tell you where they came from. Cohort aging tracks the invoices billed in a given month across their aging life, so you can see whether the January cohort ages faster than the March cohort.

• Snapshot view. Current, 1-30, 31-60, 61-90, 90+, in both dollars and percentages. Belongs in the monthly report.
• Cohort view. For each billing month, percentage still outstanding at 30, 60, and 90 days. Belongs in the quarterly review.
• Concentration view. Percentage of aging over 60 days concentrated in top 5 accounts. If this is above 60%, you have a customer-specific problem, not a process one.

The concentration view is the one most reports miss and the one that most changes what a CFO does with the information.

What does promise-to-pay accuracy actually tell you?

Promise-to-pay kept rate is the sharpest leading indicator on the report. When it moves, DSO follows.

Two related metrics to compute alongside.

• Promise-to-pay coverage. Percentage of past-due invoices that have a dated commitment on file. Above 70% means you are converting conversations to commitments. Below 40% means your team is chasing without landing dates.
• Promise-to-pay kept rate. Percentage of dated commitments that were paid within 5 days of the promised date. Above 80% means your customers mostly do what they say. Below 60% means either your accounts are stalling or your team is accepting soft promises.

A high coverage rate with a low kept rate is worse than a low coverage rate. It means the process is producing false confidence in the forecast.

How do you measure cash forecast accuracy?

Forecast accuracy is the metric that connects AR performance to CFO credibility.

• Weekly variance. Actual collections divided by forecasted collections for the week, minus one. Report this as a rolling 8-week variance.
• Bias vs variance. Are you consistently over-forecasting, under-forecasting, or randomly wrong? Consistent bias is more fixable than random noise, because it usually points to one wrong assumption (like overestimating promise-to-pay kept rate).
• Big-account attribution. When variance exceeds 5% in a week, attribute it to specific accounts. If two customers explain 80% of the miss, your forecast model is fine but your top-account risk score is off.

A cash forecast inside 5% variance is defensible to a board. Outside 10% is not.

What belongs in an operational report but not a monthly one?

Some AR metrics are useful for the AR team every week but too granular for a monthly CFO report.

Keep the following in the weekly operational deck, not the monthly.

• Reminders sent by touch type
• Emails open and reply rates
• Dispute queue depth by owner
• Individual account statuses
• Portal payment volume by day

These are actionable for the AR team, but they are noise for the CFO. Save the monthly report for trend and exception, not activity.

The mistake to avoid

The mistake is picking a metric because it is easy to compute, not because it changes a decision. DSO alone is easy and moves for reasons unrelated to collections quality. Aging alone shows where you are, not how you got there. The 12 metrics above work as a set because each one answers a distinct question, and together they let a controller defend the state of AR to a CFO in under 5 minutes. Anything else in the report is decoration.