Missouri EVV Explained: Rules, Common Mistakes, and How to Stay Compliant
If your agency bills Missouri Medicaid for personal care or home health services, Electronic Visit Verification (EVV) just went from a background compliance task to the thing standing between you and getting paid. Missouri’s Electronic Visit Verification Aggregator Solution (EAS), run by Sandata Technologies, moved from soft warnings into real, live claim denials on April 1, 2026. This guide breaks down what changed, exactly what’s causing denials, and what your agency needs to do this week to stay ahead of it.
What Is Missouri EVV and Why Did the Rules Just Change?
Missouri has required EVV for Medicaid-funded personal care and home health services since January 1, 2021, with visit data flowing into Sandata’s EAS since November 8, 2021. What’s new in 2026 isn’t EVV itself — it’s claims validation. Now, MO HealthNet (MHD) checks every EVV-required claim against the visit data sitting in EAS before it decides whether to pay it. If the two don’t match, the claim doesn’t pay.
The Soft Launch vs. Hard Launch Difference
- Soft launch — January 7, 2026: MHD started comparing claims to EAS visit data, but nothing was denied yet. Mismatched claims still paid, flagged with an informational alert on the Remittance Advice so agencies could see what would have failed once hard edits took effect.
- Hard launch — April 1, 2026: The warnings became denials. Claims for dates of service April 1, 2026 and after, with no matching verified visit in EAS, are denied outright — no grace period, no informational-only notice. (MHD hard launch bulletin)
If your agency treated the soft-launch warnings as noise instead of a preview, this is the section to read twice.
Which Missouri Providers Are Affected — and When?
The hard launch isn’t hitting every provider type at once. MHD is rolling it out in phases:
| Hard Edit Date | Provider Type(s) | Services Covered |
|---|---|---|
| April 1, 2026 | 26 and 28 | Personal care, advanced personal care, consumer-directed services, homemaker, chore, respite (DSDS-authorized) |
| May 1, 2026* | 58 | Home health care services |
| June 1, 2026* | 85 | Department of Mental Health, Division of Developmental Disabilities (DDD) services |
*MHD’s own bulletins have stated only that timing for the type 58 and 85 phases “will be provided at a later date.” The May 1 / June 1, 2026 dates above come from the Missouri Alliance for Care at Home, an industry association, not a confirmed MHD bulletin. If your agency falls under provider type 58 or 85, treat these as unconfirmed planning dates and verify current status directly with MHD or MMAC before assuming your exact denial-start date.
If you’re a provider type 26 or 28 agency, the hard edits are live now. If you’re type 58 or 85, treat the soft-launch period you’re currently in as your dress rehearsal — the same rules that just hit personal care agencies are coming for you next.
Does This Apply to Managed Care Plans Too? (Home State Health, Healthy Blue, UHC Community Plan)
Short answer: yes, in practice, even though the EVV claims validation bulletins are written for the MO HealthNet fee-for-service program. MHD’s own guidance notes that fee-for-service EVV policy “may apply to the managed care program, as well” — the three MO HealthNet managed care plans (Home State Health, Healthy Blue, and United Healthcare Community Plan) set their own specifics for things like prior authorization and claims submission, but the underlying requirement — that a visit has to exist and be verified in EAS — runs through all of them. Don’t assume a managed care member’s claim is exempt just because it’s not going through fee-for-service.
What Data Has to Match in Sandata EAS for a Claim to Pay?
For a claim to pass validation, it has to match a verified visit in EAS on five specific data points:
- Department Client Number (DCN)
- Date(s) of service
- Provider Medicaid ID
- Procedure code/modifier(s)
- Number of units
If any one of these doesn’t line up with what’s recorded in EAS, the claim is flagged — and under hard edits, denied.
”Verified” vs. “In EAS” — Why This Distinction Is Costing Agencies Money
Here’s the mistake tripping up a lot of agencies: having a visit show up in EAS isn’t the same as having it in verified status. If a caregiver doesn’t properly close out a shift in your EVV vendor’s app, the visit can sit in EAS unverified — and an unverified visit won’t satisfy claims validation, even though the service clearly happened. This is the single most common root cause behind “no match” denials, according to MHD’s own soft-launch trend reporting.
The Most Common Missouri EVV Mistakes That Trigger Denials
Based on MHD’s reported soft-launch trends and hard-launch denial reasons, most rejected claims trace back to a small handful of avoidable errors:
| Denial Reason | What It Actually Means | How to Fix It |
|---|---|---|
| Verified visit not found | Claim submitted before the visit reached EAS, or the vendor never sent it | Confirm your vendor transmits daily; don’t bill until the visit shows verified |
| Participant DCN does not match | The client ID on the claim doesn’t match the client ID tied to the EAS visit | Double-check DCN entry against eMOMED before billing |
| Provider ID does not match | The billing provider ID on the claim doesn’t match the ID in EAS | Verify provider registration in EAS matches your billing provider ID exactly |
| Unmatched units | A visit exists, but the units billed don’t match the units recorded | Reconcile scheduled vs. actual visit length before submitting |
Other habits worth breaking now: submitting claims on a batch schedule instead of after confirming EAS status, not logging into EAS at least weekly to catch problems early, and treating your EVV vendor relationship as “set it and forget it” instead of an ongoing check.
Getting this right isn’t really a software problem — it’s a workflow problem. It comes down to whether your scheduling, caregiver check-in, and billing systems are actually talking to each other, or whether someone on your team is manually cross-referencing EAS before every batch of claims goes out. If your EVV, scheduling, and billing all live in one platform like GEOH, that pre-bill check — confirming a visit is verified before the claim is submitted — can happen automatically instead of becoming one more manual step your billing team has to remember under a growing caseload. If you want a closer look at how this works in practice, we walked through it in our Missouri EVV Compliance webinar.
Missouri EVV Compliance Checklist — What to Do This Week
- Log into EAS at least weekly to confirm visits are arriving and reaching verified status — don’t wait for a denial to find out something’s wrong.
- Build a pre-bill check into your billing process: don’t submit a claim until the matching visit shows verified in EAS.
- Audit caregiver clock-out habits. Most “no match” denials trace back to visits that happened but were never properly closed out in the field.
- Confirm your EVV vendor sends data to EAS daily, not in batches — Missouri rule 13 CSR 70-3.320(3)(G) requires at least daily transmission.
- Know your denial codes. If you see Provider ID mismatch, DCN mismatch, or Unmatched Units on an RA, you’ll know exactly where to look instead of guessing.
FAQ
Is my provider type affected by the EVV hard launch yet? If you’re provider type 26 or 28, yes — hard edits have applied to claims with dates of service April 1, 2026 and after. If you’re provider type 58 (home health) or 85 (DDD), an industry association has reported anticipated hard-edit dates of May 1 and June 1, 2026, respectively, but MHD has not confirmed these in an official bulletin as of this writing — confirm current status with MHD or MMAC directly.
What does a “no match” denial on my RA actually mean? It means MHD couldn’t find a verified visit in Sandata’s EAS that matches the claim on all five required data points (DCN, date of service, provider ID, procedure code/modifier, and units). It doesn’t necessarily mean the visit didn’t happen — often it means the visit wasn’t verified, or a data element doesn’t line up.
Does this apply to my Medicaid managed care claims, or just fee-for-service? MHD’s guidance indicates the EVV claims validation policy is expected to extend to managed care as well as fee-for-service, even though Home State Health, Healthy Blue, and UHC Community Plan retain some flexibility on their own claims-submission specifics. Don’t assume managed care claims are exempt.
What do I do if a claim already denied for an EVV mismatch? Log into EAS, find the visit in question, and check its status and data elements against what was billed. Correct the mismatch (verify the visit, fix a DCN or unit discrepancy, etc.) and resubmit once the visit shows verified in EAS.
How often do I actually need to log into EAS? At minimum, weekly — but agencies going through the hard launch for the first time are better off checking more frequently until they’re confident their vendor’s data is consistently accurate and timely.
EVV compliance in Missouri isn’t getting simpler this year, and the agencies that treat it as a background IT task instead of a daily workflow are the ones ending up in the recoupment queue. If you want to see how GEOH brings EVV, scheduling, caregiver management, and billing together so your team isn’t manually double-checking EAS before every claim, take a look at GEOH.
Copyright © GEOH 2026
This guide is general information for Missouri home care and home health agencies and isn’t legal, billing, or compliance advice. Always verify current rules, rates, and deadlines directly with MO HealthNet (MHD) and Sandata, since Medicaid EVV requirements change.