Minnesota is in the middle of a structural change that makes margin recovery unusually time-sensitive right now. The state is replacing Personal Care Assistance (PCA) and the Consumer Support Grant with Community First Services and Supports (CFSS) under Minnesota Statutes 256B.85. DHS began implementing CFSS on October 1, 2024, and people move over at their annual reassessment. DHS extended the deadline, so individuals have until September 30, 2027 to complete the transition, and extended PCA services cannot be used after September 30, 2026. So right now an agency's book is split across the legacy PCA structure and the new CFSS structure at the same time, and a claim coded for the wrong one does not pay.
Layer Minnesota's rising EVV thresholds and its daily authorization feed on top of a program that is actively moving, and you get a state where margin leaks in places that did not exist a couple of years ago.
Minnesota Health Care Programs home-care, at a glance
- Program
- Medical Assistance under Minnesota Health Care Programs (MHCP), administered by DHS; PCA migrating to CFSS (256B.85) since October 1, 2024
- Waivers
- Elderly Waiver, Community Access for Disability Inclusion (CADI), and Alternative Care, among others
- EVV aggregator
- HHAeXchange, open-vendor model. Use the free state system or a third-party vendor that connects to HHAeXchange
- Timely filing
- 12 months from date of service, per the MHCP Provider Manual billing-policy chapter
The PCA-to-CFSS move, and why it splits the book
The transition is not a single switch. People move from PCA to CFSS one at a time, at each annual reassessment, across a window that now runs to September 30, 2027. That means at any given moment in 2026, a single agency is billing some members under the old PCA structure and some under the new CFSS structure. CFSS itself has two models, an agency-provider model where the agency employs the workers and bills, and a budget model where a Financial Management Services provider handles the employer side. A claim coded for the structure a member already left, or one they have not reached yet, falls out of step and does not pay.
This is a uniquely 2024-to-2027 Minnesota error. It did not exist before CFSS implementation began, and it will not exist after the transition closes. While the window is open, it is one of the largest sources of avoidable denials in the state.
HHAeXchange as the aggregator, with thresholds still rising
Minnesota uses HHAeXchange as its state EVV aggregator under an open-vendor model. A provider can use the free state-sponsored HHAeXchange system or a third-party EVV system that meets state requirements and connects to HHAeXchange. EVV use began December 1, 2021, DHS started monitoring compliance on September 1, 2024, and the compliance thresholds escalate: 50 percent on January 1, 2026 and 80 percent on July 1, 2026.
Here is the mechanism that matters for margin. Member information and authorizations flow from MMIS into HHAeXchange daily, and the provider works claims against those loaded authorizations. When a claim is submitted, Medicaid compares the billed hours, services, and codes against the EVV visit data in the aggregator. If there is no matching EVV record, or the data conflicts, the claim can be flagged for manual review, rejected, or subject to overpayment recovery.
Note that Minnesota publishes these denial drivers in general terms rather than as a single numbered claim-edit code, so the reliable way to find them is to reconcile the EVV visit data against the loaded authorization, not to wait for one tidy remittance reason. Common drivers are mismatched program codes, authorization mismatches, overlapping time logs, and billed hours that exceed the verified EVV hours.
Where the margin actually leaks in Minnesota
- PCA-to-CFSS coding mismatches. Claims coded under the structure a member already left at reassessment, or has not yet reached. This is the uniquely 2024-to-2027 Minnesota error.
- No matching EVV record. Visits with no reconcilable EVV transaction in HHAeXchange, flagged for review or rejected.
- Billed hours over verified EVV hours. Claims billing more time than the EVV record supports, a common overpayment-recovery trigger.
- Authorization mismatches from the daily MMIS feed. Claims that fall outside the authorization that came across from MMIS on program code, units, or dates.
- Silent underpayments. Claims that pay below the expected rate, never flagged as a denial, visible only when payment received is compared against payment expected, line by line.
None of these are visible from inside the scheduling view. The schedule says the visit happened. The EVV system says the worker clocked in. It is only when you reconcile the HHAeXchange visit data against the MMIS authorization and the actual remittance that the gap appears.
Why a read-only recovery layer is the right tool for this
Reeve sits read-only over whatever EMR and EVV export an agency already runs, whether that is WellSky, AxisCare, HHAeXchange, AlayaCare, or anything else, and compares what was delivered with what was authorized and what was actually paid. For a Minnesota agency, that means catching the PCA-to-CFSS coding mismatches while the migration is still moving, the visits with no matching EVV record, the billed hours over verified hours, and the silent underpayments.
Because Reeve is read-only and neutral across every EMR, it never writes to your billing workflow without your control, and it has no reason to look past a finding that implicates a billing module. It hands you a ranked list of recoverable dollars with the reason attached, the migration mismatch or the over-billed line. The ones still inside the 12-month window are the ones you can rebill now.
This is the same engine described across the rest of the site. For the broader map of revenue loss in home care, see where home-care margin leaks. For the authorization side specifically, see home-care authorization tracking. For the full playbook on getting uncollected revenue back, see home care revenue recovery.
What the free Minnesota Margin Teardown does
The way to find out whether the CFSS migration or EVV mismatches are draining your margin is to look at a real, de-identified slice of your own data, before you spend a dollar. The Margin Teardown is a one-time, read-only read of where margin is leaking in your book: the migration mismatches, the unmatched EVV, the over-billed hours, and the underpayments. It is free, and it is yours to keep whether or not you ever work with Reeve. It carries the same 3×-or-free guarantee the rest of the engine does. If Reeve does not surface at least three times its monthly fee in recoverable margin you agree is real, you do not pay.
A free, de-identified Margin Teardown reconciles your HHAeXchange visits, MMIS authorizations, and remittances and shows you exactly what slipped. Read-only. Yours to keep.