What it means on your remittance
The payer expected this service's visit data to arrive through the state-designated EVV vendor or aggregator, and it didn't. Either the visit was never exported from your EVV system, or it was captured outside the approved vendor path (for example, an alternate EVV system that isn't certified with the aggregator).
Why it happens
- Your EVV vendor isn't connected to the state's designated aggregator — visits are being captured but never leave your vendor's system.
- You switched EVV vendors and the new vendor's aggregator certification or data feed isn't live yet.
- You use an alternate EVV system that hasn't completed the state's certification process (in Ohio, alt-EVV vendors must certify with Sandata before production).
- Visit data is being submitted under different provider credentials than the ones the claim bills with, so the aggregator can't attribute the data to you.
How to fix it, step by step
- 1Confirm which system your state designates as its EVV aggregator (Ohio: Sandata; Pennsylvania: the DHS aggregator; Missouri: the EAS).
- 2Log into the aggregator directly — not your vendor's portal — and look for the visit. If it's absent there, the export path is the problem.
- 3If you use an alternate EVV vendor, verify its certification status with the state and that its aggregator feed is active for your provider IDs.
- 4Check that the provider ID your EVV system exports under matches the Medicaid ID on your claims.
- 5Once visits are flowing to the aggregator and this visit shows there, resubmit.
How to tell it apart
N824 is about the PATH the data takes; N890 is about the data not being there at all. If your visits show in your vendor's portal but claims still deny with N824, the vendor-to-state connection is broken — a systems problem to fix once, not a per-claim correction.
The bigger picture
N824 is the second of the two RARCs whose X12 text names EVV directly. It shows up most around vendor transitions and alt-EVV setups — exactly when agencies assume everything is fine because caregivers are still clocking in normally.
See if this code is quietly costing you money
Drop your Medicaid 835 into the free X-Ray. It parses in your browser and never leaves your computer.
Run the free Denial X-RayCommon questions
What does denial N824 mean?
The payer expected this service's visit data to arrive through the state-designated EVV vendor or aggregator, and it didn't. Either the visit was never exported from your EVV system, or it was captured outside the approved vendor path (for example, an alternate EVV system that isn't certified with the aggregator).
How do I fix a N824 denial?
Verify your EVV vendor is exporting to the state aggregator and that this visit actually posted there. If you use an alternate EVV vendor, confirm it is certified and connected. Once the visit is visible in the aggregator, resubmit the claim.
My caregivers clock in every day — how can the state say data wasn't submitted?
Clock-ins land in your vendor's system first. The state only sees what the vendor exports to the designated aggregator. If that export is broken or was never configured, every visit you capture is invisible to claims matching — and every claim denies the same way.