Ohio home-care margin recovery: when the visit happened and Sandata never saw it.

Ohio is a state where a delivered visit can be denied for a reason that has nothing to do with the care. The state runs a centralized Sandata EVV aggregator, and under its no-match-no-pay policy a claim is denied outright if it does not match a verified visit at Sandata. There is no pay-and-chase grace period to lean on. For a thin-margin attendant-care book, that turns Sandata visit maintenance from a back-office chore into the difference between billed and collected.

This page is about where money leaks in Ohio specifically — across the Sandata hard edits, the alternate-EVV data feeds, and the 2026 NextGen MyCare managed-care shift — and why catching it means reading your data against the state's matching rules rather than trusting that a captured visit got paid.

One aggregator, and a claim that has to match it

Ohio mandates Sandata as the state EVV system of record and aggregator. Agencies that prefer their own system can use an Alternate EVV vendor, but the visit data still has to reach the Sandata Aggregator and validate there before a claim against it can pay. That single point of truth is what makes Ohio distinctive. Capturing the visit in your own EVV database is not enough; it has to land at Sandata, in a matched state, or the claim does not pay.

Under Ohio's no-match-no-pay policy, there is no soft landing. A claim that does not match a verified Sandata visit, and does not carry a valid exemption, is denied at adjudication. The most common way money leaks in Ohio is mundane and entirely preventable: a visit that was genuinely delivered simply did not sync to Sandata in time, or synced with a data element that did not match the claim, and the claim denied. For alternate-EVV agencies whose third-party data has to feed cleanly into Sandata, that sync is the whole ballgame.

The hard edits arrived in waves

Ohio did not flip every program to no-match-no-pay at once. The hard edits phased in by program — home health services first, then DODD waivers, then MyCare — through 2025 and into 2026. The practical effect for a multi-program agency is that the same Sandata-matching discipline now applies across most of the book, but it arrived on different dates for different lines, which is exactly the kind of timing detail that lets unmatched claims slip by during a transition window and never get reworked.

That is the trap. The caregiver showed up. The clock-in happened. But the visit did not reconcile at Sandata, and under no-match-no-pay the claim was denied at adjudication, not flagged for a fix. Nobody did anything wrong on the floor. The money is lost in the sync, not in the care.

NextGen MyCare reshuffled the managed-care lane

On January 1, 2026, Ohio launched NextGen MyCare, replacing the prior MyCare Ohio program for dual-eligible members. It went live first in the legacy MyCare counties and began rolling out statewide on April 1, 2026, moving former Ohio Home Care, PASSPORT, and related enrollees into a new managed-care structure with a new set of plans. Any time who-authorizes and who-pays changes for a population, authorizations re-key and the reconciliation gap widens — and that is precisely when unmatched and underpaid claims accumulate.

Where the margin actually leaks in Ohio

From the way Ohio wires Sandata, the hard edits, and managed care together, the recoverable losses cluster in a few predictable places:

• Sandata sync failures. A visit that never reached the Sandata Aggregator in a matched state by billing time — the single most Ohio-specific denial under no-match-no-pay.
• Alternate-EVV feed gaps. For agencies on a third-party EVV system, visit data that does not transmit cleanly to Sandata, or transmits with a data element that does not match the claim.
• Phase-transition slippage. Claims caught between hard-edit go-live dates across home health, DODD, and MyCare lines that denied during a transition window and were never reworked.
• NextGen MyCare re-keying. Authorizations and member records moved during the 2026 managed-care transition, producing claims that fall outside the current authorization or route to the wrong plan.
• Silent underpayments. Claims that pay below the contracted or authorized amount — never flagged as a denial, surfacing only when payment received is compared to payment expected, line by line.

None of these show up in the scheduling view. The schedule says the visit happened; the EVV app says the caregiver clocked in. It is only when you reconcile the Sandata transactions against the actual claim lines, authorizations, and remittances that the gap appears.

Why a read-only recovery layer is the right tool for this

Reeve is built for exactly this reconciliation. It sits read-only over whatever EMR and EVV export an agency already runs — WellSky, AxisCare, HHAeXchange, AlayaCare, or any other system — and compares what was delivered against what was authorized against what was actually paid. For an Ohio agency, that means lining up the Sandata visit transactions, the claim lines, and the prior authorizations and surfacing every place they fail to reconcile: the sync failures, the alternate-EVV feed gaps, the phase-transition slippage, the NextGen MyCare re-keying, and the silent underpayments.

Because Reeve is read-only and neutral across every EMR, it has no stake in which system you run, and it never writes to your billing workflow without your control. It does not sell scheduling or EVV, so 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 unsynced visit, the mismatched element, the re-keyed authorization — and the ones still inside the filing window are the ones you can rebill now.

This is the same engine described across the rest of the site. For the mechanics of how EVV gaps become denials, see EVV billing for home care. For the broader map of revenue loss, see where home-care margin leaks. And for the claim-denial mechanics, see home-care claim denials and recovery.

What the free Ohio Margin Teardown does

The way to find out whether Sandata sync failures and the NextGen MyCare transition are draining your margin is to look — on 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 unmatched Sandata visits, the alternate-EVV feed gaps, the transition slippage, and the underpayments. It is free, it is yours to keep whether or not you ever work with Reeve, and 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.