GZ Modifier in Medical Billing: No ABN Denial Guidelines

GZ modifier indicates that an item or service is expected to be denied as not medically necessary, and a mandatory Advance Beneficiary Notice of Noncoverage (ABN) was not issued to the patient. Appending this modifier to your claim signals to Medicare that you anticipate a denial due to a lack of clinical necessity while acknowledging that no financial waiver was obtained, resulting in an automatic denial and prohibiting you from billing the patient for the service.

GZ Modifier in Medical Billing: Expected Denial, No ABN Obtained Guidelines

There’s a modifier in Medicare billing whose entire purpose is admitting a mistake happened. Not covering it up, not quietly writing it off without explanation, but formally telling Medicare: we expected this wouldn’t be covered, and we didn’t get the paperwork done to protect our ability to collect from the patient. That honesty is exactly what GZ represents, and understanding it properly is less about billing mechanics and more about what happens when a practice’s ABN process breaks down.

The GZ modifier identifies an item or service expected to be denied as not reasonable and necessary, where the provider did not obtain a valid Advance Beneficiary Notice from the patient beforehand. Unlike its close relative GA, where a signed ABN protects the provider’s ability to bill the patient after a denial, GZ represents the opposite outcome: the provider generally cannot collect from the patient at all, and absorbs the full cost of the service as a write-off. This guide covers exactly when GZ applies, why it exists as a distinct modifier rather than simply omitting the claim, and how a practice can keep it a rare exception rather than a routine occurrence.

What is the GZ Modifier?

GZ is a HCPCS Level II modifier that stands for Item or service expected to be denied as not reasonable and necessary. It’s appended to a CPT or HCPCS code when a provider anticipated that Medicare would likely deny the service for lack of medical necessity, but failed to secure a valid, signed Advance Beneficiary Notice from the patient before the service was furnished.

GZ and its close relative GA both address the same underlying situation, a service the provider expects Medicare might not cover for medical necessity reasons. What separates them entirely is whether the ABN paperwork was actually completed correctly beforehand. GA represents that it was. GZ represents that it wasn’t, and it carries a direct, unavoidable financial consequence as a result.

The Core Consequence: The Provider Absorbs the Cost

This is the single most important fact about GZ, and it’s what makes it fundamentally different from every other modifier in the ABN family. When a claim carries GZ and Medicare denies it, the provider generally cannot bill the patient for that service. The financial responsibility stays entirely with the practice.

Feature	GA (Valid ABN Obtained)	GZ (No Valid ABN)
ABN status	Signed, valid ABN on file before the service	No valid ABN was obtained
Result of a medical necessity denial	Provider can bill the patient	Provider generally cannot bill the patient
Who absorbs the cost	The patient, per the terms of the ABN	The provider, as a write-off

Why GZ Exists as a Distinct Modifier

It’s worth asking why a provider would append GZ at all, rather than simply submitting the claim without any modifier, or not billing Medicare for the service in the first place. The answer comes down to transparency and compliance protection, both for the provider and for the integrity of the claims system as a whole.

Submitting a claim honestly flagged with GZ tells Medicare exactly what happened: the provider expected a medical necessity denial, didn’t have a valid ABN, and is proceeding with full awareness that the claim will likely be denied and that the provider will absorb the cost. That’s a meaningfully different, and far safer, position than either of the alternatives. Submitting the claim without any modifier, hoping it slips through as a normal covered service, risks the appearance of attempting to bypass Medicare’s coverage rules. Billing the patient directly despite having no valid ABN, meanwhile, violates the limitation on liability protections patients are specifically entitled to.

How GZ Claims Get Processed

GZ-flagged claims follow a predictable, largely automated path once submitted.

Step	What Happens
Claim submission	The service is billed with GZ appended to the applicable CPT or HCPCS code
Automatic denial	Medicare denies the line item as provider-liable, generally without a complex manual medical necessity review
Reason code assignment	The denial is typically processed using Claim Adjustment Reason Code CO-50, reflecting a non-covered service determination
Financial resolution	The provider absorbs the cost; the patient cannot be billed for that specific service

That lack of a complex manual review is worth noting. Because GZ is essentially a self-attestation that the claim is expected to be denied, Medicare’s system doesn’t need to conduct the same kind of substantive coverage investigation it might for an ambiguous claim, the outcome is already effectively known before the claim is processed.

When Should GZ Be Used?

GZ applies in a fairly narrow, specific set of circumstances, all of which need to be true together.

Condition	Required?
The provider expects the service to be denied specifically for lack of medical necessity	Yes
No valid, signed ABN was obtained from the patient before the service was furnished	Yes
The service is one that could potentially be covered under different circumstances (not a categorical statutory exclusion)	Yes
The provider intends to proceed with billing Medicare honestly, accepting that the claim will likely be denied and the cost absorbed	Yes

That third condition matters more than it might initially seem. GZ is specifically for services that sit in genuinely uncertain medical necessity territory, not for items or services that are never covered by Medicare under any circumstances. A statutorily excluded service, cosmetic surgery, routine dental care, doesn’t call for GZ even without an ABN, since the ABN framework never applied to that service in the first place. That scenario calls for modifier GY instead.

What Counts as No Valid ABN

GZ isn’t limited to situations where an ABN was never discussed at all. Several different documentation gaps all fall under the same “no valid ABN” umbrella that triggers GZ.

Situation	Does It Trigger GZ?
No ABN was ever presented to the patient	Yes
An ABN was presented, but not signed before the service was furnished	Yes
An ABN was signed, but on an outdated or expired version of Form CMS-R-131	Yes
An ABN was signed, but is missing required elements, such as the estimated cost field	Yes
A complete, properly executed ABN on the current form version is on file	No, this is a GA scenario instead

GZ vs. GY: A Distinction Worth Reinforcing

GZ and GY both represent claims Medicare will deny, and both involve no ABN in play, but they answer fundamentally different questions and shouldn’t be confused.

Feature	GZ	GY
What triggers it	An expected medical necessity denial, without a valid ABN	A categorical statutory exclusion, where no ABN was ever required
Could the service ever be covered?	Potentially, under different documentation or circumstances	No, never, by definition
Provider liability after denial	Provider generally cannot bill the patient	Provider can bill the patient directly, since no ABN protection was ever needed
What it signals	A process failure (an ABN that should have been obtained but wasn't)	Correct identification of a service Medicare never covers

That contrast highlights something important about GZ specifically: it’s the one modifier in this family that represents an actual gap in the provider’s process, not a routine, expected billing scenario. GY reflects normal, correct handling of a categorically excluded service. GZ reflects a situation that, ideally, shouldn’t happen very often at all.

GZ Documentation Requirements

GZ modifier documentation should support that the item or service is expected to be denied by Medicare as not reasonable and necessary and that a valid Advance Beneficiary Notice (ABN) was not obtained. The medical record should clearly document the service provided, medical necessity circumstances, and supporting clinical information to ensure accurate claim submission.

Documentation Element	Why It Matters
Confirmation that no valid ABN exists for the specific service and date	Establishes the factual basis for using GZ rather than GA
Clinical documentation supporting why the service was performed despite anticipated medical necessity concerns	Supports the underlying medical decision-making, separate from the billing outcome
Internal notation of why the ABN process wasn't completed, where practical	Useful for identifying and correcting the underlying workflow gap that led to the missed ABN
Confirmation the service isn't actually a statutory exclusion that should have been coded GY instead	Prevents misapplying GZ to a scenario that never needed an ABN in the first place

Common GZ Modifier Billing Mistakes

Common GZ modifier billing mistakes include using it when a valid ABN was obtained, confusing GZ with GA or GY, and failing to document why the service is expected to be denied as not reasonable and necessary. Incorrect modifier selection or weak supporting documentation can result in claim denials, provider liability, and compliance concerns.

Mistake	What's Actually Happening
Attempting to bill the patient anyway after a GZ-flagged claim is denied	Directly violates the limitation on liability protection GZ represents; the provider cannot collect from the patient in this scenario
Using GZ for a statutorily excluded service	That scenario calls for GY, since no ABN was ever required for a categorical exclusion
Combining GA and GZ on the same claim line	These represent mutually exclusive facts (ABN obtained versus ABN not obtained) and shouldn't appear together
Treating an expired or improperly completed ABN as valid, and billing GA instead of GZ	An invalid ABN doesn't protect provider billing rights, regardless of whether it was signed; this should be coded GZ, not GA
Submitting the claim with no modifier at all, hoping it processes as a routine covered service	Risks appearing to bypass Medicare's coverage determination process rather than transparently flagging the expected denial
Treating GZ as a routine, acceptable billing outcome rather than a process failure worth correcting	A recurring pattern of GZ claims signals a systemic gap in how the practice identifies and documents expected denials before service delivery

Best Practices for Billing the GZ Modifier

For accurate GZ modifier billing, confirm that the service is expected to be denied as not reasonable and necessary and that a valid ABN was not obtained from the patient. Maintain complete clinical documentation, distinguish GZ from GA and GY, and verify Medicare coverage requirements before claim submission to reduce coding errors and compliance risks.

Treat GZ as a signal to fix a process gap, not just a modifier to append and move on from: Every GZ claim represents a specific point where the ABN workflow broke down.
Train front-desk and clinical staff to flag potential medical necessity concerns at the point of scheduling or eligibility verification, giving enough lead time to complete a proper ABN before the service, rather than discovering the issue too late.
Confirm ABN validity carefully before assuming a service qualifies for GA instead of GZ. An expired form version or an incomplete field can convert what looked like a protected claim into a provider-liable one.
Never bill the patient after a GZ-flagged denial, even informally or as a courtesy request. This directly conflicts with the protection GZ represents.
Track GZ usage over time as a practice-level metric, not just a claim-by-claim event. A rising trend is a clear signal to revisit ABN training and workflow timing.
Distinguish clearly between GZ and GY scenarios during staff training. Confusing a statutory exclusion with a medical necessity concern leads to the wrong modifier and the wrong financial outcome.
Audit denied GZ claims periodically to identify whether the same service types, providers, or scheduling patterns keep generating missed ABNs, and address the specific root cause.

Compliance Considerations

GZ occupies a genuinely dual role in Medicare compliance. Used correctly and occasionally, it’s a protective, transparent tool, proof that a practice is honestly reporting an isolated process gap rather than attempting to work around coverage rules or improperly bill a patient without proper notice. That transparency is exactly what helps a practice avoid the appearance of fraudulent billing that submitting an unflagged claim, or improperly billing the patient, would risk instead.

Used frequently, GZ becomes a different kind of signal entirely. A consistent, elevated pattern of GZ claims suggests a systemic breakdown in the practice’s ABN identification and documentation process, not a series of isolated incidents. That pattern is worth taking seriously from a compliance standpoint, not primarily because GZ itself is risky to use, but because it represents a recurring revenue loss the practice is effectively documenting about its own operations, and because a review of that pattern is likely to surface the same underlying workflow gap repeatedly until it’s actually addressed.

The healthiest way to think about GZ is as a rare, honest exception rather than a routine billing outcome. If it’s showing up often, the real fix isn’t better GZ coding, it’s a better front-end process for catching expected medical necessity concerns early enough to get a valid ABN completed before the service happens.

Building a Workflow That Keeps GZ Rare

Since GZ represents a process gap rather than a routine outcome, the most effective response isn’t better GZ coding, it’s a front-end workflow that catches expected medical necessity concerns early enough to make GZ unnecessary in the first place.

Build medical necessity screening into scheduling, not just coding. Many services with a real chance of denial are predictable based on the diagnosis and the procedure being ordered. Flagging that combination at the point of scheduling, before the patient even arrives, gives staff time to prepare a proper ABN rather than discovering the issue after the fact.
Give front-desk staff a simple, current reference for high-risk service and diagnosis combinations. Local coverage determinations and national coverage determinations change, and a reference that’s a year or two out of date can miss situations that would trigger an ABN requirement today.
Set a firm internal rule that services aren’t performed until the ABN question has been resolved, one way or the other. A service performed before anyone checks whether an ABN was needed removes the option to get one in time.
Review GZ claims monthly, not just during an annual audit. A monthly cadence catches an emerging pattern, a particular service, provider, or scheduling gap generating repeat GZ claims, while it’s still small enough to fix quickly.
Close the loop with clinical staff when a GZ claim happens. The people ordering or performing the service are usually in the best position to explain why the ABN conversation didn’t happen, and that feedback is what actually prevents the same gap from repeating.

Frequently Asked Questions About the GZ Modifier

What does the GZ modifier mean in medical billing?

GZ indicates that a service was expected to be denied as not reasonable and necessary, and that the provider did not obtain a valid, signed Advance Beneficiary Notice from the patient before the service was furnished.

Can the patient be billed if a claim with GZ is denied?

Generally, no. Because no valid ABN protected the patient’s advance notice rights, the provider cannot bill the patient for that specific service and absorbs the cost as a write-off.

What's the difference between GZ and GA?

Both apply to services expected to be denied for medical necessity. GA reflects that a valid, signed ABN was obtained beforehand, allowing the provider to bill the patient after a denial. GZ reflects that no valid ABN exists, meaning the provider cannot bill the patient.

Should GZ be used for a service Medicare never covers under any circumstances?

No, that’s a statutory exclusion, which calls for modifier GY instead, since the ABN framework never applied to that type of service in the first place.

Does an expired ABN form count as a valid ABN?

No, an ABN completed on an outdated or expired version of Form CMS-R-131, or one missing required elements like the estimated cost field, isn’t considered valid. A claim in that situation should generally be coded GZ, not GA.

Why would a provider submit a claim with GZ instead of just not billing Medicare at all?

Submitting the claim with GZ transparently documents that the provider anticipated a denial and is proceeding honestly, rather than either attempting to bypass Medicare’s coverage rules or improperly billing the patient without a valid ABN.

What does it mean if a practice frequently submits claims with GZ?

A recurring pattern of GZ claims typically signals a systemic gap in the practice’s process for identifying potential medical necessity concerns early enough to obtain a proper ABN, rather than a series of unrelated, isolated incidents.

Medical Billing Services @ 2.45% of Total Collection

Get a free assessment from our billing experts

Recent Articles

Our High Quality Medical Billing Services