Accounts Receivable in Medical Billing: A/R Follow-Up, Aging Reports, and A/R Days

Why A/R Is an Execution Problem (Not a Spreadsheet)

Accounts receivable (A/R) in medical billing is not a spreadsheet problem.
It’s an execution problem.

Most practices don’t lose money because they don’t understand A/R.
They lose money because A/R follow-up is unfocused, reactive, and disconnected from claim status reality.

Staff stay busy. Calls get logged. Notes pile up.
Cash still doesn’t move.

This guide explains what A/R really is, how aging reports and A/R days should be used, and how to run A/R follow-up like a controlled collections operation, not a guessing game.

Evidence Snapshot (What’s Not Opinion)

• HFMA MAP Keys provide standardized definitions for revenue cycle KPIs, including A/R days, to support consistent tracking and benchmarking.
• CAQH CORE Claim Status Operating Rules define how providers request electronic claim status and how payers respond using standardized processes.
• CAQH CORE’s Claim Status (276/277) Infrastructure Rule specifies real-time responses (≈20 seconds) and availability targets (≈86%) for CORE-certified entities.

Who This Is For

Small practices
A/R follow-up competes with front desk and billing duties.

Large groups
Volume hides inefficiency and poor prioritization.

Hospitals / IDNs
Governance, consistency, and escalation discipline matter most.

Not for: teams that only look at A/R once it’s already old.

Plain-English Definitions (No Confusion)

Accounts Receivable (A/R)

Unpaid balances owed for services already provided—primarily unpaid or partially paid insurance claims plus unresolved patient responsibility.

Aging Report

A report that groups receivables by how long they’ve been outstanding:

• 0–30 days
• 31–60 days
• 61–90 days
• 90+ days

Important: aging shows time, not action.

A/R Follow-Up

The structured work of:

• checking claim status
• correcting errors
• responding to payer requests
• appealing denials
• escalating stalled claims

A/R follow-up is decision-making, not just calling.

A/R Days

A KPI estimating how many days of revenue are tied up in receivables. Calculations vary, so consistency matters more than the formula.

Simple translation:
A/R is inventory. Aging tells you how old it is. Follow-up is how you move it.

Why Most A/R Processes Fail

Most SERP pages stop at definitions. What they miss is execution failure:

• teams work entire aging lists instead of priority queues
• claims are followed up without checking status first
• denials sit inside general A/R until they’re too old
• escalation happens from frustration, not thresholds
• effort is measured by touches, not outcomes

The fix is not more follow-up.
The fix is better targeting.

How A/R Should Actually Be Run

Think of A/R as three lanes, not one bucket:

When lanes blur, work explodes and cash stalls.

Step 1: Use the Aging Report to Prioritize (Not Panic)

Aging should guide focus—not trigger random calling.

How to Read Aging Correctly

Rule: not all aging deserves equal effort.

Step 2: Build a Simple A/R Priority Order

Instead of alphabetical lists, use this order:

1. High-dollar balances in 31–90
2. Recent denials with clear correction paths
3. Claims with “no movement” past your internal threshold
4. Repeating payer issues you can batch
5. Low-dollar 90+ (scheduled, limited blocks)

Key question: Can this claim still realistically be collected?
If yes → work it.
If no → document why and stop bleeding time.

Step 3: Use Claim Status Before Calling

A/R follow-up should not start with phone calls.

CAQH CORE rules exist specifically to reduce call-heavy status work.

What Status Results Tell You

Calls are escalation tools—not discovery tools.

Step 4: Separate Delays, Denials, and Underpayments

Most teams slow down because everything lives in “A/R.”

Each problem needs a different workflow.

Step 5: Install Escalation Triggers (Before Frustration)

Escalation should be predictable.

Escalate when:

• no movement past your defined threshold
• conflicting payer responses
• documentation submitted but not acknowledged
• high-dollar claims nearing risk windows

Escalation path:

• re-verify identifiers
• re-check electronic status
• call with a specific question
• escalate via portal or rep
• log outcome + next step