Skip to main content
v2026.11,610 entries · CC-BY 4.0
CASRAIRegulatory RadarNever miss a regulatory change that affects your research officeA daily digest of new regulatory and compliance content, plus 150 questions/day to Ask CASRAI. Built for research administrators and compliance officers.See Regulatory Radar CASRAI · Own product

Modifier GA: Shifting Liability With an ABN on File

Modifier GA asserts that an Advance Beneficiary Notice was issued before the service, shifting liability to the beneficiary if Medicare denies. When it is defensible, why GA lines go in as covered charges, the notice defects that void it, and GA versus GZ, GX, GY and KX.

Ask about Modifier GA: Shifting Liability With an ABN on File

Answers are drawn from this guide and the rest of the CASRAI corpus, with a link to every source.

Answers are AI-generated from CASRAI’s own published pages and can be wrong, so check the linked sources before relying on one; your question is logged without personal data — never sold, never used to train a third-party model — to show us what CASRAI is missing, so please do not type personal or confidential details. How we use this

Written and maintained by CASRAI Editorial Board

Last updated

Modifier GA is the claim-side half of a two-part act. The first half happened before the service: a beneficiary was given an Advance Beneficiary Notice of Noncoverage, understood that Medicare was expected to deny the item, and chose to have it anyway. Modifier GA is how the claim says so — and it is what makes the beneficiary, rather than the provider, liable when the denial arrives.

Because the modifier’s validity depends entirely on something that happened earlier, GA is unusual in this family: the decision is made before the encounter, not at billing. By the time a coder is looking at the claim, the answer has already been determined by whether a proper notice was issued. That is why the most common GA problems cannot be fixed by re-coding.

The Decision Rule

Modifier GA is correct when all of these hold:

  1. The item or service is one Medicare would ordinarily cover, but you expect it to be denied in this instance as not reasonable and necessary — a medical-necessity or frequency denial. This is the mandatory-ABN category. Something Medicare never covers by statute is a different situation entirely.
  2. A valid ABN was issued to the beneficiary before the service was furnished, item-specific and beneficiary-specific, with enough time for a real decision.
  3. The beneficiary selected an option on the notice and, where they chose to receive the item and have Medicare billed, signed it.
  4. The line is submitted as a covered charge. This is the mechanical detail people miss — see below.

Contractor guidance frames the same test operationally: append GA when an ABN was provided and a denial is expected because the item is not reasonable and necessary, including where the provider has determined the service will not be covered under an active Local Coverage Determination, and where any resulting denial would be a medical-necessity denial.

The mechanical detail: GA lines go in as covered

The Medicare Claims Processing Manual (Publication 100-04, Chapter 1, Section 60.4.2) tabulates the non-coverage modifiers, and the entry for GA is specific: the modifier signifies waiver of liability, an ABN is required, the beneficiary is liable — and the line item must be submitted as covered, with Medicare making a determination for payment. That is the opposite of how GZ and GY behave, where lines go in as non-covered and are simply denied.

The logic follows from what GA is for. You are not telling Medicare the service is non-covered; you are asking Medicare to adjudicate it, while flagging that if the answer is no, the beneficiary has already accepted liability. Submitting a GA line as non-covered defeats the mechanism.

The same section carries a corollary worth knowing: modifiers GA and KB cannot be used with HCPCS code A9270 (non-covered item or service), because those modifiers require covered charges. A9270 is non-covered by definition, so the two are incompatible.

On outpatient institutional claims, ABN-related billing uses occurrence code 32 with the date the beneficiary signed the notice. Section 60.4.1 explains that modifier GA is used at line level when a claim carries both services related to an ABN and services that are not: occurrence code 32 still identifies the notice, and only the lines carrying GA are treated as ABN-related and must be covered charges.

What the Record Must Show

The record that matters here is the notice itself, not the chart note. CASRAI’s guide to the Advance Beneficiary Notice covers the form mechanics; the elements that determine whether a GA claim survives review are:

  • An item-specific and beneficiary-specific reason for the expected denial. CMS guidance prohibits routine or blanket ABN issuance. A notice that says “Medicare may not pay for some services” is not a notice; it is a disclaimer, and it does not shift liability.
  • An estimated cost, so the choice was informed. A beneficiary cannot meaningfully accept liability for an unknown amount.
  • Timing that allowed a real decision. The notice has to be given far enough in advance for the beneficiary to consider it — not handed over on the table.
  • The beneficiary’s selected option and signature. The standard form offers three: receive the item and have Medicare billed, accepting liability if denied; receive it without billing Medicare and pay directly; or decline it. Only the first supports a GA claim.
  • A retrievable copy. The ABN is the evidence. Where it cannot be produced on request, the liability shift cannot be demonstrated regardless of what happened at the desk.
  • Validity over time. An ABN is generally valid for up to one year for a repeated course of treatment, absent a change in circumstances. A material change in the item, the frequency or the clinical picture calls for a fresh notice.

The Misuse That Triggers Denials and Audits

  1. Routine GA on everything. Contractor guidance names this directly as incorrect use: appending GA on a routine basis to all services a provider performs. It mirrors the prohibition on blanket ABNs, and it is trivially visible in claims data.
  2. GA where there was no expectation of denial. Also expressly incorrect. GA is a prediction backed by a notice; without the prediction, there was no basis for the notice either.
  3. GA with no ABN, or with an ABN that fails on its face. The modifier asserts a notice was given. If the notice does not exist, is generic, is undated, is unsigned, or was issued after the service, the assertion is false and liability stays with the provider.
  4. GA submitted as a non-covered line. Mechanically self-defeating, per Section 60.4.2.
  5. GA to move a research cost onto a patient. In the clinical-trial setting specifically, an ABN cannot lawfully be used to shift a sponsor-owed research cost onto a beneficiary. Doing so compounds double-billing and False Claims Act exposure rather than avoiding it — see the False Claims Act in billing and the clinical trial billing compliance checklist.
  6. Stacking incompatible liability modifiers on one line. GA, GZ and GY express contradictory positions and are not combined on a single line. Section 60.4.2 closes with the warning that modifiers indicating provider liability cannot be used on entirely no-payment claims for which the beneficiary has liability, and that inappropriate use of these modifiers may result in entire claims being returned to providers.

Modifier GA vs. Its Nearest-Confused Siblings

The G-series is a four-way decision with two axes: why is coverage in doubt (medical necessity versus statutory exclusion), and was a notice given. Answer both and the modifier is determined.

Modifier Why coverage is in doubt Notice Who is liable How the line is submitted
GA Expected denial as not reasonable and necessary Mandatory ABN issued Beneficiary As a covered charge; Medicare adjudicates
GZ Expected denial as not reasonable and necessary No ABN issued — and GZ cannot be used where an ABN actually was given Provider As non-covered; denied
GX Statutorily excluded or not a Medicare benefit Voluntary notice issued Beneficiary As non-covered; denied. May be used with GY
GY Statutorily excluded or does not meet the definition of any Medicare benefit Not required Beneficiary Non-covered by statute; denied

GA vs. GZ — the expensive one

These describe the identical clinical and coverage situation and differ only in whether the notice was issued. That difference decides who absorbs the cost. GZ is, in effect, an admission that the opportunity to shift liability was missed — and the manual states plainly that GZ cannot be used where an ABN was actually given. The practical implication is that the GA/GZ choice is made at the front desk, weeks before anyone codes the claim, and no amount of billing skill recovers a GZ.

GA vs. GY

The axis here is why Medicare will not pay. GA is for something Medicare could cover but probably will not in this case. GY is for something Medicare never covers because it falls outside the statutory benefit. Using GA on a statutorily excluded item asks Medicare to adjudicate a question it has no authority to answer differently.

GA vs. GK

GK identifies a reasonable and necessary item or service associated with a GA or GZ modifier — the covered companion to a non-covered line, most often in an upgrade scenario. It is not an alternative to GA; it sits alongside one.

GA vs. modifier KX — opposite postures on the same question

This is the comparison most worth holding onto, because both modifiers speak to coverage and they say contradictory things. Modifier KX attests that the requirements of the applicable medical policy have been met, so the service should be covered. GA anticipates that it will not be. Contractor guidance for GA even points at the LCD explicitly — append GA where the provider has determined, based on an active LCD, that the service will not be covered. Read the LCD, decide which side of it you are on, and the modifier follows. If you are reaching for both, the coverage determination has not actually been made.

Where Jurisdiction Matters

The ABN form (CMS-R-131), the mandatory-versus-voluntary distinction, the prohibition on blanket notices and the G-series liability framework are national. What varies is the coverage determination underneath — and that is the part that decides whether a GA is appropriate at all. Local Coverage Determinations differ between MACs, so the same service can be routinely covered in one jurisdiction and require an ABN in another. Novitas, Noridian, First Coast Service Options, Palmetto GBA, WPS and CGS each maintain their own LCD sets.

Two further scope limits are worth stating plainly. The ABN and the G-series apply to fee-for-service Medicare; Medicare Advantage plans operate their own notice and appeal frameworks, and a Part B ABN is not the right instrument there. And commercial payers use their own waiver-of-liability and patient-responsibility forms, with their own timing and content rules — an ABN issued for a commercial claim generally shifts nothing.

Where you cannot find guidance on point, the structure of the determination holds: is the doubt about medical necessity or statutory scope, was a compliant notice given before the service, and does the line need to be submitted as covered or non-covered.

Frequently Asked Questions

What does modifier GA mean?

That a waiver of liability statement was issued as required by payer policy — in Medicare terms, that an ABN was given to the beneficiary for an item expected to be denied as not reasonable and necessary, so the beneficiary may be held liable if it is denied.

Should a GA line be billed as covered or non-covered?

Covered. The Claims Processing Manual’s modifier table specifies that a GA line item must be submitted as covered, with Medicare making a determination for payment — unlike GZ, GX and GY lines, which are submitted as non-covered and denied.

What if no ABN was given?

Then GA is not available. GZ signals the same expected denial without a notice, and the provider remains liable. GZ cannot be used where an ABN actually was given.

Can modifier GA be used routinely to protect against denials?

No. Routine application to all services is expressly identified as incorrect use, and it mirrors the prohibition on blanket ABN issuance. Each notice needs an item-specific, beneficiary-specific reason for the expected denial.

Can GA and GY appear on the same line?

No. They express contradictory positions — GA asks Medicare to adjudicate an ordinarily-covered service, GY states the item is outside the statutory benefit entirely. The manual warns that inappropriate combinations of these liability modifiers can cause entire claims to be returned.

Does an ABN expire?

A properly-executed ABN is generally valid for up to one year for a repeated course of treatment, absent a change in circumstances. A change in the item, the frequency or the clinical situation calls for a new notice.

Does modifier GA apply to Medicare Advantage?

No. The ABN and the associated modifiers are a fee-for-service Medicare mechanism. Medicare Advantage plans have their own denial-notice and appeal processes.

Related CASRAI Resources

Sources: CMS Medicare Claims Processing Manual, Publication 100-04, Chapter 1, Sections 60.4.1–60.4.2 (line-item modifiers related to non-covered charges); CMS fee-for-service ABN guidance and Form CMS-R-131; Noridian Healthcare Solutions modifier GA guidance. Coverage determinations underlying a GA decision are jurisdiction-specific — check the LCD that applies to your claim. General reference material, not billing advice for a specific claim.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →