GA, GX, GY and GZ: The Modifiers That Assign Liability
Every other modifier in this cluster says something about the service — that it was repeated, that it was distinct, that it was bilateral. These four say something about the money. CMS puts the default plainly: on a line Medicare does not pay, the provider is liable unless a specific modifier or indicator on the claim assigns that liability to the beneficiary. The modifier is the mechanism, so leaving it off is not a neutral omission — it is a decision to absorb the balance.
Updated 8 min read
On this page
Key takeaways
- The default is that the provider is liable for a non-covered line. One of these modifiers is what moves that liability to the patient.
- Two questions produce all four: is the item never a benefit at all, or a benefit not expected to be reasonable and necessary here — and was advance notice given?
- Advance notice only changes the answer in one of those columns. Where the item is statutorily excluded, the patient owes regardless, which is why that notice is voluntary.
- GA is a rebuttable presumption, not proof. Contractors do not routinely collect the notice, and may ask for it when they have reason to doubt.
- Liability shifts only if the notice accurately identified the service and the reason it predicted turns out to be the actual reason for denial. Nothing checks that match at submission.
- GZ says no notice was issued and the provider is liable. It is the honest report of a failure that has already happened, and it is not made better by omitting it.
- A modifier applied routinely stops carrying information — and CMS tells contractors to look hardest at exactly the claims where that has happened.
The default this whole family works against
Start from what happens when nothing is said. A line Medicare does not pay leaves someone out of pocket, and the manual is explicit about who that is by default: providers are liable for these denials unless a specific modifier — or an occurrence code serving the same function on an institutional claim — assigns liability to the beneficiary. There is no neutral position. A claim that expects denial and carries none of these modifiers has answered the question, and it has answered it against the practice.
That is why these four sit oddly in a cluster about coding. They are not describing the work. They are the claim's statement about a conversation that did or did not happen before the service, and about what kind of non-coverage this is. How a Modifier Changes Adjudication sets out the general rule that a modifier is an assertion nothing verifies at payment time; nowhere is that sharper than here, where the assertion is about a signature on a form in a filing cabinet.
Two questions, four answers
The set looks arbitrary until you see that it is a grid. The first question is what kind of non-coverage is expected. The second is whether the patient was told in advance. Only the first question has a bearing on whether the second one matters.
| Expected reason for denial | Notice was issued | No notice was issued |
|---|---|---|
| A covered benefit, but not expected to be reasonable and necessary for this patient | GA — a required notice was issued and is kept on file. It need not be sent with the claim, but it must be produced on request. | GZ — no notice was issued. The modifier records that, and with it that the provider is the one liable. |
| Statutorily excluded, or not within the definition of any Medicare benefit | GX — a notice was issued voluntarily, because none was required. Reported with GY or on its own. | GY — the item is excluded or is not a benefit. Reported with GX or on its own. |
The asymmetry between the rows is the point. In the top row the notice is what moves liability, so its absence is expensive. In the bottom row the patient owes regardless, so the notice is a courtesy rather than a protection — which is exactly why the rules describe it as voluntary.
Why the bottom row needs no notice
GA is a presumption, and it is rebuttable
Notifiers do not routinely send the notice with the claim. The manual explains why in a phrase worth quoting to anyone who treats the modifier as settled: the arrangement rests on a rebuttable administrative presumption that a claim carrying the modifier means a proper form was used and delivered in compliance with the instructions. Contractors may — and the manual says should — ask for the notice whenever they are not confident that presumption holds.
The sentence that decides whether liability actually moved
That has a practical consequence that is easy to miss when the notice is treated as paperwork. The reason written on the form is not boilerplate — it is the term the protection is measured against. A form filled in with a generic phrase about Medicare possibly not paying may satisfy nobody's file audit and, more to the point, may not match whatever the remittance eventually says.
Two failure modes, opposite in shape
Withholding the modifier because it looks like inviting denial
It does not, and the manual instructs contractors accordingly: they must not make an automatic finding that a claim should be denied merely because the modifier was submitted, and the existence of a notice is not to prejudice the determination of whether a denial is justified. The modifier says what happens if denial occurs; it is not a prediction the payer is entitled to act on.Applying it to everything, so it says nothing
The manual anticipates this precisely. Where notices are given routinely for a category of items, it observes that virtually every claim including one will carry the modifier — and it lists exactly those claims among the ones a contractor should look at harder. A signal appended by default is a signal that has stopped being one, and it draws scrutiny rather than deflecting it.Reporting GZ, and what it costs
Where denial is expected on medical-necessity grounds and no notice was issued, the modifier that fits records both facts, and the second one is that the provider is liable. Reporting it accurately means absorbing a balance. The alternative is not a better outcome — it is billing a patient who was never warned, which is the thing the notice rules exist to prevent, and it is the version that turns a process failure into a compliance one.Using the wrong row
Reporting a statutory exclusion as though it were a medical-necessity case, or the reverse, misstates why the claim will be denied and therefore who owes. The distinction is not a coding nicety — it is the difference between a balance the patient owes whatever happened and one they owe only because they were told in advance.
Where the modifier's answer ends up
Common questions
Does adding GA make a denial more likely?
It should not, and CMS instructs contractors on the point directly: they are not to make an automatic finding that a claim should be denied merely because the modifier was submitted, and the fact that a notice was given is not to prejudice the determination of whether there is sufficient evidence to justify denial. The modifier states who is liable if the claim is denied; it is not a concession that it should be. Withholding it to avoid drawing attention forfeits the protection it exists to record.
Do we have to send the notice with the claim?
No. Notifiers are generally not required to submit copies routinely, and the arrangement rests on what the manual calls a rebuttable administrative presumption — the modifier on the claim is taken to mean a proper form was prepared and delivered in compliance. The corollary is the part to plan for: a contractor may request the form whenever it is not confident that presumption holds, and the manual tells them they should. The notice has to be retrievable, not submitted.
Does a signed notice guarantee we can bill the patient?
No, and this is the most consequential detail in the whole mechanism. Liability shifts only where the notice accurately specifies the items or services and where the expected reason for denial it stated turns out to be the actual reason for denial. Both conditions, and neither is checked when the claim is submitted. A notice that identified the wrong service, or that predicted one reason where the claim was ultimately denied for another, leaves the balance with the practice despite a signature and a modifier.
What is the difference between GX and GY?
They describe different things about the same situation and may appear together. One reports that the item is statutorily excluded or is not within the definition of any Medicare benefit — a fact about coverage. The other reports that a notice was issued voluntarily, which it was, because none was required for something never covered in the first place. Either may also be reported on its own, depending on whether a voluntary notice was actually given.
Is reporting GZ better than reporting nothing?
It is the accurate report, and accuracy is the standard rather than the outcome. Where denial is expected on medical-necessity grounds and no advance notice was issued, that modifier records both facts, including that the provider bears the balance. Leaving it off does not restore a protection that was never created — the notice is what creates it — and billing the patient instead is the outcome the rules were written to prevent. The place to fix a recurring pattern of it is upstream, in when notices get issued, not on the claim.
Key terms in this article
Defined once, on their own pages.
Continue learning
The notice these modifiers report, and the denials they anticipate.
The Advance Beneficiary Notice (ABN)
The instrument itself — when it is issued, and what makes one valid enough to rely on.
How to Issue an Advance Beneficiary Notice
The step-by-step version, including the part these modifiers depend on: naming the service and the reason.
Non-Covered Service Denials
The bottom row of the grid: when the plan never covered it, and why notice does not change who owes.
Billing the Patient for a Denied Claim
The full decision these modifiers declare one input to — group code, contract, and advance notice read together.
How a Modifier Changes Adjudication
Why an assertion nothing verifies at payment time is only as strong as the record behind it.
Coding, Modifiers & Edits
The cluster: what modifiers assert, which edits read them, and what the record has to show.
Authoritative sources
- CMS Medicare Claims Processing Manual, Pub. 100-04, Chapter 1 § 60.4.2 (opens in a new tab)
States that HCPCS modifiers signify a line item is not covered or not payable for a range of reasons, and that providers are liable for these denials unless a specific modifier — or an indicator such as occurrence code 32 — specifically assigns liability to the beneficiary. Elsewhere in the chapter the GZ modifier is cross-referenced as the one indicating the provider is liable, consistent with this section.
- CMS Medicare Claims Processing Manual, Pub. 100-04, Chapter 30 §§ 110.5.1–110.5.2 (opens in a new tab)
Explains that notifiers are generally not required to submit notices with claims, on a rebuttable administrative presumption that the modifier signifies a proper form prepared and delivered in compliance, and that contractors may and should request the notice where they are not confident of it. States that liability is shifted to the beneficiary only if the notice accurately specifies the items or services and the expected reason for denial turns out to be the actual reason for denial, and identifies routinely-issued notices as a circumstance warranting review. In the equipment and supplies instructions, directs contractors not to make an automatic finding of denial merely because the modifier was submitted.
- CMS MLN Booklet — Medicare Advance Written Notices of Non-coverage (MLN006266) (opens in a new tab)
Sets out when to report each of the four modifiers: a mandatory notice issued and kept on file, available on request; a voluntary notice for a service never covered; a statutorily excluded item or one outside the definition of any Medicare benefit; and an expected medical-necessity denial where no notice was issued. States that CMS may hold a provider financially liable and bar collection from the patient where a required notice was not issued or the contractor finds it invalid.