Three states moved EVV from soft warnings to hard claim denials in Q1

Three state EVV cutovers landed in the same quarter, and the operational pattern is the same in each: soft-warning enforcement (where missing or out-of-tolerance EVV records generated a flag but the claim still paid) became hard-edit enforcement (the claim bounces). For multi-state agencies, Q1 2026 is the quarter where stale EVV setup turns into AR exposure.

The three cutovers

• Michigan — January 1, 2026. Michigan Medicaid hard-edit enforcement is fully live. Missing electronic visit verification, mismatched start/end times outside tolerance, missing GPS data, or unverified service codes all bounce claims rather than warning.
• Missouri — April 2026. Hard edits begin in April. The Missouri aggregator's tolerance windows are tighter than the federal floor; agencies that operated comfortably under the soft-edit window need to retest.
• Illinois — March 2, 2026. Illinois cut over to HHAeXchange as the state EVV aggregator. New integration spec, new tolerance rules, new submission pathway. Existing integrations to the prior aggregator broke at cutover.

Why this hurts multi-state agencies more

Single-state agencies have one rulebook to track. Multi-state agencies have to maintain per-state EVV configurations: different midnight boundaries (NC's 00:01:00, others' 00:00:00), different location radius requirements, different late-check-in tolerances, different state-aggregator submission formats, sometimes different caregiver/patient ID schemas.

When a state changes from soft-edit to hard-edit, every gap in your per-state setup that didn't matter last month suddenly matters. Visits that completed in February but post-process in April with the new rules can rejection at the state aggregator and never make it to the Medicaid payer.

What your scheduling and EVV team needs to do

1. Pull state-by-state EVV exception reports for the last 90 days. Look for the patterns the soft-edit warnings flagged — those are the ones that become hard rejections under the new rules.
2. Verify state-specific tolerance windows in your EVV configuration. If you can't tell what your late-check-in tolerance is set to in Michigan vs Missouri, you're exposed.
3. Test the Illinois HHAeXchange integration end-to-end with a real visit before relying on it for production. The cutover broke the prior pathway; the new one needs validation.
4. Confirm overnight visit handling. Per-state midnight boundaries are easy to get wrong. A 10pm–6am Illinois visit needs to handle the state's split rules; the same visit in Michigan needs different rules.

What we built for this

Carelytic's EVV pipeline is per-tenant, per-state. Late check-in, early check-out, minimum visit duration percentage, location radius, and midnight boundary are all configurable per state. Overnight visits stay as one visit on the calendar (one Clock In, one Clock Out for the caregiver) but auto-split at the state's midnight boundary when exporting to the state aggregator and to billing.

The bigger lesson: state EVV rules are a moving target. The soft-edit period is when agencies should be hardening their workflows; the hard-edit cutover is when undealt-with gaps become AR aging. The states that just hardened in Q1 are a preview of states that will harden in Q2 and Q3 (Texas, Florida, and Pennsylvania are all on the watchlist).