Industry Insights Logo

Your 340B Performance Is Already Changing Under the IRA

SPONSORED CONTENT

There has been no formal announcement explaining how the Inflation Reduction Act (IRA) is playing out operationally within 340B.

Instead, it’s showing up in the data. For many organizations, it looks subtle at first. A dip in qualified claims. A shift in Medicare volume. A pharmacy that isn’t performing the way it historically has.

The IRA is already influencing how 340B programs perform. Not through a single policy change, but through a series of operational shifts that are unfolding in real time.

At a high level, the dynamic is straightforward:

The first round of IRA pricing went live January 1st, 2026.
MFP rebate activity is happening.
The 340B rebate model is still on hold.

What is less straightforward is how that reality is translating into day-to-day program performance.

1. Medicare Reimbursement Is Lower = Revenue Is Down

One of the most immediate impacts of the IRA is also one of the most straightforward.

Medicare reimbursement tied to negotiated pricing is coming in lower.

This affects both pharmacies and covered entities (CEs) directly. Before MFP rebates are even considered, less revenue is being generated per claim.

For CEs, this shows up as:

  • Reduced margins on Medicare volume
  • Lower overall 340B revenue

This is a direct loss of revenue, independent of any rebate determination.

At the same time, this reimbursement pressure compounds the impact of everything else happening downstream.

2. MFP Rebate Outcomes Are Inconsistent — Not Because of the Data

The problem is not the source data itself. CEs are submitting accurate, claim-level data.

The breakdown is happening in how that data is being relayed, interpreted, and applied across the Medicare Transaction Facilitator (MTF) and platforms like Beacon and 340B ESP.

These platforms are ultimately determining:

  • Whether a claim is considered 340B
  • Whether a rebate should be paid

As that information moves through each layer, inconsistencies are being introduced.

There is no standardized way to validate whether the final rebate determination actually reflects what happened at the point of dispense.

This leads to two critical outcomes:

  • Rebates are being paid where a 340B dispense/purchase actually occurred, creating duplicate discount exposure and repayment risk
  • Rebates are not being paid where 340B discount did not occur, where the pharmacy should receive an MFP rebate, resulting in missed revenue

What should be a clear financial outcome becomes inconsistent, and in many cases, incorrect.

3. Pharmacies Are Responding to the Risk

As these inconsistencies emerge, pharmacies, particularly large chains, are adjusting their approach to 340B participation in real time.

This shift is being driven by a combination of factors:

  • Repayment risk tied to potential duplicate discounts
  • Exposure from incorrect claim classification
  • Uncertainty around rebate eligibility and timing

To reduce that risk, many pharmacies are choosing to exclude IRA-affected drugs from 340B for Medicare payers altogether.

With fewer eligible claims entering the program, CEs are seeing declines in both claim volume and overall 340B revenue. What may look like a small change at the pharmacy level is often driving a much larger shift in program performance.

This change in behavior is not isolated, it is one of the most significant factors influencing 340B outcomes right now.

4. In-House Pharmacies Are Getting Hit on Both Sides

For organizations with in-house pharmacies, the impact often shows up differently than it does in the contract pharmacy environment. The issue is not just reduced participation or lower claim volume. It is a combination of lower reimbursement and unreliable rebate outcomes, both of which put pressure on financial performance.

At the reimbursement level, these pharmacies are already feeling the effect of IRA pricing. Medicare reimbursement is lower, which means margins are tighter from the start. On top of that, rebate payments tied to MFP can be inconsistent, delayed, or difficult to reconcile. What should act as a predictable financial offset is instead becoming another source of uncertainty.

The core issue is rebate accuracy. For in-house pharmacies, the risk can move in two directions:

  • If a rebate is paid on a claim that was actually 340B, it creates duplicate discount exposure and potential repayment risk.
  • If a rebate is not paid on a claim that was non-340B, the pharmacy misses revenue it should have received.

That is what makes this more than a reimbursement issue. Even when an organization has visibility into what was dispensed, it may still lack a structured way to compare that activity against what was ultimately recognized across MTF, Beacon, and ESP. Without that reconciliation, it becomes difficult to confirm whether rebate outcomes are actually accurate.

This creates a cash flow and reconciliation challenge, not just a reimbursement challenge. And for CEs with in-house pharmacies, that distinction matters. It means the problem is not only that revenue is under pressure. It is that providers may also lack a reliable way to verify whether the revenue they are receiving is correct.

Where the Breakdown Is Actually Happening

The issue is not a lack of effort or accuracy at the CE level. In most cases, data is being submitted correctly and on time.

The problem is happening after that step.

Manufacturers and pharmacies are relying on 340B MTF, along with platforms like Beacon and ESP, to determine whether a claim should trigger a MFP rebate. Each of these systems plays a role in how claims are interpreted, classified, and ultimately tied to a financial outcome.

The challenge is that this process is not unified.

There is no consistent framework governing how decisions are made across systems, and more importantly, no clear way to validate the outcome once those decisions are applied. Specifically:

  • No unified validation layer across 340B MTF, Beacon, and ESP
  • No standardized reconciliation process to compare outputs across systems
  • No single accurate source confirming whether the final determination is correct

As a result, a gap is forming between what happened at the point of dispense and what the system determines happened when rebates are issued.

That gap is where the real impact occurs. It is where:

  • Revenue is lost when rebates are not paid correctly
  • Rebates are misapplied, creating duplicate discount exposure
  • Compliance risk increases due to lack of verifiable alignment across systems

This is not a visibility issue alone. It is a validation issue, and without a way to reconcile these differences, even accurate data can lead to inaccurate outcomes.

Why This Is Hard to Spot

These changes are not presenting as a single, obvious failure.

Instead, they show up as:

  • Slight drops in Medicare volume
  • Variability in pharmacy performance
  • Inconsistent rebate outcomes

This decline is not being driven by rebates alone. Instead, it is the result of two pressures that are reshaping how revenue flows through the program:

  • Pharmacy behavior: with many pharmacies excluding IRA-affected Medicare claims from 340B participation, fewer qualified claims are entering the program
  • Reimbursement pressure: with lower Medicare reimbursement tied to IRA pricing compressing margins on the volume that does remain

Together, these dynamics are reducing both how much volume is captured and how much value is generated per claim.

What This Means for Your 340B Pharmacy Strategy in 2026–2027

The 340B rebate model may be paused, but the operational infrastructure behind it is already live and already influencing pharmacy behavior and claim outcomes. We are already seeing shifts in pharmacy performance tied directly to IRA dynamics, including pharmacies limiting or excluding IRA-affected drugs from 340B, variability in how Medicare claims are being handled, and clear gaps between what should qualify for rebates and what is actually being paid.

Historically, network strategy focused on access and volume. That is no longer enough. In the current environment, CEs need to look more closely at how their network is actually performing under IRA-related pressure. That means understanding which pharmacies are maintaining consistent qualified claim volume, which are experiencing unexplained drops in Medicare-related 340B activity, and where rebate outcomes are not aligning with what actually happened at the point of dispense.

These are not surface-level questions, and they cannot be answered by reported outputs alone. They require detailed data analysis, ongoing monitoring, and a program management approach that actively validates what is happening across the network, not just what is being reported back through the system.

The Bottom Line

The IRA’s impact on 340B is not limited to the rebate model conversation. The first round of negotiated pricing is already live, and it is already changing how claims are classified, how rebates are determined, and how pharmacies choose to participate.

At the center of it is a growing disconnect. There is an increasing gap between what actually happened at the point of dispense and what is ultimately recognized when rebates are determined.

And this is just the beginning.

Another round of IRA drugs will be introduced in 2027, adding further pressure to an already evolving system.

The programs that will perform best in this environment will not be the ones waiting for clarity.

They will be the ones doing the work to understand what is actually happening, validate it, and act on it.

Lindsey Martin is VP of Consulting at RxTrail. She can be reached at lmartin@rxtrail.org

Website |  + posts

Read more 340B Expert Tips

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

Site Footer Live