Skip Navigation
Updating Your 340B Policies and Procedures for the Rebate Model

Blog Post

Updating Your 340B Policies and Procedures for the Rebate Model

By Adam Rosenberg

Key Takeaways

  • Pilot drugs are ordered at WAC through the existing 340B wholesaler account, never through WAC-only or group purchasing organization (GPO) accounts when the entity plans to seek a rebate.
  • Claims data has to reach the manufacturer’s platform within 45 calendar days of dispensation, on a fixed set of standardized fields.
  • Each submission, its rebate status, and any denial become part of the compliance record an auditor can review.
  • Denials follow a defined path, from resubmission to the manufacturer to HRSA, with the 340B Administrative Dispute Resolution (ADR) process as the backstop.

Covered entities should update the purchasing, claims submission, recordkeeping, and discrepancy handling of their 340B policies and procedures for drugs in the Health Resources and Services Administration’s (HRSA) rebate pilot. Starting Jan. 1, 2027, covered entities will pay wholesale acquisition cost (WAC) for 21 pilot drugs from 10 manufacturers and receive the 340B price as a unit-level rebate after submitting claims data. Most policy documents still assume every drug arrives at the 340B price up front.

HRSA expects policies and procedures to reflect actual practice and expects covered entities to provide them when auditors ask. HRSA may also use pilot data during routine 340B audits, so a policy that describes a workflow the entity no longer follows is easy to spot.

What Should 340B Policies and Procedures Include?

Strong 340B policies and procedures document how the entity meets each program requirement and how it checks itself, through routine self-audits and corrective action. HRSA audits test those documents against eligibility rules and the duplicate discount and diversion prohibitions, and gaps can lead to refunds to manufacturers or removal from the program.

A complete policy set should address:

  • Eligibility, registration, and annual recertification in the Office of Pharmacy Affairs Information System (OPAIS)
  • Patient, provider, and location eligibility for each dispense
  • Contract pharmacy oversight, including a written contract for every registered pharmacy
  • Medicaid Exclusion File accuracy to prevent duplicate discounts
  • The GPO prohibition, for disproportionate share, children’s, and free-standing cancer hospitals
  • The orphan drug exclusion, for critical access hospitals, rural referral centers, sole community hospitals, and free-standing cancer hospitals
  • Self-audit methods, corrective action, and documented criteria for a material breach

HRSA’s fiscal year 2025 audit results include citations tied to these areas, from incorrect OPAIS records and contract pharmacies registered without a written contract to diversion and Medicaid Exclusion File errors. Stale policies that describe how a program used to run, rather than how it runs today, are among the most common problems programs bring into a review.

Why Do 340B Policies Need Revisions for the Rebate Model?

Most 340B policies describe replenishing full packages at the 340B price, a workflow that no longer applies to pilot drugs. Drugs eligible for the pilot made up less than 5.5% of 2025 340B sales. Every other drug stays on upfront discounts, so covered entities will run both purchasing models at once, and their policies need to cover both.

Once HRSA approves a manufacturer’s plan, every covered entity buying that manufacturer’s selected drugs has to follow it. All 10 approved manufacturers use the Beacon Rebate Model Platform, and all start on Jan. 1, 2027.

Each rebate submission also becomes a compliance record, built on standardized fields that HRSA can review.

How Should the Purchasing Section Change for Rebate-Eligible Drugs?

The purchasing section should direct staff to order pilot drugs through the existing 340B wholesaler account with WAC loaded, and never through WAC-only or GPO accounts when the entity intends to seek a rebate. Account routing is only the first change, since the pilot also redraws which drugs are affected, when open accumulations close out, how Medicaid claims are priced, and how cash moves:

  • Scope. The pilot covers active selected drugs for initial price applicability years 2026 and 2027, regardless of payer or indication, during each drug’s price applicability period. Naming the drug list in the policy keeps buyers from guessing.
  • Transition. Plans must accept rebate requests for up to two unreplenished accumulated packages within a 15-day grace period before Jan. 1, with claims still due within 45 days of dispense. A transition clause tells staff how to clear open accumulations on pilot drugs.
  • Medicaid billing. Manufacturers must publish a quarterly 340B ceiling price file for each National Drug Code (NDC), which covered entities use to set actual acquisition cost for Medicaid billing and sliding-fee calculations.
  • Cash flow. WAC is due at purchase while the rebate follows later, so the policy should point to a cash-flow plan that models the gap for each pilot drug before the first purchase cycle. Purchasing tools such as CostCheck can run that comparison of WAC against the expected rebate before the order goes out.

What Should the Claims Submission Section Cover?

The claims section should name who submits claims data to the platform within 45 calendar days of dispensation and how each claim is checked before it goes out, starting with mapping existing claims data to the fields HRSA allows. Manufacturers can request only the fields below, including the Bank Identification Number (BIN) and Processor Control Number (PCN) that identify a patient’s pharmacy benefit:

Pharmacy claims fieldsMedical claims fields
Date of serviceDate of service
Date prescribedClaim line number
Rx numberClaim number
Fill numberUnit of measure
NDC-11NDC-11
Quantity dispensedQuantity
Prescriber IDRendering physician ID
Service provider IDService provider ID
340B ID340B ID
RX BINHealth plan name
RX PCNHealth plan ID
Health plan ID qualifier (if available)

The fields alone don’t settle every case, so the policy can spell out how staff handle the ones that come up most:

  • Uninsured patients. BIN, PCN, and health plan fields can be marked “CASH” for uninsured or cash-paying patients.
  • Wasted or undispensed units. Each manufacturer’s plan includes its own instructions, so the policy should point to each plan by drug.
  • Status changes. Plans must allow adjustments when a claim’s 340B status changes.
  • Privacy. Pilot data fields exclude direct patient identifiers, and HRSA describes submitting claims data for a rebate as a payment-related disclosure under the Health Insurance Portability and Accountability Act (HIPAA), which the privacy section can reference.

What Records Should the Recordkeeping Section Require?

The recordkeeping section should require a complete file for every pilot drug claim, since accurate records documenting compliance are already a 340B requirement and pilot drugs add record types that didn’t exist under upfront discounts. A claim file that holds up in an audit pairs what was submitted with what came back:

  • The submission file and submission date
  • The platform’s real-time reconciliation report showing rebate status
  • Any denial notice with the manufacturer’s rationale and documentation
  • The WAC invoice matched to the rebate received
  • The quarterly 340B ceiling price file in effect on the date of dispense
  • Each manufacturer’s approved plan, which HRSA posts on its pilot page

Matching what was paid at WAC against what was rebated has to happen where the invoice data lives, since rebate-only platforms never see the invoice. Keeping those records in the same place as pharmacy service agreements, Medicaid exclusion files, and Medicare cost reports turns a data request into an export instead of a search.

How Should the Policy Handle Denials and Discrepancies?

The discrepancy section should route each issue to a defined path, because manufacturers must pay or deny a complete claim within 10 calendar days and can’t deny eligibility, diversion, Medicaid duplicate discounts, or a perceived lack of WAC purchases. 

When a denial or internal error does come through, the policy should set the order staff works through it:

  1. Resubmit incomplete claims, since a returned submission restarts the 10-day clock once the data is complete.
  2. Raise documented disputes with the manufacturer’s named point of contact.
  3. Report improper denials to HRSA at 340Bpricing@hrsa.gov.
  4. Escalate unresolved disputes through 340B ADR, which requires documentation of good-faith efforts to resolve them first.
  5. Self-disclose any internal error that meets the entity’s material breach criteria, with a corrective action plan HRSA expects to be complete within six months.

Assigning a single owner to each step keeps denials from sitting unworked while the 45-day and 10-day clocks run.

How Should Covered Entities Roll Out the Revised Policies?

Covered entities can adopt the rebate sections as an addendum tied to the pilot drug list and effective Jan. 1, 2027, since the upfront discount still governs every drug outside the pilot. An addendum keyed to the drug list can be updated without reworking the core policy set as HRSA adds or removes drugs.

The pilot has also been challenged in court, so the addendum can name an owner who tracks pilot status and adjusts the effective date if it moves. Review the rebate sections whenever a manufacturer changes its plan or HRSA updates the pilot, so the written policy keeps matching what staff actually do. 

Pharmacy, compliance, and finance staff each own a different step in the rebate workflow, so train all three on the new sections before the first pilot claim goes out. Pharmacy orders pilot drugs and submits claims, compliance works denials and keeps the audit file, and finance covers the WAC cash-flow gap and matches rebates to invoices. 

Each team owns a different step in the rebate workflow. Pharmacy orders pilot drugs through the 340B account and submits claims, compliance works denials and keeps the audit file, and finance covers the WAC cash-flow gap and matches rebates to invoices. A team still following the upfront-discount process can stall a claim at its step.

Get Your Policies Audit-Ready Before January

Covered entities whose policies match how pilot drugs are actually bought, submitted, and reconciled walk into their next audit with documentation that’s already current. Updating your policies before January? 

See 340BCheck in action to manage policies and procedures, run mock HRSA audits, and track remediation in one place, then talk to Bluesight about pairing 340BCheck and CostCheck for rebate-model compliance.


Frequently Asked Questions

Does the Rebate Model Change Which Patients Qualify for 340B?

No. The pilot changes how and when the 340B price reaches the covered entity, not patient eligibility requirements or the 340B ceiling price.

Does Each Manufacturer Need Its Own Policy?

No. HRSA standardizes the data fields, and all 10 approved manufacturers use the same platform, so one rebate addendum can cover every pilot drug. The addendum should still reference each manufacturer’s approved plan, since plans differ on details such as how to report wasted or undispensed units.

What Happens If a Claim Misses the 45-Day Submission Window?

Plans must accept claims for at least 45 calendar days from dispense and allow for extenuating circumstances. AbbVie’s Imbruvica plan, for example, reviews exception requests case by case. The policy should name who requests an exception and how the request and its outcome are documented.

How Often Should 340B Policies and Procedures Be Updated?

HRSA doesn’t set a fixed schedule, but it expects covered entities to review and update policies regularly and to revise them whenever practice changes. Moving pilot drugs from upfront discounts to rebates is that kind of change, so the rebate sections should be in place before the first pilot purchase.