Reimbursement Strategy

How CMS Defines and Applies Average Sales Price (ASP) and Sequestration Adjustments in Medicare Part B Drug Reimbursement

CMS rules and the integrity focus behind ASP-based drug payment

Every few quarters, revenue cycle teams brace for the new Medicare Part B drug payment update, and each year CMS tightens control over how those prices are built and tracked. In July 2026, the agency reinforced that stance in its proposed policies centered on program integrity. MedLearn’s ICD10monitor noted that CMS’s 2027 payment proposal “combines tougher enforcement targeting fraud with payment increases and policy changes designed to strengthen access to home health services.” The same pattern shows up in Part B reimbursement: closer oversight linked with the structured ASP methodology and sequestration adjustments.

CMS’s purpose stays clear, protect the Medicare Trust Fund while ensuring qualified providers can deliver care. As that report summarized, the proposal “reflects a dual focus: protecting the Medicare Trust Fund while supporting providers delivering high-quality care.” That mindset is why the ASP structure exists. Rather than accept unverified wholesale prices, CMS requires manufacturers to submit sales data reflecting discounts and rebates across all purchasers. Those data form the national average for each drug code. For revenue cycle managers, that means the Part B payment limit is fully sourced and audited each quarter. Missing or misloading the correct ASP file brings claim denials or recoupments later.

How CMS defines Average Sales Price for Part B drugs

ASP determination follows statute. CMS gathers drug pricing data from manufacturers, net of most rebates and volume discounts, and converts those values into a standard amount per billing code. Hospital outpatient departments, physician offices, and infusion centers rely on the same file. Each quarter sets a benchmark that MACs and Medicare Advantage organizations then use to cap payment.

Sometimes, though, facilities pay more attention to charge capture than to the accuracy of what’s behind it. MACs load the official ASP crosswalk tied to HCPCS J-codes every three months. If the date of service lands before the new quarter, the older rate stays in effect. So internal pricing or charge master estimates won’t cut it, teams need to verify that loaded rates match CMS’s current table. When they don’t, remittance advice often cites the “statutory limit” or an “MUE/ASC-related adjustment,” signaling a possible mismatch between billing period and ASP quarter.

Where sequestration enters: budget controls layered on ASP

Sequestration stems from federal budget enforcement, not drug pricing formulas. CMS applies it after calculating the ASP-based reimbursement. First the statutory ASP rate; then a uniform percentage reduction based on congressional budget mandates. The rule applies to all Part B claims unless lawfully paused.

That subtraction complicates reconciliation. Medicare remittance advice shows both the ASP-derived allowed amount and the separate sequestration line item that lowers payment. Many Medicare Advantage payers, including Aetna, Cigna, and UnitedHealthcare, use the same model, sometimes adding plan-specific offsets. With the GAO listing Medicare Advantage among “the 30 programs designated as high priority for fiscal year 2025,” and reporting improper payments of $23.7 billion, consistency in applying these reductions sits under tighter audit review.

It ties together: sequestration and ASP both function within CMS’s larger anti-fraud oversight. The July 2026 MedLearn summary noted CMS projects $82 million in annual savings from new oversight provisions aimed at preventing improper payments and fraud. Together they serve as cost-control levers, safeguarding the Trust Fund before the money leaves the Treasury. CMS Administrator Dr. Mehmet Oz put it plainly, pointing to “stronger tools to protect Medicare beneficiaries and taxpayer dollars from fraud, waste, and abuse.”

Operational impacts: documenting, reporting, and defending ASP-based claims

Operationally, ASP touches coding, charge master upkeep, software configuration, and audit response. Coders must record the proper HCPCS units per dose; even a minor variance shifts payment since the ASP rate applies per unit. Systems must hold the latest quarter’s ASP tables, and internal controls should verify those files line up with CMS postings. After payments arrive, reports must separate sequestration reductions from pricing variances so underpayments aren’t mistaken for statutory withholds.

Auditors reviewing claims check the match between billed J-code, documented administration, and the active ASP-based allowable. Denials often appear when ASP data are out of date or the billed quantity fails to match the drug strength described. Sequestration itself doesn’t cause denials, only smaller payments. Appealing that as payer error wastes time and expands AR. The better move is confirming sequestration as a statutory adjustment and noting it properly for finance tracking.

CMS’s current environment, tightened enforcement, evolving reimbursement, makes strong ASP governance essential. The agency’s message is clear: more audits are coming. Providers that let ASP updates slide or claim sequestration reversals risk delayed payments and integrity reviews they didn’t expect.

What revenue cycle teams can do now

First step, open the current ASP file and confirm it matches Medicare’s active table. Check that the charge master and pharmacy database pull from the same numbers. Make sure staff know sequestration cuts aren’t appealable, they’re statutory. Give compliance leads visibility over variance reports covering ASP-coded drugs. In today’s integrity-driven climate, consistent management of ASP and sequestration isn’t extra paperwork. It’s what keeps an organization’s Medicare revenue defensible when someone asks to see the documentation.

Sources

Claims Assistant