Build a narrow reconciliation queue for small and mid-sized Medicaid home care agencies that turns EVV exceptions, visit maintenance edits, authorization/service-code mismatches, and remittance feedback into claim-ready and payroll-ready fixes before cash is delayed.
Small to mid-sized U.S. Medicaid personal care, HCBS, and home health agencies that lack a large billing/RCM back office. Primary buyers/users: agency owners, billing managers, EVV coordinators, schedulers, payroll clerks, and outsourced billing partners who touch state EVV portals, agency-management suites, clearinghouses, and payer remittances.
The hypothesis is well supported: EVV has become a federally mandated data layer, but the operational failure mode is not simply “capture visits.” It is exception cleanup across several systems before billing and payroll close.
1. Federal mandate creates non-optional workflow. CMS/Medicaid says Section 12006(a) of the 21st Century Cures Act mandates EVV for all Medicaid personal care services and home health services that require an in-home visit. That makes EVV a recurring compliance and payment dependency, not an optional optimization.
2. State programs explicitly tie exceptions to verified visits and paid claims. Illinois’ 2025 EVV Program Manual defines an exception as an alert identifying missing EVV verification data points and says “All Exceptions must be fixed for an EVV record to be a verified visit.” The same manual defines manual EVV records as records whose verification data points are captured or modified after service delivery, and it defines a state threshold as the acceptable limit of modified/manual EVV records calculated as a percent of paid claims. It also says providers should have policies for verifying time worked when exceptions require a manual modification.
3. Billing linkage is real, not theoretical. Illinois’ manual says all listed billing codes require the corresponding EVV Type of Service on file as part of a verified EVV to correctly bill DDD. HHAeXchange’s New York EVV compliance content states that EVV visit records must match paid claims and, if a claim line has multiple visits, every visit must have a compliant EVV record. Virginia DMAS FAQ search results state soft edits ended January 1, 2024 and claims with EVV errors would be denied payment for relevant home health services.
4. State aggregator complexity forces cross-system reconciliation. Pennsylvania uses an open EVV model: providers may use their own EVV vendor/system if it captures the six Cures Act data elements and interfaces with the DHS Aggregator. Illinois uses an Open Choice model where provider-choice systems must interface test with HHAeXchange and providers must complete Data Aggregator training. This creates the exact “agency system + state aggregator + payer/claim workflow” split the product would reconcile.
5. Vendors already expose the pain language. Axxess has an “EVV Exception Center” that lets users “manage, correct and resubmit EVV data when EVV exceptions occur.” HHAeXchange’s Visit Maintenance page says visit management must be “ready for downstream processes like billing, payroll, and compliance with EVV,” quotes an administrator saying it used to take “multiple steps and windows” to correct, edit, and confirm visits, and advertises dashboard visibility into what needs attention and “what exceptions exist.” HHAeXchange EDI best practices discuss paid/denied visits, adjustment/void submissions, TRN claim numbers, manual confirmation, visit edits, and discrepancies between visit and EVV start/end times.
6. Workflow terms map cleanly to a queue product. The recurring clauses are: EVV exception, visit maintenance, missed clock-in / missed visit, manual edit, manual confirmation, claim rejection or denial, authorization, service code / EVV Type of Service, payroll, remittance / TRN claim number, and state aggregator. These are not marketing abstractions; they are the labels agencies already see in portals, manuals, and support content.
EVV has moved from implementation project to enforcement and cash-flow control. PCS mandates have been live for years, HHCS deadlines and state implementations have matured, and states are increasingly connecting EVV records to claim validation, paid-claim monitoring, and aggregator feeds. Agencies that survived initial EVV rollout now face the daily grind: fix exceptions before claims go out, keep caregiver payroll accurate, handle remittance/denial feedback, and avoid a growing share of manual-edit compliance risk.
The timing is also favorable because large agency-management suites are broad systems of record. They prove demand but leave a wedge for a lightweight overlay that does not replace scheduling, EMR, EVV capture, or clearinghouse billing. A small agency may not want a platform migration, but it may pay for a queue that says: “these 37 visits block billing, these 12 affect payroll, these 5 need authorization/service-code correction, and these 3 came back on remittance.”
A weekend-buildable MVP should avoid being a full EVV vendor. Start as an exception/reconciliation workspace that imports CSV/API exports and produces worklists.
Core MVP:
Do not build initially: caregiver mobile app, EVV capture, claims clearinghouse, payroll processor, state-by-state rules engine, or direct portal automation. Those are integration moats later, but they are too heavy for the first proof.
Best wedge: “EVV exception cleanup before billing close” for agencies in states with open EVV models and aggregator workflows. Sell to billing managers and owners with a cash-flow message: fewer rejected/denied claims, fewer late payroll corrections, and fewer hours spent toggling between EVV portal, scheduling/billing system, and remittance files.
Initial channels:
Primary substitutes:
Competitive read: broad platforms already have exception centers, visit maintenance, billing, and payroll modules, so the product cannot win by saying “we manage EVV.” It must win by being narrower, faster to deploy, vendor/state-portal agnostic, and focused on the last-mile reconciliation between EVV exceptions, claim readiness, payroll readiness, and remittance outcomes.
The strongest public evidence comes from state manuals and vendor support/marketing, not from raw agency P&Ls. That proves workflow burden and compliance linkage, but not exact revenue leakage. The market may also be more satisfied with current platform modules than public pages suggest; HHAeXchange’s Visit Maintenance and Axxess’s EVV Exception Center are direct substitutes. A founder should interview agencies before building, specifically asking: how many visits are in exception status at billing close, how many claims are denied/rejected for EVV or service-code mismatch, how payroll disputes are handled after manual edits, and whether a CSV-first overlay would be trusted with PHI/claim data.
Real recurring cash-flow and admin pain, but integration complexity and incumbent proximity make this a discovery-heavy healthcare workflow rather than an obvious quick build.