Free webinar: From Discount to Rebate · Thu, Nov 5 · 3:30 PM ETRegister
Aventi Health logo
Book a Demo
340B TPA basics

What does a 340B TPA do?

A 340B third-party administrator (TPA) helps a covered entity run the operational side of its 340B program—qualifying claims, tracking virtual inventory and replenishment, supporting contract pharmacy and split billing, and producing the reports and records used for oversight—while the covered entity remains responsible for compliance.[4][3][8]

This page explains the main TPA jobs in plain language, what HRSA still expects of the covered entity, and how Aventi Health, an independent 340B TPA serving 300 covered entities, 24 of them hospitals, approaches the work.

Last updated: . Claims about HRSA rules and industry practice link to public sources below.

See the demo Compare 340B TPAsSee what a TPA does
Core jobs

What a 340B TPA typically does

Industry definitions converge on the same operational stack: qualify claims, manage inventory and replenishment, support pharmacies, and keep records the covered entity can defend.

  • Eligibility matching

    Match prescriptions and medical utilization to eligible 340B encounters using data from the covered entity’s EHR, pharmacy and billing systems—so the patient, provider and site meet program rules before a dispense is treated as 340B.[4][8]

  • Virtual inventory, accumulation and replenishment

    Track 340B-eligible units separately from non-340B stock (often without a second physical inventory), accumulate quantities by NDC until a package can be replenished, and coordinate replenishment orders with the pharmacy and wholesaler.[6][8][5]

  • Contract pharmacy workflows

    Sit between the covered entity and its registered contract pharmacies: move claim and dispense data, support network operations, and help the entity retain the records HRSA expects for oversight. The covered entity still needs a written contract and an active OPAIS listing before 340B dispensing begins.[1][3][8]

  • Split billing for in-house and mixed-use pharmacies

    Separate eligible outpatient utilization from inpatient or otherwise ineligible utilization so replenishment hits the right account—340B, GPO or WAC. Hospitals commonly rely on TPA split-billing software for this in mixed-use settings.[6][5]

  • Reporting and audit readiness

    Produce reports and transaction histories used for internal reconciliation, Medicaid duplicate-discount controls, manufacturer data requests and HRSA audits. HRSA expects covered entities to maintain fully auditable records and to oversee contract pharmacy arrangements.[2][1][5]

  • Newer rebate and ESP claims roles

    Help prepare and submit claims-level data for manufacturer platforms such as 340B ESP and, under HRSA’s 340B Rebate Model Pilot starting January 1, 2027, rebate submissions for selected drugs. The covered entity remains responsible for the submissions and for program integrity.[7][5][9]

In practice

How those TPA jobs fit together

Day to day, a TPA is the technology and reporting layer between the covered entity, its pharmacies and, often, the wholesaler.[8][5] A dispense or charge posts; the TPA’s qualification engine checks whether that utilization is 340B-eligible; eligible units move into an accumulator; when enough quantity exists, a replenishment order is placed on the covered entity’s 340B account (or, under a rebate model for selected drugs, related claims data is prepared for submission).[6][7][8]

For contract pharmacy, HRSA’s framework is separate from the TPA product. The covered entity must have a written contract that lists participating pharmacy locations, register each pharmacy in 340B OPAIS and wait until the pharmacy shows as active before 340B dispensing, oversee the arrangement, keep records HRSA can audit, and self-disclose problems.[1][3] The TPA supports data flow and tracking; it does not replace those entity duties.

For hospital mixed-use pharmacies, split-billing software assigns outpatient-eligible utilization toward 340B replenishment and routes inpatient or ineligible utilization to GPO or WAC accounts, which is why virtual inventory and NDC-level accumulation are central features of modern 340B software.[6]

Non-negotiable

The covered entity remains responsible for compliance

HRSA holds the covered entity accountable—not the TPA—even when a vendor runs the software.

  • HRSA’s 2010 contract pharmacy notice states that use of a contract pharmacy does not lessen a covered entity’s duty to administer 340B in compliance with the statute and guidelines, and that the covered entity bears full responsibility and accountability for preventing diversion and duplicate discounts.[3]
  • HRSA’s current contract pharmacy page requires covered entities to oversee contract pharmacies, use an independent audit firm at least annually, maintain auditable records, and report non-compliance with a corrective plan.[1]
  • HRSA recommends quarterly internal audits, written policies and procedures for oversight (including review of the patient eligibility system), and reconciliation of dispensing, purchasing and billing records.[2]
  • Vendor FAQs and industry explainers make the same point in operational language: a TPA supports administration; program compliance responsibility remains with the covered entity.[4][8]

Practical takeaway: choose a TPA for the quality of its qualification logic, pharmacy integrations, reporting and audit trail—and keep your own policies, reconciliations and independent audits strong enough that you can defend the program if HRSA asks.

How Aventi helps

An independent 340B TPA built for operations and 2027 rebates

  • Independent and founder-owned

    Aventi is not owned by a wholesaler, PBM or pharmacy chain. We answer to covered entity clients.

  • Contract pharmacy + split billing together

    One platform for contract pharmacy and in-house/mixed-use split billing, with contingency-based pricing and no true-ups.

  • Scale that matches real programs

    Aventi serves 300 covered entities, 24 of them hospitals, with a 10,000+ pharmacy network and specialty gateways including BioPlus, Accredo, Optum and many other specialty pharmacies.

  • Rebate module: Included for Aventi TPA clients

    Pharmacy and medical rebate claim preparation for the 2027 HRSA rebate model, plus 340B ESP and Truzo support, is Included for Aventi TPA clients. Covered entities that keep another TPA can still use Aventi for rebate claims—contact us for pricing.

Compare ownership, services and public rebate readiness on our 340B TPA comparison, or see Aventi for covered entities.

FAQ

340B TPA questions, answered

TPA stands for third-party administrator. In 340B, a TPA is a vendor that helps a covered entity manage program operations such as claims qualification, inventory and replenishment, contract pharmacy workflows, split billing, reporting and audit support. Industry research notes that people in 340B often use “TPA” specifically for billing and inventory management software, even though firms also offer broader services.

No. HRSA does not require covered entities to hire a TPA. Contract pharmacy arrangements are voluntary, and each covered entity decides how to meet program requirements. Many entities use a TPA because contract pharmacy networks, mixed-use pharmacies and manufacturer data requests make day-to-day administration hard to run by hand.

The covered entity. HRSA’s contract pharmacy guidance states that using a contract pharmacy does not lessen the covered entity’s duty to prevent diversion and duplicate discounts, and that the covered entity bears full responsibility and accountability. A TPA can supply tools and records; HRSA still holds the covered entity accountable.

Virtual inventory is a software approach that lets a pharmacy keep one physical stock while the TPA tracks which dispenses are 340B-eligible and which are not. Eligible units accumulate until enough quantity exists to replenish at 340B pricing. Split-billing software uses the same idea in hospital mixed-use pharmacies to separate 340B, GPO and WAC replenishment.

A TPA typically sits between the covered entity and its registered contract pharmacies: matching prescriptions to eligible encounters, tracking accumulators, coordinating replenishment with the wholesaler, supporting fee and revenue reporting, and retaining records the covered entity needs for oversight. HRSA still requires the covered entity to have a written contract, register each pharmacy in OPAIS, oversee the arrangement and maintain auditable records.

Split billing separates eligible outpatient utilization from inpatient or otherwise ineligible utilization so replenishment orders go to the correct wholesaler account—340B, GPO or WAC. Hospitals commonly use TPA split-billing software in mixed-use pharmacies to automate that separation and keep an audit trail.

Many do. Under HRSA’s 340B Rebate Model Pilot, covered entities submit claims-level data for selected drugs so manufacturers can pay rebates that effectuate the 340B ceiling price. Industry research also found that some TPAs assist with 340B ESP claims submissions tied to manufacturer contract-pharmacy restrictions. The covered entity remains responsible for the submissions and for program compliance.

Aventi Health is an independent, founder-owned 340B TPA serving 300 covered entities, 24 of them hospitals. Contract pharmacy and split billing run on one contingency-based platform with no true-ups, and the rebate module is Included for Aventi TPA clients. See aventihealth.com/340b-tpa-comparison for a sourced side-by-side with other TPAs.

Sources

  1. HRSA, Contract Pharmacy Services — https://www.hrsa.gov/opa/implementation-contract
  2. HRSA, 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
  3. Federal Register, Notice Regarding 340B Drug Pricing Program—Contract Pharmacy Services (75 FR 10272, March 5, 2010) — https://www.federalregister.gov/documents/2010/03/05/2010-4755/notice-regarding-340b-drug-pricing-program-contract-pharmacy-services
  4. Omnicell, "What is a 340B TPA?" (340B TPA FAQ) — https://www.omnicell.com/specialty-pharmacy/340b-tpa/
  5. Health Affairs Scholar / PMC, Growing administrative complexity in the 340B program and the rise of third-party administrators (PMC10986201) — https://pmc.ncbi.nlm.nih.gov/articles/PMC10986201/
  6. The Craneware Group, Key Features to Look For in 340B Split-Billing Software Solutions (2025) — https://www.thecranewaregroup.com/news-events/news-insights/2025/key-features-to-look-for-in-340b-split-billing-software-solutions/
  7. HRSA, 340B Rebate Model Pilot Program — https://www.hrsa.gov/opa/340b-model-pilot-program
  8. RxTrail, "What Should a TPA Do in 340B?" (February 12, 2026) — https://www.rxtrail.com/post/what-should-a-tpa-do-in-340b
  9. Aventi Health, 340B Rebate Model — https://aventihealth.com/340b-rebate-model
  10. Aventi Health, 340B TPA Comparison — https://aventihealth.com/340b-tpa-comparison

Accessed November 5, 2026.

Related pages

See what a modern 340B TPA looks like in practice

Walk through eligibility, contract pharmacy, split billing and rebate claims in one system—before you renew with your current vendor.

See the demo Get a Free 340B Assessment

Return to Aventi Health homeCompare 340B TPAs340B TPA for covered entities