What it means on your remittance
On its own, N56 is a generic wrong-procedure-code remark — not an EVV code everywhere. In Ohio Medicaid remittances, ODM's error guide publishes CARC 272 + N56 as the EVV 'Procedure Code does not match' error: there is no visit in your EVV account that matches this provider, recipient, and service — the visit doesn't exist, isn't in Verified status yet, or was recorded under a different payer or service.
Why it happens
- No visit exists in the EVV system for this provider + recipient + service combination (ODM's guide lists this first).
- The visit exists but is not in Verified status — stuck in exceptions like a missed clock-in/out or an unauthorized service.
- The visit was recorded under a different payer or a different service than the one billed.
- The claim was billed before the visit reached Verified — the race condition state programs repeatedly warn about.
How to fix it, step by step
- 1Find the visit in your EVV portal for the denied date of service.
- 2If there's no visit, determine whether one was ever captured. A missed clock-in may need a manual visit entry with a documented reason code (ODM's resolution path: 'Adding a Manual Call to an Existing Visit' / 'Creating a Visit').
- 3If the visit exists but isn't Verified, open its exceptions and clear each one — missed calls, unauthorized service, missing fields — until the status flips to Verified.
- 4If the visit is Verified but recorded under the wrong service or payer, correct the service key so it matches what you billed.
- 5Rebill only after the visit shows Verified. Billing first guarantees a repeat denial.
How to tell it apart
Like N521, N56's official X12 meaning is generic — 'procedure code billed is not correct/valid for the services or date billed.' It becomes an EVV signal in Ohio's published 272+N56 pairing, where it means 'no verified visit matches this service.' Outside that context, treat a bare N56 as an ordinary coding issue: check the procedure code against the fee schedule before hunting EVV records.
The bigger picture
This is the code that punishes billing-before-verified most directly. Ohio's own pay condition is that the visit must be 'Verified' in the Sandata aggregator — a claim that races its own visit data will land here even though the visit is real and the coding is right.
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 N56 mean?
On its own, N56 is a generic wrong-procedure-code remark — not an EVV code everywhere. In Ohio Medicaid remittances, ODM's error guide publishes CARC 272 + N56 as the EVV 'Procedure Code does not match' error: there is no visit in your EVV account that matches this provider, recipient, and service — the visit doesn't exist, isn't in Verified status yet, or was recorded under a different payer or service.
How do I fix a N56 denial?
Find the visit in your EVV portal. If it's stuck in an exception (missed call-in/out, unauthorized service), clear the exceptions until the visit reaches Verified status, then rebill. If the visit was recorded under the wrong service or payer, correct it, re-verify, and resubmit. Never bill before the visit shows Verified.
The procedure code on my claim is definitely correct — why N56?
On an Ohio home-care remittance with CARC 272, N56 usually isn't about your coding at all. It's ODM's published signal that no VERIFIED visit matched the service you billed. Your code can be perfect while the visit behind it is missing, unverified, or filed under a different service.