340B Split Billing Explained: How to Avoid the Most Common Audit Failure (2026)
340B compliance starts at the dispensing window. Photo: Unsplash
The 340B Drug Pricing Program saves covered entities billions of dollars annually. For Federally Qualified Health Centers (FQHCs), disproportionate share hospitals (DSH), and other safety-net providers, those savings fund clinical programs that would not otherwise exist. But the program comes with strict compliance requirements, and nothing trips up covered entities more consistently than split billing errors.
This guide breaks down how split billing works, where entities make mistakes, what HRSA looks for during audits, and how to build a system that holds up under scrutiny. Whether you run a single-site FQHC or a multi-location hospital outpatient pharmacy, the mechanics covered here apply directly to your operation.
For a broader look at how prescription pricing works outside the 340B context, RxGrab's guide on insurance vs. cash pricing covers the consumer side of the equation. For context on how supplements interact with the medications 340B pharmacies dispense, Health Britannica's berberine guide highlights the CYP enzyme interactions that pharmacists should be aware of. If you're evaluating the tax implications of your pharmacy operations as a business unit, CEOCult's healthcare business tax resources are worth reviewing.
What Is 340B Split Billing?
Split billing is the mechanism a covered entity uses to route each prescription to one of two inventory channels at the point of dispense:
- 340B channel: The prescription is filled using drugs purchased at the discounted 340B ceiling price. The entity captures the spread between 340B cost and the reimbursement amount (insurance payment, patient copay, or cash price).
- Non-340B (WAC/GPO) channel: The prescription is filled using drugs purchased at standard wholesale acquisition cost or through group purchasing organization contracts. No 340B discount is applied.
The split happens either physically (two separate inventories of the same drug) or virtually (a single inventory with software-based tracking that "replenishes" 340B stock after eligible dispenses). Most modern pharmacies use the virtual inventory model because maintaining two physical stocks of every NDC is impractical at scale.
Why split billing exists
The 340B statute (Section 340B of the Public Health Service Act) prohibits two things absolutely:
- Diversion: Dispensing 340B-purchased drugs to patients who are not eligible.
- Duplicate discounts: Receiving both a 340B discount and a Medicaid rebate on the same drug unit.
Split billing is the operational control that prevents both. If your split billing system cannot reliably distinguish eligible from ineligible patients at the point of dispense, you are structurally exposed to diversion findings. If it cannot flag Medicaid claims for exclusion from 340B purchasing, you are exposed to duplicate discount findings.
Every 340B transaction must be traceable back to a qualifying patient relationship. Photo: Unsplash
The Patient Definition: Where Most Entities Get It Wrong
HRSA's definition of a "340B-eligible patient" is narrower than most covered entities assume. According to HRSA's Patient Definition Final Notice (published in the Federal Register, 2007, and reinforced in subsequent guidance), a patient must meet all of the following criteria:
- The individual receives healthcare services from a provider who is either employed by or has a contractual arrangement with the covered entity.
- The individual receives a health care service or range of services from the covered entity that is consistent with the scope of services provided to other patients of the entity.
- The covered entity has established a relationship with the individual such that the covered entity maintains records of the individual's health care.
- The individual receives a prescription that is written by a provider who is part of the covered entity's scope of grant or other qualifying arrangement.
Read those requirements carefully. They exclude several patient categories that covered entities commonly (and incorrectly) route through the 340B channel:
- Emergency department patients at DSH hospitals who receive a prescription but have no ongoing relationship with the entity's outpatient services.
- Referral-only patients who see a specialist at the entity for a single consult but receive primary care elsewhere.
- Patients whose prescriptions are written by non-covered providers (e.g., a community physician who is not employed by or contracted with the covered entity).
- Discharged inpatients whose prescriptions are written as part of a discharge plan from an inpatient stay (inpatient prescriptions are not eligible for 340B outpatient pricing in most cases).
Split Billing Scenarios: Eligible vs. Ineligible
The following table covers the most common patient scenarios that 340B pharmacies encounter. Understanding these distinctions is the foundation of a compliant split billing system.
| Scenario | 340B Eligible? | Billing Channel | Why |
|---|---|---|---|
| FQHC patient with an active chart, Rx written by FQHC provider | Yes | 340B | Meets all four criteria of the patient definition |
| FQHC patient, active chart, Rx written by outside specialist (not contracted) | No | WAC/GPO | Prescriber is not part of the covered entity's scope |
| DSH hospital outpatient clinic patient, Rx from clinic provider | Yes | 340B | Outpatient encounter with covered provider qualifies |
| DSH hospital ED patient, Rx written at discharge, no follow-up scheduled | No | WAC/GPO | ED-only encounter typically does not establish the required relationship |
| Patient seen at a registered child site of the covered entity | Yes | 340B | Child sites are part of the covered entity's registered scope |
| Medicaid fee-for-service patient (state uses Medicaid exclusion file) | No* | WAC/GPO | Must bill at WAC to prevent duplicate discount (Medicaid rebate applies) |
| Medicaid managed care patient (state carves out 340B) | Yes* | 340B | If the MCO contract permits and the state has carved out 340B, eligible |
| Uninsured patient, active chart, Rx from entity provider | Yes | 340B | Insurance status does not determine 340B eligibility |
| Walk-in patient filling a prescription from an outside provider, no chart | No | WAC/GPO | No established relationship, prescriber not part of covered entity |
| Contract pharmacy fill for an eligible patient with valid referral | Yes | 340B | Contract pharmacy fills are eligible if patient meets definition |
*Medicaid eligibility for 340B varies by state and by whether the state uses fee-for-service or managed care. Always verify your state's specific policy and exclusion file requirements.
The Five Most Common Split Billing Mistakes
HRSA audit findings cluster around a handful of recurring errors. Every one of these is preventable with the right systems and training.
1. Defaulting all prescriptions to the 340B bucket
Some entities configure their pharmacy system to route all prescriptions through 340B unless manually overridden. This "opt-out" approach is the fastest path to an audit finding. The correct model is "opt-in": a prescription should only enter the 340B channel after the system confirms the patient meets the eligibility criteria. If eligibility cannot be confirmed at the point of dispense, the prescription defaults to the non-340B channel.
2. Not verifying the prescriber's relationship to the covered entity
Patient eligibility is necessary but not sufficient. The prescriber must also be part of the covered entity's workforce or have a qualifying contractual arrangement. An FQHC patient who sees their own doctor at the FQHC for primary care but gets a prescription from an outside dermatologist cannot route that prescription through 340B, even though the patient has an active chart at the FQHC.
Maintaining an up-to-date provider roster that your pharmacy system can check against in real time is essential. When providers leave the entity or new providers join, the roster must be updated immediately. Stale rosters are a common source of audit findings.
3. Ignoring the Medicaid exclusion file
The 340B statute explicitly prohibits "duplicate discounts": receiving both a 340B drug price and a Medicaid drug rebate on the same unit. To prevent this, HRSA and CMS require covered entities to use the Medicaid exclusion file. When a Medicaid fee-for-service patient fills a prescription, the entity must bill that claim at the non-340B price so the state can collect the manufacturer rebate. If the entity uses 340B pricing on a Medicaid FFS claim, the manufacturer pays the discount twice.
The complexity increases with Medicaid managed care. Whether 340B pricing applies to Medicaid MCO patients depends on state-level carve-in/carve-out decisions and the specific MCO contract terms. Some states allow covered entities to use 340B for Medicaid MCO patients; others do not. If your entity operates in multiple states, you need state-by-state rules built into your split billing logic.
4. Failing to document the qualifying encounter
HRSA auditors do not just check that a patient has a chart at the covered entity. They verify that the patient had a qualifying encounter within a reasonable timeframe relative to when the prescription was filled. The definition of "reasonable timeframe" is not precisely specified in HRSA guidance, which is why this becomes such a frequent audit discussion point.
Best practice: tie 340B eligibility to a documented outpatient encounter within the past 12 months. Some entities use tighter windows (6 months) for extra protection. The key is consistency. Whatever window you choose, apply it uniformly and be able to demonstrate that policy in writing if audited.
5. Inadequate contract pharmacy oversight
Contract pharmacies fill 340B prescriptions on behalf of the covered entity, but the covered entity retains full responsibility for compliance. Many entities sign contract pharmacy agreements and then rely entirely on the contract pharmacy's systems to make eligibility determinations. This is a structural risk.
The covered entity must independently verify that the contract pharmacy is correctly identifying eligible patients, properly segregating or replenishing 340B inventory, and submitting accurate claims data. Most entities that have lost 340B eligibility in recent years had significant contract pharmacy compliance gaps.
Virtual inventory models require software that tracks every unit from purchase to dispense. Photo: Unsplash
What HRSA Looks For During a 340B Audit
HRSA audits follow a structured process. Understanding the audit methodology helps you build your compliance program around the same framework auditors use to evaluate you.
Pre-audit data request
Before the on-site visit, HRSA requests a standard data package that includes:
- 340B covered entity registration information and all child sites
- List of all contract pharmacies with agreement dates
- Provider roster (all prescribers authorized to write 340B-eligible prescriptions)
- Sample of 340B claims for a specified time period (typically 30-90 days)
- Split billing methodology documentation
- Medicaid exclusion file processes and evidence of implementation
- Policies and procedures for 340B compliance
On-site review
During the on-site audit, HRSA reviewers pull individual claims from the sample and trace them end-to-end:
- Patient verification: Is this patient in the covered entity's medical records? When was their last qualifying encounter?
- Prescriber verification: Is the prescriber on the entity's provider roster? Were they on the roster at the time the prescription was written?
- Drug verification: Was the dispensed drug purchased at 340B pricing? Can the entity produce the 340B purchase order or virtual inventory record?
- Payer verification: If the claim was billed to Medicaid FFS, was the entity using 340B pricing (which would indicate a duplicate discount)?
- Contract pharmacy verification: If dispensed at a contract pharmacy, did the covered entity have a valid agreement in place? Can the entity demonstrate oversight of the contract pharmacy's eligibility process?
Common audit outcomes
HRSA categorizes findings into three tiers:
- No findings: The entity's 340B program is compliant. No corrective action required.
- Findings with corrective action plan (CAP): HRSA identifies specific compliance gaps and requires the entity to submit a plan to address them within a defined timeframe. Most audits with findings result in CAPs.
- Removal from the program: Reserved for systematic or egregious violations. Rare but not theoretical. Entities that have been removed typically had widespread diversion, no split billing controls, or repeated failure to comply with prior CAPs.
Building an Audit-Proof Split Billing System
The difference between entities that pass audits cleanly and those that receive findings usually comes down to system architecture, not intent. Almost every covered entity wants to be compliant. The ones that fail are the ones whose systems cannot prove compliance at the individual claim level.
Required components
- Real-time patient eligibility verification: At the point of dispense, the system must check whether the patient has an active relationship with the covered entity and a qualifying encounter within your defined timeframe. This cannot be a batch process that runs overnight. It must happen before the prescription is filled.
- Provider roster integration: The pharmacy system must cross-reference the prescribing provider against the entity's current roster. If the prescriber is not on the roster, the claim routes to non-340B automatically.
- Medicaid exclusion logic: The system must identify Medicaid FFS claims and route them to the non-340B channel. For Medicaid MCO claims, the system must apply state-specific rules.
- Audit trail at the claim level: Every routing decision (340B or non-340B) must be logged with the data that supported the decision: patient ID, encounter date, prescriber ID, payer type, and timestamp. If an auditor asks why a specific claim was routed to 340B, you need to produce the answer in minutes, not days.
- Contract pharmacy data feeds: If you use contract pharmacies, your system must ingest their claims data and apply the same eligibility logic. You cannot rely on the contract pharmacy to make this determination independently.
Virtual inventory vs. physical inventory
Most covered entities use the virtual inventory (also called "replenishment") model. Here is how each approach works:
Physical inventory model: The pharmacy maintains two separate stocks of the same drug. One stock is purchased at 340B pricing, the other at WAC/GPO. When filling a prescription, the pharmacist physically pulls from the appropriate stock. This provides clean separation but creates significant operational burden: double storage, double ordering, double expiration tracking, and constant risk of accidentally pulling from the wrong bin.
Virtual inventory model: The pharmacy maintains a single stock of each drug (purchased at WAC/GPO). After dispensing a prescription to an eligible 340B patient, the system generates a "replenishment" order that replaces the dispensed unit at the 340B price. The entity captures the price difference. This model is simpler operationally but requires software that accurately tracks every unit from purchase through dispense and replenishment.
The virtual model is the industry standard for good reason: it eliminates physical inventory errors, reduces waste from expired 340B stock, and scales better across multiple locations. But it absolutely requires a software system that can handle the tracking. Spreadsheet-based virtual inventory is a contradiction in terms.
State-Level Variations That Affect Split Billing
340B is a federal program, but several aspects of split billing are governed by state law and state Medicaid agency decisions. The most impactful variations:
- Medicaid carve-in vs. carve-out: Some states "carve in" 340B to their Medicaid managed care contracts, meaning MCOs pay 340B-level reimbursement and no manufacturer rebate is collected. Other states "carve out" 340B, allowing covered entities to use 340B pricing on MCO claims while the state collects the rebate separately. Your split billing system must know which model your state uses.
- State supplemental rebate programs: Some states collect supplemental drug rebates beyond the federal Medicaid rebate. These supplemental programs can create additional duplicate discount exposure if your split billing system does not account for them.
- Contract pharmacy restrictions: Several states have enacted laws limiting or regulating contract pharmacy arrangements. These laws can affect which contract pharmacy claims are eligible for 340B pricing.
- State audit programs: Beyond HRSA, some state Medicaid agencies conduct their own audits focused on duplicate discount prevention. Your split billing documentation must satisfy both federal and state reviewers.
Manufacturer Restrictions and Their Impact on Split Billing
Since 2020, multiple drug manufacturers have imposed restrictions on 340B pricing for contract pharmacy arrangements. As of 2026, over 30 manufacturers limit or deny 340B pricing on drugs dispensed through contract pharmacies unless the covered entity provides claims-level data to the manufacturer or a designated third-party administrator (TPA).
These restrictions complicate split billing because they create a third pricing tier: drugs that would be eligible for 340B pricing based on patient eligibility but are not available at 340B pricing because the manufacturer refuses to honor the discount at contract pharmacies. Your split billing system must track which manufacturers have restrictions, which drugs are affected, and whether your entity has submitted the required data to restore pricing for each manufacturer.
HRSA has stated that these manufacturer restrictions violate the 340B statute, but enforcement has been slow. In the meantime, covered entities bear the operational burden of tracking manufacturer-specific rules alongside patient eligibility rules.
Self-Audit Checklist: 10 Questions to Ask Before HRSA Does
Run through this checklist quarterly. If you cannot answer "yes" to every item with documentation to back it up, you have work to do.
- Can your pharmacy system demonstrate, for any individual claim, why it was routed to the 340B channel (patient eligibility, prescriber verification, encounter date)?
- Is your provider roster current as of today? When was it last updated?
- Does your split billing system default to non-340B when eligibility cannot be confirmed?
- Are Medicaid fee-for-service claims excluded from 340B purchasing?
- Do you have written policies for 340B patient eligibility, and are pharmacy staff trained on them?
- For contract pharmacies: can you produce the contract agreement, and do you receive and review claims data from every contract pharmacy?
- Is your 340B database (OPAIS) registration accurate? Are all child sites listed? Are terminated sites removed?
- Can you produce a 340B utilization report broken down by provider, payer type, and location within one business day?
- Do you have a process for handling manufacturer restrictions on contract pharmacy 340B pricing?
- Have you conducted an internal compliance review in the past 12 months with documented findings and corrective actions?