CPT code 20931: Structural allograft for spine surgery billing guide

Key takeaways

CPT code 20931 covers a structural allograft used in spine surgery only. It is an add-on code, so it always rides alongside a primary spine procedure code.

Medicare values 20931 separately. The 2026 national file lists a work RVU of 1.76, practice expense and malpractice RVUs of 0.59 each, and a total of 2.94.

CPT 20930 and CPT 20936 are the graft codes Medicare never pays separately, because both carry status indicator B and are always bundled.

A 20931 line with no primary spine procedure code on the same claim denies automatically.

Practice management software like Pabau can flag a missing primary procedure code before the claim leaves your practice.

CPT code 20931 reports a structural allograft placed during spine surgery. Medicare pays for it separately, unlike the two graft codes it is most often confused with.

Here is the official AMA descriptor: Allograft, structural, for spine surgery only (List separately in addition to code for primary procedure). That parenthetical is the operative rule. The code never stands alone on a claim.

The + designator in the AMA CPT book marks 20931 as an add-on code. Payers process the line only when a valid primary procedure code appears on the same claim.

CMS assigns 20931 a ZZZ global period, so the graft has no global period of its own and follows the primary procedure. Its multiple procedure indicator is 0, which means the modifier 51 payment reduction never applies to this line.

CPT 20931 vs CPT 20930: Structural vs morselized allograft

This pair produces most of the coding errors in the graft family. The two codes look almost identical on a superbill, and only one of them is separately payable.

The payment difference matters more here than the clinical one. CPT 20930 carries status indicator B, so Medicare folds it into the primary procedure and pays nothing extra. A note that describes chips instead of a block moves the case from a paid line to a bundled one.

The operative note is the audit defense. If the surgeon documents cancellous allograft chips packed into the disc space, a payer can downcode to 20930 whatever the claim says.

Never assign 20931 without confirming that the note describes mechanical support. Capturing graft type in digital intake forms settles the question before the claim goes out.

CPT 20931 vs CPT 20936: Allograft vs autograft for spine surgery

CPT 20936 covers autograft harvested locally, through the same incision as the spine procedure. The bone comes from the patient, typically ribs, the spinous process or laminar fragments. CPT code 20931 uses donor cadaveric bone instead.

Reporting both codes is allowed when both graft types are used. Payment is a separate question. Because 20936 carries status indicator B, Medicare never pays it separately, so the line documents the case rather than adding revenue.

Autograft taken through a separate incision behaves differently. CPT 20937 (morselized) and CPT 20938 (structural) are both active codes, worth 4.41 and 4.89 total RVUs in 2026. Confirm graft provenance and harvest route in the operative report before choosing between them.

Primary procedure codes that pair with 20931

CPT code 20931 must always accompany a primary spine surgery procedure code. The pairings below come up most often in fusion and reconstruction work.

This list is not exhaustive. Any primary spine surgery code that clinically requires a structural allograft can pair with CPT code 20931. Check current edits through the CMS Physician Fee Schedule lookup for the active policy year, since bundling rules update annually. Practices billing graft harvest work as well should review CPT code 20902.

RVU values for CPT code 20931

CPT code 20931 is separately valued under Medicare’s resource-based relative value scale. The 2026 national file gives it a work RVU of 1.76, a practice expense RVU of 0.59, and a malpractice RVU of 0.59. Total RVU is 2.94.

The work component is surgeon credit. Sizing, shaping and seating a structural graft takes operative time beyond the fusion itself, and CMS values that time. Any reference showing 20931 with a work RVU of zero is describing 20930 or 20936.

Facility and non-facility values match because CMS flags the non-facility practice expense as NA for this code. Spine surgery is not expected outside a facility, so the two columns mirror each other.

These values move. The January 2025 file listed a work RVU of 1.81 and a total of 3.33. That makes 2026 a drop of about 12 percent in total RVUs. Model the current year rather than carrying last year’s figure into your fee schedule.

Verify every figure against the current CMS relative value files before you load it into a fee schedule. Values change with each January final rule and with quarterly corrections. Claims management software that maps RVU totals to claim history shows where an add-on code is being under-reported.

Which spine graft codes Medicare bundles

Three add-on codes in this family are paid and two are not. The status indicator in the CMS file is the fastest way to tell them apart.

Status B means payment is always bundled into another service, so no RVUs are assigned and no separate payment is ever made. Report 20930 and 20936 when the record calls for them, but do not build revenue expectations around either line.

Medicare reimbursement and the 2026 fee schedule

Medicare pays for CPT code 20931 by multiplying each RVU component by its geographic index, then applying the conversion factor. At the 2026 conversion factor of $33.4009, the unadjusted national allowance is about $98.

• National allowance: 2.94 total RVUs at the 2026 conversion factor of $33.4009 works out to $98.20 before geographic adjustment.
• Two conversion factors in 2026: Qualifying APM participants use $33.5675, which lifts the same 2.94 RVUs to $98.69. Everyone else uses $33.4009.
• Geographic adjustment: The Geographic Practice Cost Index moves the allowance up or down by locality, so treat the national figure as a starting point.
• Facility and non-facility: Both settings pay the same for 20931, because CMS mirrors the facility practice expense into the non-facility column.
• Commercial payers: Rates follow the contract rather than the fee schedule. Ask your payer relations team for contracted rates by locality.
• Annual updates: RVUs and the conversion factor reset each January, and CMS issues quarterly corrections during the year. Confirm the current-year rate before you load it into a fee schedule.

The 20931 allowance pays the surgeon for placing the graft. Tissue acquisition cost sits outside it. In hospital and ASC cases, the facility bills the implant cost on its own claim. Device pass-through codes such as HCPCS code C1756 follow the same split. Confirm who is billing the tissue before the professional claim goes out.

Modifiers that apply to 20931

CMS publishes payment indicators for every code, and those indicators answer most modifier questions for 20931 directly.

These indicators sit in the same CMS relative value file as the RVUs, so pull both once a year. Confirm payer-specific policy too, since commercial plans can diverge from Medicare on modifier 62. Cross-check code detail against the AAPC CPT lookup when a payer disputes the pairing.

Documenting why two surgeons were needed is what makes a modifier 62 claim survive review. HIPAA-compliant documentation practices keep that reasoning in the record where an auditor can find it.

Documentation requirements for a 20931 claim

Documentation carries medical necessity. A correctly coded claim still denies when the operative note does not support the code. The OIG targets spine surgery add-on codes in post-payment review for exactly that reason.

• Graft type stated explicitly: The note must call the allograft structural, or describe load-bearing placement such as a bone block supporting the anterior column. Vague wording invites a downcode to 20930.
• Work performed, not only material used: 20931 carries surgeon work credit, so the note should describe sizing, shaping and seating the graft.
• Graft source documented: The note must identify the tissue as allograft from a donor, separating it from autograft coded 20936, 20937 or 20938.
• Graft dimensions or configuration: Record graft size and shape where available, since those details support the structural designation.
• Primary procedure cross-referenced: The graft description should tie directly to the primary spine procedure performed on the same date.
• Indication and medical necessity: Record the spinal diagnosis, such as degenerative disc disease or spondylolisthesis, that made the fusion and the graft necessary.
• Tissue supplier noted: When the facility supplied the graft, a line confirming that prevents a duplicate billing dispute later.

Practices running paperless clinical documentation can build these elements into an operative note template as required fields. That beats retrofitting a note after a denial arrives. A structured format such as SOAP progress notes also leaves an auditable trail for post-payment review.

ICD-10 diagnosis codes to pair with 20931

CPT code 20931 needs a diagnosis code that establishes medical necessity for a structural allograft. The codes below cover the spinal pathologies that most often lead to fusion surgery.

Diagnosis selection has to reflect the documented condition. A code chosen for billing convenience will not support a structural allograft on review. Check your Medicare Administrative Contractor local coverage determinations as well, since fusion coverage policy varies by contractor.

Common billing errors and audit risks

The OIG flags spine surgery add-on codes as audit targets because the errors are both frequent and expensive. Knowing the patterns lets a billing team self-audit before claims go out.

• Billing 20931 with no primary procedure code: The most frequent denial trigger. Every 20931 line needs at least one primary spine procedure code on the same date of service.
• Coding 20930 when the note supports 20931: 20930 is bundled, so that choice forfeits the whole separate payment. Coding 20931 when only chips were placed carries the opposite risk on audit.
• Expecting payment for 20936: Local autograft from the same incision is status B and never pays separately. A revenue forecast built on that line will not hold.
• Billing the graft twice: In hospital and ASC cases the facility usually bills the implant. A professional claim for the same tissue creates duplicate billing exposure.
• Appending modifier 51: The multiple procedure indicator is 0, so modifier 51 only invites a reduction that should never apply.
• Missing graft type in the operative note: A technically correct code still fails post-payment audit when the note does not support structural placement.
• Using 20931 outside spine surgery: The descriptor says spine surgery only. Applying it to extremity graft work in a sports medicine practice creates a clear pattern for medical review.

How Pabau keeps spine graft claims paired

A code reference tells you what 20931 is. It cannot stop a claim leaving your practice without the primary procedure code attached.

That is where the denials come from. The operative note is dictated after the case, billing submits on schedule, and the add-on line goes out unpaired. Spine, orthopedic and regenerative medicine practices all hit this, because graft detail lives in the note rather than on the claim.

Practice management software like Pabau keeps documentation and claim submission in one system. Billing staff can see whether the note supports the code before the claim transmits. Automated workflows run the checks a coder would otherwise do by hand.

• Add-on pairing validation: Flags a 20931 line with no valid primary spine procedure code on the same claim.
• Documentation completeness checks: Prompts for graft type, graft source and the primary procedure before the claim is released.
• Modifier guidance: Surfaces the modifiers that fit the procedure set and keeps modifier 51 off add-on lines.
• Claim status by stage: Shows pending, submitted, processing, paid and error claims in one view, with days overdue on each.
• Automated patient communications: Sends pre-operative instructions and post-care notes from the same record the coder works in.
• Audit trail: Links the operative note to the submitted claim, which is what post-payment review asks for.

EHR integration is the next thing to review if 20931 denials keep recurring. The medical practice management software market now includes tools built for surgical specialty billing, where add-on code accuracy shows up directly in collections.

Catch add-on code denials before they leave your practice

Pabau checks that every CPT code 20931 line carries a valid primary spine procedure code. It also ties the claim back to the operative note that supports it.

Book a demo

Conclusion

Most 20931 denials trace to three things. The claim carries no primary procedure code. The wrong graft code was chosen between 20930 and 20931. Or the note never says the graft was structural.

On the payment side, 20931 is an active, separately payable code that carries surgeon work credit. The spine graft codes with no RVUs at all are 20930 and 20936. Treating them the other way round costs a practice money it has already earned.

Pabau checks add-on pairing while the claim is still being built, before it reaches the payer. To see how that works on spine surgery billing, book a demo with our team.

Continue your research

Billing another bone graft code? CPT code 20957 covers microvascular bone graft work, with its own RVUs, modifiers and documentation rules.

Coding a non-surgical bone healing adjunct? CPT code 20979 explains how low intensity ultrasound stimulation of bone is billed and documented.

Picking the right seventh character on a fracture? ICD-10 code S52.131R shows how encounter-specific characters decide whether a diagnosis code is billable.

Working out who bills the device? HCPCS code C1756 walks through pass-through payment and the facility claim lines that carry it.

Frequently asked questions