Starting January 1, 2027, a slice of your 340B purchasing may stop working the way it has for three decades. Under the 340B Drug Pricing Program’s revised rebate pilot, covered entities buy selected drugs at wholesale acquisition cost first, then file a claim to get the 340B discount back. The discount only comes through if the dispense data behind that claim is complete and correctly formatted.
That changes what ‘compliant’ means day to day. The rebate now depends on whether your data clears validation before a submission deadline, not on your 340B status alone. Preparing for that means working through a specific sequence.
| Step | Action |
| 1 | Know what’s changing at the point of purchase |
| 2 | Confirm your submission window |
| 3 | Audit your dispense data against the required fields |
| 4 | Close the gaps before they cost you margin |
| 5 | Automate validation and reconciliation before you submit |
| 6 | Build in flexibility while the pilot is still moving |
Know What’s Changing at the Point of Purchase
Covered entities will buy selected drugs at WAC, not the 340B ceiling price, for a defined group of drugs pulled from CMS’s Medicare negotiation list for initial price applicability years 2026 and 2027. The full drug-level detail sits in CMS’s own fact sheets for 2026 and 2027.
The scope is deliberately narrow: HRSA has confirmed the included drugs represent under 5.5% of total 340B sales, with the remaining 94.5% staying on the upfront discount model through 2027. For everything outside that share, nothing about your current workflow changes, yet.
For the drugs that are in scope, the sequence flips. You place the order at the higher price, dispense to an eligible patient, then submit claims-level data to recover the difference after the fact, through a validated claim rather than at the point of sale.
Audit Your Dispense Data Against the Required Fields
Before you touch a workflow diagram, check whether your current data actually contains what a rebate claim needs. HRSA’s notice limits required fields to standardized claims data already generated in the ordinary course of pharmacy and medical billing:
- Date of service
- NDC-11
- Quantity dispensed
- Prescriber ID
- Service provider ID
- 340B ID
- Rx BIN and Rx PCN
- Health plan ID
The notice also draws a hard line on what manufacturers can’t ask for. HRSA declined manufacturer requests for purchasing or clinical data, keeping the requirement to claims-level fields your team is already producing for Medicare, Medicaid, and commercial billing.
If your 340B Dispense Data already supports those billing processes cleanly, the rebate submission is mostly a formatting exercise. If it doesn’t, that’s the gap to close first.
Confirm Your Submission Window
Covered entities get a defined window from the date of dispensation to submit 340B rebate claims, and manufacturers must pay or deny within 10 calendar days of receiving a complete submission. If a submission comes back incomplete, the clock restarts, which puts the real deadline pressure on your data quality, not just your calendar.
HRSA’s notice requires manufacturers to provide documented rationale for any denial, and suspicion of diversion or a Medicaid duplicate discount, on its own, isn’t valid grounds to refuse payment. Every denial has to point to a specific, defensible reason.
15-Day Grace Period for Unreplenished Packages
The transition period comes with one built-in cushion. Manufacturer plans must cover up to two packages per drug during the changeover, with a 15-day grace period for entities to submit rebate requests on inventory dispensed before the pilot’s effective date. That grace period doesn’t extend your total submission window; it protects inventory that was already moving through the system when the rules changed.
Close the Gaps Before They Cost You Margin
A denied claim leaves the WAC-to-ceiling spread sitting on your books as unrecovered cost, not realized savings. The gaps that produce denials tend to come from the same place. Eligibility data, dispense records, and rebate obligations live in separate systems, each with its own identifiers and update schedule. Clean 340B Dispense Data is what separates a paid rebate from a denied one, and manual MEF reconciliation is the step most likely to introduce the mismatch that trips up a claim.
OPAIS Mismatches and Medicaid Exclusion File Errors
Two specific 340B compliance failure points show up repeatedly in audit findings. Incorrect OPAIS records accounted for 62% of audit findings in FY 2024, and 91% of duplicate discount findings that same year traced back to inaccurate or incomplete Medicaid Exclusion Files. Because MEF submissions cover entire populations of claims rather than single transactions, one incorrect file can expose thousands of claims at once, far beyond the single claim that triggered the review.
Automate Validation and Reconciliation Before You Submit
Manual reconciliation across TPA, EHR, and pharmacy systems doesn’t scale to a submission window measured in days. Bluesight’s 340BCheck closes that gap by unifying claims data into a single record and preparing submission-ready files before anything goes to a manufacturer. Paired with CostCheck, it gives closed-loop visibility from purchase through rebate receipt, so what was submitted and what was actually paid sit side by side.
Real-Time 340B Eligibility Validation at Dispense
Rather than sampling a portion of transactions, 340BCheck validates every transaction at the time of dispensation, checking patient, provider, and location against OPAIS the same day. Exceptions surface immediately, before they become part of a submitted claim.
Automating 340B TPA Reconciliation
The mismatches that produce denials usually start with manual matching across file formats that were never designed to talk to each other. Automated 340B TPA Reconciliation cross-references TPA claims against administration and eligibility data directly, which reduces duplicate discount exposure concentrated in contract pharmacy claims.
Real-Time Audit Tracking and Rebate Reporting
Once a claim is submitted, 340BCheck tracks status from submission through payment or denial in a single dashboard, replacing the spreadsheet tracking most teams have relied on for compliance audits. CostCheck then confirms what was actually paid against what was claimed, closing the loop between the rebate expected and the rebate received.
Build in Flexibility While the Pilot Is Still Moving
This isn’t the first version of the 340B rebate model. HRSA has already reversed course once.
| Date | Event |
| Dec 1, 2025 | Covered entity stakeholders sued to block the original 2025 pilot under the Administrative Procedure Act |
| Dec 29, 2025 | A federal district court granted an injunction, pausing the pilot nationwide; the First Circuit declined to lift it |
| Jan 20, 2026 | HHS dismissed its own appeal and withdrew the 2025 pilot |
| Feb 10, 2026 | The district court formally vacated the 2025 notice |
| Aug 3, 2026 | HRSA published a revised notice with narrower scope; manufacturer plans were due August 24, 2026 |
That history is a reason to build your reconciliation process on a platform that can adjust to updated field requirements or a shifted timeline, rather than hardcoding today’s rules into a workflow you’d have to rebuild if they move again.
See how 340BCheck prepares rebate-ready data for the transactions that will be affected, and get a system in place before the first claim is due.