In August 2026, the Health Resources and Services Administration (HRSA) scheduled a rebate pilot for the 340B program to start January 1, 2027, covering 25 drugs from 13 different manufacturers. Previously, a near-identical version of this pilot was blocked before launching, and there is no guarantee this one survives to January 1 either. Regardless of how the litigation plays out, manufacturer plans were due to HRSA by August 24, 2026. Waiting for legal certainty before starting the readiness work potentially leaves no runway left if the date holds.
Regardless of how that plays out, make sure to:
- Map which drugs are in scope
- Model the wholesale acquisition cost (WAC) cash-flow gap
- Treat every rebate submission as a compliance record
What the 340B Rebate Model Pilot Covers
The pilot replaces the upfront 340B discount with a rebate, but only for a defined slice of the program. Covered entities buy selected drugs at WAC through their existing distribution channels, then submit standardized claims data and receive a rebate that brings the net price down to the 340B ceiling. Those 25 drugs, from 13 manufacturers, affect roughly 5.5% of total 340B sales; everything else continues under the current upfront discount system.
The pilot’s key dates carry the whole timeline:
| Date | Process |
| September 24, 2026 | HRSA posts which manufacturer plans it approved |
| December 2026 | Manufacturers send covered entities their required 90-day notice |
| January 1, 2027 | The pilot goes live on the 25 selected drugs |
Step 1: Map Which Drugs Fall Inside the Pilot
Exposure isn’t uniform. A hospital that doesn’t stock any of the 25 pilot drugs is looking at a very different readiness timeline than one that dispenses several at volume, so mapping comes before modeling anything else.
Checklist:
- Pull NDCs for all 25 pilot drugs against your own formulary
- Flag purchase volume and current 340B savings by drug
- Watch for manufacturer plan approvals HRSA posts September 24, 2026
- Confirm December 2026 90-day manufacturer notices name your entity correctly
Step 2: Model the Cash Flow Gap from Paying WAC Upfront
WAC is due at purchase, while the rebate lands on a separate, later timeline tied to claims submission and manufacturer processing. A covered entity that hasn’t modeled that gap before January 1 finds out its actual size in real time, against a live budget.
Checklist:
- Map the timing gap: WAC due at purchase, rebate paid on a separate, later timeline
- Estimate monthly cash tied up per pilot drug at full WAC
- Identify which sites feel this first, typically higher-volume 340B program participants
- Set a bridge reserve or short-term financing line before the first cycle
Step 3: Treat Every Rebate Submission as a Compliance Record
Under the current system, a covered entity denied a duplicate-discount claim can argue eligibility after the fact. Under the pilot, that argument doesn’t exist in the same form. Manufacturers can’t deny a rebate for eligibility, diversion, or a missing WAC purchase; those disputes route to HRSA through an audit or dispute process instead of manufacturer negotiation.
The submission itself, built on standardized claims fields, becomes the compliance record sitting in front of HRSA. Getting it right the first time matters more than being ready to argue a denial later.
Checklist:
- Confirm manufacturers can’t deny rebates for eligibility, diversion, or duplicate discount under the pilot
- Know that HRSA, not the manufacturer, now handles rebate disputes
- Confirm your claims data maps to the standardized submission fields
- Build a pre-submission validation step, since there’s no clean way to argue after
How Can I Monitor 340B GPO Prohibition Automatically
Group purchasing organization (GPO) exclusion rules aren’t new, but the way most programs check for violations hasn’t kept pace with how fast a violation can happen. Most programs still spot audit under 25% of transactions, leaving a GPO purchase on an excluded drug to sit unnoticed for a full quarter before the next manual review. Real-time WAC and GPO tracking closes that gap before the purchase happens, flagging risk at the point of order instead of after the invoice arrives.
Checklist:
- Check your current audit coverage: most programs still spot audit under 25% of transactions
- Identify the gap: manual, quarterly review misses exclusion violations between checks
- Confirm your purchasing tool tracks WAC and GPO ratio changes in real time
- Set alerts to flag risk before the purchase happens
How Hospitals Can Measure Ongoing Success of a 340B Compliance Program
Compliance leads need something to report besides pass or fail, especially with a new HRSA-facing data stream about to start. OPAIS mismatches remain the leading adverse finding two fiscal years running, which makes sync frequency a measurable input rather than a background task.
Time-to-closure on findings tells its own story. A program that logs, remediates, verifies, and closes a finding within weeks is operating differently than one still working through the same issue at the next audit cycle.
Checklist:
- Track your adverse finding rate as a year-over-year trend, not a single pass-or-fail result
- Set your self-audit target at 100% of transactions, not a sample
- Track time from finding to closure across tasking, remediation, and verification stages
- Monitor OPAIS sync frequency and mismatch count, since OPAIS errors lead findings
What’s the Best 340B Software That Integrates with OPAIS
OPAIS integration is the first filter worth applying to any software decision, not something to check after the fact. A daily OPAIS sync surfaces a mismatch the same week it appears, well ahead of the next quarterly reconciliation. From there, real 340B compliance software centers document management and the audit trail, and prepares submission-ready rebate files, going further than a tool that only raises alerts or flags eligibility.
Checklist:
- Confirm your platform syncs with OPAIS daily
- Choose 340B compliance software built for the job, not a generic audit tool adapted to it
- Check whether the platform centers documentation management rather than alerts alone
- Verify the platform prepares submission-ready rebate files, going beyond eligibility flags
- Make sure the platform connects to purchasing data as well as compliance data
Pairing 340BCheck and CostCheck for Rebate Readiness
Mapping, cash flow, and the compliance record split cleanly across two platforms, not one tool trying to do all three jobs. 340BCheck validates eligibility against every transaction and builds the audit trail before anything gets submitted. CostCheck models the purchase decision itself, WAC against an assumed rebate, and reconciles the invoice afterward against what actually came back.
| Function | 340BCheck | CostCheck |
| Role | Compliance and audit trail | Pre-purchase decision support |
| What it validates | Patient, provider, and location eligibility | WAC vs. rebate at point of purchase |
| What it tracks after purchase | Submission-ready rebate files | Invoice-level reconciliation |
| OPAIS connection | Daily sync | N/A |
Checklist:
- Keep both platforms working from one shared pilot drug list, not two separately maintained ones
- Assign one owner accountable for the full loop, purchase decision through reconciliation
- Set a review cadence for reconciling what was paid against what came back
- Give compliance and purchasing shared visibility into the same transaction record
How Do I Prepare for a HRSA 340B Audit Under the Pilot
The pilot adds to HRSA’s standard audit process rather than replacing it, layering new documentation requirements onto reviews that are already producing adverse findings at a high rate. HRSA audited 115 covered entities in fiscal year 2025, nearly half of them coming back adverse. Centralizing documentation determines how a data request actually feels when it arrives.
Programs that keep the following in one place can turn a request into a same-day export:
- Contract pharmacy agreements
- Cost reports
- Policies and procedures
- Rebate and reconciliation records under the pilot
Programs without that groundwork spend weeks reconstructing a year of activity from scattered files instead.
Checklist:
- Know your baseline: HRSA audited 115 covered entities in FY25, nearly half came back adverse
- Know HRSA’s data request typically covers eligibility documentation, contract pharmacy records, and Medicaid Exclusion File status
- Confirm your documentation covers pilot-specific rebate and reconciliation records, on top of existing audit files
- Centralize contract pharmacy records, cost reports, and rebate files in one place
The Pilot’s Litigation History, and Why the Status Still Matters
HRSA published the January 1, 2027 date in a formal notice. But a near-identical version of this pilot was blocked by injunction days before its own launch date once already, and HHS scrapped that version rather than continue the appeal. That history doesn’t make the current pilot less real or less worth preparing for. It means status, not just the calendar, needs tracking between now and January.
The scope itself has already moved once, from an original 10 drugs to the current 25, with public comments split along predictable lines: covered entities far more skeptical than manufacturers and technology vendors, who were largely supportive.
Checklist:
- Build in a contingency plan for a delayed or paused start, this exact pilot has slipped once already
- Avoid locking contracts, staffing, or system changes irreversibly to January 1
- Track HRSA’s own notices directly rather than treating today’s date as the final word
Get Ready Before the Notices Arrive
Map your drug list, model your cash-flow gap, and confirm your submission process is built to withstand HRSA scrutiny before the first pilot claim goes out.
Talk to Bluesight today about pairing 340BCheck and CostCheck for 340B rebate readiness.