US Medical BillingRevenue cycle solutions
Medicare billing

The Advance Beneficiary Notice (ABN)

The Advance Beneficiary Notice of Noncoverage (ABN) is a standardized written notice that a provider or supplier gives a Medicare beneficiary before furnishing an item or service that Original Medicare is expected to deny, typically because it may not be considered reasonable and necessary. Issued and formatted according to CMS instructions, the notice explains why payment is expected to be denied and lets the beneficiary choose whether to receive the service and accept potential financial responsibility. Because coverage rules, contractor policy, and the notice form itself change over time, providers confirm current requirements with CMS and their Medicare Administrative Contractor (MAC) rather than relying on a fixed rule.

Updated 7 min read

On this page

Key takeaways

What an ABN is and why it exists

An ABN is a formal, standardized notice used within Original Medicare so a beneficiary can make an informed choice before receiving a service that Medicare is likely to deny. The underlying concept comes from Medicare's limitation-on-liability provisions, which protect beneficiaries from unexpected charges when neither they nor the provider knew a service would be denied. By giving advance written notice, a provider documents that the beneficiary was informed, which is what allows the provider to bill the beneficiary if Medicare later denies the claim.

The notice most commonly applies where a service could be considered not medically necessary under Medicare's coverage rules, such as frequency limits or conditions described in a local coverage determination (LCD). Coverage policy is set through national and local coverage determinations, which change over time, so whether a given service warrants an ABN is a judgment made against current policy.

Scope

When providers issue an ABN

Providers generally consider an ABN when they have a genuine, specific reason to expect Medicare will deny a particular item or service. The notice is not intended to be delivered routinely to every patient or as a blanket disclaimer, and CMS guidance addresses the difference between appropriate case-by-case use and improper routine issuance.

  • A service may exceed a coverage frequency limit or fall outside conditions described in an LCD or national policy.
  • A service may be considered not reasonable and necessary for the patient's documented condition.
  • Certain items or suppliers face mandatory notice expectations under specific Medicare rules that vary by service category.

There is a distinction between services expected to be denied as not reasonable and necessary and services that Medicare never covers because they are statutorily excluded. The mandatory ABN process centers on the former. For excluded services, a provider may still choose to issue a voluntary notice as a courtesy, but the limitation-on-liability protections work differently. Confirming which category applies, and the current instructions for each, is done against CMS guidance rather than a fixed assumption.

Important

What makes a notice valid

For an ABN to support billing the beneficiary after a denial, it generally must be delivered correctly and completed with enough specificity that the beneficiary can make an informed decision. CMS specifies the current form, its fields, and delivery expectations, and these details are periodically revised.

  1. Deliver in advance

    The notice is provided before the item or service is furnished, with enough time for the beneficiary to consider options and ask questions.
  2. Identify the specific service

    It names the particular item or service expected to be denied rather than describing services in vague or blanket terms.
  3. State a reason and estimated cost

    It gives a plain-language reason payment may be denied and a good-faith cost estimate so the financial stakes are clear.
  4. Offer a genuine choice

    The beneficiary selects an option indicating whether to receive the service and how they wish the claim to be handled, then signs and dates the notice.

Caution

How the ABN affects claims and liability

When a valid ABN is on file, the provider can submit the claim to Medicare and, depending on the beneficiary's selected option, bill the beneficiary if Medicare denies payment. Medicare claims commonly carry a modifier from the HCPCS code set to signal to the MAC that a notice is on record; other modifiers signal that no notice was obtained. The exact modifier conventions are defined by CMS and applied according to current instructions.

Illustrative ABN status scenarios and their general billing effect
Illustrative ABN status scenarios and their general billing effect
ScenarioGeneral effect on beneficiary liability
Valid ABN signed; beneficiary elects to receive service and be billed if deniedProvider may bill the beneficiary if Medicare denies the claim
No ABN obtained where one was requiredLiability generally cannot be shifted; charge may become a write-off
Defective or late ABNMay be treated as if no valid notice existed for liability purposes
Voluntary notice for a statutorily excluded serviceBeneficiary is typically responsible regardless, as the service is never covered

Effects are general and depend on current CMS rules, the specific service, and how the claim adjudicates.

The outcome ultimately depends on how Medicare adjudicates the claim and on the beneficiary's selected option. Reviewing the remittance advice and the beneficiary's notice together clarifies who bears the balance; see reading the Medicare remittance and MSN for how those documents describe the outcome.

Variation and staying current

Several ABN details are not fixed and should be confirmed against authoritative sources at the time of use. These include the approved form version and its expiration, delivery and retention expectations, which service categories require notice, applicable cost or frequency thresholds, and modifier conventions.

Form and instructions
CMS publishes the standardized notice and its completion instructions, and updates them periodically; providers verify the current version.
Contractor policy
MAC-level coverage articles and LCDs shape when a service is likely to be denied, and these differ by jurisdiction and change over time.
Service-specific rules
Some categories of items and suppliers have their own notice expectations distinct from the general reasonable-and-necessary use case.

Tip

Frequently asked questions

Is an ABN required for every Medicare patient?

No. The notice is intended for case-by-case use when a provider has a specific, genuine reason to expect Medicare will deny a particular item or service. CMS guidance treats routine, blanket issuance to every patient as improper. Whether a notice is appropriate depends on current coverage policy for the service in question.

Does an ABN guarantee the provider will be paid by the patient?

No. A valid, properly executed ABN generally allows the provider to bill the beneficiary if Medicare denies the claim, but the notice must meet CMS requirements for timing, specificity, reason, cost estimate, and signature. A defective or late notice may fail to shift liability, and the actual outcome depends on how the claim adjudicates.

How does an ABN differ from prior authorization or eligibility verification?

They address different questions. Eligibility verification confirms whether a person has active Medicare coverage, and prior authorization is a pre-service approval process used for certain services. An ABN addresses the expectation that a covered-category service will be denied, usually as not reasonable and necessary, and documents the beneficiary's informed choice to proceed.

Is an ABN used with Medicare Advantage plans?

The ABN is a feature of Original Medicare fee-for-service. Medicare Advantage plans administer coverage under their own rules and use their own beneficiary notices and appeal processes. Providers confirm the specific plan's requirements rather than assuming the Original Medicare process applies.

What happens if the ABN is filled out incorrectly?

A notice that is delivered too late, uses vague or coercive wording, omits the reason or cost estimate, or is unsigned may be considered defective. In that case it generally does not transfer financial responsibility to the beneficiary, and the denied charge may become a provider write-off. Current CMS completion instructions define what makes a notice valid.

Ready to improve your revenue cycle?

Explore our services and knowledge base to see how we can help.