Managing Medicare ABNs From Patient Notice Through Billing

A Medicare Advance Beneficiary Notice of Noncoverage (ABN) is not simply a form for collecting a patient’s signature before providing a service Medicare may not pay for. It is a specific Original Medicare notice with specific requirements.

When a Medicare ABN is required and properly delivered, it gives the beneficiary advance notice that Medicare is expected to deny payment for an item or service and allows the patient to make an informed decision about whether to proceed.

Proper notice can also be necessary for the provider or supplier to shift financial liability to the beneficiary in circumstances governed by Medicare’s limitation-on-liability requirements.

For a medical practice, the difficult part is rarely finding the form. The challenge is identifying the appropriate situation early enough, completing the notice correctly, explaining it to the patient, documenting the patient’s choice, and ensuring the billing team knows an ABN was issued.

That makes ABN compliance a workflow issue as much as a billing issue.

---

Key Takeaways

• An ABN is a specific Original Medicare financial-liability notice, not a blanket waiver for Medicare patients.
• Potential ABN situations need to be identified before the item or service is furnished because a missed advance-notice requirement generally cannot be repaired retrospectively.
• A patient signature alone does not establish that an ABN was properly delivered. Timing, specificity, cost information, beneficiary selection, and completion all matter.
• Practices need to distinguish Original Medicare from Medicare Advantage before initiating the applicable notice workflow.
• ABN information must move from pre-service staff through patient notification and documentation to billing so claim handling reflects what occurred.
• Monitoring should evaluate both missed ABNs and unnecessary or improperly issued notices rather than treating higher ABN volume as evidence of better compliance.

---

How the Medicare ABN Process Works

Understand What an ABN Is Designed to Do

The Advance Beneficiary Notice of Noncoverage, Form CMS-R-131, applies to Original Medicare fee-for-service in situations covered by CMS requirements.

The ABN is used in specified circumstances when a provider or supplier believes Medicare is likely to deny payment and advance notice is required under Medicare’s applicable financial-liability rules.

CMS also permits voluntary ABN use in certain circumstances, but voluntary notices do not operate in the same way as required ABNs for transferring financial liability.

A common example is an item or service that Medicare usually covers but is expected to be denied in the particular situation because applicable Medicare coverage requirements are not met.

The distinction matters.

An ABN should not be treated as a blanket waiver that practices ask every Medicare patient to sign. It also should not be used simply because staff are uncertain whether a claim will be paid.

The practice needs to understand why Medicare is expected to deny the particular item or service and whether the ABN requirements apply to that situation.

The ABN Decision Often Starts Before the Patient Arrives

A reliable ABN process begins upstream from billing because the information needed to identify a potential ABN situation must reach the appropriate staff before the item or service is furnished.

If the billing department discovers after the service that a required ABN was not provided in advance, the practice generally cannot correct that failure by obtaining the notice retrospectively.

That means practices need a way to identify potential ABN situations during scheduling, order review, eligibility or coverage review, pre-service preparation, or another appropriate point before care is furnished.

Exactly where that happens depends on the practice.

A specialty office may identify potential coverage limitations while reviewing a procedure order. A laboratory workflow may identify frequency or medical-necessity concerns before testing. Another practice may rely on billing or authorization staff to review certain scheduled services before the patient’s appointment.

What matters is that the responsibility is defined.

Workflow Point	Operational Responsibility
Service or order identified	Recognize whether an ABN situation may exist
Coverage review	Determine the specific reason Medicare payment is expected to be denied
Before the service	Provide the appropriate notice with enough time for the patient to consider the options
Patient decision	Obtain the required selection, signature, and date
Clinical service	Proceed according to the patient’s choice and applicable requirements
Billing	Submit the claim appropriately based on the ABN and service circumstances
Record retention	Maintain the ABN with the appropriate patient documentation

Without this connection between front-end and back-end workflows, ABNs are easily missed.

Timing Matters

An ABN is an advance notice.

CMS requires effective delivery before the potentially noncovered item or service is furnished and sufficiently far in advance for the beneficiary to understand the notice, consider the available options, and make an informed choice.

That means the ABN should not become a piece of paperwork hurriedly presented after the service has already occurred.

Operationally, practices need to determine who is responsible for presenting the notice and at what point in the patient’s visit.

The patient should have an opportunity to understand why Medicare is expected to deny payment, consider the estimated financial impact, and make the applicable choice before proceeding.

This is one reason identifying the issue before check-in—or at least before the service itself—is preferable to discovering it during claim submission.

A Signature Alone Does Not Make an ABN Valid

A common compliance mistake is treating the patient’s signature as the primary objective.

A beneficiary’s signature does not cure an ABN that was delivered too late, completed inadequately, or otherwise failed to satisfy applicable notice requirements.

Among other requirements, the ABN identifies the item or service at issue, explains why Medicare may not pay, and includes a good-faith estimate of the beneficiary’s expected cost consistent with CMS instructions. The beneficiary then selects among the options provided on the CMS form and signs and dates the notice.

The explanation needs to be specific enough for the patient to understand the reason Medicare is expected to deny payment.

A vague statement such as “Medicare may not cover this” does not accomplish the same purpose as explaining the applicable reason for the expected denial.

The practice should also use the current CMS-approved form and instructions rather than relying indefinitely on a saved copy whose status has not been verified.

CMS maintains the current Form CMS-R-131 and instructions, so practices should establish a reliable source for obtaining the form rather than hard-coding a particular expiration date into internal training materials.

Patients Need a Meaningful Choice

The purpose of the ABN is not simply to protect the practice financially. It gives the beneficiary information needed to decide what to do next.

The CMS form presents beneficiary options concerning whether to receive the item or service and, when applicable, whether a claim should be submitted to Medicare. Staff should use the current form and instructions rather than paraphrasing those choices into an informal practice-specific waiver.

Staff responsible for delivering ABNs need to understand those choices well enough to explain the process without pressuring the patient toward a particular selection, particularly when the patient is surprised by the potential cost.

If employees treat the ABN as “something you have to sign before we can continue,” the practice misses the purpose of the notice. The beneficiary should receive enough information to understand why Medicare is expected to deny payment, consider the potential financial consequences, and make an informed choice among the applicable options on the notice.

ABNs and Medicare Advantage Are Different Workflows

The standard CMS-R-131 ABN is associated with Original Medicare fee-for-service. Practices should not automatically apply that same workflow to patients enrolled in Medicare Advantage.

Medicare Advantage plans operate under coverage determination, notice, and appeal requirements that differ from the Original Medicare ABN process.

For the practice, that means insurance identification matters before staff reach for an ABN.

Employees need to distinguish between Original Medicare and Medicare Advantage and follow the appropriate process for the patient’s coverage. Practices participating with Medicare Advantage plans should understand the applicable plan and CMS requirements rather than assuming the Original Medicare ABN can be substituted.

This is another reason ABN responsibility should not rest solely with whoever happens to be at the front desk. The workflow needs enough payer knowledge behind it to determine which process applies.

---

Build ABNs Into the Revenue Cycle

Billing Needs to Know What Happened

An ABN can be completed correctly and still fail operationally if the information never reaches the billing team.

Medicare claim submission may require appropriate modifiers or other billing treatment based on whether a valid ABN was obtained and the circumstances of the service.

Billing staff therefore need reliable visibility into whether an ABN was issued, whether it was completed appropriately, and which option the beneficiary selected.

The practice should establish where the signed ABN is stored and how the billing team knows it exists. Depending on the EHR and practice-management system, that might involve a document type, workflow flag, or task. It might also involve a charge-entry notation or another standardized mechanism.

The process should not depend on someone remembering to tell the biller that the patient signed a form.

This is where ABN compliance and revenue-cycle operations directly intersect. The front-end notice and the back-end claim need to tell the same story.

Retain the ABN With the Patient Record

Documentation is important because the practice may later need to establish what notice the beneficiary received and what decision was made.

CMS guidance generally calls for retaining the ABN for five years from discharge or completion of delivery of care when no other applicable requirements under state law impose a different retention period. Electronic retention of a signed paper ABN is acceptable under CMS guidance.

The beneficiary should also receive a copy of the completed notice.

Practices should establish a consistent storage location rather than allowing ABNs to be scanned into miscellaneous document categories where they are difficult to retrieve.

Retention becomes particularly important if a patient later questions financial responsibility or a claim is reviewed.

Staff Need to Know Their Part of the Process

Not every employee needs to become an expert in Medicare coverage policy.

They do need to understand their role.

Scheduling or pre-service staff may need to recognize services that require additional review. Billing personnel may determine whether an expected denial creates an ABN situation.

Front-office or clinical staff may be responsible for presenting the notice. Billing staff needs to know how the patient’s decision affects claim submission.

Training should therefore follow the workflow rather than consist solely of reviewing the form.

A practical ABN process should make clear:

• which situations trigger review for a possible ABN
• who determines whether the notice is required
• who completes and presents the notice
• how the reason for expected noncoverage and estimated cost are established
• where the completed ABN is stored
• how billing is notified of the patient’s selection

This separation of responsibilities prevents employees from improvising Medicare policy at the point of service.

Monitor the Process for Missed ABNs and Invalid Notices

ABN problems often become visible through billing outcomes.

If the practice repeatedly encounters denials for services that should have triggered an ABN review, the problem may be occurring upstream. Staff may not recognize the service. Coverage information may not be reaching the right person. The review may also be happening after the patient has already received care.

Practices should also look at whether completed ABNs are usable.

Missing patient selections, incomplete explanations, absent signatures, incorrect timing, or outdated workflows can undermine the purpose of the notice.

A focused review of ABN-related denials and a sample of completed notices can help leadership determine whether staff are identifying the right encounters and delivering notices at the appropriate time. It can also help leadership determine whether staff are completing them correctly and carrying the beneficiary’s decision through to claim submission.

The goal is not simply to increase the number of ABNs collected. It is to improve the accuracy of when and how they are used.

Overuse can be a warning sign just as missed ABNs can be. If staff routinely obtain ABNs whenever coverage is uncertain, leadership should determine whether employees are using the notice as a substitute for understanding the applicable Medicare coverage and notice requirements. Monitoring should therefore evaluate both missed notices and unnecessary or improperly issued notices.

---

Connect the ABN Process From Coverage Review Through Billing

Advance Beneficiary Notices sit at the intersection of Medicare compliance, patient financial communication, and revenue-cycle operations.

If the practice treats the ABN as a billing form, the need may not be identified until it is too late. If it treats the ABN as a front-desk waiver, employees may collect signatures without understanding when the notice is appropriate. If the completed form never reaches billing, claim submission may not reflect what occurred before the service.

A reliable process connects all of those functions.

The practice identifies the potential coverage issue before the service and determines whether an ABN is appropriate. It gives the beneficiary meaningful advance notice and documents the patient’s decision. The practice retains the completed notice and carries the information through to claim submission.

That is what turns the ABN from another Medicare form into a functioning operational control.

---

Frequently Asked Questions About Medicare ABNs

About the Author

Jennifer Blevens-Smith is the founder and principal consultant of Integral Clinic Solutions. With more than two decades of experience supporting independent medical practices, she helps physicians, practice administrators, and healthcare leaders strengthen credentialing, payer contracting, revenue cycle operations, compliance workflows, and practice management. Her work focuses on translating complex healthcare requirements into practical operational processes. These processes improve consistency, reduce administrative burden, and support long-term practice success.

Need Help Strengthening Your Medical Practice Operations?

Integral Clinic Solutions provides practical support for medical practices navigating credentialing, contracting, revenue cycle operations, compliance workflows, front-office systems, and practice management challenges.

Explore more operational guidance, compliance insights, and healthcare business resources on the Integral Clinic Solutions blog. New articles and updates are added regularly for practice owners, administrators, and healthcare teams.

Disclaimer: This content is for informational and educational purposes only and does not constitute legal, coding, billing, compliance, financial, or medical advice. Healthcare practices must verify all operational requirements with applicable payers, regulators, and qualified professionals. Read our full Legal & Compliance Disclaimer.