
Few coding concepts affect revenue — and audit risk — as directly as bundling. The rules decide whether two services on the same date of service are paid separately or paid as one. Report them the wrong way and you either leave money on the table or submit improper claims.
This page explains what bundling means, what unbundling is and why it is improper, how modifiers fit in, and how to reduce audit risk. Coding references are date-stamped and should be checked against the current CMS National Correct Coding Initiative (NCCI) tables before use. Last reviewed 2026-10-08.
What “bundled” means
Bundling is the principle that certain services are considered part of a larger service and are not paid separately. CMS enforces this through the NCCI Procedure-to-Procedure (PTP) edits: a table of code pairs in which one code (Column 2) is treated as a component of the other (Column 1).
When both codes of a pair appear on a claim:
- The Column 2 code is denied as bundled into Column 1, unless a valid modifier overrides the edit.
- Each code pair carries a modifier indicator: an indicator of 0 means no modifier can override the pair — the bundling is final. An indicator of 1 means a modifier may override it when the documentation supports a truly separate service.
- Commercial payers often build their own edits on the NCCI framework, sometimes adding their own policies. Always check the payer’s published policy in addition to the NCCI table.
Bundling is not punishment; it reflects clinical reality. A pre-operative assessment, a post-procedure dressing change, or a diagnostic step that is an inherent part of the procedure is one service, not several billable ones.
What “unbundled” means — and why it is improper
Unbundling is the improper practice of reporting component services separately to obtain higher payment, when a single comprehensive code describes the complete service or when the NCCI edits say the services are bundled.
The classic forms:
- Fragmenting. Billing the individual components of a procedure (for example, each step of a multi-step intervention) instead of the one comprehensive code that describes the whole service.
- Modifier misuse. Appending a modifier — most often modifier 59 — to bypass a bundle when the services were not actually separate, so both codes pay.
- E/M plus procedure. Billing a routine evaluation and management visit on top of a procedure when the E/M work was simply the decision-making inherent in the procedure itself.
Unbundling is a compliance issue, not just a denial issue. The HHS Office of Inspector General has publicly reported on the misuse of modifier 59, and routine modifier use to defeat bundles is a known audit target. Intent does not have to be proven for an auditor to recover overpayments — incorrect billing alone is enough.
Modifiers 59 and XE, XP, XS, XU: used appropriately, with care
Modifier 59 (Distinct Procedural Service) signals that a procedure was separate from another service on the same date — different session, different site, or different problem. CMS introduced the more selective X{EPSU} modifiers as subsets of modifier 59:
- XE — Separate Encounter. The service occurred during a distinct encounter.
- XS — Separate Structure. The service was performed on a separate organ or anatomic structure.
- XP — Separate Practitioner. The service was performed by a different practitioner.
- XU — Unusual Non-Overlapping Service. The service does not overlap the usual components of the main service.
Key rules for using them correctly:
- Choose the most specific modifier. CPT guidance says modifier 59 should not be used when a more descriptive modifier is available. If the distinction is a separate encounter, use XE — not 59.
- Do not stack them. Reporting both modifier 59 and an X{EPSU} modifier on the same line is incorrect; the specific modifier already carries the distinction.
- The modifier must match the record. Every modifier is a statement about what happened. The note must describe the separate encounter, separate site, or separate practitioner — the modifier alone is not evidence.
- Check the modifier indicator first. If the NCCI pair carries an indicator of 0, no modifier overrides the edit. Adding one is futile and looks bad on review.
- Payer policies vary. Some payers require the specific X{EPSU} modifier; others still accept 59. Check the payer’s companion guide before choosing.
Related but different: modifier 25 is for a significant, separately identifiable E/M service on the same day as a procedure. It is appended to the E/M code, never to the procedure code — and confusing it with modifier 59 is a common and costly error.
Reducing audit risk
Run your coding operation against this checklist:
- Look up the edit before appending a modifier. Check the current NCCI PTP table for the code pair and its modifier indicator. Never quote an old edition’s edits as current.
- Document the distinction at the point of care. “Separate encounter” or “separate site” must be in the note, not inferred later during an appeal.
- Audit your own modifier 59 usage. Pull a sample of claims with modifier 59 or X{EPSU} modifiers and verify each against the note. A pattern of modifiers without matching documentation is the finding auditors look for.
- Watch automated coding defaults. Billing systems or templates that append modifiers by default — to “get the claim paid” — are a liability. Every modifier on every claim must be supported.
- Track CO-97 denials. The “bundled services” denial code (CO-97) tells you where your coding and the payer’s edits disagree. Group them by code pair, fix the workflow, and appeal only the claims where the documentation genuinely supports a separate service.
If your practice is seeing rising bundled-service denials, the problem is usually upstream in coding — not at the payer. A structured denial management process finds the pattern; a coding review finds the cause.
Frequently asked questions
What is the difference between bundled and unbundled billing?
Bundled billing reports services as the comprehensive code (or accepts the NCCI component denial) when services are part of one larger service. Unbundled billing improperly reports the components separately to increase payment.
Is unbundling the same as upcoding?
No, but they are cousins. Upcoding assigns a higher-level code than documented; unbundling splits one service into separately billed components. Both inflate payment improperly, and auditors look for both.
When is it legitimate to bill both codes of a bundled pair?
When the two services were genuinely distinct — a separate encounter, a separate anatomic site, a different practitioner, or an unusual non-overlapping service — and the NCCI modifier indicator for the pair allows an override (indicator 1). The documentation must support it.
Can I appeal a CO-97 bundled denial?
Yes, if the documentation shows the services were truly separate and the modifier indicator permits an override, appeal with the record attached. If the bundling was correct, adjust the claim and fix the workflow that produced it.
Do all payers use the same bundling edits?
No. Medicare uses the NCCI edits; commercial payers often adapt them and add proprietary policies. A pair that pays separately under one payer may bundle under another.
How often do NCCI edits change?
NCCI tables are updated quarterly, and edits are added, deleted, and revised over time. Always verify against the current published tables for the date of service — never rely on memory or an old reference.
Bundling rules punish sloppiness and reward precision. If your coding workflow needs an outside review from dedicated medical coding services, Get a Free Billing Audit.
Medical Billing & Revenue Cycle Management is a remote company serving practices in all 50 states: +1 (307) 396-4107 or contact@medicalbillingservicesgroup.com.
General educational information, not legal advice or a guarantee of reimbursement. Requirements vary by payer, plan, setting and date of service. CPT is a registered trademark of the American Medical Association.