Most behavioral health billing teams have one AR process: someone opens the aging report once a week, sorts by dollar amount or by days outstanding, and starts working whatever looks worst. That’s not a follow-up process. It’s triage, and by the time a claim is worth triaging, it’s already lost value.
- “Working the aging report” and having an AR follow-up process are not the same thing — one reacts to whatever’s already old, the other prevents claims from aging into that bucket at all.
- MGMA’s benchmark caps healthy AR over 90 days at roughly 12-15% of total AR, and HFMA flags anything above that range as revenue genuinely at risk of write-off.
- A scheduled touchpoint model checks every claim on a fixed timeline — regardless of dollar amount or how clean it looks on submission — instead of waiting for it to surface as a problem.
- Weekly aging-bucket review is a monitoring habit, not a follow-up system — HFMA’s own guidance treats weekly review as the cadence for catching drift, not the mechanism that prevents it.
Here’s what actually happens inside claims follow-up at a shop running on reactive aging-report review. Every claim sits untouched from the day it’s submitted until it crosses whatever threshold triggers attention — usually 60 or 90 days.
Nobody’s watching it between day 1 and day 60. If the payer needed additional documentation on day 12, or a clearinghouse rejection got quietly reworked without anyone confirming it landed, that claim doesn’t surface until it’s already deep in a bucket MGMA’s AR benchmark treats as a warning sign.
A scheduled touchpoint model runs the opposite way. Every claim gets a defined check-in built into its timeline the moment it’s submitted — a status pull at day 14, a payer contact at day 30, an escalation review at day 45.
That check-in happens whether or not anything looks wrong yet. The claim doesn’t have to look old to earn attention; it earns attention because a date on a calendar said so.
A follow-up check built into a claim’s timeline at submission — day 14, day 30, day 45 — that runs regardless of dollar amount or how clean the claim looked going out, so a stalled claim surfaces before it ages into a harder-to-collect bucket.
The gap between these two models shows up fastest on the claims nobody thinks to worry about — the small, routine ones. A team working the aging report by dollar amount will always chase the $8,000 claim before the $340 one.
Scheduled touchpoints don’t care about size. Every claim gets the same day-14 check, which is exactly why the small claims that quietly pile up into real money by day 90 get caught while they’re still cheap to fix.
If the first time anyone looks at a claim is the day it shows up on a 60- or 90-day aging bucket, the aging report isn’t a monitoring tool anymore — it’s the entire follow-up strategy. That’s backwards. The report should be a check on the system, confirming the scheduled touchpoints are working — the same weekly-review discipline HFMA’s MAP Keys guidance describes. It shouldn’t be the mechanism that finally notices a claim exists.
This is also where clean VOB work and disciplined follow-up connect. A benefit detail missed at intake — an out-of-network flag, a benefit-year reset — doesn’t announce itself.
It shows up as a denial or a stall weeks later, and a shop only checking the aging report won’t catch it until it’s aged past the point where a quick correction is possible. A day-14 touchpoint catches the same issue while it’s still a phone call instead of a denial to appeal.
Payer-by-payer patterns matter here too. One payer’s “normal” processing time isn’t another’s, and a fixed touchpoint schedule only works if it’s calibrated to what each payer actually does. Calibrating it means starting from each payer’s actual turnaround pattern rather than an industry average.
That’s the kind of payer-specific benchmarking PayerLenz benchmarking exists to track — not a guess at what “day 30” should mean, but the actual reimbursement and turnaround pattern for that payer.
Isn't checking every claim on a schedule more work than just working the oldest ones?
It’s more structured work, not more total work. A scheduled touchpoint on a clean claim takes a minute — confirm status, move on. The time actually gets spent on the claims that need it, caught at day 14 instead of day 90, when the fix is still simple.
What's a reasonable touchpoint schedule to start with?
A common structure checks status around day 14, initiates payer contact by day 30 if unresolved, and escalates by day 45 — inside the 30-40 day Days in AR range MGMA and HFMA treat as healthy. The exact intervals should flex by payer, since processing norms vary.
Does this replace the aging report entirely?
No — the aging report still matters as a system check, confirming the scheduled touchpoints are actually catching what they’re supposed to. The difference is which one drives the work day to day.
Why do smaller claims matter if they're not worth much individually?
Because reactive review almost always prioritizes by dollar amount, small claims sit the longest and are the ones most likely to quietly cross into the 90-day bucket MGMA’s benchmark treats as at-risk. A scheduled model treats every claim the same regardless of size.
- Payer-calibrated touchpoint schedules instead of one generic cadence for every claim
- Small claims get the same day-14 attention as large ones, before they compound
