See the Aventi 340B Rebate Model Demo.
340B TPA FAQ

What is virtual inventory in 340B?

Virtual inventory is a way to run 340B without keeping a separate shelf of 340B drugs. The pharmacy dispenses from its regular stock, software checks afterward which uses were for 340B-eligible patients, and those units are tallied by drug and package size. When eligible use adds up to a full package, the covered entity reorders that exact product at the 340B price, and the new stock simply refills the shelf. The 340B inventory is “virtual” because it exists as a running balance in the records, not as separate bottles. HRSA has described replenishment models as permissible as long as every 340B order traces back to earlier use by eligible patients.[1][3]

In one line

Buy at a regular price → dispense → accumulate eligible use → replenish at the 340B price.

The replenishment loop

Four steps, repeated every day

The 340B price shows up on the reorder, not on the drug that was given to the patient.

  1. 1

    Stock the shelf at a non-340B price

    A virtual inventory starts with neutral stock bought on a regular account (for hospitals subject to the GPO prohibition, typically WAC). Nothing on the shelf is labeled 340B.[5][11]

  2. 2

    Dispense or administer

    Patients get the drug from that one shared inventory. Whether a given use counts as 340B is decided after the fact, from the claim or charge and the encounter behind it.[1]

  3. 3

    Qualify and accumulate

    Software applies your eligibility rules and adds each qualifying unit to a balance for that drug and package. Ineligible and inpatient use goes to other accounts.[1][10]

  4. 4

    Replenish at the 340B price

    Once the 340B balance equals an available package size, a 340B order is placed and the balance is drawn down. On arrival the drug loses its identity and is just stock again.[1]

HRSA’s own short definition: replenishment is “a process by which a covered entity reorders drug inventory based on actual prior drug usage.” For the account-by-account mechanics in a hospital, see 340B accumulators and split billing.[1]

Choosing a model

Physical vs. virtual 340B inventory

The two can be combined: a separate physical stock in one setting and a virtual inventory in another. Apexus training calls this a hybrid model.

Physical (separate) inventoryVirtual (replenishment) inventory
What sits on the shelf340B drugs kept apart from other stock, in their own bins or a separate location.One shared inventory. 340B status lives in the accumulator balance, not on the bottle.[1][10]
When 340B status is decidedBefore dispensing: staff pick from the 340B stock for an eligible patient.After dispensing: the use is qualified, then accumulated toward a 340B reorder.[1]
Where it fitsSettings where 340B stock can be kept apart and dispensed only to patients already known to be eligible.Mixed-use hospital areas and most contract pharmacies, where patient status isn’t known at the shelf.[4][10]
Start-upBuy 340B stock up front for expected eligible use.Buy neutral stock on a regular account first; 340B purchases only follow eligible use.[5][11]
Main compliance risk340B units given to an ineligible patient, or physical counts that don’t match records.Units accumulated that shouldn’t have been, or 340B orders larger than the eligible balance.[1][8]
What proves itDispensing logs and periodic physical counts tied to 340B invoices.Claim-level accumulation records tied to each 340B purchase, NDC by NDC.[1][7]

Either way, HRSA’s proposed 2015 guidance treated a gap between the recorded and actual number of 340B drugs as a potential diversion problem, whether the entity kept a virtual or a separate physical inventory.[1][13]

Contract pharmacy

The same idea, across two companies

At a contract pharmacy, eligibility depends on your prescribers, locations and patient records, so the claim is qualified after it’s filled and the 340B purchase follows.

Pharmacy fills from its own stock

The contract pharmacy dispenses the prescription and bills the payer as usual.

TPA qualifies the claim

The claim is matched to your eligible prescribers and locations and, if it qualifies, accumulated for that pharmacy.

Order on your account

When a package is reached, a 340B order is placed in the covered entity’s name. The wholesaler bills the covered entity.

Shipped to the pharmacy

The replacement ships straight to the pharmacy and refills its shelf. That’s the ship-to, bill-to arrangement.

HRSA’s 2010 guidance says the covered entity purchases the drug, keeps title and sets its price, and that the manufacturer or wholesaler bills the covered entity but ships directly to the contract pharmacy. It also says inventory and record segregation is one of many methods to stay compliant, and that HRSA doesn’t intend to limit the methods entities use.[3]

HRSA recommends reconciling dispensing, purchasing and billing records as part of contract pharmacy oversight. See how contract pharmacy setup works with a TPA.[6]

Reading a balance

The four states of a virtual inventory balance

Every drug, package and account has a running balance. Here’s what each state means for savings and for compliance.

Accumulating

Eligible units are building but haven’t reached a full package. Nothing can be ordered at the 340B price yet. HRSA’s sample audit request still counts these units in your 340B universe.[1][7]

Ready to order

The balance covers at least one package of that exact product. A 340B order can be placed, and whatever is left over carries forward.[1]

Unreplenished and aging

Eligible use that never turns into an order, often slow movers or partial packages. It means savings you aren’t capturing, and the units still sit in your 340B universe with records to support them. Re-labeling old purchases as 340B after the fact (“banking”) is a different practice HRSA cautioned against.[1][7][11]

Negative (over-replenished)

More was bought at the 340B price than eligible use supports. This usually surfaces after a correction wipes out accumulations that were already ordered against, and it needs a fix with the wholesaler or the manufacturer.[8][9]

HRSA’s 2015 proposal also said that accumulating a unit that shouldn’t count is a problem even before any order is placed, and that entities should return unused or expired 340B drugs and account for waste, backed by written procedures for reconciling discrepancies.[1]

Where balances go wrong

Common causes, and the four ways to fix them

Causes

  • Unit and package conversion

    In one Apexus case study, an EHR charge-mapping change recorded each dose from a multi-dose vial as a full package, inflating accumulations until 340B purchases outran eligibility.[8]

  • NDC changes and shortages

    Replenishment is matched on the product actually used. When buyers switch NDCs or vial sizes during a shortage, the accumulator has to be updated or balances drift.[8][10]

  • Reversals and eligibility errors

    Reversed claims and bad eligibility data sent to the 340B vendor are common sources of ineligible 340B purchases.[9]

  • Lost charges and waste

    If a use never generates a charge, or waste isn’t accumulated, the replacement gets bought on a higher-priced account instead of 340B.[11]

  • Manual adjustments

    Hand edits to balances are sometimes needed, but each one should be documented so the purchase trail still holds up.[8][10]

Fixes

  1. 1
    Return it

    If caught early, the 340B product may be returned to the wholesaler and repurchased at a non-340B price. Return windows are usually shorter than credit-and-rebill windows.[8][9]

  2. 2
    Credit and rebill

    The wholesaler reprices the purchase to a non-340B account, typically only within about 3 to 6 months of the purchase date.[8][9]

  3. 3
    Repay the manufacturer

    When a return or rebill isn’t possible, the covered entity repays affected manufacturers directly. HRSA expects diversion-related noncompliance to be resolved with manufacturers even when it isn’t a material breach.[9][14]

  4. 4
    Decide on disclosure

    Check the issue against the material breach threshold in your policies; if it meets it, HRSA’s self-disclosure process applies. Either way, document the cause, the fix and the affected purchases.[8][14]

In the Apexus case study, one charge-mapping error touched 30 NDCs and left 23 with negative balances; the team returned 7, rebilled 10 and repaid manufacturers directly for 6.[8]

In an audit

What HRSA asks about virtual inventory

  • Item H of the data request: how you account for 340B inventory, physical or virtual replenishment.[7]
  • A 340B universe that includes every accumulation designated as 340B, replenished or not.[7]
  • Claim-level fields for each use, including the NDC, quantity and the account it was purchased on.[7]
  • Someone who can navigate the split-billing or third-party software during testing.[7]

The statute requires covered entities to let HRSA and manufacturers audit records that pertain to diversion and duplicate discounts, so the accumulator history is part of your compliance file. For the full audit process, see how to prepare for a HRSA 340B audit.[13]

HRSA guidance

What HRSA has said about replenishment, and what still applies

  1. 2010
    Contract pharmacy notice

    Sets the ship-to, bill-to arrangement and says inventory and record segregation is only one of many acceptable methods. HRSA does not limit how entities stay compliant.[3]

  2. 2013
    GPO prohibition release 2013-1

    Said a hospital subject to the GPO prohibition that orders on actual prior usage can’t tally 340B-ineligible outpatient use for orders on a GPO account. A federal court vacated it on March 31, 2026, and HRSA’s policy page now marks it vacated.[1][12]

  3. 2015
    Proposed omnibus guidance

    Described replenishment models in the most detail HRSA has published: order only on actual prior eligible use, package-size reorders, auditable records for every 340B order. It was withdrawn in January 2017 and never finalized.[1][2]

  4. Ongoing
    HRSA FAQs

    Hospitals need a tracking system to use 340B in mixed-use areas, auditable records of what accumulated where, and a non-GPO account for when a 340B product isn’t available.[4][5]

  5. Today
    Audit data request

    HRSA’s audit data request asks whether you use physical or virtual inventory and includes unreplenished accumulations in the 340B universe.[7]

The 2015 proposal is cited here only for how HRSA described replenishment; it isn’t binding. The statute’s ban on transferring 340B drugs to non-patients is what makes an unsupported 340B order a diversion problem.[2][13]

How Aventi helps

Virtual inventory you can see and defend

Real-time capture and splitting

Claims are captured and purchases split as they happen, so balances stay current and there are no end-of-month true-ups.

Audit-ready by default

Claim-level history behind every replenishment, duplicate discount monitoring and a dedicated account manager when an auditor asks for your 340B universe. See the reports a TPA should provide.

Contract pharmacy and split billing

We run contract pharmacy and split billing for 300 covered entities, 24 of them hospitals, across a network of 10,000+ pharmacies.

Ready for 2027 rebates

The rebate module is Included for Aventi TPA clients, with real-time 340B ESP and Truzo (Kalderos) integration. Learn about the 2027 340B rebate model.

FAQ

340B virtual inventory: common questions

Yes. HRSA has described replenishment models as permissible as long as the covered entity stays compliant with all 340B requirements, and its contract pharmacy guidance says it doesn’t limit the methods entities use. The condition is that every 340B order is backed by auditable records of earlier use by eligible patients.[1][3]

A physical inventory keeps 340B drugs on their own shelf and decides eligibility before dispensing. A virtual inventory uses one shared stock, decides eligibility after the fact, and reorders at the 340B price once eligible use adds up to a full package. Some programs run a hybrid of the two.[1][10]

There has to be stock on the shelf before any eligible use can accumulate, so the first purchases are made on a non-340B account. For hospitals subject to the GPO prohibition that has typically meant WAC, and HRSA expects a non-GPO account to be available when a 340B product isn’t.[5][11]

Yes. HRSA’s sample audit data request says that for virtual inventory, the 340B universe includes all accumulations designated as 340B, whatever their replenishment status. Auditors may also ask someone to walk them through the split-billing or third-party software.[7]

It means more product was bought at the 340B price than the eligible balance supports, usually found after a correction removes accumulations that were already ordered against. The fix is a return, a credit and rebill with the wholesaler, or direct repayment to the manufacturer.[8][9]

Replenishment is meant to replace the product that was actually used, so split-billing systems are loaded and matched by 11-digit NDC, which identifies the manufacturer, product and package size. When an exact match isn’t possible, document why and what was done.[1][7][10]

The pharmacy fills prescriptions from its own stock. The TPA identifies eligible claims and accumulates them, then 340B replenishment is ordered on the covered entity’s account, billed to the covered entity and shipped to the pharmacy under the ship-to, bill-to arrangement in HRSA’s 2010 guidance.[3]

HRSA recommends quarterly internal audits and annual independent audits of contract pharmacies, including reconciliation of dispensing, purchasing and billing records. Reviewing accumulator exceptions more often helps catch problems while wholesaler return and rebill windows are still open.[6][9]

Sources

  1. Federal Register, 340B Drug Pricing Program Omnibus Guidance (proposed), 80 FR 52300 (Aug. 28, 2015), Drug Inventory/Replenishment Models and Part C sections — https://www.federalregister.gov/documents/2015/08/28/2015-21246/340b-drug-pricing-program-omnibus-guidance
  2. OIRA (reginfo.gov), 340B Program Omnibus Guidelines, RIN 0906-AB08, concluded action: withdrawn (Jan. 30, 2017) — https://www.reginfo.gov/public/do/eoDetails?rrid=126712
  3. Federal Register, Notice Regarding 340B Drug Pricing Program—Contract Pharmacy Services, 75 FR 10272 (Mar. 5, 2010), comment responses and essential element (a) — https://www.federalregister.gov/documents/2010/03/05/2010-4755/notice-regarding-340b-drug-pricing-program-contract-pharmacy-services
  4. HRSA FAQ, May a hospital use 340B-priced drugs in “mixed-use” settings … if the hospital cannot track which drugs are used for inpatients and which ones are used for outpatients? — https://www.hrsa.gov/about/faqs/may-hospital-use-340b-priced-drugs-mixed-use-settings-such-surgery-department-where-both-inpatients
  5. HRSA FAQ, Our mixed-use area has only inpatients or 340B eligible outpatients … is it required to start with a WAC inventory? — https://www.hrsa.gov/about/faqs/our-mixed-use-area-has-only-inpatients-or-340b-eligible-outpatients-we-do-not-have-any-340b
  6. HRSA FAQ, What are the audit and compliance parameters under the contract pharmacy guidelines? — https://www.hrsa.gov/about/faqs/what-are-audit-compliance-parameters-under-contract-pharmacy-guidelines
  7. 340B Prime Vendor Program (Apexus), Sample HRSA 340B Audit Data Request List for Covered Entities (item H and 340B universe instructions) — https://www.340bpvp.com/Documents/Public/340B%20Tools/sample-hrsa-340b-audit-data-request-for-covered-entities.pdf
  8. Apexus, Case study: Fixing 340B Inventory Errors Due to EHR Billing Corrections — https://www.apexus.com/about-us/articles-and-updates/fixing-340b-inventory-errors-due-to-ehr-billing-corrections
  9. Apexus, Expert Tip: Resolve Negative 340B Accumulations (published in 340B Report, Nov. 30, 2023) — https://www.apexus.com/about-us/articles-and-updates/expert-tip-resolve-negative-340b-accumulations
  10. Apexus, 340B Certificate Program Curriculum (Replenishment and Separate Physical Inventory Models; Split-Billing Software Maintenance and Compliance; Contract Pharmacy Inventory Management) — https://www.apexus.com/340b-certificate-program/resources/program-curriculum
  11. Pharmacy Times, Minimizing WAC Exposure to Decrease Drug Expense in the Virtual Inventory Setting — https://www.pharmacytimes.com/view/minimizing-wac-exposure-to-decrease-drug-expense-in-the-virtual-inventory-setting
  12. HRSA, 340B Policy Releases (Release 2013-1 marked vacated by Premier, Inc. v. HRSA, No. 24-cv-3116, D.D.C. Mar. 31, 2026) — https://www.hrsa.gov/opa/program-requirements/policy-releases
  13. 42 U.S.C. § 256b(a)(5)(B)–(C) (diversion; auditable records) (Cornell LII) — https://www.law.cornell.edu/uscode/text/42/256b
  14. HRSA Office of Pharmacy Affairs, Program Integrity (self-disclosure, corrective action, manufacturer repayment) — https://www.hrsa.gov/opa/program-integrity

Last updated November 19, 2026. This page is general information, not legal advice. Check HRSA’s current guidance and your own counsel for your program.