Skip to content
Evaluation and management

Modifier XU

Unusual non-overlapping service — a service that is distinct because it does not overlap the usual components of the main service

Modifier XU covers distinct services that do not fit the separate-site, separate-encounter or separate-practitioner categories. It states that the service did not overlap the usual components of the main procedure, and it is the hardest of the four to support.

Use it when

  • A service genuinely distinct for a reason none of the other X modifiers describes
  • Work that falls outside the usual components of the primary procedure
  • Only where the reason for distinction can be stated plainly in the record

Do not use it when

  • A separate site, encounter or practitioner better describes it — use XS, XE or XP
  • As a substitute for modifier 59 when no specific reason exists
  • Where the service is simply an inconvenient bundle to clear

A worked example

A service is performed alongside a primary procedure that would ordinarily include it, but in this instance it addressed something outside the primary procedure's usual scope.

None of the other three X modifiers fits — the site is the same, the encounter is the same, the practitioner is the same. XU states that the work did not overlap the primary procedure's usual components.

The burden here is high. The note has to explain what was done and why it fell outside the primary service, in terms a reviewer can follow without knowing the specialty.

What decides it

XU is the catch-all and therefore the one most likely to be misused. Where the other three X modifiers describe an objective fact — a site, a time, a person — XU describes a judgement about scope.

That makes it the closest of the four to modifier 59 in character, and it attracts similar scrutiny. Reaching for XU because no other modifier fits is a signal that the services may genuinely have been bundled.

Where it is correct, it is correct, and it should be used rather than falling back on 59. But the honest test is whether you can write one sentence explaining the non-overlap. If not, the claim probably should not carry it.

Denial codes this affects

Modifiers often confused with this one

Terms used here — NCCI Edits · Modifier · CPT Code

How we handle it — Medical Coding · Denial Management · Claims Management

Primary sources

What the payers and code-set maintainers actually publish about modifier XU.

Questions about modifier XU

When a service is genuinely distinct for a reason none of the other X modifiers describes — the work did not overlap the usual components of the primary procedure. It is the catch-all of the four and the hardest to support.

Marginally, in that it names a reason. But XU describes a judgement about scope rather than an objective fact like a site or a time, which makes it the closest of the four to 59 in character and it attracts similar scrutiny.

Write one sentence explaining what fell outside the primary service's usual components. If you cannot write it plainly enough for a reviewer outside your specialty to follow, the services were probably genuinely bundled.

Only if the non-overlap is real. Reaching for XU because nothing else applies is usually a signal that the edit is correct rather than that the catch-all is needed.

Find out what your denials are costing you

A free billing audit reviews your denial rate, AR aging and clean claim rate against industry benchmarks. Takes about two minutes to request. No sales pitch.

No setup fees · You pay when we collect · Pricing from 3% of net collections