EVV exceptions and the claims that follow: who fixes what, and when the claim can go

What is an EVV exception?

An EVV exception is a visit record that failed one of the checks the state or its aggregator runs before the visit can be matched to a claim. The visit happened, but the electronic record does not prove it the way the rule requires, so the visit cannot be billed until someone corrects the record or documents why it cannot be corrected.

The rule comes from section 12006(a) of the 21st Century Cures Act, which requires states to use EVV for Medicaid personal care services and home health services delivered as in-home visits¹. CMS describes the system as one that verifies six things about each visit: the type of service, the individual receiving it, the date, the location, the individual providing it, and the time the service begins and ends². An exception is one of those six elements missing, wrong or outside the state’s tolerance.

States had to have EVV running for personal care by January 1, 2020 and for home health by January 1, 2023, with the federal match reduced in steps, up to 1 percent, for states that missed the dates¹. That deadline pressure is why states built their matching rules tightly, and why the aggregator, not your scheduling software, has the final word on whether a visit is verified. The EVV billing page covers the system models states chose. This post is about what happens after a visit fails.

What are the common exception reasons?

Most exceptions fall into six buckets, and CMS named the first three itself: a check-in for a scheduled visit with no check-out, a caregiver who entered an incorrect EVV ID, and a check-in from an unconfirmed phone number, so the caregiver cannot be shown to have been present². The rest come from the state’s own tolerances and from the authorization behind the visit.

Every row ends with a person who is not the biller. The biller sees the exception first because it blocks the claim, but the fix almost always lives with the scheduler, the EVV administrator or the caregiver. A billing team that clears exceptions alone ends up guessing, and a guessed edit is the first thing a state reviewer reads.

Why is the claim held, and for how long?

The claim is held because the state’s claims system compares each billed visit against the verified visit data, and a visit with an open exception has no verified record to match. CMS’s bulletin describes this design in Connecticut: the EVV data, the service authorization and the claims system are integrated, and any claim that exceeds the authorized amount is reduced to the authorized amount and to the confirmed visit data². Bill an unverified visit into a system like that and the line is cut or denied, not pended for a courtesy call.

How long the hold lasts is set by the state and sometimes by the managed care plan. The window for manual edits, the cut-off for the aggregator to accept corrections and the claim’s own timely filing clock all run at once, and each state publishes its own figures, so this post gives none. What you control is the gap between the visit and the fix. An exception cleared the next day costs a day. An exception cleared at month end costs a billing cycle, and sometimes the claim.

Who owns the exception queue?

Give it one owner with a daily routine and a hand-off list. In most agencies that owner is an EVV coordinator or the scheduling lead, with the biller as the person who refuses to release a visit that is not verified. CMS put the accountability where it belongs: providers should be monitored and held accountable for exceptions to the data that must be recorded, including missing or invalid check-in and check-out data that has to be manually cleared to confirm a visit².

A workable split looks like this. Caregivers attest to times and locations the same day, by whatever method the state allows. The scheduler corrects assignments and adds unscheduled visits with the approved reason. The EVV administrator maintains phones, devices, caregiver IDs and member records in both the vendor system and the aggregator. The biller runs the schedule-to-EVV reconciliation before each batch and reports the open count, the oldest open exception and the three most common reasons every week. The reporting page shows where that line sits in a weekly report.

Which denials follow an EVV problem?

Three codes show up when an unverified or mismatched visit reaches the payer anyway. CO-16 says the claim is missing information the payer needs, and some states and plans return it when a visit has no verified record at all. CO-198 says the service went beyond the units, visits or dates the authorization allowed, which is what the over-authorization exception becomes if the biller releases it. CO-18 is the duplicate: a visit edited and resubmitted while the first attempt is still sitting in the payer’s system.

Each is cheaper to prevent than to appeal, and the prevention is the same in every case. The visit is released only when the aggregator shows it verified, the units match the authorization, and nothing for the same member, caregiver and time span has already gone out.

What should an agency owner ask for each week?

An agency owner should ask for four numbers and one list each week: visits delivered, visits verified, exceptions open and exceptions older than seven days, and the caregivers, clients or locations that generated the most exceptions, named, so the fix happens in the field rather than in the back office.

An exception count that falls over a quarter means scheduling and caregivers have changed how they work. One that stays flat while the open count grows means the queue has no owner. Either way, the claims follow the visits, so the exception report is the earliest view you will get of next month’s cash.