# Reading the EVV Status & Compliance dashboard

> The EVV Status page confirms EVV is live and reconciles verified visits against what you billed, so you catch denials before DODD does.

Canonical: https://enmantle.com/help/evv-status-and-denials · Section: Time Clock, GPS & EVV · Updated: 2026-09-20

Once EVV is turned on, the `EVV Status` page is where you confirm it's live and reconcile your verified visits against what you billed — before DODD does the same and denies a claim. This guide walks the page and the four things it watches for.

## Check that EVV is enabled

Under Billing, open `EVV Status`. At the top it reads "EVV is `enabled`" or "EVV is `not yet enabled`," with a `go-live` date once it's live. Enablement is "managed by the platform team and gated on Sandata certification" — Enmantle is a DODD-approved alternate EVV vendor that submits to Sandata. Below, the `Provider accounts` section lists each `Medicaid Provider ID`; it reads `None configured yet.` until your accounts are set up.

## The EVV Compliance & Denials workspace

Under the status panel sits the `EVV Compliance & Denials` workspace — "Read-only reconciliation between Electronic Visit Verification and billing for the selected service-date window." Set the `Start` and `End` dates (it defaults to the last 30 days). Every section stays empty while EVV is not yet enabled, so an empty page usually means EVV isn't certified for your agency yet.

## The four sections

- `Verification summary` — active EVV visit counts by status, plus a `Not verified but billed` list: the rows the EVV gate flags because you billed them before the visit was verified. A `Total visits` count sits up top.
- `Units mismatches` — "Billing rows whose billed units exceed the units the verified visit supports — a DODD denial risk." It compares `Billed units` against `Visit units`.
- `Post-lock de-verifications` — locked billing rows whose visit is no longer verified — "a submitted claim now at eMBS-66 risk."
- `EVV denials` — DENIED claims that came back with an EVV-related eMBS reason code (`66`, `70`, or `71`), joined to the current visit status.

## Work it before you submit

1. Start with `Verification summary` and clear the `Not verified but billed` rows — wait for verification, correct the visit, or leave the row off the invoice.
2. Fix any `Units mismatches` so billed units match what the verified visit supports.
3. Check `Post-lock de-verifications` for claims you've already submitted that lost verification, and follow up.
4. For anything under `EVV denials`, read the reason code, fix the source, and re-bill.

> This dashboard is your early warning. Every row here is a denial you can prevent or recover — and it's far cheaper to clear it here than to chase it after eMBS bounces the claim.

## Next steps

- Get a client ready first: [EVV readiness for a client](/help/evv-readiness-for-a-client).
- See where billing rows come from: [From clock-ins to a clean eMBS invoice](/help/clock-ins-to-embs-invoice).
- The rules behind the dashboard: [Ohio DODD EVV, in plain English](/ohio-dodd-evv).