What it means on your remittance
On its own, N521 is a generic provider-information mismatch — it is not an EVV code everywhere. But in Ohio Medicaid remittances, ODM's own error guide publishes CARC 272 + N521 as the EVV 'Provider ID does not match' error: the Provider Medicaid ID on the claim is not in Sandata, either because you haven't registered a Sandata account or because your Sandata account uses a different Medicaid ID than the one you bill under.
Why it happens
- You never registered with the state's EVV vendor portal, so your Provider Medicaid ID simply isn't in the EVV system (Ohio ODM's guide names this cause first).
- Your EVV account is registered under a different Medicaid ID than the one on your claims — common after adding service lines, locations, or a second NPI.
- The payer sent a claim for a provider ID that isn't subject to EVV, and the mismatch fired anyway (ODM's guide lists this as the other published cause).
How to fix it, step by step
- 1Identify which Medicaid ID your Sandata (or alt-EVV) account is tied to — ODM publishes a Sandata resource specifically for looking this up.
- 2Compare it character-for-character with the billing provider Medicaid ID on the denied claim.
- 3If you have no EVV account for that ID, register with the Sandata provider portal using the ID you bill under.
- 4If the account exists under a different ID, align them — either re-register or correct the billing ID — so visit data and claims carry the same provider identity.
- 5Resubmit the claim once the IDs match.
How to tell it apart
Important: N521's official X12 meaning is a generic provider-information mismatch — it is NOT an EVV code everywhere. It becomes an EVV denial specifically in Ohio Medicaid remittances, where ODM's error guide publishes CARC 272 + N521 as the 'Provider ID does not match' EVV error. If you see N521 without CARC 272, or outside a home-care Medicaid context, investigate it as an ordinary provider-enrollment mismatch first.
The bigger picture
In Ohio's system, the same underlying error appears differently by program: ODM/MCO remittances show 272+N521, DODD's eMBS shows Error 70, AGE shows EV000/EV002, and MyCare plans printed N363 alerts before their enforcement dates. One root cause, four different code faces.
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 N521 mean?
On its own, N521 is a generic provider-information mismatch — it is not an EVV code everywhere. But in Ohio Medicaid remittances, ODM's own error guide publishes CARC 272 + N521 as the EVV 'Provider ID does not match' error: the Provider Medicaid ID on the claim is not in Sandata, either because you haven't registered a Sandata account or because your Sandata account uses a different Medicaid ID than the one you bill under.
How do I fix a N521 denial?
Register with the Sandata provider portal (or your certified alternate EVV vendor) using the same Medicaid ID you bill with. If you already have an account, confirm which Medicaid ID it's tied to and align it with the ID on your claims. Then resubmit.
I've billed this payer for years — why is my provider ID suddenly not matching?
Billing enrollment and EVV registration are separate systems. Your Medicaid enrollment can be perfect while your EVV registration doesn't exist or sits under a different ID. The mismatch only started denying claims when your state's EVV enforcement date arrived.
Does N521 always mean an EVV problem?
No — and that matters. By its official X12 definition, N521 is a general mismatch between the provider information you submitted and what the payer has on file. It signals EVV specifically when paired with CARC 272 on Ohio Medicaid home-care remittances, because that's the pairing ODM publishes for its EVV provider-match error.