Overview
Modifier XU (Unusual Non-Overlapping Service) is the catch-all X-modifier introduced by CMS in 2015 to identify a service as distinct when none of the other three X-modifiers (XE for separate encounter, XP for separate practitioner, XS for separate structure) specifically applies. It is used when genuine distinctness exists between two services that would otherwise be bundled by NCCI (National Correct Coding Initiative) edits, but the basis for distinctness is not clearly encounter, practitioner, or structural separation.
Clinical applications include services that are distinct because they address genuinely separate clinical problems on the same anatomic structure, services that are distinct because one is diagnostic and the other therapeutic with appropriate temporal or clinical separation, or other distinctness scenarios where the service is genuinely non-overlapping with the bundled-to service. For example, a nerve conduction study and concurrent EMG on the same patient might be billed with Modifier XU if NCCI bundles them inappropriately for the specific clinical scenario.
Modifier XU is intentionally less specific than XE/XP/XS, which reflects CMS's design choice: the specific X-modifiers are preferred when they apply because they articulate precise distinctness basis. XU is reserved for legitimate distinctness that falls outside the three specific categories. This creates a documentation burden — because XU is non-specific, coders should articulate in the record why the service is unusual and non-overlapping, supporting audit defensibility.
Payer acceptance is similar to other X-modifiers. Medicare recognizes XU; commercial payer support is mixed, with many systems still preferring Modifier 59. Audit exposure for XU is arguably higher than other X-modifiers because its catch-all nature invites scrutiny — Office of Inspector General reviews have flagged Modifier 59 and its X-modifier successors for audit plan focus.
For RCM operations, Modifier XU should be used sparingly and with clear documentation. Practices that rely heavily on XU as a default X-modifier without supporting documentation expose themselves to audit risk. Coders should first evaluate whether XE, XP, or XS applies; only when none of those is appropriate should XU be used. When XU is used, the specific distinctness rationale should be documented in both the clinical record and the coding note.
Denial patterns associated with Modifier XU include payer non-recognition (requiring Modifier 59 fallback), audit findings for insufficient documentation of distinctness, and overuse patterns that trigger provider-specific audit focus. Practices should monitor XU usage rates against service mix to identify outlier providers or coders whose XU rates are disproportionately high, as these patterns attract both internal compliance attention and external audit risk. Internal policy should require coder or supervisor sign-off on XU application, with documentation of why XE, XP, and XS were considered and ruled out, to create audit-defensible decision trails.
Industry benchmark
Modifier XU usage: should be lowest of X-modifiers when properly applied. Overuse patterns: audit risk indicator.
Worked example
A patient undergoes nerve conduction study (NCS) and EMG on the same date. NCCI edits bundle these procedures in certain combinations, but the specific clinical scenario involves a new symptomatic region requiring EMG distinct from the NCS evaluation. The EMG is billed with Modifier XU to identify the unusual non-overlapping service. Documentation describes the distinct clinical question for EMG vs. NCS. The payer processes both procedures; documentation supports audit defensibility.
Look it up in CMS data
Free reference pages and tools rebuilt from the current CMS release files, for looking up the CMS data behind this term.
In the CMS October 2026 HCPCS file, modifier XU is "Unusual non-overlapping service, the use of a service that is distinct because it does not overlap usual components of the main service", in effect since January 1, 2015; 8 current Medicare billing and coding articles name it. Modifier XU in the modifier list.
In the 2026 Q4 CMS National Correct Coding Initiative procedure-to-procedure tables (release v323r0, effective October 1, 2026), 1,732,820 practitioner code pairs are active and 70.4% of them carry modifier indicator 1: an NCCI-associated modifier such as 59, XE, XS, XP or XU can bypass the edit when the record documents a distinct service. The hospital outpatient table holds 1,406,699 active pairs, 96.4% of them with indicator 1. The two codes of an indicator 0 pair are never paid together on the same date, whatever modifier is appended.
Grouping the 2026 Q4 practitioner pairs by column-1 code shows where an NCCI-associated modifier (59 or XE, XS, XP, XU) can most often separate a bundled pair. Ranges are bare code numbers; ranges with fewer than 2,000 active pairs are left out.
| Column-1 code range | Active pairs | Indicator 1 share |
|---|---|---|
| 81000–81999 | 46,877 | 98.5% |
| 0002M–0020M | 2,063 | 96.3% |
| 0001U–0571U | 43,866 | 93.9% |
| 87000–87999 | 3,012 | 88.0% |
| 94000–94999 | 2,623 | 83.3% |
| 95000–95999 | 8,425 | 82.3% |
| 14000–14999 | 3,122 | 77.5% |
| 36000–36999 | 26,520 | 75.8% |
| 28000–28999 | 47,256 | 75.7% |
| 10000–10999 | 3,596 | 75.4% |
The lowest shares sit in 99000–99999 (48.2%), 77000–77999 (52.9%) and 01000–01999 (53.1%): more of those edits are indicator 0, so a distinct-service modifier will not unbundle the pair.
Frequently asked questions — Modifier XU (Unusual Non-Overlapping Service)
When should I use Modifier XU?
When genuine distinctness exists but XE, XP, and XS do not apply. XU is a catch-all; XE, XP, and XS are preferred when their specific basis applies.
Is Modifier XU more audit-prone than other X-modifiers?
Yes, because its non-specific nature invites scrutiny. Documentation of distinctness rationale is especially important for XU application.
Why did CMS introduce X-modifiers?
To replace overused Modifier 59 with more specific alternatives that force coders to articulate why services are distinct, improving both accuracy and audit defensibility.
Disclaimer
This glossary entry is operational reference for revenue-cycle and medical-billing professionals. It is not legal, clinical, or contractual advice. Industry benchmarks cite named public sources where available; always verify against the current guidance from the authority body before relying on a number in a contract, policy, or compliance filing.