PharmaDossier
Pricing & Access

Revised CMS ASP Files: Reconcile the Quarter, Version, and HCPCS Code

A step-by-step guide to reconciling revised CMS Medicare Part B Drug Payment Limit Files by date of service, hub version date, and HCPCS dosage unit under CR 14521.

Ran Chen
Ran Chen
16 min read · Published · Source-cited

The reconciliation unit is quarter, version date, and HCPCS—not “the current ASP”

When market-access directors, reimbursement managers, and hospital revenue-cycle teams discover that a Medicare Part B payment rate diverges from their commercial model or claim remittance, the most common instinct is to search for “the current CMS ASP file.” That single conceptual shortcut creates immediate operational errors. In Medicare Part B drug reimbursement, there is no monolithic “current ASP.” Instead, every allowable payment is governed by three independent, non-interchangeable coordinates: the payment-effective quarter determined strictly by the claim’s date of service; the specific CMS file version date and publication status for that quarter; and the Healthcare Common Procedure Coding System (HCPCS) billing code and its exact dosage unit—not the manufacturer’s National Drug Code (NDC) or packaging.

Conflating these coordinates leads to severe compliance and revenue-cycle failures. Teams routinely apply a newly released October file to August dates of service, mistake a manufacturer’s submission in the CMS Average Sales Price Data Collection System for an immediate public payment limit, or assume that when CMS posts a revised file, Medicare Administrative Contractors (MACs) automatically reprocess previously paid claims. None of these assumptions hold under CMS operating rules.

Under Section 1847A of the Social Security Act and governing federal regulations at 42 CFR 414.904, Medicare Part B pays the lesser of the actual charge on the claim or 106 percent of Average Sales Price (ASP), subject to the limitations in 414.904(d) and the exceptions in 414.904(e). For multiple-source codes, 42 CFR 414.904(b) sets that ASP as the volume-weighted average of manufacturers’ ASPs for products in the billing code; the published Payment Limit is usually 106 percent of that figure, not the NDC invoice. Manufacturers calculate and report ASP at the 11-digit NDC level under 42 CFR 414.804. Reconciling these layers requires understanding how CMS translates NDC-level transaction data through a two-quarter statutory lag into contractor-ready HCPCS payment limits.

Map date of service to the payment-effective file, then read the hub label

The foundational rule of Medicare Part B pricing is the two-quarter lag. Manufacturers calculate ASP at the 11-digit NDC and must submit it within 30 days after the close of the calendar quarter (42 CFR 414.804(a)(1) and (a)(5)). CMS then maps those submissions to HCPCS codes and publishes payment limits that become effective two quarters after the sales quarter. The CMS fact sheet Understanding the Medicare Part B Drug Payment Limit File, this lag is the time between the first day of the sales quarter and the first day of the quarter when the payment limit based on those sales becomes effective.

Specifically, first-quarter sales (January 1 through March 31), submitted by manufacturers between April 1 and April 30, determine the payment limits effective July 1 through September 30. Second-quarter sales (April 1 through June 30), submitted by July 30, determine the payment limits effective October 1 through December 31. Third-quarter sales determine the January 1 payment file, and fourth-quarter sales determine the April 1 file. This lag is central to understanding ASP lag and buy-and-bill economics in the first quarters after launch, where commercial acquisition costs may shift months before Medicare reimbursement updates.

Claim Date of Service WindowManufacturer Sales QuarterManufacturer Submission DeadlineCMS general public-release timingCR 14521 Status & DOS Window
October 1, 2026 – December 31, 2026Q2 2026 (Apr 1 – Jun 30, 2026)July 30, 2026Generally a few days before 10/01/2026Active Cycle: DOS 10/01/26 – 12/31/26
July 1, 2026 – September 30, 2026Q1 2026 (Jan 1 – Mar 31, 2026)April 30, 2026Generally a few days before 07/01/2026Prior Quarter 1: DOS 07/01/26 – 09/30/26
April 1, 2026 – June 30, 2026Q4 2025 (Oct 1 – Dec 31, 2025)January 30, 2026Generally a few days before 04/01/2026Prior Quarter 2: DOS 04/01/26 – 06/30/26
January 1, 2026 – March 31, 2026Q3 2025 (Jul 1 – Sep 30, 2025)October 30, 2025Generally a few days before 01/01/2026Prior Quarter 3: DOS 01/01/26 – 03/31/26
October 1, 2025 – December 31, 2025Q2 2025 (Apr 1 – Jun 30, 2025)July 30, 2025Generally a few days before 10/01/2025Prior Quarter 4: DOS 10/01/25 – 12/31/25

Once the date of service identifies the applicable payment-effective quarter, operators must examine the official CMS hub (Medicare Part B Drug Payment Limit File). CMS groups files by calendar year and attaches a status descriptor and release date to each downloadable table. A live inspection of the CMS hub modified on September 8, 2026 at 12:55 PM reveals a critical pattern that illustrates why date reconciliation cannot be generalized:

  • October 2026 Payment Limit File and NDC-HCPCS Crosswalk: Both labeled preliminary 09/08/2026. These represent initial calculations for the upcoming quarter.

  • July 2026 Payment Limit File: Labeled Final revised 09/08/2026. Concurrently, the July 2026 NDC-HCPCS Crosswalk remained labeled Final 06/17/2026. The payment allowance file was updated, but its corresponding crosswalk was not.

  • April 2026 Payment Limit File: Labeled Final revised 09/08/2026, while the April 2026 Crosswalk was last updated revised 03/30/2026.

  • January 2026 Payment Limit File: Labeled Final revised 09/08/2026, while the January 2026 Crosswalk was last updated revised 03/30/2026.

  • October 2025 ASP Pricing File: Labeled Final 09/08/2026, representing the fourth lookback quarter.

This snapshot proves that the Payment Limit File and the NDC-HCPCS Crosswalk for the exact same quarter can carry different version dates. An operator who checks only the crosswalk date will miss a September 8 revision to the payment allowance, while an operator who looks only at the payment limit date might search in vain for a crosswalk update that CMS never issued.

A preliminary file on the public hub is not a contractor implementation event. CMS states that it generally releases files a few days before the upcoming quarter’s effective date and that preliminary files are available several days before final files are released to contractors, allowing correspondence on payment-rate accuracy. The 09/08/2026 preliminary October 2026 hub label is an observed posting for this cycle; it is not a substitute for that general rule. Official contractor operations are governed by formal Change Requests. Transmittal 13831, issuing Change Request 14521 (CR 14521, issued June 30, 2026), establishes the operational calendar for this cycle. Business requirement 14521.2 instructs contractors to retrieve the October 2026 ASP NOC pricing file and, if released, the revised July 2026, April 2026, January 2026, and October 2025 ASP NOC pricing files from the CMS ASP webpage on or after September 18, 2026, with a formal effective date of October 1, 2026, and a claims processing implementation date of October 5, 2026. Treating a 09/08/2026 preliminary October 2026 public file as if contractors had already implemented CR 14521 will mix a hub label with a later retrieve and implementation event.

Do not swap in a different CMS file object

A frequent source of reconciliation failure is substituting one CMS data product for another. The Medicare Part B drug pricing ecosystem contains several distinct file families, each created for specific institutional settings, statutory authorities, and billing workflows. Using a hospital outpatient file for a physician-office buy-and-bill claim or confusing an NDC crosswalk with an allowance schedule invalidates the audit.

First, in the Calendar Year 2026 Physician Fee Schedule (PFS) final rule, CMS formally renamed the historical “ASP Pricing Files” to the Medicare Part B Drug Payment Limit File. The CY 2026 PFS final-rule policy table records that rename so other methodologies, including Maximum Fair Price (MFP), can appear in the same public file. Chapter 17 and CR 14521 state that the published files already contain the applicable 106 percent ASP, 106 percent WAC, or 95 percent AWP limits, so contractors must not recalculate those add-ons. That is not the same as every row equaling 106 percent of ASP: 42 CFR 414.904(e)(1) pays hepatitis B, pneumococcal, influenza, and COVID-19 vaccines at 95 percent of AWP; 414.904(e)(4) sets the initial period when ASP is unavailable at an amount not to exceed 103 percent of WAC; and 414.904(e)(3) keeps blood and blood products other than clotting factors on the October 1, 2003 methodology. Appendix B of the ASP FAQ still documents Vaccine AWP% and Blood AWP% columns on the payment-limit file.

Second, seasonal influenza and COVID-19 vaccine pricing has been moved off the quarterly payment-limit file. Under CMS vaccine-pricing guidance (Vaccine Pricing), external parties should use the dated 2026–2027 Seasonal Influenza and COVID-19 Vaccine Pricing File (hub listing 08/27/2026) instead of the quarterly payment-limit file for those products.

File ObjectPrimary PurposeStatutory / Policy BaseTarget Care SettingSubstitution Risk
Medicare Part B Drug Payment Limit FilePublished allowance per HCPCS dosage unit across ASP, WAC, AWP, and MFPSSA §1847A; 42 CFR 414.904; CY 2026 PFS Final RulePhysician office, freestanding clinic, buy-and-billCanonical Part B standard; cannot be substituted by NOC or crosswalk
NDC-HCPCS CrosswalkMaps 11-digit package NDCs to Level II billing codes and dosage unitsCMS Data Collection System mapping rulesBilling conversion, claims cross-referencingContains no price or payment limit; does not verify Medicare coverage
ASP Not Otherwise Classified (NOC) FileProvides contractor payment limits for unclassified codes (e.g., J3490, J3590, J9999)Medicare Claims Processing Manual Ch. 17 §20.1.3Newly launched biologics lacking permanent J-codesApplies only to unclassified codes; cannot price permanent HCPCS
Seasonal Vaccine Pricing FileSeparate payment limits for seasonal influenza and COVID-19 immunizationsSSA §1842(o); 42 CFR 414.904(e)(1); CMS Vaccine GuidanceOutpatient, pharmacy, and office preventive clinicsMoved off the quarterly file; use the dated seasonal vaccine pricing file
OPPS Addendum A & Addendum BOutpatient Prospective Payment System status indicators, APCs, and copayments42 CFR Part 419; Annual OPPS RulemakingHospital Outpatient Departments (HOPDs)Hospital outpatient departments should use OPPS Addenda, not this PFS-oriented payment-limit file
DME MAC NDC-HCPCS CrosswalkSeparate DME NDC-HCPCS crosswalk for certain DME supplier claimsCh. 17 §20.3; CMS Understanding the Payment Limit File fact sheet; CR 14521.3Home infusion and durable medical equipment suppliersNot interchangeable with the ASP-website NDC-HCPCS Crosswalk; CR 14521.3 still uses the quarterly ASP file for DME infusion drugs

Understanding these dataset boundaries prevents cross-setting confusion. For instance, teams navigating interim billing for newly approved molecules often struggle with J-code timing and interim billing risk for buy-and-bill biologics, where pricing shifts between NOC files, local MAC pricing, and permanent quarterly tables. Similarly, billing teams reviewing denied submissions should refer to analysis on biosimilar HCPCS and NDC crosswalk errors causing claims denial rather than assuming the national Payment Limit File contains a pricing error.

Correction before publication is not a restatement after publication

A widespread misconception among manufacturers and providers is that any change in underlying sales data immediately triggers a public file restatement. In truth, CMS enforces a rigid regulatory divide between pre-publication data corrections and post-publication restatements. This framework is articulated in two primary CMS guidance documents: the Average Sales Price (ASP) Restatement Policy Overview and the companion Manufacturers’ Guide to Correcting ASP Data Errors (both updated with formal publication notices in March 2026).

Under this policy, manufacturers that discover reporting errors must submit corrected data through the CMS ASP Data Collection System immediately. However, how CMS handles those revisions depends entirely on when they arrive relative to the publication cycle:

  • Pre-Publication Correction Window: The formal pre-publish correction deadline is the 10th day of the month preceding the effective date of the payment limits. The manufacturers’ correction guide uses a related formulation: the 10th day of the month preceding publication of the next quarter’s file. For an October 1 effective file, the Restatement Policy Overview deadline is September 10. If corrected data arrive by that cutoff, CMS may recalculate the current quarter before public release. That event is a correction, not a restatement.

  • Post-Publication Restatement Thresholds: If corrected data arrive after the 10th-day cutoff or after the file has already been released to the public and contractors, CMS does not automatically reissue the table. Reopening a published fee schedule imposes severe administrative overhead on MACs, clearinghouses, and providers. Therefore, CMS conducts a quantitative impact analysis and applies strict multi-variable thresholds before approving a restatement.

For a mid-quarter restatement of the current quarter, CMS has discretion to restate immediately only when the recalculated payment limit meets three of the following four criteria:

  1. Absolute Dollar Impact: A change in the payment limit of at least ±$1.00 per HCPCS billing unit.

  2. Percentage Impact: A percentage change in the payment limit of at least ±10.00 percent.

  3. Volume Threshold: Historical Medicare utilization of at least 100,000 HCPCS billing units in the 12-month period preceding the current quarter.

  4. Program Dollar Impact: An estimated total allowed payment impact of at least ±$100,000 across the Medicare program if all claims were reprocessed.

If an error does not clear three of these four tests, CMS will not issue a mid-quarter restatement for the active quarter. Instead, the correction is evaluated for prior-quarter restatement during a subsequent cycle.

For prior-quarter restatements, CMS maintains a lookback window of up to four preceding quarters. Because prior-quarter adjustments are rolled into scheduled quarterly releases rather than interrupting active mid-quarter claims processing, CMS applies a lower threshold requiring at least two of the following four criteria:

  1. Absolute Dollar Impact: A change in the payment limit of at least ±$0.050 per HCPCS billing unit.

  2. Percentage Impact: A percentage change in the payment limit of at least ±5.00 percent.

  3. Volume Threshold: Historical Medicare utilization of at least 50,000 HCPCS billing units in the 12 months preceding the current quarter.

  4. Program Dollar Impact: An estimated total allowed payment impact of at least ±$50,000.

Manufacturers must submit corrected prior-quarter data by the 30th day of the month following the end of the previous quarter. If an error requires extensive auditing or if submissions miss this window, CMS policy explicitly states that the restatement will be delayed by at least one additional quarter. When CMS does restate a rate, it inserts an explicit date descriptor into the Payment Limit File itself (for example, appending a revision date note to the specific HCPCS row).

flowchart TD
    A["Manufacturer Submits Corrected ASP Data"] --> B{"Submitted by 10th day of month preceding effective date?"}
    B -- Yes --> C["Pre-Publication Correction: CMS Recalculates Before Initial Public Release"]
    B -- No --> D{"Evaluation for Mid-Quarter Current Quarter Restatement"}
    D --> E{"Meets >= 3 of 4 Criteria?<br/>1. Dollar >= ±$1.00/unit<br/>2. Percent >= ±10.00%<br/>3. Volume >= 100k units<br/>4. Allowed Impact >= ±$100k"}
    E -- Yes --> F["Immediate Mid-Quarter Public Restatement & In-File Date Descriptor"]
    E -- No --> G{"Evaluation for Prior Quarters (Up to 4-Quarter Lookback)"}
    G --> H{"Meets >= 2 of 4 Criteria?<br/>1. Dollar >= ±$0.050/unit<br/>2. Percent >= ±5.00%<br/>3. Volume >= 50k units<br/>4. Allowed Impact >= ±$50k"}
    H -- Yes --> I["Prior Quarter Restatement Included in Next Scheduled Quarterly File"]
    H -- No --> J["No public Payment Limit restatement"]
CMS Decision Logic for Pre-Publication Corrections versus Post-Publication Restatements

This rigorous filter explains why a manufacturer’s internal accounting restatement does not automatically translate into a changed number on the CMS website. Commercial teams tracking regulatory filings under CMS-10110 ASP reporting and Part B Maximum Fair Price effectuation must recognize that data corrections exist in the manufacturer reporting tier long before—if ever—they alter public payment allowances.

What a revised file does—and does not—do to claims

The most consequential error in provider revenue-cycle operations is assuming that a CMS file revision triggers automated claim reprocessing. When CMS issues a “Final-revised” file for a past quarter, practice managers often expect automatic adjustments or fear immediate mass recoupments. Medicare operational rules directly contradict this assumption.

In every quarterly recurring update transmittal, CMS provides explicit binding instructions to its contractors. In Transmittal 13831 / Change Request 14521, business requirement 14521.4 states unambiguously:

This sentence is the overlay rule for a revised payment file. Medicare Administrative Contractors load the revised files into their claims processing systems on a prospective overlay basis. Once implemented (October 5, 2026 for the CR 14521 cycle), the revised payment limit governs claims processed or reprocessed on or after that implementation with dates of service in the file’s window. Claims already processed remain unadjusted unless brought to the contractor’s attention under 14521.4.

This operational reality interacts directly with Medicare Claims Processing Manual, Chapter 17 (Drugs and Biologicals), Section 20. Chapter 17 establishes that payment limits in revised ASP and NOC payment files supersede the payment limits published prior to that document. Contractors are required to accept the files as made available by CMS without alteration. Specifically, contractors shall not make additional calculations, because CMS has already embedded the statutory 106 percent ASP, 106 percent WAC, or 95 percent AWP rules directly into the Payment Limit column.

Additionally, Chapter 17, Section 20.1.3 reinforces that the presence or absence of a drug or biological in the CMS Payment Limit File does not establish Medicare coverage. A code listed on the file may still be subject to National Coverage Determinations (NCDs) or Local Coverage Determinations (LCDs). Conversely, if a product is omitted from the quarterly file, absence does not establish non-coverage. FAQ 7.6 and CR 14521.5 send those claims to the MAC to determine a payment limit under Chapter 17, section 20.1.3.

If a revised file lowers a published limit, CR 14521.4 still means the MAC will not search out already-processed claims. If a restated limit is higher than an already-paid amount, capturing any difference likewise requires bringing the specific claim to the contractor; this article does not instruct how to bill, reopen, or appeal. Adjacent acquisition benchmarks, such as those documented in CMS NADAC drug acquisition costs analysis or downstream exposure under IRA Part B negotiation and provider reimbursement risk, further emphasize why passive reliance on MAC systems creates balance-sheet volatility.

Reconcile the HCPCS dosage unit, then stop

The final step in the reconciliation protocol is resolving the mathematical mismatch between commercial purchasing packages and Medicare billing units. Providers purchase pharmaceutical products by NDC package—vials, pre-filled syringes, blister packs, or multi-dose cartridges. Medicare, by contrast, reimburses strictly per HCPCS Level II billing code dosage unit.

CMS Frequently Asked Questions on ASP Data Collection (Appendix B) explicitly defines the Payment Limit column as the maximum allowed amount per HCPCS Level II Code Dosage (examples: 1 mL, 10 mg, 150 IU). The NDC-HCPCS Crosswalk maps package NDCs to that dosage unit. FAQ 6.9 states that partial units are not accepted and that CMS rounds to the closest billing unit; if a vial contains 9.8 mg and the HCPCS code defines one billing unit as 10 mg, CMS rounds the vial to one billing unit on the crosswalk.

Reimbursement errors occur when billing departments divide an invoice price by nominal milligrams rather than using the official crosswalk multiplier, or when they attempt to reconcile an invoice against a third-party fee schedule that truncated decimals. To ensure absolute audit integrity, operators should follow a standard five-step checklist:

  1. Step 1: Isolate the Date of Service. Examine the claim or remittance advice and record the exact date of service. Map that date to the governing payment-effective quarter using the two-quarter statutory lag calendar. Never select a file based on today’s date or the date the remittance was received.

  2. Step 2: Verify the Latest Hub Version Date. Navigate to the CMS Medicare Part B Drug Payment Limit File hub. Locate the section for the governing calendar year and identify the downloadable table for that payment quarter. Check the label: confirm whether it is preliminary, Final, or Final-revised, and record the exact modification date.

  3. Step 3: Confirm the File Object. Ensure that the downloaded document is indeed the Part B Drug Payment Limit File. If the product is a seasonal influenza or COVID-19 vaccine, switch immediately to the dedicated seasonal vaccine schedule. If the claim was billed under an unclassified code, locate the corresponding NOC file.

  4. Step 4: Check HCPCS Code and Billing Units. Locate the exact HCPCS Level II code row. Read the published Payment Limit against the HCPCS Level II Code Dosage. Confirm billed units use that dosage unit rather than an NDC package count. Check whether the row contains an in-file restatement date descriptor.

  5. Step 5: Review Claims Reprocessing Status. If the row reflects a restated rate that diverges from a previously paid amount, record whether the claim was processed before the contractor implementation date (October 5, 2026 for CR 14521). CR 14521.4 means already-processed claims are not mass-adjusted unless brought to the contractor’s attention.

Sources

Topics
Ran Chen
Contributing Editor
Ran Chen

Founder, PharmaDossier. Life-sciences operator covering market access, specialty pharma, biosimilars, and regulated healthcare growth.

Follow on LinkedIn →