If you lead a Federally Qualified Health Center (FQHC), pharmacy operation, finance team, or 340B compliance program, 2027 may introduce a significant operational change: for certain drugs and manufacturers participating in the 340B Rebate Model Pilot, your entity may need to purchase at wholesale acquisition cost (WAC), submit claims-level information, and receive the 340B benefit later through a rebate.

That is more than a pricing adjustment. It changes your organization’s cash-flow exposure, data responsibilities, vendor oversight, reconciliation process, and audit trail.

This guide explains the 2027 340B rebate model requirements that covered entities should prepare for now. It also separates requirements described in current HRSA materials from provisions that remain proposed, pilot-specific, or subject to change.

Important disclaimer: The 340B Rebate Model Pilot and its implementation details may change as HRSA, HHS, manufacturers, and other stakeholders issue additional guidance. This article is for educational purposes only and is not legal, accounting, regulatory, or compliance advice.

What Is Confirmed for the 2027 Pilot?

Based on current HRSA materials and the published 2027 pilot framework, the following points should be treated as the primary planning assumptions:

The pilot is scheduled to begin January 1, 2027.
It applies to a limited group of drugs associated with the Medicare Drug Price Negotiation Program’s selected drugs for initial price applicability years 2026 and 2027.
Manufacturer participation is voluntary.
Once a manufacturer’s rebate plan is approved, affected covered entities purchasing the selected drugs should expect to follow that plan.
Covered entities may purchase affected drugs at WAC rather than receiving the 340B discount upfront.
Rebate requests generally must be supported by standardized, claims-level data.
Covered entities generally have up to 45 calendar days from the date of dispense to submit the required information.
Manufacturers are expected to pay or formally deny a complete request within 10 calendar days of submission.
Manufacturer plans must provide implementation notice and identify the technology platform used for submissions.

The current framework is not the same as a final, permanent redesign of the entire 340B program. It is a limited pilot. Your entity should therefore build a flexible operating model rather than hard-code assumptions that may become outdated.

For a plain-language explanation of the payment flow, review How the 340B Rebate Model Works: A Guide for Covered Entities.

The Core 2027 Requirements for Covered Entities

1. Maintain current eligibility and compliance documentation

The rebate model does not eliminate the underlying requirements for covered entity eligibility, patient eligibility, outpatient status, diversion controls, or Medicaid duplicate-discount prevention.

Your entity should maintain an organized documentation package that includes:

Current 340B identification and registration information.
Eligible site and child-site records.
Pharmacy and dispensing-location information.
Policies for patient eligibility and outpatient dispensing.
Medicaid billing and carve-in or carve-out decisions.
Contract pharmacy arrangements, if applicable.
Purchasing-account and inventory controls.
Internal monitoring and corrective-action records.
Applicable manufacturer communications and approved rebate-plan materials.

This documentation is important even if eligibility information is not required for every rebate submission field. A manufacturer denial should not become a substitute for a formal HRSA audit or other compliance process. Your organization must be able to demonstrate that the underlying transaction was legitimate and properly controlled.

2. Capture complete claims-level data

The pilot framework limits the data that manufacturers may require. Current materials describe standardized fields for pharmacy and medical claims, including information such as:

Date of dispense or service.
NDC-11 or other applicable drug identifier.
Quantity or units.
Prescriber information.
Covered entity 340B identification.
Pharmacy benefit routing information, such as BIN and PCN, where applicable.
Claim or prescription identifiers.
Other fields necessary to validate the rebate request.

The exact fields may vary by claim type and approved manufacturer plan. Do not assume that a spreadsheet exported from your pharmacy system will automatically satisfy the final submission requirements.

Your IT and data teams should create a data dictionary that identifies:

Each required field.
The source system.
The data owner.
The validation rule.
The submission format.
The correction process when data is missing or inconsistent.

Tablet displaying integrated claims, inventory, and compliance analytics

3. Preserve pharmacy, purchase, and wholesaler records

Although current pilot materials limit the claims data manufacturers may request, your entity still needs pharmacy and purchasing records to support internal validation and reconciliation.

For affected drugs, retain records that connect:

Wholesaler order and invoice details.
WAC acquisition price.
NDC and package size.
Quantity purchased.
Date received.
Inventory movement.
Date dispensed or administered.
Quantity dispensed.
Claim submission.
Rebate approval, denial, and payment.

For an in-house pharmacy, this means your pharmacy management system, wholesaler reports, purchasing accounts, and general ledger must be able to communicate reliably.

For a contract pharmacy arrangement, you also need clear accountability between your entity, the contract pharmacy, TPA, claims platform, and any other intermediary. Your contract does not transfer your ultimate responsibility for oversight.

Review GapRx’s 340B contract pharmacy solutions if your organization needs stronger oversight, auditing, or network-level reporting.

4. Submit requests within the required timeframe

The current pilot framework generally provides 45 calendar days from dispense for a covered entity to submit the required rebate information.

That window can disappear quickly when claims are held for insurance corrections, reversed and rebilled, delayed by a TPA, or affected by missing prescriber or pharmacy data.

Your operating model should include:

A daily or near-daily submission schedule.
Aging reports for unsubmitted claims.
Alerts before the 45-day deadline.
Documented procedures for corrected claims.
Exception queues for incomplete records.
Escalation rules for vendor delays.
A process for documenting extenuating circumstances.

A monthly batch process may create unnecessary risk. The safer approach is to monitor the submission clock at the transaction level.

5. Prevent duplicate discounts

Duplicate-discount prevention remains a central 340B control. Your entity must continue to understand how affected claims interact with:

Medicaid rebates.
Medicaid managed care arrangements.
Medicare Drug Price Negotiation requirements.
Manufacturer rebate validation.
Internal payer and billing workflows.

Do not assume that a manufacturer’s platform will identify and solve every duplicate-discount issue. The platform may validate a claim for rebate processing, but your entity still needs documented policies, system edits, and monitoring.

Your compliance team should test whether Medicaid status, payer information, claim reversals, and resubmissions are consistently represented across the pharmacy system, TPA files, and rebate platform.

6. Track manufacturer validation, payments, and denials

A rebate submission should have a complete status history. At a minimum, your team should be able to identify status of each request.

The current framework contemplates manufacturer payment or documented denial within 10 calendar days after a complete submission. That timeline is useful, but it does not eliminate the need to monitor delays, partial payments, duplicate submissions, or unexplained denials.

A denial report without a reason code is not an adequate management tool. Your finance and compliance teams should know:

Why the claim was denied.
Whether the denial is correct.
Whether additional information can cure the issue.
Who owns the follow-up.
When the dispute must be escalated.
How the financial exposure is recorded.

Department-by-Department Preparation

Pharmacy leaders

Pharmacy leaders should map affected drugs to dispensing locations, wholesalers, inventory workflows, claim systems, and reversal processes. Confirm that staff understand the difference between the date of dispense, date of billing, and date of submission.

Finance and CFO teams

Finance should model the effect of purchasing at WAC before rebate receipt. Include drug volume, payment timing, expected denial rates, inventory levels, accounts receivable aging, and available working capital.

Read 340B Rebate Model Readiness: The Proven Framework for Managing Cash Flow Volatility for a broader cash-flow planning framework.

Compliance leaders

Compliance teams should update policies, test duplicate-discount controls, review documentation retention, and establish a recurring audit of claims, denials, payments, and exceptions.

GapRx’s HRSA Audit & 340B Compliance services can help covered entities build an audit-ready control environment.

IT and data teams

IT teams should validate interfaces, file formats, field mapping, data security, user access, and exception reporting. Do not wait for the manufacturer platform registration notice to discover that your systems cannot produce the required information.

Executive leadership

CEOs and boards should treat the rebate model as both a compliance initiative and a liquidity initiative. Establish ownership, approve contingency funding, and require regular reporting on expected rebates, paid rebates, denials, aging, and cash exposure.

Healthcare professional reviewing 340B financial and compliance dashboards

What Is Still Evolving?

Several details should not be presented as permanently settled:

The final list of manufacturers and drugs participating in the pilot.
Manufacturer-specific plan instructions.
Exact platform registration and onboarding procedures.
Final field-level implementation requirements.
Procedures for correcting or disputing denied requests.
The long-term future of the rebate model after the pilot.
The interaction between future legislation, HRSA guidance, and other drug-pricing policies.

Monitor HRSA’s 340B Model Pilot Program page and retain every manufacturer notice received by your organization.

A Practical Readiness Checklist

Before January 2027, your entity should be able to answer “yes” to these questions:

Have we identified affected drugs, manufacturers, pharmacies, and dispensing channels?
Can we produce the required claims-level data from source systems?
Can we submit complete requests within 45 days?
Do we have alerts for aging and approaching deadlines?
Can we match purchases, inventory, dispenses, claims, payments, and accounting entries?
Do we have documented duplicate-discount controls?
Can we track denials and escalate disputes?
Have we reviewed TPA and vendor service-level obligations?
Has finance modeled WAC purchasing and rebate timing?
Can leadership see the program’s financial and compliance status in one dashboard?

If the answer to several questions is “not yet,” your entity has a preparation gap: not necessarily a failure. The important step is to identify the gap early enough to correct it.

Final Takeaway

The 2027 340B rebate model requirements will place greater emphasis on claims accuracy, submission timeliness, manufacturer validation, payment tracking, reconciliation, and working-capital governance.

For FQHCs and other covered entities, readiness means building a controlled process from purchase through payment. Your organization should not rely on disconnected vendor reports, manual spreadsheets, or undocumented assumptions.

Contact GapRx to evaluate your rebate workflow, vendor oversight, financial exposure, and audit readiness before implementation. Learn how our 340B Rebate Model Solution can help your organization prepare, implement, and manage the transition with confidence.

2027 340B Rebate Model Requirements: What Covered Entities Need to Prepare