Contents
As the 340B rebate pilot approaches its January 2026 launch, one of the most debated questions is whether covered entities should be required to submit purchase data to claim 340B rebates. At first glance, the idea may sound like a safeguard against duplicate discounts. But in practice, tying rebate claims to purchase data risks undermining the very integrity the pilot is supposed to protect.
Why Manufacturers Want Purchase Data
Manufacturers argue that access to purchase data serves several purposes:
Verifying the purchasing entity – confirming that the covered entity itself, not a contract pharmacy or third party, purchased the units for which a rebate is claimed.
Confirming the purchase price – ensuring that units were obtained at WAC.
Preventing early misuse – reducing the risk that rebate claims are submitted for 340B-priced units acquired before the pilot’s effective date.
On paper, these appear to be reasonable goals. But as with many 340B issues, the details matter.
Why Purchase Data Doesn’t Work in Practice
Here’s the problem: 340B purchases don’t always happen in lockstep with claims. Transactions are often accumulated and then swept into a future 340B purchase. If rebate submissions were held until purchase data could be attached, the timing would never consistently align with rebate cycles, and this would also cause challenges with accurate and consistent claims reporting.
It’s like checking the grocery store receipt weeks after the food has already been eaten — the timing mismatch makes it nearly impossible to reconcile what was purchased with what was consumed.
The reality is that transactional data (prescriptions and medication administrations) at the time of 340B eligibility determination is the cleanest, most consistent way to identify duplicate discounts. The covered entity and dispensing pharmacy are already captured in the claim submission — we don’t need to layer on purchase data to confirm who dispensed the drug.
If the entity submitting a 340B rebate claim isn’t the same entity making the purchase, that’s a compliance issue worth addressing — but it’s not what HRSA set out to solve with the rebate pilot.
Rebate Calculations Must Be Standardized
Another concern is how rebate amounts are calculated. If manufacturers tie rebates to the actual purchase price paid by the entity, rebate amounts could vary wildly. That approach undermines transparency and fairness.
Rebates must be based on a standard formula — WAC minus the 340B ceiling price — applied consistently. Otherwise, manufacturers could adjust rebate payments in ways that are opaque to covered entities and impossible to validate. Access to purchase data makes this inconsistency more likely, not less.
The Transitional Period: Integrity Matters
There is no denying that the transition period around January 1, 2026, will be challenging. Some entities could accidentally (or even intentionally) submit rebate claims for drugs purchased under the 340B program prior to the pilot’s start date.
But here’s the key: requiring purchase data won’t eliminate that risk. It will only complicate the process. The responsibility ultimately lies with covered entities to ensure claims submitted for rebates did not already result in a 340B purchase. This expectation isn’t unique to the rebate pilot — it’s part of the broader culture of compliance in healthcare.
Importantly, this risk is primarily limited to entities that maintain physical 340B inventories. Settings that utilize virtual inventory models should result in a retrospective purchase and be easily managed through this transitional period.
Keep It Simple, Keep It Honest
If we overload the rebate process with purchase data, we risk creating a system that is more complex and less reliable. The pilot’s goal is to evaluate whether a rebate model can work. That evaluation depends on accurate, timely, and consistent data — which means focusing on transactional claims, not purchase records.
Covered entities must do their part to submit claims with integrity. Manufacturers must do their part to honor rebate calculations in a standardized way. Only then will the pilot give us meaningful insight into whether this approach can protect the 340B program while meeting the needs of all stakeholders.
