A Medicaid resident’s billing path can change during a long-term care stay. Someone billed under fee-for-service (FFS) Medicaid may later move into a Medicaid managed care organization (MCO) plan. This can happen after initial enrollment, when a new applicant spends a short time in FFS before being assigned to or selecting a plan.
It can also happen when a state moves certain populations, including long-term care residents, into managed care, often under a Managed Long-Term Services and Supports (MLTSS) program. For dual-eligible residents, the same thing happens on the Medicare side when a resident enrolls in a D-SNP, which changes crossover and secondary billing at the same time.
These changes are easy to miss because the resident’s Medicaid ID may stay the same. However, the payment rules, payer responsibility, authorization requirements, claim format, and billing process may all change. If the switch is missed, a claim may be sent to the wrong payer, leading to denials, rebilling, or delayed payment.
Everything that follows depends on how quickly your team learns about the change. Close that gap and each problem below stays a routine correction. Leave it open and the same problems become write-offs.
The Payer Changes, Even When the Member ID Doesn’t
Under FFS, you bill the state Medicaid agency or its fiscal agent directly.
As for managed care, the state pays a private plan, which becomes your payer. You now bill the MCO with a different claim address payer ID, submission portal, and often a separate EDI enrollment.
The resident’s state Medicaid member ID usually stays the same through the transition, but the payer behind it changes. Most MCOs issue their own member ID and require it on claims.
The most obvious indication of this issue is denial. The claim filed to Medicaid FFS becomes rejected, usually with an explanation that the individual is covered by managed care. On the remittance this typically appears as CARC 109, often paired with a remark directing you to the member’s managed care plan. There is nothing wrong with the claim; FFS just no longer has liability for the resident.
If your team reads that denial as a data error and resubmits it to FFS, the second claim bounces the same way, and days tick by. That lost time matters because the MCO often has its own timely filing limits, leaving less time to correct and submit the claim to the right payer.
The Effective Date is Where Money is Lost
The single most important detail in a transition is the effective date. Medicaid managed care enrollment is frequently back-dated, often to the first of a month, which means the plan may be responsible for dates of service you already billed under FFS.
Two things follow. First, FFS payments for the retroactive period can be recouped, showing up later as takebacks against your remittance. Second, the same dates now have to be rebilled to the Medicaid managed care organization. The transition date governs, so the longer it takes to notice, the more retroactive cleanup you inherit. Reconciling those overlapping dates cleanly, before recoupments and rebills collide, is the heart of the work.
In most states you should void or adjust the affected FFS claims yourself – a passive takeback lands on a later remittance and makes reconciliation harder. Void first, then rebill the plan, so the two sets of dates never overlap in an open status.
Reduce claim denials due to missed changes in benefit coverage with an automated insurance tracking tool
Medicaid Prior Authorization Does Not Carry Over
Prior authorization obtained under FFS does not automatically transfer to the Medicaid managed care organization. These set their own authorization and level-of-care rules, and a stay that was fully covered under FFS can suddenly need the plan’s approval, sometimes retroactively.
These two facts sound contradictory, but they work together: the FFS authorization does not transfer permanently, yet the plan is generally required to honor it temporarily. That temporary window is your runway to obtain the plan’s own approval.
Most states and plans provide a continuity-of-care period that requires the MCO to honor existing services and authorizations for a transition window after enrollment. The length varies by state and plan, commonly falling in the range of 30 to 90 days.
For dual-eligible residents, remember that continuity of care on the Medicaid side does not extend the Medicare authorization or benefit period – those clocks run separately.
Network Status and Timely Filing
Two more items decide whether the rebill pays. The first is network status. Your facility has to be contracted with the specific MCO the resident was assigned to, to be paid at normal rates.
A resident can land on a plan you do not contract with, which turns a routine claim into an out-of-network problem that may require a single-case agreement or a lower payment. Escalate that case out of the billing queue immediately – a single-case agreement should be negotiated before the dates age.
The second is timely filing. Each MCO sets its own filing limit, and it is often tighter than the FFS deadline you are used to. Many plans and state contracts do provide an exception for retroactive enrollment or coordination of benefits, running the clock from the date of the other payer’s denial or remittance – but that exception is not universal, it usually has its own shorter deadline, and typically requires you to attach the FFS denial as proof. Do not assume you have it. Confirm the exception in the plan’s provider manual, and if you rely on it, submit the remittance showing the FFS denial with the claim.
Because the practical clock can start around the transition, a switch discovered late can blow the filing window on dates the plan would otherwise have paid. Late discovery is the most common reason a recoverable transition becomes bad debt.
Don't miss our next article
What To Do About the Ones Already in Your AR
Before you change your process, work the backlog you already have.
Start by pulling every denial in the last 90-180 days carrying CARC 109 – that is your main list. Then re-verify the current coverage for every active Medicaid resident, because a back-dated enrollment can exist on residents whose claims have not been submitted yet.
That second step is the one teams skip, because re-verifying a full census by hand is not realistic. A platform that already re-verifies every active resident on a schedule simplifies it into a transparent report.
Continuous Changes Tracking
Every item above is manageable when you catch the transition and Medicaid eligibility changes within days. The failure mode is always the same: the switch is discovered weeks later, through a denial, after authorizations lapsed and filing clocks ran. Manual, once-a-month eligibility checks are simply too slow to catch a change that can be back-dated and silent.
This is where continuous Medicaid coverage verification and tracking pays for itself, and it is the part of the workflow worth investing in. An automated platform like Approved Admissions re-verifies every active resident on a set schedule and compares each result to the last, so a move from FFS into a managed-care plan is flagged as a specific, detailed change, routed straight to the responsible biller.
Approved Admissions synchronizes patient lists daily from EHR and billing platforms, so new admissions and discharges are always reflected, and it flags Managed Medicaid enrollments and terminations specifically, which is exactly the transition described in this article.
From there, staff can confirm the effective date, re-route the claim to the correct MCO, and invoke continuity of care while there is still time.
A Quick Checklist When You Spot a Transition
When a resident moves from FFS to managed care, work the change in order:
- confirm the enrollment effective date; identify the MCO, its payer ID, and its submission channel;
- check whether your facility is in network with that plan;
- secure or transfer authorization and invoke continuity of care with documentation;
- note the MCO’s timely-filing limit;
- rebill the affected dates to the plan and watch for FFS recoupments;
- and update the resident’s payer in the EHR so nothing else routes to the wrong place.
Worked in that sequence, even a retroactive switch stays a manageable cleanup rather than a lost claim.


