D3426 is the CDT code for each additional root treated beyond the first during the same apicoectomy surgery.
D3426 has no meaning by itself: it is a counting unit, and everything that goes wrong with it is a counting error. Billed without a base apicoectomy on the claim, it rejects as an orphan line before a human ever reviews it. Billed with the wrong unit count, it either gives away a resected root or invites an audit that refunds the extra. The codebook wires it to two specific base codes: D3421 for premolars and D3425 for molars both carry a first-root qualifier and point here when more than one root is treated, while the anterior code D3410 carries neither, which makes the anterior pairing a documented exception rather than a routine claim.
What D3426 covers
D3426 is the apicoectomy family’s add-on: one unit for each root beyond the first that gets resected during the same surgical session. The base code, D3421 on a premolar or D3425 on a molar, pays for the surgery itself, the flap, the bone access, the closure, and the first root. D3426 pays for the additional root-end work happening inside that already-open field. Its descriptor frames it as typical of premolar and molar surgery and, like every code in the family, excludes retrograde filling material, which stays on D3430 per root sealed.
Because it is an increment and not a procedure, three structural rules follow:
- It never stands alone. No base apicoectomy on the claim, same tooth and date, means the line has nothing to attach to.
- Its unit is the root, counted from the operative note.
- It shares the family’s exclusions, so a sealed additional root is always two lines, the D3426 unit plus a D3430 unit.
Where the code attaches, and where it doesn’t
The codebook wires the family asymmetrically, and the wiring is the billing rule. D3421 and D3425 both say first root in their nomenclature and both direct you to D3426 when more than one root is treated. D3410, the anterior code, says neither: no root qualifier, no pointer. An anterior apicoectomy is written as a per-tooth service.
That leaves the two-rooted anterior, occasionally a mandibular incisor, in a gap the codebook doesn’t squarely address. The descriptor’s typically-premolar-and-molar language describes the usual case rather than banning others, but the missing cross-reference on D3410 means carrier claim edits are generally built around the premolar and molar pairings. Treat a D3410-plus-D3426 claim as an exception to document: operative note naming both roots, a radiograph showing them, and if the add-on still rejects, the codebook’s own fallback for procedures its codes don’t describe is D3999 with a narrative.
Counting units the way an auditor does
The unit count is the entire content of this code, and an auditor reads it against two documents:
- The operative note. Roots resected must be named individually, mesiobuccal, distobuccal, palatal, because the add-on count is roots treated, not roots the tooth anatomically has. A three-rooted molar where only two root ends were resected supports one unit, not two.
- The radiograph. The pre-op film establishes the lesion; the post-op film, where the plan wants one, shows the resections. A claim whose unit count outruns what the images show is the claim that gets refunded.
Root anatomy cuts both ways. Upper first premolars often have two roots, lower molars sometimes have an extra distolingual root, and mesiobuccal roots on upper molars are one root even when they carry two canals; D3426 counts roots, not canals. Bill from what the surgeon documented, and make the documentation name each root.
Pricing: an increment, not a downgrade
Fee schedules price D3426 as marginal work, typically well below the base code, because the expensive parts of the surgery (anesthesia, flap, access, closure) are paid once through D3421 or D3425. A low allowance on the add-on line is therefore the design, not a bundling error to appeal. The EOB items actually worth checking:
- Unit count paid versus billed. Plans occasionally process multi-unit lines as one.
- Whether the plan wants units on one line or repeated lines. Clearinghouse and payer preferences differ; a rejected multi-unit line sometimes just needs re-splitting.
- Frequency rules on the family. These are plan-dependent (Hawaii Dental Service’s published endodontic guidelines, for one, make a repeat apicoectomy not billable to the patient within 24 months by the same office), and the window catches the add-on along with the base code.
The review posture is also inherited: the base code carries the clinical justification (why surgery rather than retreatment on D3348 or its siblings), and D3426 rides on that answer. No separate narrative is needed for the add-on beyond the named roots.
Getting it right in the PMS
- Link D3426 to its base codes. Dependent-procedure rules that require D3421 or D3425 on the same date and tooth kill the orphan-line rejection at the point of entry.
- Allow multiple units on both D3426 and D3430, or every three-rooted molar undercounts.
- Put the unit logic in the procedure label. “Apicoectomy, each additional root (add-on to D3421/D3425)” makes the structure visible at selection time.
- Post the whole surgery on one date. Split-date posting is the most common way the add-on gets separated from its base.
- Cross-check units against the operative note before submission, not after the EOB. The note’s root list is the number; anatomy charts and habit are not.
For how multi-unit lines are entered on the claim form, see the ADA dental claim form guide.
FAQs
- Which codes does D3426 go with?
- D3421 (premolar, first root) and D3425 (molar, first root); both descriptors direct you to D3426 when more than one root is treated at the same surgery, and its own descriptor says it is typically used with premolar and molar surgeries. It cannot be billed alone; a claim carrying D3426 with no base apicoectomy on the same tooth and date rejects as an unsupported add-on. The anterior code D3410 has no first-root language and no pointer to D3426, so pairing them is a rare, documented exception for a genuinely two-rooted anterior tooth, not a standard combination.
- How many units of D3426 do I bill?
- One per root treated beyond the first, at the same surgical session, on the same tooth. A two-rooted upper first premolar with both root ends resected is D3421 plus one unit. A three-rooted upper molar with all roots treated is D3425 plus two units. The unit count must match the roots named in the operative note; that note, not the tooth's typical anatomy, is what supports the claim, because root anatomy varies and a reviewer will not assume the extra roots were treated.
- Does D3426 include the retrograde filling on that root?
- No. Its descriptor carries the same exclusion as the base codes: retrograde filling material is not included. The seal is D3430, reported per root sealed, so an additional root that was both resected and sealed generates two lines, a D3426 unit and a D3430 unit. And if more than one filling is placed in a single root, the codebook sends that to D3999 with a description rather than doubling D3430.
- Why did the plan pay D3426 at a fraction of the base code?
- Because add-on codes are priced as increments, not as full procedures. The flap, access, and closure are paid once through the base code; D3426 covers the marginal work of resecting another root inside the same surgical field, and most fee schedules set it well below D3421 or D3425. That is expected pricing, not a downgrade to appeal. What is worth checking on the EOB is the unit count: a plan that paid one unit against a claim for two is a processing error, and plan-dependent frequency rules on the family can also clip repeat surgeries.
Related codes
Need help billing this code?
We handle D3426 claims daily.
If your team is spending time on denials, narratives, or carrier follow-up for this code, we can take it off your plate. We work inside your PMS and post payments the same week.
CDT codes are maintained by the American Dental Association. This page is an editorial billing guide, not the official ADA code descriptor. Verify current coverage policies with each carrier before submitting claims.