Beacon Rebate Pilot – Week 1 Update

14 Nov Beacon Rebate Pilot – Week 1 Update

HRSA’s 340B Rebate Model pilot remains on schedule for January 1, 2026, despite the ongoing federal government shutdown. Beacon Channel Management has issued updated manufacturer guidance, revised its FAQ on November 3, and opened registration for all covered entities.

Key Program Updates

Implementation Date: January 1, 2026 — unchanged.
Manufacturers: Eight approved, covering nine MFP drugs.
Registration: Each 340B ID must register and complete bank verification through Beacon at:
cm.beaconchannelmanagement.com/enrollments/registrations

Documentation Required:

• Employer Identification Number (EIN)
• IRS CP-575 Letter confirming EIN
• Articles of Incorporation
• Current W-9 (latest IRS revision)

FAQ Update: All purchase-data fields were removed. Rebates will now be based on the date of dispense or administration, not purchase date.

Scope: Applies to all covered-entity types and care settings — retail, contract pharmacy, provider settings, and clinic-administered drugs.

Note:
Grantee covered entities, including FQHCs, must register each 340B ID individually, but users can manage multiple IDs inside one Beacon login.

Common Question: The Pilot Is Voluntary, Right?

Some clients have asked if they can opt out and continue purchasing these drugs using traditional 340B pricing.

Answer:
Participation is mandatory if an entity wants access to 340B pricing on the nine rebate-model drugs.

Manufacturers have transitioned these NDCs to the HRSA-approved rebate mechanism. Covered entities that do not register and submit rebate claims through Beacon will lose access to 340B ceiling prices for these drugs.

All other (non-rebate) drugs continue under standard 340B purchasing rules.

Purchase Timing and Validation

Dispense-first replenishment workflows may continue.

Each rebate claim must be supported by a WAC purchase made through the entity’s 340B account. Beacon and manufacturers will verify purchases using wholesaler data feeds; invoice uploads are no longer required.

Claims that cannot be matched to a WAC purchase within roughly 30–45 days may later be denied or reversed. HRSA has not confirmed exact timing requirements, but assume there will be a limit.

Action:
Rebate submissions should not occur until a corresponding WAC purchase has been made and is visible in wholesaler data. HRSA has not specified whether the purchase must occur before or after the dispense date.

Bank Account Structure

Beacon now limits each 340B ID to one verified bank account for rebate payments.

All sites under the same ID share that account. Entities with multiple 340B IDs may register:

• different accounts, or
• the same account for consolidated deposits.

Rebates are paid directly to the verified account, not through the wholesaler.

Impact:
Each unique 340B ID must be registered in Beacon and linked to a verified bank account. Entities may consolidate or separate funds depending on their internal processes.

Package Purchases vs. Unit Rebates

• WAC purchases occur at the package level.
• Rebates are calculated at the unit level based on dispenses.
• Manufacturers reconcile units dispensed to package purchases through wholesaler data.
• Beacon does not display a package-level reconciliation report.

Low-volume NDCs dispensed slowly from existing WAC stock will still qualify if submitted within 45 days of the dispense date.

Recommendation:
Maintain an internal unit-to-package ledger (FIFO) to track how WAC packages draw down through dispensed units. This helps ensure eligibility, supports internal reconciliation, and protects against manufacturer denials.

Transition Period

Manufacturer look-back windows for unreplenished accumulations vary 14–45 days, and some allow only one package per NDC.

HRSA has not standardized these look-back periods.

Ponaman guidance:
Replenish all 340B accumulations for in-scope drugs before December 31, 2025 to avoid stranded savings — but do not stockpile physical 340B inventory in December.

ESP and Contract-Pharmacy Eligibility

Rebate-model drugs do not require claim uploads into 340B ESP. All rebate claims will flow through Beacon.

However, ESP still controls contract-pharmacy eligibility. Beacon cross-references ESP to determine which pharmacies are approved. Claims from non-eligible contract pharmacies will not qualify.

Data-Field Readiness

Beacon’s templates for medical and pharmacy claims require several new data elements that many TPAs do not currently export:

• Rendering Provider NPI (listed as “Rendering Physician ID”)
• Claim Number
• Claim Line Number

These fields typically come from a covered entity’s billing or EHR system, not TPA accumulation feeds.

TPAs may need to adjust mapping or pull this data directly from billing systems. Until updates are complete, some files may require manual data supplementation — so begin conversations with TPAs and IT teams now.

Ponaman is working with Beacon and major TPAs to confirm how these fields will be populated and will share updates as standards emerge.

Additional Considerations

Cash Flow:
WAC purchases precede rebates. Most rebate payments are issued within ~10 days of submission.

Data Security:
Manufacturers confirm SHA-3 hashing and salting of identifiers; overall risk is low.

Audit Preparedness:
HRSA has not yet defined the audit process for rebate-eligible claims. Ponaman will advise clients once guidance is released. Continue monitoring your 340B program as usual.

Ponaman Perspective

The rebate model is advancing quickly, and operational details continue to evolve. Covered entities should now:

• Complete Beacon registration and bank verification.
• Align purchasing timing with Beacon submission workflows.
• Prepare reconciliation processes for single-account deposits and unit-to-package tracking.
• Keep ESP contract-pharmacy relationships up to date.
• Replenish all 340B accumulations before year-end while avoiding stockpiling.
• Understand that Beacon participation is required to maintain 340B pricing for the nine rebate-model drugs.

Ponaman consultants are available to support registration, data readiness, and transition planning as organizations prepare for January implementation. Book a call with us to discuss your plan — this transition will take a village.