Revenue cycle operations

How Do You Track Medicaid Coverage Changes on Encounters You’ve Already Written Off?

Most billing teams have some version of a process for this. Here is what those processes catch, where they structurally break, and why the failure is almost never about effort.

There are three ways billing teams track Medicaid changes on closed encounters manually: periodic batch re-runs of eligibility, patient callbacks through financial counseling, and spot review of aged accounts before final write-off. Each one works. None of them scales to the full population of uncompensated encounters, because all three depend on a review happening to land after a benefit change occurs and before the filing window closes.

The problem is not that billing teams are not working hard enough. It is that the timing of a Medicaid benefit change is unpredictable, and a periodic process cannot reliably intersect an unpredictable event.

The three things teams actually do

Almost every safety net provider we talk to is doing at least one of these. They are all reasonable. It is worth being precise about what each one is good at before talking about what it misses.

Periodic batch eligibility re-runs

A list of self-pay or uncompensated accounts gets pushed back through the eligibility system on a schedule — monthly for some organizations, quarterly for most, annually for a few. It is cheap, it requires no new vendor, and it does find coverage. The limitation is that it returns current status, not status as of the date of service, and it only sees changes that happened before the run.

Patient callbacks through financial counseling

A counselor reaches out to a self-pay patient, learns that Medicaid was approved two months ago, and the account gets rebilled. This is the highest-yield method per account touched, and it also serves the patient. It is also the hardest to scale, and it has a selection problem: the patients whose encounters went uncompensated are disproportionately the patients whose phone numbers and addresses have changed.

Spot review of aged accounts before write-off

Before an account is closed to bad debt or sliding fee, someone gives it a last look. In practice, because the queue is longer than the hours available, this becomes sampling rather than review — and the sample is usually chosen by balance size. That selects for the biggest accounts, which is rational, but it has no relationship to which accounts had a benefit change.

Why the timing does not work

Follow one encounter through a quarterly review cycle and the structural problem becomes obvious. Nothing here requires anyone to make a mistake.

  1. 1

    January — the encounter closes

    Eligibility came back with no billable coverage. The encounter moves to self-pay. Everything about this decision was correct on the information available.

  2. 2

    March — the quarterly re-run

    The account goes back through eligibility. Still nothing. It gets marked as reviewed, which in most systems means it is now less likely to be looked at again.

  3. 3

    April — the Benefit Profile moves

    An application filed in March is approved with an effective date that reaches back past January. The encounter is now billable. Nothing in the revenue cycle generates a signal, because nothing in the revenue cycle is looking.

  4. 4

    June — the next re-run

    The account may or may not be in this batch; many organizations scope the re-run to accounts from the last 90 days, which this one no longer is. If it is included, the eligibility response shows current coverage — which a staff member still has to connect back to a January date of service to realize it matters.

  5. 5

    The window closes

    The change happened in a gap between reviews. No one did anything wrong. The revenue is gone anyway.

Shortening the interval helps, but it does not solve the problem — it only narrows the gap. Any periodic process has gaps by definition, and the change is free to happen inside one.

The volume problem, worked through

Timing is the harder problem, but volume is the one that makes the timing problem unfixable with staffing. Here is the arithmetic, using round numbers as an illustration rather than a benchmark — substitute your own.

Say a health center carries 8,000 uncompensated encounters in an average year. To catch a benefit change within 30 days of it occurring, each of those encounters needs to be examined roughly twelve times over the course of the filing window. That is 96,000 examinations a year. At even two minutes each — optimistic, since a meaningful check means comparing current benefit detail against a specific past date of service, not just reading a yes or no — that is about 3,200 hours, or a full-time role and a half doing nothing else.

And the yield on that work is low per touch by design. The overwhelming majority of those 96,000 examinations return nothing, because on any given check most Benefit Profiles have not moved. A human being asked to perform a task with a 2% hit rate, 96,000 times, will not sustain accuracy — and would be poorly deployed even if they could.

This is the real reason manual tracking fails. Not lack of diligence. It is a surveillance task with a low base rate and an unpredictable trigger, which is precisely the category of work humans are worst at and systems are best at.

The signal problem: four changes a status check will not show you

Even a team with unlimited hours would still hit the third wall. An eligibility response tells you whether coverage exists now. These four movements are what actually make a past encounter billable, and none of them announce themselves in a yes-or-no answer.

Benefit scope expands

Coverage existed all along and your check said yes — but the service category was excluded. When the scope broadens, the encounter moves inside the benefit without the coverage status changing at all.

A payer is added or changed

Managed care assignment shifts, or a secondary payer appears. The patient still shows as covered. The party responsible for your January claim is now someone else.

Denied, then approved on appeal

The determination that closed your encounter was reversed, frequently with an effective date reaching back past the visit. The appeal happened between the patient and the state; your revenue cycle was never a party to it.

Lapsed benefits are reinstated

Coverage dropped for a procedural reason and was restored — often with no gap, which means the encounter was covered the whole time and your check simply caught the trough.

These are attributes of the Medicaid Benefit Profile, not of coverage status — which is why watching status, however often, will not surface them.

What manual review genuinely does better

This is not an argument that your team should stop working accounts. Manual review beats any system on the complicated single account — the one with a coordination-of-benefits question, an unusual documentation history, or a payer dispute that requires someone to pick up a phone and exercise judgment. It is also the only method that serves the patient at the same time, which matters at a health center in ways that do not show up on a revenue report.

The mismatch is specific. Humans are good at depth on one account and bad at continuous surveillance across thousands. Asking your billing staff to do the second thing is what costs you the first.

Frequently asked questions

Can’t we just re-run eligibility more often?

It helps, and it is worth doing. But it narrows the gap rather than closing it, and it does not address the signal problem: an eligibility response reports current status, not whether the Benefit Profile behind a specific past date of service now supports reimbursement. You can run it weekly and still not be told that a denial was overturned on appeal.

How far back should we look at written-off encounters?

As far back as your filing windows remain open, which varies by payer and by state, and which for retroactive determinations may run from the determination date rather than the date of service. That distinction is what makes older encounters worth revisiting more often than teams assume.

Does our EHR or practice management system do this already?

Most will re-run eligibility on demand or on a schedule, which is the batch method described above. What they generally do not do is hold a closed encounter under continuous watch and compare Benefit Profile detail against that encounter’s date of service. Worth confirming with your vendor rather than assuming either way.

Would hiring another biller solve this?

It would add capacity to a task that scales badly. The arithmetic above puts continuous manual surveillance of a mid-sized uncompensated population beyond one additional role, at a hit rate that makes the work hard to sustain. A biller is usually worth more on complex accounts than on repetitive checks.

Do we have to integrate anything to change this?

Not with RetroCAID. There is no EHR integration, setup is handled by phone and typically takes under an hour, and pricing is contingency — you pay only after you are reimbursed. Your team keeps every patient-facing interaction; what changes is that the encounters they have already closed stay under watch.

Keep your written-off encounters under watch

A straightforward conversation about your facility and the encounters your team has already closed. Implemented by phone in under 60 minutes.

Contact us See how monitoring works

5,000+ FACILITIES  ·  49 STATES + DC & USVI  ·  NO EHR INTEGRATION  ·  PAY ONLY AFTER REIMBURSED

Tracking Medicaid Coverage Changes After Write-Off was last modified: October 27th, 2026 by Fix Healthcare Technology, LLC