CMS’s Medicaid Deferral Power Just Cleared Its First Court Test. There’s No Ceiling On It.
A federal court’s refusal to block a $259 million CMS Medicaid deferral against Minnesota confirmed three things compliance and finance leaders should already be planning around: no regulatory cap on deferral size, a documentation burden that falls entirely on the state, and managed care encounter data now squarely inside the review.
On April 6, 2026, a federal court denied Minnesota’s motion to block a $259 million CMS Medicaid deferral, the first court ruling on a mid-stream challenge to this enforcement tool. The court found no regulatory cap on deferral size and held that an approved corrective action plan does not stop a deferral. The burden falls on the state to prove its claims are allowable. CMS has since deferred $1.3 billion from California and requested Minnesota’s managed care encounter data. Minnesota’s own deferral has grown to $350 million, and both sides must report to the court by September 3, 2026.
A $259 million deferral, five legal theories, and one denied injunction
On February 25, 2026, CMS notified Minnesota that it was deferring more than $259 million in federal Medicaid matching funds, citing concerns about the allowability of expenditures across 14 high-risk service categories, including personal care, home and community-based services, and claims from providers flagged as high-risk for fraud or aberrant billing. Minnesota called the deferral more than fifteen times larger than any prior deferral it had received.
The state sued CMS on five legal theories: a Fifth Amendment due process claim, an Administrative Procedure Act claim, a Spending Clause claim, and an ultra vires theory, and sought a preliminary injunction to force CMS to release the funds while the case proceeded. On April 6, 2026, the court said no in State of Minnesota v. Oz, Case No. 26-cv-1701 (D. Minn.).
The court’s own framing: the deferral is an investigative step “comparable to an audit,” not a final decision, and states seeking emergency relief “will face substantial procedural hurdles.”
The court didn’t just deny an injunction. It defined how far CMS can go.
The court was explicit that its ruling reflects the record “at this stage” and does not foreclose Minnesota ultimately prevailing. But for any state, or any plan paid through that state’s Medicaid dollars, the practical takeaway is the same: courts are not inclined to intervene early, and the documentation burden sits with the party being investigated.
Minnesota was the test case. It was not the only target.
Timeline since the April 6, 2026 ruling.
- Apr. 29, 2026CMS deferred an additional $91 million from Minnesota, bringing the state’s total to $350 million.
- May 7, 2026The court paused the litigation for 120 days so CMS and Minnesota could attempt to resolve the deferral outside of court. A status report is due September 3, 2026.
- May 13, 2026CMS deferred $1.3 billion from California, the largest deferral in agency history, using two estimation methods for the home-care portion that CMS did not fully explain.
- OngoingCMS has sent program-integrity information request letters to Florida, Maine, and New York, a step that has preceded compliance action or deferral in other states.
This is not a states’-rights story. It is a documentation story.
Most coverage of this ruling reads it as a states’-rights story: an aggressive federal posture, a state pushing back, a court declining to intervene early. Payer readers should read it as a documentation story instead. The court did not decide whether Minnesota’s claims were actually improper, and it said so explicitly. It ruled only that CMS does not have to be right yet to freeze the money, and that the burden falls on the state to prove otherwise, for as long as CMS keeps asking questions.
The detail that should get a compliance leader’s attention is not the dollar figure. It is that CMS explicitly asked Minnesota for Medicaid fee-for-service and managed care encounter data to help determine whether the deferred claims were allowable. A plan’s own reporting becomes evidence in a fight it is not formally a party to.
CMS does not have to be right yet to freeze the money. The state has to prove otherwise, for as long as CMS keeps asking.
One court ruling, four functions carrying real exposure
Compliance
Needs a live monitoring process for CMS program-integrity inquiries, deferrals, and withholdings in every state of operation, not just the states already in the news.
Finance / Actuarial
Cannot assume a state’s approved corrective action plan removes deferral risk. Cash-flow contingency planning needs its own line for state Medicaid funding delay.
Data governance / IT
Encounter data for CMS-flagged high-risk categories, home care, behavioral health, NEMT, needs to be complete and reconcilable before a state-level request arrives.
Legal / Government relations
Should track Minnesota v. Oz and related litigation directly, since the ruling sets practical precedent for how courts will treat deferral challenges elsewhere.
The ruling didn’t create new law. It confirmed how much room CMS already has.
No single function owns this on its own. The table below assigns responsibility; the list after it sequences the work.
| Function | Required response | Evidence to retain |
|---|---|---|
| Compliance | Track CMS program-integrity inquiries, deferrals, and withholdings in every state of operation; build an early-warning process for state-level information requests tied to Medicaid managed care. | Log of state-level CMS inquiries and their status, updated as new states are contacted. |
| Finance / Actuarial | Model capitation and cash-flow exposure if a state’s Medicaid funding is deferred or delayed; do not assume an approved state corrective action plan removes deferral risk. | Contingency cash-flow scenario covering a state Medicaid funding delay of 90 days or longer. |
| Data governance / IT | Confirm encounter data completeness, timeliness, and reconcilability against claims history for CMS’s identified high-risk service categories before a state-level request surfaces gaps. | Encounter data completeness audit for home care, behavioral health, NEMT, and other flagged categories. |
| Legal / Government relations | Monitor Minnesota v. Oz and related litigation for precedent affecting the plan’s own states; assess exposure if the plan’s state is added to CMS’s review list. | Litigation tracking memo, updated after the September 3, 2026 status report. |
Within 7 days
Confirm whether your state(s) of operation are named in a CMS deferral, withholding, or program-integrity information request.
Within 30 days
Audit encounter data completeness for CMS’s identified high-risk categories in your state(s). Find gaps before a state-level request surfaces them.
Within 60–90 days
Build a standing capitation and cash-flow contingency scenario for state Medicaid funding delay. Monitor the September 3, 2026 status report. These are editorial recommendations, not confirmed regulatory requirements.
The open question is how far this pattern travels. California’s deferral is already larger than Minnesota’s by a factor of five, using estimation methods CMS has not fully explained. Whether the September 3, 2026 status report produces a negotiated resolution, a narrowed deferral, or an escalation will be the first real signal of where this enforcement posture settles.
Plans in states with large or fast-growing home care, behavioral health, or NEMT utilization, the same categories CMS has flagged across Minnesota, California, and its inquiry states, should treat this edition as a preview rather than someone else’s dispute. The states not yet named are not necessarily states that will stay unnamed.
Questions payer leaders should ask
- 01Is our state one of the states CMS has already contacted (Minnesota, California, Florida, Maine, New York), or could it plausibly be next?
- 02If our state’s Medicaid program were deferred federal funds, do we know how quickly that would affect our own capitation payment timing?
- 03Can we produce complete encounter data for behavioral health, home care, NEMT, or other high-risk categories on short notice, across multiple rounds of requests?
- 04Does our compliance planning assume that an approved corrective action plan stops a deferral? The Minnesota ruling says it does not.
- 05Who in our organization is tracking Minnesota v. Oz and the September 3, 2026 status report deadline?
- 06Are we prepared for a documentation cycle that could extend indefinitely rather than close after a single response?
Sources
- KFF: What to Know About Recent Federal Actions Involving State Medicaid Program Integrity (published June 9, 2026, updated July 16, 2026)
- Snell & Wilmer: Federal Court Upholds CMS Medicaid Funding Deferral — Key Takeaways (April 30, 2026)
- State of Minnesota v. Oz, Case No. 26-cv-1701 (D. Minn., Apr. 6, 2026)
- HHS.gov: HHS Defers More Than $1 Billion in Medicaid Payments to California, Minnesota Pending Review of High-Risk Claims in Crackdown on Fraud (July 21, 2026)
Until next week, stay briefed.
Frequently asked questions
What is a Medicaid funding deferral?
A deferral is CMS pausing federal matching payments for state Medicaid claims already made, pending state documentation proving the claims are allowable. Unlike a withholding, which targets future funds and requires a hearing first, a deferral applies to past expenditures and can be issued without a prior hearing.
Did the court rule that Minnesota committed fraud?
No. The court did not decide whether Minnesota’s claims were actually improper. It ruled only that Minnesota had not shown it was likely to succeed on its legal challenge or that it would suffer irreparable harm before the underlying dispute is resolved.
Is there a limit on how much CMS can defer?
The court found no regulatory cap on deferral size and no bar on CMS pursuing a deferral and a withholding against the same state at the same time.
Does an approved corrective action plan protect a state from a deferral?
Not necessarily. CMS approved Minnesota’s 17-element corrective action plan, and the deferral remained in place regardless.
What happens next in this case?
CMS and Minnesota must submit a status report to the court by September 3, 2026, under a 120-day litigation pause intended to give both sides time to resolve the deferral outside of court.