Accounts receivable follow-up in behavioral health depends on a claim getting a scheduled touch point before it ages past the point of easy recovery — not on how good the eventual phone call is once a claim has already sat untouched for 60 or 90 days.
Most facilities don’t have a follow-up problem. They have a scheduling problem — claims sit in a queue with no defined day-14, day-30, or day-45 checkpoint, and by the time someone looks at them, the easy recovery window has already closed.
- Healthy days in AR runs 30-40 days industry-wide; the average behavioral health facility runs closer to 65-75 days because of carve-out complexity and heavier documentation requirements.
- Collection probability drops sharply once a claim crosses 90 days outstanding — the same claim gets meaningfully harder to collect the longer it sits untouched.
- A healthy AR distribution keeps 85%+ of claims under 60 days and less than 10% over 90 days.
- AR follow-up needs scheduled touch points — day 14, day 30, day 45, day 60 — not a queue someone gets to “when there’s time.”
- Behavioral health-specific factors (carve-out routing, prior authorization requirements, session limits) mean generic medical AR benchmarks understate how much discipline BH follow-up actually requires.
Why Behavioral Health AR Runs Older Than the Textbook Number
The Healthcare Financial Management Association (HFMA) and MGMA both put healthy days in AR at 30 to 40 days, with top-performing practices under 25. Behavioral health facilities routinely run well above that — not because their billing teams are less capable, but because the underlying claims are structurally more complicated to move through the payer’s system.
Session limits, prior authorization renewal cycles, and carve-out plans routed to a separate administrator than the medical benefit all add real time to a claim’s path to payment. Federal regulators have documented that behavioral health services face more frequent utilization reviews and shorter authorization windows than comparable medical care — which is exactly the kind of friction that shows up later as an aging claim, not as an obvious denial, before AR follow-up ever gets involved. That’s not an excuse to accept 65-75 days as normal — it’s the reason a generic medical AR process, applied without adjustment, consistently under-performs in behavioral health.
The Claim Aging Curve Nobody Budgets For
- Day 14: status check — most clean claims should have an EOB or clear status by now
- Day 30: first active follow-up call if no response has come back
- Day 45: escalation, denial-pattern check against the same payer
- Day 60-90: supervisor-level escalation before the claim crosses the point of steep collection decline
- Claims worked in whatever order they were submitted, not by age or risk
- No defined checkpoint before a claim quietly crosses 60 or 90 days
- Follow-up happens when someone notices a payer hasn’t responded, not on a schedule
- The oldest, hardest-to-collect claims get the least consistent attention
The difference between these two approaches shows up almost entirely in the tail of the aging report. A scheduled process catches most problems by day 45, while they’re still recoverable. A queue-based process finds the same problems around day 75 or 90, after collection probability has already dropped substantially.
Once a claim crosses 90 days outstanding, its likelihood of full collection drops meaningfully and keeps falling the longer it sits. If more than 20-25% of a facility’s receivables sit past 90 days, that’s a signal of a systemic follow-up gap, not a handful of unlucky claims.
Where AR Follow-Up Connects to the Rest of the Revenue Cycle
AR follow-up is downstream of almost every other function in the revenue cycle, which means it inherits problems it didn’t create. A claim denied for an authorization mismatch belongs to denial root-cause resolution, not just a follow-up call asking the payer to reconsider. A claim aging past its utilization review authorization window without an extension request on file is a UR timing problem showing up in the AR report. Treating AR follow-up as a standalone function, disconnected from why claims are aging in the first place, means re-solving the same problem every month instead of fixing it once.
This is also where the aging report becomes a genuinely useful diagnostic tool rather than just a collections list. A facility that reviews which payers consistently show up in the 60-90 day bucket, and cross-references that against denial reason codes, usually finds the same two or three root causes repeating across dozens of claims — which is a much cheaper problem to fix than chasing each claim individually.
What's a healthy days in AR benchmark for a behavioral health facility?
Industry benchmarks from HFMA and MGMA put healthy days in AR at 30 to 40 days, with top performers under 25. Many behavioral health facilities run higher — 65 to 75 days is common — due to carve-out routing, authorization renewal cycles, and heavier documentation requirements specific to the specialty.
Why does collection probability drop so sharply after 90 days?
The longer a claim sits unresolved, the more likely the underlying issue — a missed timely filing deadline, a lapsed authorization, or a payer dispute — has compounded into something harder to fix. Claims followed up on within the first 30-45 days are addressing problems while they’re still straightforward; claims followed up on after 90 days are often fighting a harder, more entrenched issue.
Should AR follow-up be handled by the same team that submits claims?
It can work either way, but the two functions need a shared feedback loop regardless of org structure. AR follow-up surfaces the denial and aging patterns; claims submission and VOB are what actually fix the root cause. Splitting the teams without connecting the data just means the same problems keep recurring.
If you want to see where your own AR is aging and why, reach out to Revenue Logic and we’ll walk through your aging report with you.
- Scheduled follow-up cadence, not a reactive queue
- Aging patterns fed back into denial management and claims submission, not handled in isolation
