EVV claim denials in home care: why they happen, and how to recover the money.

For years, an Electronic Visit Verification (EVV) record was something agencies kept because the state asked for it. Then it became the thing that decides whether a claim pays. Across the country, Medicaid programs now compare the EVV record against the claim. When the two do not reconcile, the claim denies, even if the caregiver showed up, did the work, and documented it. For a thin-margin personal-care book billed in small units, those denials are not a paperwork nuisance. They are the margin.

This guide is the operator's version: where the EVV rule came from, what every state actually checks, the handful of reasons clean visits still deny, and what it takes to turn a denial back into a paid claim.

Where the EVV mandate came from

EVV is federal. It comes from Section 12006(a) of the 21st Century Cures Act, signed into law on December 13, 2016. The law required state Medicaid programs to implement EVV for personal care services by January 1, 2020, with a good-faith-effort extension available to January 1, 2021. Home health care services followed, with a deadline of January 1, 2023. States that did not comply faced reductions in their federal medical assistance percentage (FMAP). That is why EVV looks different state to state but exists everywhere. The federal floor is uniform. The implementation is each state's own.

What EVV verifies is also federally defined. Every compliant system has to capture six data elements for each visit:

• The type of service performed.
• The individual receiving the service.
• The date of the service.
• The location of service delivery.
• The individual providing the service.
• The time the service begins and ends.

Those six elements are the federal common denominator. The denials come from how each one has to line up before payment is released: with the claim, with the authorization, and with the state's aggregator.

Open, closed, and aggregator models, and why it matters

States implement EVV in different shapes. Some run an open or provider-choice model, where an agency can use any compliant EVV vendor as long as the data reaches the state. Others mandate a single state vendor or aggregator that every visit must flow through. And many managed-care states layer plan-level requirements on top, so a single agency can be feeding visits into more than one system at once.

The model matters because it decides where a visit can get lost. In an aggregator state, a visit that never reaches the aggregator in an accepted, matched status is invisible to the payer no matter how well it was documented in your own software. In a multi-plan state, a visit accepted by one plan's portal can still fail another plan's authorization rules. The federal six elements are constant; the path each visit travels is not.

The denial triggers that cost agencies the most

Most EVV-related denials trace back to a small set of mismatches. Knowing them is the first step to catching them:

• The visit never reached the aggregator. A capture that stayed in the agency's own EVV system, or failed to post in an accepted status, leaves the claim with nothing to match against.
• Unit mismatches. The units billed do not equal the units on the accepted EVV visit. This is one of the most common and most preventable EVV denials.
• Time discrepancies. The clock-in and clock-out times on the EVV record do not align with the visit billed, often because of a manual edit made after the fact.
• Location or geofence failures. The captured location does not match the expected service location, flagging the visit for review or denial.
• Authorization drift. The service code, units, or dates fall outside the approved prior authorization. The EVV record may be fine, but the claim is outside what was authorized.
• Excessive manual edits. Several states now track the share of visits corrected by hand and penalize agencies that lean on edits instead of accurate capture at the point of care.

None of these reflect a failure of care. They are reconciliation failures: the gap between what happened on the floor and what the payer's systems can confirm.

How EVV denials become recoverable revenue

Most EVV denials are recoverable, because the underlying service was real. Recovery is a reconciliation exercise: line up the EVV visit transactions against the claim lines and the prior authorizations, find every place they fail to match, fix the ones that can be fixed, and rebill the ones still inside the filing window.

In practice that means surfacing the unmatched visits, the unit mismatches, the time and location flags, and the authorization drift, then triaging by recoverability and by how much filing time is left. A denied claim that can be corrected and resubmitted before the timely-filing deadline is money you still have a right to. A denial that ages out of the window is gone. The difference between the two is almost always whether anyone reconciled it in time.

This is the core of what Reeve does. It sits read-only over whatever EMR and EVV export an agency already runs, whether that is WellSky, AxisCare, HHAeXchange, AlayaCare, or anything else. It reconciles the EVV record against the claim and the authorization, surfacing the recoverable denials with the reason attached. It does not sell scheduling or EVV, so it has no reason to look past a finding. For the specific mechanics of how a compliant visit still denies, see EVV billing for home care. For the broader picture, see where home-care margin leaks.

The takeaway for operators

EVV is not going away, and the enforcement keeps tightening. States are moving from pay-and-chase to hard edits that deny at adjudication, and several now penalize excessive manual edits. The agencies that protect their margin treat EVV reconciliation as a revenue function, not a compliance chore. They capture accurately at the point of care, reconcile EVV against claims and authorizations continuously, and rework recoverable denials before they age out. The money is rarely lost in the care. It is lost in the match.