Guide

MUEs: how many units Medicare believes

Summary

A Medically Unlikely Edit, or MUE, caps the number of units of one CPT or HCPCS code that Medicare will pay for one patient on one date of service; CMS publishes the specific cap for each code. Billing above the cap on a single line gets that line denied or reduced, regardless of whether the higher count was clinically accurate. Some MUEs are hard caps that can't be appealed for that date of service; others assume the excess is merely improbable, not impossible, and allow an appeal with supporting documentation.

By Gale Editorial · Updated 2026-07-26. Every figure cited to a dated source. How we write.

What an MUE actually caps

A Medically Unlikely Edit sets the maximum units of service one provider can report for one code, for one patient, on one date — and CMS publishes the specific value for each code that has one 1. It exists to catch a claim line that's implausible on its face: a unit count high enough that it's more likely a data-entry error or a miscoded service than an accurate description of what happened.

The cap applies per line, per date, per code — not per visit, per diagnosis, or across the whole claim. A claim with several different codes, each within its own MUE, can still be entirely correct even if the total unit count across the claim looks high.

Units, for this purpose, mean whatever the code's own descriptor counts — a time increment, a supply quantity, an injection count, or a simple per-service count, depending on the code. Reading the code's own unit definition matters before assuming a high number is automatically suspicious; some codes are built to be reported in genuinely large counts as a routine matter, and MUE values for those codes are set accordingly high.

MUE versus NCCI bundling — different mechanism

An MUE denial and a bundling denial can look similar on a remittance, but they're two different edits solving two different problems. NCCI's procedure-to-procedure edits block specific pairs of codes from being paid together on the theory that one is normally part of the other 2; an MUE, by contrast, caps how many units of a single code are plausible on a single date, independent of what else was billed 1.

Read the denial's actual reason before choosing how to fix it — attaching 59, XE, XS, or XU to a claim that actually tripped a unit cap addresses the wrong rule and won't resolve the denial.

Not every MUE denial is final

Some MUE values are hard caps: CMS treats exceeding them on a single date of service as essentially never correct, and no amount of documentation reverses the denial for that line. Other MUE values are set more conservatively — CMS assumes the excess is clinically improbable rather than truly impossible, which leaves room to appeal with documentation that supports why the higher count was accurate for that specific patient and date 1.

The practical difference matters before you spend time building an appeal: check whether the specific code's MUE is the kind that can be documented around, rather than assuming every unit denial is worth contesting.

A worked example

A practice bills a code six times for one patient on one date, and the MUE for that code is set at four. The remittance comes back with only four units paid and the remaining two denied — not the whole line, just the units above the cap. If the chart genuinely documents six separate, medically necessary instances of that service on that date, and the code's MUE is the kind CMS treats as clinically improbable rather than absolutely impossible, an appeal with that documentation is worth filing.

If instead the six units were the result of a data-entry habit — rounding up, or reporting a units field that doesn't map cleanly to what was actually done — the fix isn't an appeal, it's correcting how the units are being counted at the point of entry so the same overage doesn't repeat on the next claim.

Where to look up the value before you bill

CMS publishes MUE values alongside the broader NCCI edit files, and the same source explains which unit counts are hard caps versus which allow appeal 1. Checking the value before submitting a high-unit claim line — rather than after a denial — avoids the delay of resubmission and keeps the claim inside your payer's timely-filing window instead of eating into it.

MUE values are also revised periodically, so a count that was payable in a prior period isn't guaranteed to still be under the current cap; recheck a high-volume code's MUE when you notice a change in how a line is paying.

This is worth building into a routine rather than a one-time lookup: a practice that bills the same handful of high-unit codes repeatedly benefits from checking those specific MUE values on a fixed schedule — quarterly is a reasonable cadence for a solo practice — rather than discovering a revision only after a batch of claims has already gone out at the old count.

Reading and appealing a units denial

A unit-cap denial on the remittance ties back to a specific MUE for that code; before appealing, confirm your MAC — since MAC-specific instructions and local review processes govern how the appeal is handled 3. CMS's program instructions in the Internet-Only Manuals lay out the claims-processing rules an appeal has to work within 4.

An appeal on an MUE that allows one needs documentation specific to that date of service — why this patient, this date, genuinely required more units than the cap assumes — not a general statement that the service was medically necessary.

An MUE isn't the same question as medical necessity

A service can be entirely medically necessary and still exceed its code's MUE — the two are separate questions, and passing one doesn't guarantee passing the other. A high but clinically justified unit count that a payer is unlikely to cover in full is a different problem from an MUE-blocked line, and it's handled through the ABN — the Advance Beneficiary Notice of Noncoverage a practice issues before delivering a service likely to be denied 5 — rather than through an MUE appeal.

Don't assume a documented medical need automatically overrides a hard-cap MUE — for those codes, the fix is billing within the cap and handling any genuinely necessary excess through the appropriate coverage or notice process, not through disputing the edit itself. Confusing the two processes is a common source of wasted appeal effort: no ABN, however properly issued, converts a hard-cap MUE denial into a payable claim.

Common questions

No. CMS assigns MUE values only to codes where a unit cap is meaningful — many codes have no MUE at all, or a value high enough that it rarely matters in ordinary practice. The edit is most relevant for codes commonly billed with multiple units, like certain injections, supplies, or time-based services.

Check whether the denied line was reduced for exceeding a unit count on a single code, versus denied because it paired with another code on the same date. A unit-count problem on one line by itself points to an MUE; a denial tied to a second, different code on the claim points to a bundling edit instead.

Not reliably, and not honestly if the count wasn't accurate. Some MUEs allow appeal with supporting documentation rather than a modifier alone; hard-cap MUEs don't allow an override at all. Attaching an unrelated modifier to force payment past a genuine unit cap is the pattern that draws review, not a fix.

CMS sets and publishes national MUE values for most codes; your Medicare Administrative Contractor's role is in how a denial is processed and appealed for your jurisdiction, not in setting the underlying cap itself. Confirm which MAC processes your claims before starting an appeal, since the process is jurisdiction-specific.

An MUE is a hard or conditional cap on units Medicare will pay for a code on one date, unrelated to whether the service was covered at all. An Advance Beneficiary Notice applies when a covered service is likely to be denied for a different reason, such as medical necessity — the two situations call for different handling.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

  1. 1.Centers for Medicare & Medicaid Services (2026). Medically Unlikely Edits. Centers for Medicare & Medicaid Services (CMS). linkThat an MUE caps units of one code per patient per date, that CMS publishes the value per code, and that some MUE denials can be appealed with documentation while others cannot.
  2. 2.Centers for Medicare & Medicaid Services (2026). NCCI for Medicare. Centers for Medicare & Medicaid Services (CMS). linkThat NCCI procedure-to-procedure edits block specific code pairs from paying together, a mechanism distinct from an MUE's per-code unit cap.
  3. 3.Centers for Medicare & Medicaid Services (2026). Medicare Administrative Contractors. Centers for Medicare & Medicaid Services (CMS). linkThat Medicare claims administration and appeals processing is regionalized by MAC, and CMS publishes which MAC serves each jurisdiction.
  4. 4.Centers for Medicare & Medicaid Services (2026). Internet-Only Manuals (IOMs). Centers for Medicare & Medicaid Services (CMS). linkThat CMS's claims-processing program instructions, including the rules an MUE appeal has to work within, are published in the public Internet-Only Manuals.
  5. 5.Centers for Medicare & Medicaid Services (2026). Beneficiary Notices Initiative (BNI). Centers for Medicare & Medicaid Services (CMS). linkThat the Advance Beneficiary Notice of Noncoverage is published under CMS's Beneficiary Notices Initiative and is issued before billing a Medicare patient for a likely-denied service, distinct from an MUE appeal.

https://www.gale.care/for-providers/fs-mue-limits · 5 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

Findability, by specialty

How practices like yours get found in local search and AI answers — the honest playbook, per specialty.

SEO for private practices · SEO for AI search / answer engines (all verticals)