How to Choose a 340B TPA, and How to Audit the One You Already Have

If you're working out how to choose a 340B TPA, the per-claim fee on the proposal is the least interesting number in front of you. A third-party administrator sits between your claims data and your contract pharmacy network, and it decides, thousands of times a month, which prescriptions qualify for 340B pricing. Ask most compliance officers why the system accepted one prescription and rejected another, and the answer gets vague quickly. That gap, between what the TPA does and what the covered entity actually understands about how it does it, is where missed savings and HRSA audit findings quietly pile up every year.

This guide covers both sides of the problem. First, what to test before you sign with a new vendor. Second, how to run a 340B TPA audit on the administrator you already have. It's written for compliance officers, pharmacy directors and 340B program managers at hospitals, health centers, Ryan White clinics and infusion centers across the U.S., and it stays vendor-neutral, because the right answer depends on the shape of your program rather than on whose logo is on the dashboard.

Key takeaways

• Knowing how to choose a 340B TPA starts with one idea: it is closer to vetting a long-term compliance partner than buying software. Weight qualification accuracy above price.
• Test every finalist live against a sample of your own claims, including borderline cases, before you sign.
• The covered entity, not the TPA, answers to HRSA. Audit your TPA at least annually, with a lighter quarterly claims check.
• Audit both directions: claims marked eligible that shouldn't be (diversion, duplicate discount risk) and claims rejected that should qualify (missed savings).
• Switch vendors with a parallel run, full historical data export and updated OPAIS records, never with a hard cutover.

What Is a 340B TPA?

A 340B third-party administrator (TPA) is a vendor that reviews prescription and encounter data to decide which drugs dispensed through contract pharmacies, and sometimes in-house pharmacies, qualify for 340B pricing. It then manages replenishment orders, billing and reporting between the covered entity, its pharmacies and its wholesaler. The covered entity, not the TPA, remains accountable for compliance in an HRSA audit.

That last sentence is the one most programs underweight, and it shapes everything about how to choose a 340B TPA. HRSA's contract pharmacy guidance places oversight responsibility squarely on the covered entity, and HRSA audit findings are issued to the entity, not its vendors. Your TPA can be wrong in ways that cost you money or create findings, and the dashboard will rarely tell you so. If you're new to the program mechanics, our primers on how 340B works and 340B contract pharmacy arrangements are a useful foundation.

Not every "340B vendor" does the same job

Why the Vendor Matters More Than the Per-Claim Price

Most RFPs are still decided on fee per claim, mainly because it's the easiest number to drop into a spreadsheet next to a competitor's. The problem is that a lower per-claim rate tells you nothing about whether the platform is capturing the prescriptions in the first place. A TPA that costs a little more but applies your patient definition, prescriber eligibility and site rules accurately will usually outperform a discount vendor whose rules quietly drop a slice of legitimate claims every month. Nobody receives an invoice for claims that were never captured, which is exactly why this failure survives for years inside otherwise well-run programs.

The opposite failure is just as expensive. A TPA that reads your qualification rules too generously, or whose accumulator logic doesn't line up with wholesaler and payer data, creates diversion and duplicate discount exposure that surfaces only during an HRSA audit or a manufacturer review, often long after the claims have been replenished at 340B prices. Our page on how duplicate discounts happen walks through the most common pathways.

And the fit changes over time. Contract pharmacy networks grow, EHRs get replaced, manufacturer restrictions shift and HRSA's audit focus moves from year to year. A vendor that suited your program at implementation can become a liability three years later simply because nobody revisited the configuration. That's a different failure from picking the wrong vendor. It's a failure to keep checking, and it's the habit this article is meant to build.

What Changed for 340B TPAs in 2025 and 2026

Many TPA buying guides were written before the current wave of manufacturer, state and federal changes. Any vendor you evaluate today should be able to explain, in specifics, how its platform handles each of these. (Status reflects information available at publication; several items are still evolving, so confirm current requirements before you build contract language around them.)

• Manufacturer contract pharmacy restrictions and claims-data conditions. Many manufacturers limit 340B pricing at contract pharmacies or require claims data through platforms such as 340B ESP. Your TPA needs to apply each policy drug by drug and support timely data submission. See our manufacturer restrictions tracker and guide to 340B contract pharmacy restrictions.
• State contract pharmacy laws. A growing number of states now limit manufacturer restrictions on contract pharmacy distribution. Your vendor's logic, and your legal strategy, may differ by state. Track changes with our 340B state law tracker.
• Medicare negotiated prices (MFP). With Medicare Drug Price Negotiation prices in effect from 2026, manufacturers are not required to provide both the maximum fair price and the 340B price on the same unit. Ask how the TPA identifies affected drugs and claims.
• Rebate models. HRSA's 340B rebate model pilot, announced in 2025, would shift some drugs from upfront discounts to post-purchase rebates, and its status has continued to move. A TPA needs claim-level data and reconciliation that can support rebate submissions. Read what to prepare for the rebate model and model the cash-flow impact with our rebate calculator.
• Medicare Part B modifiers and Medicaid carve-in / carve-out. Hospital split-billing software must apply Medicare 340B claim modifier rules correctly, and every vendor must respect your Medicaid Exclusion File election and state managed care rules.

How to Choose a 340B TPA: 9 Criteria That Actually Matter

Use these criteria to evaluate every finalist the same way. Each one includes the question to put to the vendor directly.

1. Qualification rule configuration

Every covered entity's patient definition has its own texture: specialty pharmacy nuances, mixed-use carve-outs, outpatient status rules, eligible locations from your Medicare cost report, and referral capture logic. Ask the vendor to show, claim by claim, how your specific rules are built into the system rather than applied as a generic template. A slide of checkboxes is not the same thing as a live walkthrough using sample claims from your own patient population.

Ask the vendor: "Show me exactly which data fields decide that this claim qualifies, and where I can change that rule."

2. Replenishment model

Some TPAs replenish against actual units dispensed; most contract pharmacy arrangements use a virtual inventory model that tracks eligible units through an accumulator without a separate physical 340B stock. Each approach carries trade-offs in reconciliation work, exposure if a claim is later found ineligible, and the reports you'll need to hand an auditor. Know which model you are buying before you sign.

Ask the vendor: "What happens to accumulated units and replenishment orders when a claim is reversed or later deemed ineligible?"

3. Accumulator and duplicate discount logic

This is where a lot of exposure hides. Accumulator logic has to reconcile against Medicaid billing, your carve-in or carve-out status, 340B ceiling price data and a growing list of manufacturer programs, and it has to update fast enough to avoid double-counting. Ask how often accumulators refresh and what happens when a manufacturer or payer file lags behind a dispensing event. Our split billing and duplicate discount review tests exactly this.

Ask the vendor: "How do you identify Medicaid fee-for-service and Medicaid managed care claims, and how often is that logic updated?"

4. Data feed integrity

A TPA is only as reliable as the data flowing into it. Decisions should rest on complete, clean, correctly timestamped feeds from your EHR, pharmacy management system and every contract pharmacy. If one pharmacy's feed goes down for a day, will the vendor tell you, or will the gap simply never show up?

Ask the vendor: "What alerts do we receive when a feed is late, incomplete or malformed, and how quickly?"

5. Manufacturer restriction and data submission handling

With dozens of manufacturers now attaching conditions to contract pharmacy pricing, the TPA must apply drug-level and pharmacy-level exclusions, honor any single-pharmacy designations you've made, and support claims-data submission where you choose to participate.

Ask the vendor: "Walk me through how a new manufacturer policy gets configured, who approves it, and how quickly."

6. Fee structure and total cost

The advertised number is usually the per-claim fee, not the total cost. Implementation fees, monthly minimums, contract pharmacy add-on fees and audit-support or reporting fees can turn an attractive quote into the more expensive option by year two. Get every fee category in writing before comparing vendors side by side.

Ask the vendor: "List every fee we could be invoiced for during the contract term, including ones we may never trigger."

7. SLA terms and implementation timeline

SLAs should name actual response and resolution windows for data discrepancies, not "commercially reasonable efforts." Ask for a realistic implementation timeline from a reference client of similar size and contract pharmacy count; vendors often quote timelines that assume internal staffing most covered entities don't have on day one.

Ask the vendor: "Can we speak with a client of our size who implemented in the last 18 months?"

8. Contract pharmacy network support

Ask how the vendor handles OPAIS registration changes, how it routes and reconciles claims when one patient fills at several contract pharmacies, and how it manages pharmacy chains with different data formats. Platforms that look identical in a single-pharmacy demo can behave very differently once real network complexity arrives. Our contract pharmacy management service sees this gap often.

Ask the vendor: "Show me reconciliation for a patient who used three different contract pharmacies last quarter."

9. Reporting, data ownership and security

Audit-ready reports should be self-serve, not custom requests. Confirm that you own your data, that the contract guarantees full claim-level export during the term and after termination, and that the vendor signs a HIPAA business associate agreement and can provide current security attestations such as a SOC 2 Type II report.

Ask the vendor: "If we terminate, what exactly can we export, in what format, and for how many years?"

Building an Honest 340B TPA Comparison

A useful 340B TPA comparison doesn't start with a feature checklist copied from each vendor's website. It starts with your own claims data. Pull a sample of recent prescriptions, include several edge cases you know are borderline under your patient definition, and ask each finalist to adjudicate them live. The vendor willing to do that in front of you, with your data, is telling you something. So is the vendor that steers you back to a generic demo environment.

Then push past the easy cases. Ask how the platform handles a split-fill prescription, a patient who transfers care mid-treatment, a prescriber who leaves your organization, and a 340B-eligible claim that a payer reverses weeks after dispensing. Vendors are well practiced at demonstrating the clean scenarios. The messy ones are where platforms really differ, and where your future audit exposure lives.

If you remember one thing about how to choose a 340B TPA, make it this: score every finalist on the same weighted criteria. The weights below are a starting point; adjust them to your program.

Qualification accuracy gets the heaviest weight for a simple reason: it is the one category where a shortfall compounds silently every single day the contract is in effect.

12 RFP questions for anyone learning how to choose a 340B TPA

1. How is our specific patient definition configured, and who on our side can view and approve rule changes?
2. What source data does each eligibility decision rely on, and can we see that data at claim level?
3. How often do accumulators update, and how are reversals and rebills handled?
4. How do you identify Medicaid FFS and managed care claims in each state where we operate?
5. How do you apply manufacturer contract pharmacy restrictions and single-pharmacy designations?
6. Do you support claims-data submission to manufacturer platforms, and is there a fee?
7. How will your platform handle Medicare negotiated-price drugs and any rebate model requirements?
8. What alerts do we receive for missing or late feeds, and within what timeframe?
9. What are your contracted response and resolution windows for data discrepancies?
10. Which reports are self-serve, and which require a custom request or fee?
11. What data can we export during the term and after termination, and for how long is it retained?
12. Can you provide a SOC 2 Type II report, a signed BAA and two references of similar size?

What a Real 340B Split Billing Software Comparison Looks At

Behind the sales language, a 340B split billing software comparison comes down to a handful of technical questions. They matter most for hospitals with mixed-use areas, where the same drug may be purchased on 340B, GPO or WAC accounts depending on the patient's status.

None of this comes through in a demo without some prodding. Ask each vendor to build a report that mirrors an HRSA audit sample request from its test environment, then trace every data point back to its source with you.

How to Audit My 340B TPA: A 7-Step Process

If you're asking how to audit your 340B TPA, the honest answer is: more often than most programs do, and with more independence from the vendor's own reporting than most compliance teams build in. A meaningful 340B TPA audit uses source records the vendor did not generate. Here is the process we recommend.

1. Set scope and pull independent data. Define the review period, sites and contract pharmacies in scope. Pull data from your EHR, pharmacy systems and wholesaler invoices directly, not only from the TPA portal.
2. Test claims marked eligible. Pull a statistically meaningful sample of claims the TPA qualified and verify each one against your patient definition, prescriber records, eligible locations and dispensing records. Do not rely on the vendor's own eligibility flag.
3. Test claims the system rejected. Pull a separate sample of non-qualified claims and check whether any should have qualified. Missed captures are invisible unless you look for them deliberately, and this step often pays for the audit. Our revenue recovery and optimization work starts here, and 340B referral capture is a frequent source of missed volume.
4. Reconcile replenishment to dispensing. Compare replenishment orders against 340B-eligible dispensing for the same period. A persistent mismatch in either direction is one of the clearest signs that the qualification logic or the accumulator feed has drifted.
5. Test duplicate discount controls. Confirm Medicaid FFS and managed care claims are handled according to your carve-in or carve-out election and your Medicaid Exclusion File listing, and that reversals flow through correctly.
6. Verify OPAIS and contract records. Check that OPAIS lists every active contract pharmacy and child site correctly, and that written contract pharmacy agreements match what the TPA is actually processing. HRSA registration and recertification support can close gaps here.
7. Audit invoices and contract terms. Confirm per-claim fees match the contracted rate, contract pharmacy fees are billed correctly, and services bundled at signing (such as certain reports) haven't been itemized separately since. Pricing rarely changes without notice, but scope and bundling drift over multi-year contracts.

Document findings, root causes and corrective actions. If the review uncovers a potential material breach, such as systematic diversion or duplicate discounts, involve counsel promptly: HRSA expects covered entities to self-disclose material breaches and work with affected manufacturers on repayment. An independent 340B mock audit or independent TPA review gives you a defensible record, and our audit readiness scorecard is a quick way to see where you stand today.

How often should you audit your TPA?

High-volume programs and those with many contract pharmacies benefit from a rolling quarterly review instead of a single annual pass. For what auditors focus on, see the 25 areas HRSA examines and our guide on how to prepare for a HRSA 340B audit.

Red Flags That Mean It's Time to Look Elsewhere

A few patterns tend to show up before a covered entity starts researching how to switch 340B TPA vendors:

• Recurring, unexplained gaps between expected and actual claim volume.
• Support tickets on data discrepancies that stay open for weeks.
• Audit-ready reporting that requires a custom request, and sometimes a fee, every time.
• Account team turnover so frequent that nobody at the vendor understands your program's specific qualification rules anymore.
• Slow or inconsistent configuration of new manufacturer restrictions.

The same discipline behind how to choose a 340B TPA applies here. Any one of these is worth a direct conversation with your vendor. Two or more, sustained over several quarters, usually means the relationship has run its course.

How to Switch 340B TPA Vendors Without Breaking Compliance

Migration is one of the riskiest operational moments in a 340B program, so switching 340B TPA vendors without breaking compliance deserves its own plan rather than a rushed timeline. Before you start, check your current contract's termination notice period and data export rights, since some vendors narrow export scope once a contract ends.

Train pharmacy and billing staff on the new workflow before go-live, not during it; a gap in staff understanding in the first weeks of a new system is where preventable errors cluster. Make sure historical data needed for future HRSA audits stays accessible for your full record retention period. If your written policies reference the old vendor, update them as part of the project; our policy development and training team can help.

How to Reduce 340B TPA Fees Without Cutting Corners

Programs looking at how to reduce 340B TPA fees often assume the only lever is a lower per-claim rate. There's usually more room than that:

• Volume tiers. Tiered pricing can lower costs as claim volume and contract pharmacy count grow. Revisit pricing whenever you add a pharmacy relationship, not only at renewal.
• Bundled audit support. Negotiate audit-support reporting into the base contract before signing, instead of paying for it each time HRSA or a manufacturer comes calling.
• Rate locks. Confirm in writing whether multi-year contracts lock rates; some vendors reserve the right to adjust fees annually unless the contract says otherwise.
• Remove unused add-ons. Audit invoices for modules or pharmacy fees tied to relationships you no longer use.
• Recover missed captures first. Improving qualification accuracy often delivers more than any fee cut.

The lowest-fee vendor is rarely the lowest-cost vendor once missed captures and compliance exposure are counted. Negotiate fees, but negotiate them with a vendor you've already confirmed is qualifying claims correctly.

What "Best 340B Software" Actually Means for Your Program

Search for the best 340B software and every vendor's marketing page claims the title. In practice there is no universal winner. Fit depends on entity type, claim volume, contract pharmacy count and how much internal bandwidth you have to manage the relationship:

• Health systems and DSH hospitals need deep split-billing logic, GPO prohibition controls and multi-site reporting.
• Critical access hospitals need a vendor that applies the orphan drug exclusion correctly and offers support sized for a small team.
• FQHCs need strong patient-definition logic tied to scope of project and grant-supported sites.
• Ryan White grantees need configuration that reflects grant eligibility and, where applicable, rebate-based participation.
• Infusion centers need accurate administration-level capture and handling of high-cost, frequently restricted drugs; see our infusion center consulting.

The right question isn't which vendor wins industry awards. It's whose qualification logic, replenishment model and support structure match the shape of your program.

Where an Independent 340B Review Fits

Your TPA has a commercial interest in its own platform, and your internal team is often stretched thin. An independent reviewer that doesn't process claims or sell software can test the TPA's decisions against your policies and source records with no stake in the outcome. That's the model behind our 340B compliance services. You can read more about our independence and how a review works, or check pricing.

Conclusion

Knowing how to choose a 340B TPA and knowing how to audit the one you have are really the same discipline applied at different moments: test the logic against your actual claims, don't take fee transparency or SLA promises at face value, and treat the vendor relationship as an ongoing compliance responsibility rather than a one-time purchase. Programs that build a habit of checking their administrator's work, instead of assuming the dashboard tells the whole story, tend to catch both missed savings and compliance exposure long before either becomes something they have to explain to HRSA.

Sources and further reading

• HRSA Office of Pharmacy Affairs: 340B Program Integrity and audits (hrsa.gov/opa).
• HRSA 340B OPAIS: covered entity and contract pharmacy registration database (340bopais.hrsa.gov).
• HRSA, Notice Regarding 340B Drug Pricing Program: Contract Pharmacy Services, 75 Fed. Reg. 10272 (March 5, 2010).
• U.S. Government Accountability Office, GAO-18-480: Drug Discount Program: Federal Oversight of Compliance at 340B Contract Pharmacies Needs Improvement (2018).
• 340B Prime Vendor Program (Apexus): policy and procedure resources and the 340B ACE credential (340bpvp.com).
• CMS guidance on Medicare Part B 340B claim modifiers and the Medicare Drug Price Negotiation Program (cms.gov).

This article is general educational information, not legal advice. 340B requirements change; confirm current HRSA, CMS, state and manufacturer requirements before acting.