What reporting should a 340B TPA provide?
HRSA doesn’t publish a list of reports a 340B TPA must produce. It holds the covered entity responsible for compliance and for keeping auditable records, so your TPA’s reports are how you show you’re meeting that duty. At a minimum, a TPA should give you claim-level eligibility detail (including claims it rejected and why), accumulator and replenishment reports, a monthly financial statement you can book from, Medicaid and duplicate discount checks, a change log for your eligibility settings, and an export that drops straight into a HRSA audit’s 340B universe. If you submit to 340B ESP or the 2027 rebate pilot, add submission and status reports for those too.[1][2][5]
- Claim-level eligibility detail
- Accumulator and replenishment
- Monthly financial statement
- Medicaid and duplicate discount checks
- Eligibility settings change log
- Audit-ready 340B universe export
HRSA sets the duty. Your TPA supplies the proof.
Reports from the pharmacy
HRSA’s 2010 contract pharmacy guidance says the pharmacy will give the covered entity reports consistent with customary business practices, for example quarterly billing statements, status reports of collections, and receiving and dispensing records. In most programs, the TPA is the one that assembles them.[1]
A tracking system you can check
The same guidance calls for a tracking system that prevents diversion, and for the covered entity to compare its prescribing records with the pharmacy’s dispensing records on a set schedule. HRSA’s sample contract language mentions quarterly sample comparisons and a six-month comparison of 340B purchasing and dispensing.[1]
Records that stand up to an audit
Auditable records must be kept for as long as federal, state and local law require, and the statute lets HHS and manufacturers audit covered entity records. HRSA also expects independent audits of contract pharmacy arrangements and asks entities to reconcile dispensing, purchasing and billing.[1][2][4]
HRSA leaves the method to you: its 2010 guidance says it intentionally doesn’t specify the method, personnel or items for getting the information you need, as long as you meet your obligations.[1]
Eight reports, who reads them, and how often
| Report | What it should show | Who uses it | Typical cadence |
|---|---|---|---|
| Claim-level eligibility detail | Every claim the TPA reviewed, the decision (340B or not), and the reason: location, prescriber, patient, drug, or payer. Rejected claims matter as much as accepted ones.[1][5] | Pharmacy director, compliance | Monthly, plus on demand |
| Accumulator / virtual inventory | Units accumulated by NDC and account, what has been replenished, what is still open, and reversals that reduced an accumulation.[5] | Pharmacy buyer, compliance | Continuous; reviewed monthly |
| Replenishment and invoice tie-out | Orders the TPA generated, matched to wholesaler invoice lines, shipments received, and any discrepancies the pharmacy reported.[1] | Pharmacy buyer, finance | Each order cycle |
| Financial statement and remittance | Script volume, sales, administrative fees, dispensing fees, estimated 340B drug cost and adjustments such as true-ups or carve-out fees, in a format finance can book from.[1][7] | CFO, controller | Monthly |
| Medicaid and duplicate discount checks | Medicaid claims excluded under a carve-out, claims flagged by BIN/PCN or payer, and how each was handled, so you can show no drug got both a 340B price and a Medicaid rebate.[5] | Compliance | Monthly; quarterly review |
| Eligibility settings change log | Who added or removed a site, prescriber, pharmacy or drug rule, when, and from what date it applied. Auditors ask how each claim was qualified.[5] | Compliance, 340B coordinator | On every change |
| Contract pharmacy oversight | Activity by pharmacy, pharmacies registered but unused, and the inputs for quarterly self-audits and the annual independent audit.[2][5][6] | Compliance, internal audit | Quarterly and annually |
| Manufacturer data and rebate status | What was sent to 340B ESP and whether each claim came back Conforming or Non-Conforming; for the 2027 rebate pilot, rebate claims submitted, paid and denied.[8][9][10] | Pharmacy director, finance | Each submission cycle |
Cadences are common practice, not HRSA rules. Setting up a new arrangement? See how contract pharmacy setup works with a TPA.
A four-check monthly close
- 1
Prescribing vs dispensing
Sample eligible prescriptions from your own records and confirm they match what the pharmacy dispensed and the TPA qualified.[1]
- 2
Purchasing vs dispensing
Tie replenishment orders and wholesaler invoices back to the accumulations that triggered them. HRSA’s sample contract language suggests doing a full comparison at least every six months.[1]
- 3
Remittance vs ledger
Book gross sales as revenue and the administrative and dispensing fees as expense, and treat true-ups and carve-out fees as adjustments.[7]
- 4
Rebate claims under the 2027 model add a fifth check. See 340B rebate reconciliation.
Can your TPA build the 340B universe?
The sample HRSA data request asks for a list of every 340B drug furnished, administered or dispensed during the sample period, preferably in Excel, plus a table naming the system or software behind each data set. Its example table lists the TPA as a typical source for entity-owned pharmacy data.[5]
Full timeline and document list: how to prepare for a HRSA 340B audit.
- a.Patient ID (medical record or Rx number)
- b.Prescribing location and dispensing pharmacy
- c.Date written
- d.Date dispensed or administered
- e.Drug name
- f.NDC
- g.Quantity
- h.Ordering provider
- i.Every payer (primary, secondary, tertiary, Medicaid)
- j.Purchase account and 340B ID
- k.Acquisition price
Source[5]
Red flags in a report pack
- Only summary totals, with no way to drill down to the claim
- Rejected or non-eligible claims don’t appear anywhere
- Exports come as PDFs instead of a file you can sort and filter
- No record of who changed an eligibility setting, or when
- Large true-ups that the statement doesn’t explain
- History disappears when you leave, or costs extra to get back
Questions to ask your TPA
- Can we export claim-level data ourselves, in Excel or CSV, at any time?
- Do your reports show non-eligible claims and the reason for each?
- Can you produce a 340B universe for a sample period with every field the HRSA DRL asks for?
- Do you keep a dated log of changes to our sites, prescribers, pharmacies and drug rules?
- Who owns the data, and how much history do we get if we switch TPAs?
- How do you show 340B ESP and rebate claim status alongside our TPA data?
Thinking about a change? Read how to switch 340B TPAs and compare 340B TPAs.
Reporting finance and compliance can both use
One view of the program
Net 340B benefit, claims by status, and savings and fees by pharmacy, with centralized reporting and portal access for your team.
No end-of-month true-ups
Real-time claim capture and purchase splitting mean fewer surprises on the statement. We run contract pharmacy and split billing for 300 covered entities, 24 of them hospitals.
Compliance built in
Audit-ready claims, duplicate discount monitoring, Good Faith Inquiry tracking, and real-time 340B ESP and Truzo (Kalderos) integration. See how ESP submissions work.
Rebates in the same reports
The rebate module is Included for Aventi TPA clients, with MFP reconciliation tools, so 2027 rebate claims sit next to your TPA data. Learn about the 2027 340B rebate model.
340B TPA reporting: common questions
Sources
- Federal Register, Notice Regarding 340B Drug Pricing Program—Contract Pharmacy Services, 75 FR 10272 (Mar. 5, 2010), essential elements (f) and (g) and Appendix — https://www.federalregister.gov/documents/2010/03/05/2010-4755/notice-regarding-340b-drug-pricing-program-contract-pharmacy-services
- 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
- HRSA Office of Pharmacy Affairs, Program Integrity (audits, annual recertification, self-disclosure) — https://www.hrsa.gov/opa/program-integrity
- 42 U.S.C. § 256b(a)(5)(C), auditing of covered entity records (Cornell LII) — https://www.law.cornell.edu/uscode/text/42/256b
- 340B Prime Vendor Program (Apexus), Sample HRSA 340B Audit Data Request List (DRL) for Covered Entities (updated Sept. 10, 2026) — https://www.340bpvp.com/Documents/Public/340B%20Tools/sample-hrsa-340b-audit-data-request-for-covered-entities.pdf
- National Coalition of STD Directors, 340B HRSA Audit Overview and Checklist (updated Oct. 12, 2021) — https://ncsddc.org/wp-content/uploads/2021/10/HRSA-Audit-Overview-and-Checklist-10.12.21-1.pdf
- Community Link Consulting, Accounting for Contract Pharmacy Activity: Not Just the Revenue — https://www.communitylinkconsulting.com/blog/accounting-for-contract-pharmacy-activity-not-just-the-revenue
- 340B ESP Help Center, How to Review Submitted Claims Data in 340B ESP — https://help.340besp.com/en/articles/17069695-how-to-review-submitted-claims-data-in-340b-esp
- 340B ESP Help Center, Post-submission Validations — https://help.340besp.com/en/articles/16985760-post-submission-validations
- Federal Register, Notice Regarding 340B Rebate Model Pilot Program (Aug. 3, 2026) — https://www.federalregister.gov/documents/2026/08/03/2026-15633/notice-regarding-340b-rebate-model-pilot-program
Last updated November 17, 2026. This page is general information, not legal advice. Check HRSA’s current guidance and your own counsel for your program.