What a denied D2950 actually is
Every payer speaks in two codes on an EOB. The CARC (Claim Adjustment Reason Code) is the category of what happened; the RARC (Remittance Advice Remark Code) is the detail. When a core buildup is denied alongside an approved crown, the CARC is almost always 97 — the payer's way of saying this buildup isn't a separate benefit; it's baked into what we already paid for the crown.
The CDT descriptor is what the payer is leaning on. D2950 — "Core buildup, including any pins when required" — is defined as building up an anatomical crown when there is insufficient tooth strength and retention for the restorative crown. It explicitly should not be reported when the procedure only fills an undercut, box form, or concave irregularity created during the prep. So when a payer bundles it, they're betting the "buildup" was really just prep filler.
The prefix matters here more than almost anywhere. CO-97 — Contractual Obligation — means the provider writes it off; a participating dentist cannot balance-bill the patient for it. If it were the patient's responsibility it would carry PR instead, and a bundling call under a par contract does not. That's exactly why an incorrect 97 is worth fighting: left alone, it's lost practice revenue you quietly eat, and it never even shows up as a patient balance to chase.
Why it always carries a remark — and why that's the whole fork
CARC 97 is a payment-adjacent code: under X12 it's only valid on the 835 when paired with a RARC remark. A bare "97" with no remark is itself a defect worth questioning. And the specific remark is where the entire decision lives — because it tells you whether you're looking at a true bundling ruling or a documentation hold dressed up as one.
So the first move is never to appeal, argue, or re-file blindly. It's to read the remark. Here are the ones that most often ride along with a denied D2950, and exactly what each is telling you to do:
The most common causes on a dental claim
Nearly every denied D2950 traces back to one of five things — and only two of them are actually "bundling":
- It really was just prep filler. The material only removed an undercut or box form during crown prep — so per the CDT descriptor, the payer is right → stop reporting D2950 unless >50% structure loss / <3mm sound dentin remains; report the correct restorative code, or nothing.
- No pre-op periapical or narrative was attached, so the payer defaults to "included in the crown" → always attach an unobstructed full-tooth pre-op PA plus a one-line narrative: ">50% coronal structure missing; buildup required for crown retention."
- The crown's seat/insertion date wasn't reported — the payer holds or denies the buildup until the crown is proven placed → resubmit with the crown's seat date (many carriers pay the buildup only on the crown's prep or seat date).
- Same date of service as the crown tripped an automatic bundling edit on a vital tooth → report the buildup on its true completion date; if it's genuinely same-day and necessary, appeal with the not-a-filler narrative, not a modifier.
- Practice-management software auto-bundled the buildup into the crown fee before submission → turn off auto-bundling so D2950 goes out as its own line, with its own fee, on the same claim as the crown.
How to fix a denied D2950, step by step
- 1. Read the EOB/835 and split the two denials. Separate a true bundling call (CARC 97 + N19/M15, CO group = write-off) from a documentation or seat-date hold (Delta 5BU/570/5L8 or "pending crown seat date"). They resolve on different tracks.
- 2. If it's documentation or seat-date: resubmit. Attach the unobstructed pre-op periapical and a short clinical narrative, and add the crown's seat/insertion date. No appeal letter needed — this is a completion, not a dispute.
- 3. If it's a true bundling ruling and the buildup met the CDT definition: appeal. Quote the ADA position — bundling separate procedures to limit a benefit is against ADA policy — and the D2950 descriptor, attach the pre-op PA showing >50% loss, and state the buildup was for retention, not to eliminate an undercut.
- 4. Track timely-filing on both lines and fix the setting. CO-97 write-offs silently expire, and the buildup line runs its own clock apart from the crown. If overturned, confirm the payer reprocesses at the full separate allowance (ADA position: crown + buildup), and turn off auto-bundling so it doesn't recur.
Corrected claim or appeal? The sharp fork.
This is the decision offices get backwards most, and it costs money both ways. Match the track to the code:
- Missing pre-op radiograph, missing narrative, or missing crown seat date → resubmission with attachments (or a corrected claim adding the seat date). Nothing was disputed; you simply never gave the payer what it needed. Fast track, no appeal letter.
- A true bundling/incidental ruling (CARC 97 + N19/M15) on a buildup that genuinely met the CDT definition → formal appeal, because the payer made an adjudication decision you're contesting on policy grounds — cite the ADA anti-bundling position and the descriptor.
Offices lose money by writing appeal letters for what was really a missing-attachment resubmission (slow and unnecessary) — and by resubmitting the identical claim for a genuine bundling call, which just re-denies. The buildup is real, already earned clinically, and only lost to a documentation gap or an unfought edit. Catching it before timely-filing runs out on the buildup line is where the recovery lives.
Frequently asked
Why was my D2950 core buildup denied when the crown was approved?
The payer ruled the buildup is included in the crown's allowance — a bundling denial, usually CARC 97 with remark N19 (incidental) or M15 (bundled component). It most often happens because no pre-op radiograph or narrative was attached, so the payer assumed the “buildup” was just filler removed during crown prep. Per the CDT descriptor, D2950 is only separately payable when placed because of insufficient tooth structure, not to eliminate an undercut.
Should I file an appeal or just resubmit the buildup claim?
Match the track to the reason. If the denial is a missing pre-op periapical, missing narrative, or a missing crown seat date, resubmit with those attachments — no appeal letter required. If it's a genuine bundling/incidental ruling (CARC 97 + N19/M15) on a buildup that met the CDT definition, file a formal appeal citing the ADA anti-bundling position and attaching the pre-op radiograph. Resubmitting an identical claim on a true bundling call just re-denies.
Does CO-97 on a buildup mean I can bill the patient?
No. CARC 97 under group code CO is a Contractual Obligation, which means a participating dentist must write it off and cannot balance-bill the patient. That is precisely why a wrong bundling denial is worth challenging — left alone it is lost practice revenue you absorb, not a patient balance. Patient-responsibility denials carry the PR group code instead, which a bundling call on a par contract does not.
Why does the payer want the crown's seat date before paying the buildup?
Many carriers only reimburse D2950 on the crown's prep or seat (insertion) date, and some hold the buildup until the crown is proven placed. If you billed the buildup before the crown was seated, or omitted the seat date, the claim is held or denied pending that date. This is a resubmission fix — add the crown's seat/insertion date — not an appeal, because nothing was actually disputed on the merits.
Text us the D2950 you were about to write off.
We'll read the remark, tell you free whether it's a bundling ruling or just a missing radiograph, and exactly what turns it over. If it's worth recovering, the rail files it on the right track. If it isn't, you'll know that too.
This guide is general educational information about dental claim adjustment codes, not legal, billing, or coding advice. Code definitions follow the X12 CARC/RARC standard and the ADA CDT descriptor for D2950; individual payers may attach different RARCs, use payer-specific EOB codes, or require different documentation. Always read the specific remark on your EOB and confirm current payer requirements.