Electronic Visit Verification used to feel like a compliance checkbox. Agencies implemented it because they had to, set up an app for their DSPs, and moved on. In 2026, that approach is actively costing agencies money. States that previously accepted soft compliance with EVV are now running hard edits that automatically reject claims with missing or inaccurate visit data before any human reviewer ever sees them. EVV is no longer a background compliance requirement. It is a front-line revenue protection tool, and the way your agency captures and processes EVV data determines whether your claims get paid on the first pass or pile up in a denial queue.
Here is how Vertex EVV Manager works and why the connection between EVV and billing is the part that actually matters.
What EVV Is Required to Capture
Under the federal 21st Century Cures Act, EVV systems must capture six data elements for every qualifying service visit:
- The type of service performed
- The individual receiving the service
- The date of the service
- The location where the service was delivered
- The individual providing the service
- The time the service begins and ends
Every one of these elements must be present and consistent with the billing claim that corresponds to the visit. When any element is missing, inaccurate, or inconsistent with what was billed, the claim fails EVV validation and is rejected before payment is issued.
How Vertex EVV Manager Captures Visit Data
Vertex EVV Manager is an app-based tool designed for DSPs working in home and community settings. When a DSP arrives at a client’s location to begin a service session, they open the app and clock in. The app captures the start time, confirms the client identity, records the service type, and verifies the location through GPS or address confirmation depending on the setting.
The process takes about 30 seconds. When the session ends, the DSP clocks out through the same app. Departure time is recorded. The visit record is complete and transmitted.
The design priority for the DSP-facing interface is simplicity. A DSP who is arriving at a client’s home, preparing to provide meaningful direct support, should not have to navigate a complicated system to comply with EVV requirements. Vertex EVV Manager’s interface is built for the field, not for the office, which means DSPs who are not technology-confident can complete the process reliably without extensive training.
Why the Billing Connection Is Everything
Here is where most EVV implementations fall short. An EVV app that captures visit data and stores it in a system that is separate from the billing platform has not solved the problem. It has just moved it.
When EVV and billing operate in separate systems, someone has to reconcile them before claims can be submitted. A billing coordinator who exports EVV data from one platform and compares it against service records in another is doing manual work that introduces errors, consumes time, and delays submission. When EVV exceptions exist, they are discovered during this reconciliation process rather than at the point of service, which means the window for correction is shorter and the billing delay is already underway.
Vertex EVV Manager is integrated directly with Vertex Billing Manager. When a DSP completes a visit verification through the EVV app, that data flows directly into the billing workflow. When a billing coordinator prepares a claim, the EVV record is already associated with it. If there is an EVV exception, it surfaces before the claim is submitted rather than after it is rejected.
This integration changes what billing coordinators spend their time doing. Instead of reconciling EVV records against billing records manually, they are reviewing pre-submission error notifications and resolving exceptions before they ever become denied claims. The revenue cycle shortens. The clean claims rate improves. The administrative load on the billing team decreases.
Handling Community-Based Services
One of the most common EVV challenges for IDD agencies is services delivered in community settings rather than at a fixed home address. A client receiving community integration supports may be at a restaurant, a park, a job site, or a family member’s home on any given service day. GPS-based EVV systems that expect a static home address generate location exceptions for every community-based visit, creating a compliance headache that does not reflect any actual service delivery problem.
Vertex EVV Manager is designed for IDD community service delivery specifically, not adapted from a home health model that assumes a fixed location. The app supports community-based location capture and is configured to work within the service parameters each state uses for HCBS verification, which means community integration services generate clean EVV records rather than systematic exceptions.
State Aggregator Connections
Every state that has implemented EVV uses an aggregator to receive and validate visit data from providers. Common aggregators include Sandata and HHAeXchange, and some states mandate specific systems while others allow provider choice. Regardless of which aggregator a state uses, visit data submitted by providers must reach the aggregator in the correct format before a claim can be processed.
Vertex EVV Manager is configured for each state’s aggregator requirements as part of the implementation process. Providers using Vertex in Michigan connect to HHAeXchange. Providers in Pennsylvania connect to Sandata. Providers in states using other aggregators connect accordingly. The state-specific configuration is handled at the platform level rather than requiring agency billing staff to manage the technical connection independently.
What EVV Compliance Looks Like in Practice
For an IDD agency with strong EVV compliance, the daily operational picture looks like this: DSPs complete clock-in and clock-out in Vertex EVV Manager at every qualifying visit. Exceptions, when they occur, surface immediately in a supervisor dashboard rather than accumulating until billing. Billing coordinators see EVV-validated service records when preparing claims and do not need to separately verify that EVV was completed before submitting. Claims include the EVV data elements required by the state and payer, and hard-edit validation passes on first submission.
For an agency without that integration, the picture is different: billing coordinators are managing a separate reconciliation process, exceptions are discovered late, and claims age while EVV issues are resolved after the fact.
Connect with the Vertex Systems team to see how Vertex EVV Manager works in practice and what the integration with billing looks like for your specific state and payer mix.
