Sign in

Attachments and requested documentation · Last verified 2026-08-30

CARC 250 denial code on dental claims

Independent publisher · Drafted with AI assistance, verified against primary sources · Credentialed review pending

CARC 250 is the “Wrong document sent” code on a dental remittance. Correct it and resubmit inside the filing window; this is not an appeal.

Group code: X12 places no group-code restriction on 250. A group code always travels with a CARC, and it — not the CARC — assigns financial responsibility, so read the one on your remittance rather than assuming.

Registry entry: X12 Claim Adjustment Reason Code 250 — active, with no deactivation date. Read on the list published 2025-11-01.

Verdict

Technical — fix and resubmit

The route here is correcting the identified defect and resubmitting as a corrected claim, inside the timely-filing window, rather than arguing the decision.

Read the payer's criteria before resending anything. Sending more of the same document is how a 250 becomes a 226.

The appealability verdicts on these pages are Dentovio's editorial classification. No standards body or payer publishes an appealability taxonomy: X12 defines what a code means, not what to do about it. Each verdict is built from the code's own mechanics and the payer and federal documents cited on the page, and it is a starting point for triage rather than a prediction of any outcome.

What it means in dental

Documentation arrived, but it was not the document the payer needed.

The third member of the attachment family, and the one most often missed when a practice routes every attachment problem to 252. A wrong-document denial usually means the narrative or image sent answers a different question than the payer's policy asks — a post-operative image where the criteria call for a pre-operative one, or a narrative describing the treatment rather than the finding that justified it.

What to do

  1. 1.Identify precisely which document the payer's policy names for the procedure
  2. 2.Send that document, dated and labelled, rather than the whole record
  3. 3.Track the response window; the request does not stay open indefinitely

Remark codes verified with this CARC

X12 defines no CARC-to-RARC pairings. Each combination below is either a payer's own published crosswalk — true for that payer's internal reason code, not as a general rule — a CAQH CORE-required combination, or a remark whose registry meaning describes this adjustment.

N850 · Required combination under the CAQH CORE rule

A narrative describing this service was not supplied, or the one supplied is unusable.

What to do: Write a narrative that states the finding the payer's criteria require, not a description of the procedure.

A CORE-required combination for 250 (and for 163 and 164) — not for 252, despite how often the pairing is published that way (v3.10.0, February 2026).

Read with this code

Sources

Last verified 2026-08-30. Dentovio is an independent publisher — not a payer, the ADA, X12, CAQH CORE, or any government agency. Code meanings and remark-code meanings on this page are Dentovio's own wording, written from the official X12 Claim Adjustment Reason Code and Remittance Advice Remark Code lists and linked back to them; X12 holds the copyright in those lists and its descriptions are not reproduced here. CDT codes are referenced by number only; CDT is the American Dental Association's copyrighted code set and this page does not reproduce ADA descriptors. Appealability verdicts are Dentovio editorial classification, not a standard. Every fact traces to the code steward's registry, a federal rule or manual, a HIPAA operating rule, an association publication, or a named payer's own document — never to a billing blog. This page was drafted with AI assistance and verified against the primary sources linked here. It has not been reviewed by a credentialed dental billing specialist, attorney, or clinician. Educational billing reference only — not billing, legal, or clinical advice. Plan contracts control individual outcomes, and processing policies usually live in the payer's provider manual rather than in the signed agreement. How this data is verified