CMS Outlines Operational Path for 2028 Maximum Fair Price Compliance

On July 16, 2026, the Centers for Medicare & Medicaid Services (CMS) issued a new draft guidance that fills in critical operational details for the Inflation Reduction Act’s drug price negotiation program. The document explains how pharmaceutical manufacturers will be expected to implement Medicare’s negotiated prices when they go live in 2028, with specific expectations for both pharmacy-dispensed and physician-administered therapies.

For life sciences companies, this guidance is not just a compliance checklist, it is the emerging playbook for how negotiated Maximum Fair Prices (MFPs) will flow through buy-and-bill channels, Part D dispensing, and Medicare Advantage networks. Below, we unpack the key mechanics and flag operational issues that commercial, market access, and finance teams will need to address.

How Manufacturers Must Deliver the Negotiated Price

CMS is giving manufacturers two primary mechanisms to ensure that Medicare beneficiaries and providers actually receive the new negotiated price at the point of care. In practice, these pathways dictate how cash flows and data will move across the supply chain.

Upfront pricing at acquisition

Under this route, manufacturers (and, where relevant, intermediaries) must ensure that the acquisition cost paid by the pharmacy or provider is at or below the negotiated Medicare rate when the product is purchased. This approach pushes the discount into the initial transaction, limiting the need for post-hoc reconciliation and reducing working capital risk for providers.

Retrospective rebate payments

The alternative is a “pay and true-up” model. Providers or pharmacies purchase at prevailing prices, then receive a rebate equal to the difference between the actual acquisition cost and the applicable negotiated price. This is operationally familiar for many plans and manufacturers, but it requires robust data capture, claim verification, and timely payment processes to avoid provider cash‑flow pressure.

Manufacturers will need to decide which pathway (or mix of pathways by product, channel, or plan type) best aligns with their existing contracting infrastructure and their tolerance for administrative complexity.

The Role of the Medicare Transaction Facilitator

To coordinate the complex exchange of utilization data and financial flows, CMS plans to use a specialized contractor referred to as the Medicare Transaction Facilitator (MTF). The MTF is designed as a central utility, with two distinct functional components that will sit between manufacturers, plans, and providers.

Data module-verifying eligible use

The data module will act as the verification engine. Its role is to confirm that a particular product was actually dispensed or administered to an eligible Medicare beneficiary and that the claim falls within the scope of the negotiated price program. For Part B, this will involve linking HCPCS claims and package-level information; for Part D and Medicare Advantage, it will rely on plan data and encounter records.

Payment module-routing funds to dispensing entities

Once a claim is validated, the payment module will coordinate the flow of funds from manufacturers to pharmacies, hospitals, and physician practices. In a retrospective rebate model, this module becomes the backbone that ensures the negotiated discount reaches the dispensing entity tied to the verified claim, rather than sitting in plan or intermediary accounts.

From a manufacturer perspective, the MTF introduces a standardized infrastructure but also adds a new integration point, teams will need to prepare for technical onboarding, testing of data feeds, and reconciliation processes.

Part B Alignment, Data Sources, and the 14-Day Rule

A significant focus of the draft guidance is harmonizing operational rules for Part B drugs with existing Part D processes. CMS is explicit that timely and accurate payment to providers is a core policy objective, which has implications for data quality and internal timelines.

Data sourcing for Original Medicare vs. Medicare Advantage

For Original Medicare, CMS intends to draw from its centralized claims data warehouse, using approved Part B claims to support verification and payment calculations. For Medicare Advantage, CMS will rely on encounter data submitted by plans. The agency is soliciting feedback on the feasibility and reliability of these data sources, including whether new reporting timelines or expanded use of package-level codes are necessary to support accurate pricing and rebates.

Enforced 14-day payment window

Once the data module sends a verified claim to a manufacturer, the company will have a firm 14-day window to process and issue any applicable refund or rebate. This timeline will require manufacturers to build or adapt rapid payment workflows, potentially separate from traditional quarterly or monthly rebate cycles, to avoid compliance risk and provider dissatisfaction.

Mandatory enrollment in central systems

Manufacturers with products covered by negotiated prices will be required to register in the centralized data and payment systems tied to the MTF. CMS is also considering whether participating providers should be required to enroll in these systems as a condition of participation in certain managed care contracts, which could indirectly impact network design and contracting strategy.

These elements together push manufacturers toward more real-time data handling and faster financial settlement than many current commercial arrangements.

How CMS May Standardize Retrospective Refund Calculations

A core operational challenge in implementing retrospective rebates is determining the appropriate “acquisition cost” to use as the basis for calculating the refund, especially across diverse purchasing arrangements and distribution channels. To limit complexity, CMS is considering a standardized default metric for Part B claims, and has floated four potential methodologies:

Option 1A - WAC, billing-code level, weighted by sales

This option would use Wholesale Acquisition Cost (WAC) averaged at the HCPCS or billing-code level, weighted by overall sales volume. It favors simplicity by working at an aggregated code level but may obscure variation between different package presentations.

Option 1B - WAC, 11-digit package level

Here, WAC would be tied to the specific 11-digit National Drug Code (NDC) or package identifier. This increases precision and can better reflect actual purchasing behavior, but it is more data‑intensive and may be harder to administer consistently across all sites of care.

Option 2A - ASP, billing-code level, weighted by sales

This methodology would rely on Average Sales Price (ASP) at the billing‑code level, again weighted by sales volume. It aims to align the default acquisition cost more closely with real net prices while retaining billing-code granularity.

Option 2B - ASP, billing-code level, weighted by claims package mix

The fourth option would still rely on ASP at the billing-code level but would weight the calculation by the distribution of package codes observed on actual submitted claims. This approach attempts to blend real-world utilization patterns with net price data, potentially providing a better proxy for typical acquisition costs in practice.

Manufacturers should evaluate these options against their own pricing, discounting, and channel strategies. The choice of methodology could materially affect refund amounts, budget impact, and internal forecasting for 2028 and beyond.

Interplay With 340B Pricing and Medicare Advantage Cost-Sharing

The draft guidance also addresses how the negotiated prices will coexist with other federal pricing programs and Medicare plan structures, clarifying several points that have substantial implications for compliance and patient affordability.

No stacking of 340B and negotiated prices

CMS indicates that manufacturers will not be required to stack discounts when a product is already subject to the 340B ceiling price. If the 340B price is lower than the negotiated Medicare price, the manufacturer’s obligation is to honor the 340B ceiling, not add an additional IRA-based discount on top. This reduces the risk of multiple overlapping federal price concessions on the same unit.

Medicare Advantage coinsurance must reflect the negotiated price

For Medicare Advantage beneficiaries receiving therapies covered under the negotiation program, in-network coinsurance must be calculated based on the new lower negotiated price, not the pre-negotiation list or contract price. This is intended to ensure parity in financial relief between Medicare Advantage enrollees and those in Original Medicare, and will require MA plans to update benefit designs, pharmacy claims systems, and provider contracts.

These clarifications will be particularly important for manufacturers that have significant exposure to safety-net hospitals, 340B entities, and MA-heavy therapeutic areas such as oncology and cardiometabolic disease.

Key Deadlines, Comment Opportunities, and Onboarding Milestones

CMS has opened a formal window for stakeholders to shape the final operational rules and timelines, and manufacturers should treat these dates as critical for internal planning.

Public comment period

The draft guidance is open for public comment for 60 days, with submissions due by 11:59 PM Pacific Time on September 18, 2026. Comments must be submitted electronically via email to CMS, and manufacturers should consider coordinated responses across market access, policy, legal, and finance functions.

Updated information collection and portal readiness

Later this summer, CMS plans to publish an updated information collection package that will describe in more detail the data elements and reporting expectations tied to the MTF and related systems. This will be the key reference for IT and data teams as they design or adapt interfaces.

Manufacturer onboarding for the 2028 cycle

Official onboarding of manufacturers into the facilitation portals supporting the 2028 negotiated price cycle is scheduled to begin on May 1, 2027. Companies will need to have core systems, data feeds, and internal governance structures ready ahead of that date to avoid last-minute remediation and potential disruptions.