Average Sales Price: Read the Medicare Part B Drug Payment File
Billing

Average Sales Price: Read the Medicare Part B Drug Payment File

Use the service-date quarter, HCPCS billing unit, and NDC crosswalk to calculate an expected Medicare Part B drug limit without mistaking price for coverage.

August 31, 2026
9 min read

Average sales price, or ASP, is a manufacturer-reported pricing benchmark that CMS uses to set many Medicare Part B drug payment limits. It is not the pharmacy's acquisition cost, and the presence of a drug in a CMS payment file does not establish coverage.

For repeat billing, configure software or a reimbursement reference for routine lookups and unit conversion. Keep the CMS files for audit and exception review when the setup is new, the product changed, or the remit does not match the expected amount.

What average sales price explains

CMS calculates ASP from quarterly manufacturer sales data after defined price concessions. For most separately payable Part B drugs and biologicals, the payment limit is 106 percent of ASP. CMS publishes the resulting limit at the HCPCS code level, where one line states the code dosage and the amount allowed per billing unit.

The familiar phrase ASP plus 6 percent is a payment-limit method, not a guaranteed six-percent margin. A pharmacy may buy the product at a different net cost, and a payer can apply coverage, enrollment, contract, coding, deductible, coordination, or claim-edit rules before the remit reaches the pharmacy.

ASP is also not the only method in the file. CMS can use wholesale acquisition cost, average wholesale price, contractor pricing, and other statutory methods. Preventive vaccine pricing has its own rows and current seasonal files. Read the method and notes on the exact line instead of applying 106 percent to every product.

The service date chooses the quarterly file

CMS publishes the Medicare Part B Drug Payment Limit File for calendar quarters. The July 2026 final file applies to dates of service from July 1 through September 30, 2026. A claim from June uses the April file even if the team researches or resubmits it in August.

The file has a two-quarter data lag because CMS needs a complete manufacturer sales quarter and a reporting window before the limit becomes effective. That lag is part of the method; it does not make the effective quarter optional.

CMS can revise prior files after manufacturer restatements or data corrections. Record the file's effective quarter, final or preliminary status, publication or revision date, and retrieval date. When an older claim is reprocessed, compare the version used by the contractor with the latest CMS version for that service-date quarter.

A July 2026 line for a 600 mg dose

Use an August 15, 2026 Original Medicare fee-for-service Apretude claim as a file-reading example. This is an illustrative calculation from the July 2026 CMS files, not a coverage determination or a promise that a pharmacy may bill the service.

The July payment-limit file lists HCPCS J0739 for injectable cabotegravir with a code dosage of 1 mg and a payment limit of $7.294 per billing unit. The July PrEP NDC-HCPCS crosswalk maps Apretude NDC 49702-0264-23 to J0739 and shows 600 HCPCS billing units for the 600 mg product dose.

I reproduced this example directly from the files, not from a search snippet or secondary calculator. I downloaded CMS's July 2026 payment-limit and crosswalk ZIPs. The Section 508 payment CSV gives J0739 a 1 mg dosage and a $7.294 limit. The PrEP crosswalk CSV gives NDC 49702-0264-23 600 billable units. Multiplying those two file values produces $4,376.40.

Illustrative Q3 2026 rate math

600 mg administered ÷ 1 mg per HCPCS billing unit = 600 claim units. 600 units × $7.294 payment limit = $4,376.40 expected product limit.

Do not add another 6 percent to $7.294. The published payment-limit amount already contains the applicable CMS calculation. Also keep the administration service separate from the drug line; the drug limit does not automatically include payment for administering it.

The file lists zero coinsurance for this PrEP drug line, but that field still does not prove that the patient, product, pharmacy, or service satisfies every coverage and billing requirement. The team's coverage and enrollment evidence must answer those questions.

This example is an Original Medicare fee-for-service pricing illustration. CMS's PrEP guidance separates practitioner-supplied injections from pharmacy-supplier pickup or mail-order claims, and Medicare Advantage claims go to the member's plan. Confirm who supplied the drug, which enrollment route applies, and the pickup or mailing service date before using the rate.

The crosswalk solves an identity problem

The product arrives with an NDC, while the professional claim usually reports a HCPCS drug code and quantity. The CMS crosswalk connects those identities and shows the package-to-billing-unit relationship used in the payment file.

Start with the dispensed or administered product's full NDC, then confirm the HCPCS code and dosage descriptor. Our HCPCS versus CPT guide explains why the product code and the administration service code answer different claim questions.

Stop when the package strength, route, NDC, HCPCS descriptor, or administered quantity does not agree. Software can assemble an NDC-HCPCS mapping and convert units, but that output is a candidate claim line. A qualified reviewer still resolves mismatched product facts and confirms the current code source.

A missing line is unresolved, not automatically uncovered

CMS says the payment-limit file and crosswalk are not formularies. A code's presence does not establish coverage, and its absence does not establish noncoverage. The crosswalk is not a comprehensive list of every NDC that Medicare could pay.

When CMS does not publish a limit, the local Medicare Administrative Contractor may establish one for an otherwise covered drug using the applicable method, such as WAC or invoice pricing. That is where contractor-specific variation lives. The pharmacy needs the MAC's current written instructions for its jurisdiction and billing route.

Do not substitute an OPPS addendum, DME crosswalk, seasonal vaccine file, or a commercial payer schedule merely because it contains the same code. Those files serve different settings and payment rules. Preserve the file name and source so another teammate can reproduce the rate decision.

Keep one Part B drug payment-limit record

A useful rate check lets a second person reproduce the expected amount without assuming the file answered coverage. Keep these facts together:

  • Claim context: patient account reference, service date, item or service, billing entity, enrollment route, contractor, and claim setting.
  • Product identity: 11-digit NDC, drug name, package strength and route, HCPCS code, full code dosage, administered or dispensed quantity, discarded quantity when applicable, and supporting product record.
  • Rate source: CMS file name, effective quarter, preliminary or final status, publication or revision date, retrieval date, payment method, stated payment limit, coinsurance field, notes, and the matching crosswalk row.
  • Calculation: source quantity divided by the HCPCS code dosage, resulting claim units, published limit per unit, expected product limit, and any separate administration line.
  • Interpretation: the file's stated result, unresolved coverage or coding fact, authoritative and payer evidence checked, likely route, confidence, owner, and stop or qualified human-review trigger.

Stop automated pricing when the service date and file quarter disagree, a CMS revision changes the applicable line or expected amount, product and code units do not reconcile, more than one HCPCS code remains plausible, a product is missing, the claim setting requires a different file, or coverage and enrollment are not established. Plain-English software output can explain a rate; it cannot prove the correct claim line.

Compare the limit with the payer's actual adjudication

The CMS limit is a benchmark for an eligible traditional Medicare Part B line. A pharmacy should compare it with its contract, submitted units, payer response, and remittance rather than treating the benchmark as the cash amount. The broader fee schedule guide shows where a rate source fits in an expected-payment record.

If the remit differs, first verify the service-date file, code dosage, units, payment method, and any primary-payer or patient-responsibility amounts. Then use the claims-adjudication guide to keep the payer's stated result separate from the fact the team still needs to resolve.

Use software for routine lookups

For an occasional check, hcpcs.codes offers a browser-based view of the quarterly table and crosswalk. It is a convenience copy, so confirm a disputed or high-dollar result against the current CMS files. Medicare contractors also publish fee lookup tools for some routes, but those results are jurisdiction- and benefit-specific.

Commercial references such as Optum DrugReimbursement.com add NDC-to-HCPCS search, billing units, and current Medicare Part B rates. In a pharmacy workflow, DocStation's BIN Billing can translate D.0 claims to 837P and apply configured Medicare fee-schedule lookups, so the pharmacist can see the expected value without handling spreadsheets. A qualified reviewer still needs to resolve conflicting product identity, route, coverage, or payer evidence.

Average sales price FAQ

Is ASP the pharmacy's acquisition cost?

No. ASP is a statutory manufacturer-reported benchmark that includes defined concessions and exclusions. Compare the CMS payment limit with the pharmacy's actual net acquisition cost as a separate business calculation.

Are ASP, AWP, and WAC interchangeable?

No. They are different benchmarks. CMS uses ASP for many separately payable Part B drugs, but some products or periods use WAC, AWP, contractor pricing, or another method. The official file states the applicable limit and notes.

Does a payment-limit row prove Medicare coverage?

No. CMS expressly separates pricing from coverage. Confirm the benefit, medical necessity, enrollment route, contractor or plan policy, code, and service-date facts before treating the row as relevant to a claim.

Which ASP file applies to an older claim?

Use the file effective for the claim's date of service, then check whether CMS later revised that quarter. Keep the exact file version used for the original decision and the current revised version when the claim is reprocessed.

What should the pharmacy do when the drug is missing?

Confirm the NDC, HCPCS code, service date, setting, and relevant CMS file first. If the product remains absent, use the local MAC's current written contractor-pricing and coverage instructions. Stop when the code, coverage, or route remains unresolved.

Medical Billing

Turn clinical services into reimbursed revenue

See how DocStation helps pharmacies check eligibility, create cleaner claims, and keep revenue moving after the clinical service is complete.