HCPCS Code A9270: Non-Covered Item or Service Billing Guide

Key Takeaways

HCPCS Code A9270 identifies any non-covered item or service with no specific HCPCS Level II code

A9270 must always be paired with an appropriate liability modifier – GY, GL, or GX – to assign beneficiary or provider liability; the TS (follow-up service) modifier may additionally be applied in outpatient follow-up contexts per MAC guidance. Submitting without any liability modifier triggers CWF processing errors

A specific HCPCS code must always be used when one exists – A9270 is a last-resort fallback, not a general-purpose non-coverage code

Pabau’s claims management software helps billers flag modifier requirements and track non-covered claim lines to reduce denials

Most claim denials tied to HCPCS Code A9270 are not coding errors. They are modifier errors. Billers submit A9270 without a liability indicator, the Common Working File flags the claim as unprocessable, and the line item gets rejected before a human reviewer ever sees it. According to CMS, HCPCS Code A9270 belongs to the Miscellaneous Supplies and Equipment category and identifies any non-covered item or service for which no specific HCPCS Level II code exists. The code itself does not cause problems. Using it incorrectly does.

This reference guide covers the official description of A9270, when to use it versus a specific HCPCS code, required modifier pairings, Medicare and DME billing rules, Advance Beneficiary Notice requirements, and the most common submission mistakes that lead to denials or audits.

HCPCS Code A9270: Definition and Clinical Description

HCPCS Code A9270 carries the official CMS description: “Non-covered item or service.” As maintained by CMS and classified under Miscellaneous Supplies and Equipment in HCPCS Level II, this code does two distinct jobs depending on context.

• Fallback identifier: Used when a product or service has no specific HCPCS Level II code assigned to it and the provider needs to identify the line item on a claim.
• Non-coverage flag: Used when a specific code exists but the item is considered statutorily excluded or does not meet the definition of a Medicare benefit, and the provider needs to document that non-covered status on the claim.

The code is not a procedure code, an evaluation and management code, or an E&M-complexity indicator. Any framing that describes A9270 as representing a “moderate-complexity encounter” is inaccurate – that description belongs to CPT office visit codes, not to miscellaneous supply codes. A9270 is strictly a supply and equipment classification under the A-code series of HCPCS Level II.

From a CMS classification standpoint, A9270 sits alongside other A-series radiology supply codes, contrast agents, and radiopharmaceuticals, but it occupies a unique position as the catch-all non-coverage placeholder. Providers using claims management software should verify that their system supports modifier-required flagging on A9270 line items before submission.

When HCPCS Code A9270 Applies: Coverage and Exclusions

The single most important rule governing A9270 use: providers must use the most specific HCPCS code available. A9270 is only appropriate when no specific code exists for the item or service being reported. This is not a stylistic preference – it is a documented CMS requirement reinforced by Medicare Administrative Contractor guidance.

A PDAC (Pricing, Data Analysis and Coding) product review from 2016 illustrates how this plays out in practice. When Thuasne USA submitted a maternity support belt for coding review, PDAC determined that no specific HCPCS code applied to the product and assigned A9270 as the appropriate billing code. That decision is product-specific and does not generalize to other orthopedic or support products. Billers encountering similar items should request their own PDAC review rather than assuming A9270 applies.

For outpatient claims, Noridian Medicare guidance is explicit: providers are required to use detailed HCPCS codes to identify non-covered services. A9270 is permitted only when no specific code exists, paired with the appropriate modifier to deny the line item as beneficiary or provider liable. This applies in both DMEPOS and outpatient hospital billing contexts. Keeping accurate compliance records for non-covered item submissions reduces audit exposure significantly.

Modifiers Required with A9270 Billing

Submitting A9270 without a modifier indicating beneficiary or provider liability triggers a CWF (Common Working File) processing error under CMS Transmittal R332CP. The claim becomes unprocessable at the system level before any clinical review occurs. Each modifier carries a distinct legal and billing meaning – they are not interchangeable.

GY Modifier: Statutory Exclusion

The GY modifier signals that an item or service is statutorily excluded from Medicare coverage or does not meet the definition of a Medicare benefit under the applicable statute. Established in CMS Program Memorandum B0158, GY is the correct modifier when the exclusion is mandated by law rather than by medical necessity criteria. Personal comfort items and cosmetic services fall into this category. When A9270 + GY is submitted, Medicare processes the claim specifically to generate a denial notice, which the beneficiary can then submit to secondary insurance if applicable.

GL Modifier: Medically Unnecessary Upgrade

The GL modifier indicates that a medically unnecessary upgrade was provided at no charge to the beneficiary. In DMEPOS billing, this applies when a supplier furnishes a higher-cost item than Medicare would cover, and the beneficiary pays nothing extra. A9270 + GL tells the payer that the non-covered item was provided as an upgrade, with provider liability for the cost difference. This modifier is particularly relevant for DME suppliers providing enhanced equipment features not covered under the standard benefit.

GX Modifier: Voluntary Advance Beneficiary Notice

The GX modifier, established effective April 1, 2010 (CMS Transmittal 1840), indicates that a voluntary ABN was issued to the beneficiary prior to service delivery. Unlike a mandatory ABN scenario, a voluntary ABN covers situations where the provider expects a denial not because of medical necessity concerns but because coverage simply does not exist for the item. When A9270 + GX is submitted, it signals voluntary patient notification without a mandatory ABN requirement. This distinction matters for compliance purposes and shapes the provider’s liability exposure.

TS Modifier: Follow-Up Service

The TS modifier applies in outpatient claim contexts to identify follow-up services within a procedure package. Per Noridian MAC guidance, TS is among the acceptable modifiers when submitting A9270 on outpatient claims to deny the line item as beneficiary or provider liable. Its use is context-dependent and less common than GY or GL in standard non-covered item scenarios. Billers should verify payer-specific guidance before applying TS with A9270, as commercial insurers and Medicaid programs may not recognize this combination the same way Medicare does.

For practices managing high volumes of non-covered item claims, structured billing compliance practices that document modifier selection rationale at the point of service reduce the risk of systematic errors across claim batches.

DME Billing Context for A9270

HCPCS A9270 plays a specific role in DMEPOS (Durable Medical Equipment, Prosthetics, Orthotics, and Supplies) billing. When DME suppliers need to report a supply item that has no assigned HCPCS code, A9270 serves as the appropriate fallback. CMS Carriers Manual guidance states that when no appropriate NOC code exists, suppliers must continue using A9270 to bill DMERCs (Durable Medical Equipment Regional Carriers) for statutorily non-covered items and for items that do not meet the definition of a Medicare benefit.

• No specific HCPCS code exists: A9270 is the required identifier for unclassified DME supplies with no assigned code in the HCPCS Level II system.
• Item fails Medicare benefit definition: Even if a specific code exists, if the item does not meet benefit criteria, a non-covered claim line using A9270 may be appropriate depending on the clinical scenario.
• PDAC verification required: For novel or borderline products, suppliers should seek PDAC coding verification before assuming A9270 applies. The CGS Medicare coding verification process provides product-specific determinations.
• Jurisdiction matters: DMEPOS claims are processed by regional MACs. Noridian and CGS have published specific guidance on A9270 usage in their jurisdictions. Confirm with the applicable MAC before submitting.

For DME suppliers billing across multiple jurisdictions, maintaining separate documentation of each MAC’s A9270 guidance is essential. Rules around modifier pairings and ABN requirements can vary at the contractor level even when the underlying CMS policy is consistent. Practices using structured coding references alongside their billing workflows reduce the risk of applying one MAC’s rules to a different jurisdiction’s claims.

Manage Non-Covered Claims Without the Guesswork

Pabau's claims management tools help billing teams flag modifier requirements, track non-covered line items, and document ABN workflows before submission. See how practices reduce A9270-related denials with structured billing support.

Book a demo

ABN Requirements and Claim Submission

An Advance Beneficiary Notice of Noncoverage is a written notice that a provider gives a Medicare beneficiary before furnishing a service that Medicare may not pay for. ABN requirements interact with A9270 billing in two distinct ways depending on whether the non-coverage is statutory or based on medical necessity.

Mandatory ABN Scenarios

When a provider believes Medicare may deny a claim because an item or service may not be reasonable and necessary, a mandatory ABN must be issued before the service is provided. If no ABN is given and Medicare denies the claim, the provider cannot bill the beneficiary. For A9270 scenarios involving medical necessity concerns (rather than statutory exclusions), failing to issue an ABN before delivery eliminates the provider’s ability to collect from the patient.

Voluntary ABN Scenarios

When an item is statutorily excluded – meaning it is never covered by Medicare regardless of medical necessity – an ABN is not technically required. Providers may still issue a voluntary ABN as a courtesy to inform the beneficiary of their financial responsibility. Using the GX modifier with A9270 signals that a voluntary ABN was issued. This protects the provider’s ability to collect patient payment and gives the beneficiary documentation for any secondary payer submission.

Practices that use digital forms for ABN delivery can automate the notice workflow, time-stamp the delivery, and capture patient signatures electronically – creating a defensible audit trail for every non-covered item transaction. Manual paper ABN processes leave documentation gaps that surface during MAC reviews.

Step-by-Step Claim Submission with A9270

1. Confirm no specific HCPCS code exists for the item or service using the CMS HCPCS database and PDAC resources.
2. Determine the non-coverage reason: statutory exclusion (GY), medically unnecessary upgrade (GL), voluntary notice issued (GX), or follow-up service context (TS).
3. Issue ABN if required (mandatory for medical necessity denials, voluntary for statutory exclusions) and document patient signature with date and time.
4. Enter A9270 on the claim line with the appropriate modifier appended directly to the code (e.g., A9270-GY).
5. Include a clear item or service description in the claim narrative field to support the modifier selection and reduce manual review delays.
6. Retain documentation including the ABN, modifier selection rationale, and any PDAC correspondence in the patient record.

For commercial insurers and Medicaid, the same logical process applies but modifier requirements and ABN-equivalent documents differ by payer. Never assume Medicare modifier rules translate directly to other payers without confirming the specific plan’s non-covered item billing policy. Practices managing multi-payer HIPAA-compliant billing workflows should maintain payer-specific rule sets for A9270 modifier combinations.

Common A9270 Billing Mistakes and Audit Risks

The most frequent A9270 errors fall into three categories: modifier omissions, specificity failures, and documentation gaps. Each carries distinct compliance and financial consequences.

• Submitting A9270 without any modifier: CMS Transmittal R332CP confirmed that A9270 without a liability modifier triggers CWF processing issues. The claim is flagged as unprocessable. This is the most common technical error and the easiest to prevent with a pre-submission modifier check.
• Using A9270 when a specific code exists: If a HCPCS Level II code covers the item (even if it falls under a NOC designation), that code must be used instead of A9270. Defaulting to A9270 for convenience constitutes a coding error and can trigger a pattern-of-abuse flag during MAC reviews.
• Applying the wrong modifier: GY, GL, and GX are not interchangeable. GY is for statutory exclusion. GL is for medically unnecessary upgrades furnished without charge. GX is for voluntary patient notification. Using GY when GL applies, or GX when a mandatory ABN was required, creates a mismatch between the claim record and the clinical documentation.
• Missing or defective ABN documentation: An ABN signed after service delivery, or one that does not describe the specific item and estimated cost, is generally treated as invalid. Medicare will not protect provider payment collection if the ABN process was defective.
• Generalizing PDAC decisions: A PDAC ruling applies to the specific product and application described in the original submission. Applying a prior PDAC decision to a different product model, size, or clinical application is not appropriate without a new review.

Audit risk increases when A9270 appears frequently across a practice’s billing data without consistent modifier patterns or corresponding ABN documentation. MACs review claim patterns by code, and a high volume of A9270 submissions with varied or missing modifiers is a common audit trigger. Structured practice management software that flags non-covered claim lines at the point of entry reduces this exposure by enforcing modifier requirements before claims leave the practice.

A9270 vs. Related Non-Coverage Codes

A9270 is not the only non-coverage mechanism in HCPCS. Understanding how it relates to discontinued predecessor codes and to the GY modifier itself helps billers apply the right tool for each scenario.

Before CMS Program Memorandum B0158 (effective January 1, 2002), separate codes handled non-covered services by provider type: A9160 for non-covered podiatry services, A9170 for non-covered chiropractic services, and A9190 for personal comfort items not covered by Medicare statute. A9270 replaced all three as a unified placeholder. In the same 2002 transmittal, CMS also deleted the original GX modifier (“Service not covered by Medicare”) and replaced it with the new GY (statutory exclusion) and GZ (not reasonable and necessary) modifiers. A new, unrelated GX modifier was later established in 2010 with a different meaning – “Notice of liability issued, voluntary under payer policy” – and is the GX currently in use and described elsewhere in this article. Keeping this historical context in mind prevents billers from encountering legacy code references in older documentation and applying them incorrectly to current claims.

When a specific HCPCS NOC (Not Otherwise Classified) code exists for a category of supply – even if the individual item is not covered – that NOC code should be used with the appropriate modifier rather than A9270. A9270 sits below NOC codes in the specificity hierarchy. Using it when a relevant NOC code exists violates the CMS requirement to use the most detailed code available and can affect compliance management audit results for the practice.

Expert Resources

Expert Picks

Need a complete HCPCS billing reference? CMS HCPCS Overview provides the official structure, annual update process, and Level I/II distinctions maintained by CMS.

Looking for PDAC coding verification guidance? CGS Medicare Coding Verification explains how DMEPOS suppliers can request product-specific HCPCS code assignments.

Managing non-covered claims across your practice? Pabau’s claims management software helps billing teams track modifier requirements, flag non-covered line items, and reduce submission errors.

Want to improve billing documentation workflows? Practice management software features outlines how structured billing tools reduce audit exposure for high-volume non-covered claim scenarios.

Conclusion

HCPCS Code A9270 is a precise tool with a narrow use case. It applies only when no specific HCPCS Level II code exists for the item or service, and it must always carry a liability modifier – GY for statutory exclusions, GL for medically unnecessary upgrades, or GX for voluntary patient notification. The TS modifier (follow-up service) may additionally apply in outpatient follow-up contexts per MAC guidance but does not itself assign liability. Submitting without a modifier, using A9270 when a specific code exists, or issuing a defective ABN each create distinct compliance risks that trigger CWF errors, MAC reviews, and loss of patient billing rights.

Practices managing DMEPOS or outpatient non-covered claim lines benefit from structured claim review before submission. Pabau’s claims management software supports modifier tracking, ABN documentation workflows, and non-covered line item flagging so billing teams can catch A9270 errors at the point of entry rather than after a denial. To see how Pabau handles non-covered claim workflows, book a demo.

Frequently Asked Questions