EVV billing and EVV compliance are not the same thing.

The 21st Century Cures Act (Public Law 114-255) established the federal requirement for electronic visit verification in Medicaid home care. States have been rolling out EVV systems since 2020, with personal care services and home health phased in on different timelines. By now, most agencies running Medicaid personal care are operating under a live EVV requirement, and most of them have built some kind of EVV process into their daily operations.

So when an EVV claim denial shows up on the remittance, the first reaction is usually confusion. The caregiver checked in. The app logged the visit. Why is it denying?

The answer almost always comes down to one distinction: EVV compliance and EVV billing are not the same job. Compliance is about whether the visit record exists. Billing is about whether that record reached the right system, in the right format, within the right window, and matched the claim correctly. An agency can satisfy EVV requirements from a regulatory standpoint and still have its claims denied because the billing side of the EVV loop broke down somewhere.

What EVV actually requires — and where the billing layer sits on top of it

Federal EVV requirements set a minimum standard: a verifiable electronic record of who provided the service, what service was provided, when it started and ended, where it was provided, and who received it. States implement this through their own EVV systems — either a state-managed system that agencies are required to use, or an open-model system where agencies can use their own EVV technology as long as it interfaces with the state's aggregator.

That aggregator is where most EVV billing problems originate. The aggregator is the clearinghouse between your agency's EVV data and the state Medicaid system or managed-care organization. Your caregiver checks in on the app. The app records the event. That event then needs to be transmitted to the aggregator in the correct format, within a specific window, with the correct matching identifiers. If any of that chain breaks, the aggregator does not have a complete record for the visit — even if your internal system shows it as complete.

When you build a claim for that visit and submit it, the payer compares the claim against what the aggregator has. If the aggregator has no record, or a partial record, or a record that does not match the claim, the claim denies.

The four EVV billing gaps that produce most of the denials

Transmission failures between the agency's system and the aggregator

This is the most common gap, and the hardest to catch because it is invisible inside the agency's own software. The visit shows as completed in the EMR. The caregiver's check-in and check-out are both logged. But the transmission to the aggregator failed — a connectivity error, a format mismatch, a rejected record that nobody reviewed — and the aggregator never received it.

The agency submits the claim assuming the EVV data is behind it. The payer checks the aggregator, finds nothing, and denies. The denial code comes back, usually referencing EVV non-compliance, and now the agency has to trace back to a visit that happened weeks ago and figure out why the transmission failed.

The fix: compare your EMR's completed visit log against the aggregator's received records before building each billing cycle's claims. Not after. Before. Any visit that is in your system but not in the aggregator is a potential denial that you can still prevent.

Location and timestamp flags

EVV systems verify not just that a visit happened, but where it happened and when. If the app registers an unusual GPS location — the caregiver's phone showed them somewhere other than the client's address — the visit may be flagged as non-compliant, even if the caregiver was physically at the correct location and the app simply had a bad reading.

The same issue applies to timestamps. A caregiver who checks in three minutes early or forgets to check out until after they have driven away creates a record that does not exactly match the authorized visit time. Some payers will accept small variances. Others will flag or deny.

These flags pile up quietly. A billing staff member reviewing claims does not see them unless they know to look in the aggregator portal, not just the agency's EMR. The EMR may show the visit as complete. The aggregator has a flag on it. The claim goes out, the flag comes back as a denial.

Paper backup visits that never made it into the electronic record

Most state EVV systems have a paper backup process for visits where the caregiver could not use the electronic method — connectivity issues in rural areas, a client who does not allow phone use in the home, a technology failure. The backup process is supposed to be temporary, with the visit record manually entered into the EVV system afterward.

In practice, paper backup visits are a consistent source of EVV billing gaps. The visit happens. The paper form is collected. The manual entry never happens, or happens late, or happens with incomplete data. The claim goes out. The aggregator has no record of that visit, or a late-entered record with mismatched data. Denial.

Payer-specific format and window requirements on top of the state standard

State EVV requirements are the floor, not the ceiling. Managed-care organizations that administer Medicaid waiver programs frequently impose their own requirements on top of the state standard. A different submission window. A different set of required data fields. A different matching logic between the EVV record and the claim.

An agency billing three managed-care organizations in the same state may be handling three different EVV billing specifications, plus the state Medicaid fee-for-service standard, simultaneously. The agency's EVV process may be fully compliant with the state standard and still be missing a managed-care-specific requirement that causes denials with that particular payer.

This is not documented in any single place. It requires knowing each payer's EVV billing requirements specifically and verifying that your submission process satisfies all of them — not just the baseline.

Why the retrofit gap creates its own category of billing risk

Many agencies that were operating before their state's EVV rollout went through an implementation period where they used a separate EVV system that was not fully integrated with their existing EMR. The EVV system captured visit records. The EMR continued to manage scheduling and billing. The two systems had to be manually reconciled to make claims work.

That retrofit architecture creates a structural gap. Even after full EVV implementation, agencies that built their billing workflow around a disconnected EVV system often have a reconciliation step that is manual, error-prone, and easy to skip when the billing team is busy. The result is a category of EVV billing gaps that is not about technology failure — it is about a process that requires human attention to close and does not always get it.

Agencies that fully integrated their EVV solution with their EMR at implementation are generally better positioned here, but even integrated systems have edge cases: visit types that fall outside the integration, client locations that require exceptions, caregiver situations that require manual handling. Every exception is a potential gap.

What to actually do about it

The agencies that keep EVV billing gaps low do a few things consistently that the agencies with persistent EVV denials do not.

They run an EVV exception report before each billing cycle, not after. The aggregator portal — or the integration between your EMR and the aggregator — will usually show you which visits have flags, transmission failures, or missing records. Reviewing that report before building claims lets you catch and resolve exceptions while there is still time to do so.

They resolve paper backup visits within 24 to 48 hours, not at the end of the week. The longer a paper backup visit sits unentered, the harder it is to reconstruct correctly. The caregiver moves on to other visits. The details get fuzzy. Manual entry made from a three-day-old paper form is more likely to have mismatched timestamps or missing fields.

They know their payers' EVV billing requirements specifically, not just the state standard. For each managed-care organization in the payer mix, someone at the agency should know the submission window, the required data fields, and the matching logic. That information should be written down and updated when payers change their requirements — which they do, and not always with advance notice.

They track EVV denial rate by payer, not just in aggregate. If one managed-care organization is generating most of the EVV denials, that is a specific signal that something about the EVV billing process for that payer is wrong. Seeing it broken out by payer makes the root cause findable. Seeing it only in aggregate makes it look like a general EVV problem, which is harder to fix.

Where this fits in the broader billing picture

EVV billing gaps are one category of the margin leak that affects home-care agencies — alongside unbilled hours, lapsed authorizations, and rate mismatches. For a full view of how those leaks interact, see the overview of where home-care margin leaks. For agencies that also want to understand how EVV denials fit into the broader denial management picture, the piece on why home-care claims get denied covers the full denial landscape.

The practical point is that EVV billing gaps are fixable, but they require a process that looks at what the aggregator received — not just what the agency's system recorded. Those are two different data sources. The gap between them is where the denials live.