Why Your Days in A/R Is the Most Honest Metric in Your Revenue Cycle

Days in A/R doesn't lie. Most revenue cycle metrics can be massaged — claim volume, gross charges, even denial rates. But Days in A/R is a running clock on how long your money sits uncollected, and no amount of optimistic reporting changes the number. If your cash isn't coming in, this metric will tell you before anything else does.

I've worked with practices that reported low denial rates and high clean claim percentages — and still couldn't make payroll. When I pulled their Days in A/R, the answer was sitting right there. In my experience, this is the single metric that tells you the most about the health of your entire revenue cycle, end to end.

What Days in A/R Actually Measures

Days in A/R represents the average number of days between the date of service and the date payment is received. It answers a simple question: how long does it take your organization to get paid?

The formula is straightforward: divide your total outstanding accounts receivable by your average daily net charges. The result is a number of days. That number tells you how efficiently — or inefficiently — your entire revenue cycle is converting services into cash. A high number means money is sitting in the pipeline. A low number means it's flowing.

What makes this metric so honest is that it reflects every upstream failure. A coding error that triggers a denial adds days. A missed authorization that delays payment adds days. A registration mistake that sends a claim to the wrong payer adds days. Every breakdown in the revenue cycle eventually shows up in this number.

Industry Benchmarks: Where Do You Stand?

Here's how I frame Days in A/R benchmarks with the organizations I work with:

• Under 30 days: Excellent. Your front end is tight, claims are going out clean, and your follow-up process is working. This is the target for high-performing commercial-heavy practices.
• 30–40 days: Acceptable. There's room for improvement, but you're not bleeding. Most well-managed multi-specialty groups land here.
• 40–50 days: Needs attention. Something systemic is dragging collections down — usually denial rework time, front-end gaps, or understaffed A/R follow-up.
• 50+ days: At risk. Cash flow is compromised, and write-offs are likely climbing. This usually means multiple root causes are compounding.

One important caveat: payer mix matters. Organizations with a heavy Medicare or Medicaid population will typically see higher Days in A/R than commercial-dominant practices. Government payers process differently, and their timelines are less negotiable. That doesn't mean you ignore a high number — it means you need to benchmark against peers with a similar payer mix, not just the industry average.

The 5 Root Causes That Drive Days in A/R Up

When I audit a revenue cycle and see elevated Days in A/R, I'm looking at five specific areas. These are the root causes I see over and over again.

1. Front-End Eligibility and Authorization Failures

If eligibility isn't verified before the patient is seen — and I mean truly verified, not just a cursory check — you're building claims on a shaky foundation. Missing or expired authorizations are the same story. These failures don't just cause denials; they cause denials that take weeks to rework because they require clinical documentation, peer-to-peer calls, or retroactive auth requests. Every day in that rework cycle is a day added to your A/R.

2. Claim Submission Delays

I've seen organizations that batch claims weekly. Some only submit after coding is "complete" for the entire week. Every day between date of service and claim submission is a free day you're giving the payer. Same-day or next-day submission should be the standard. If your workflow doesn't support that, your workflow is costing you money.

3. Denial Rate and Rework Cycle Time

It's not just your denial rate that matters — it's how long it takes to work a denial from receipt to resolution. I've seen organizations with a 10% denial rate and a 45-day rework cycle. That's 10% of your revenue sitting untouched for over a month after the initial denial. The denial itself is a problem; the rework delay is what inflates your A/R.

4. Payer Mix and Slow-Pay Payers

Some payers simply pay slower than others. Workers' compensation, certain Medicaid managed care plans, and out-of-state commercial plans are notorious. You can't change their processing timelines, but you can manage around them — prioritizing follow-up on these payers earlier and more aggressively rather than treating all payers the same.

5. A/R Follow-Up Staffing and Workflow Gaps

This is the one nobody wants to talk about. If your A/R follow-up team is understaffed, undertrained, or working without a structured workflow, claims sit. They age out of the 30-day bucket into 60, then 90, then 120. And every day that passes, the probability of collection drops. A/R follow-up isn't glamorous work, but it's where revenue goes to either get collected or die.

Diagnosing Your A/R Aging

The first thing I do when assessing Days in A/R is break the total into aging buckets: 0–30 days, 31–60 days, 61–90 days, 91–120 days, and 120+ days. The distribution tells you more than the average.

A healthy A/R should have the vast majority of dollars — 70% or more — sitting in the 0–30 day bucket. If you're seeing significant volume in the 61–90 day range, you have a rework problem. If the 91–120 day bucket is growing, you have a follow-up problem. And anything over 120 days is, realistically, a write-off risk. The probability of collecting a claim over 120 days old drops below 20% for most payers.

I tell every organization I work with: your 120+ bucket is not an A/R asset. It's an accounting entry that's almost certainly overstating your expected revenue. The sooner you face that, the sooner you can focus resources where they'll actually produce results — in the 31–60 and 61–90 day buckets where recovery is still realistic.

The 90-Day Fix: Three Actions That Reliably Reduce Days in A/R

If I had 90 days and three moves to bring Days in A/R down, here's exactly what I'd prioritize:

First: same-day claim submission. Eliminate every unnecessary day between date of service and claim drop. This means coding turnaround needs to be same-day or next-day, charge entry needs to be immediate, and claims need to go out the door the same day they're ready. This single change can reduce Days in A/R by 3–7 days on its own.

Second: front-end Verification at every encounter. Not just new patients — every visit. Insurance changes, plan year rollovers, Coordination of Benefits updates, authorization expirations. Running real-time eligibility at check-in catches the problems that would otherwise become denials 30 days later. This prevents the downstream rework that inflates A/R aging more than any other single cause.

Third: systematic A/R follow-up by payer bucket. Stop working A/R alphabetically or by account number. Segment by payer and age bucket. Hit the highest-dollar, oldest claims first within each payer group. Assign specific payers to specific team members so they build expertise and relationships. Track touches per day, resolution rate, and dollars recovered per FTE. Make it measurable and make it visible.

The Connection Between Denial Intelligence and Days in A/R

Here's what most people miss: Days in A/R is a downstream symptom. Denials are the upstream cause. When you fix your top three denial root causes — whether that's eligibility failures, coding errors, or authorization gaps — you're not just reducing your denial rate. You're directly reducing the volume of claims that get stuck in rework, which directly reduces your A/R aging.

I've seen practices reduce Days in A/R by 8–12 days simply by addressing their top three denial categories. No new software, no staffing changes — just focused root cause analysis and targeted process fixes. That's the power of denial intelligence applied strategically.

If you want to know where your revenue cycle actually stands, start with Days in A/R. It won't tell you a comfortable story — but it will tell you the truth.