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

How does 340B ESP claims data submission work with a TPA?

340B ESP is the platform many manufacturers use to collect 340B claims data under their contract pharmacy and in-house pharmacy policies. Your TPA usually does the sending. Your ESP admin adds the TPA’s partner access token and grants it “Read and Write Submissions,” and the TPA then submits your 340B-qualified claims through ESP’s software development kit (SDK). ESP keeps only claims for drugs covered by a manufacturer policy, hashes the prescription number before upload, and checks each claim against that manufacturer’s rules, marking it Conforming or Non-Conforming. Manufacturers use the data to find duplicate rebates. The rebate pilot that starts January 1, 2027 runs separately in Beacon, so many entities will feed both.[1][2][6][8]

The pipeline

From a qualified claim to a manufacturer match

  1. 1

    Qualify

    The TPA decides a claim is 340B-eligible. ESP asks that claims be fully audited by your administrator and replenished against before you send them.[1]

  2. 2

    Filter and map

    Only NDCs under a manufacturer policy are kept; the rest drop out automatically. Every row needs the 340B ID and the dispensing pharmacy’s ID.[1][5]

  3. 3

    De-identify

    The Rx number and product serialization number are hashed with salted SHA-3 before upload, so ESP treats the file as a HIPAA de-identified data set.[1]

  4. 4

    Submit

    A TPA submits through the SDK. Staff can also upload Excel or CSV files in the Claims Data module.[1][4]

  5. 5

    Validate

    ESP checks each claim against the manufacturer’s policy and returns Conforming or Non-Conforming, with Issues and Warnings.[6]

  6. 6

    Match

    Manufacturers use the data to find Medicaid, Medicare, TRICARE and commercial rebates that shouldn’t have been paid, and usually go to the payer first.[1]

340B ESP doesn’t decide why a duplicate rebate happened. A rebate administrator, PBM or plan may have failed to pass along information, and ESP says covered entities and manufacturers can work through those cases in good faith.[1] For how carve-in, carve-out and the Medicaid Exclusion File fit in, see 340B duplicate discounts and the Medicaid Exclusion File.

Two ways in

TPA submission vs. uploading it yourself

Both routes land in the same place and get the same validation. The difference is who builds the file and where you look for the results.[4][7]

TopicTPA through the SDKManual upload
Who sends it[1][2][4]Your TPA (or another authorized partner), on your behalfYour own staff, signed in to 340B ESP
Setup[2][3][4]The TPA onboards with 340B ESP; your admin adds its access token with Read and Write SubmissionsColumn mapping template for each file layout
Pre-submission checks[3][5]Handled in the TPA’s own submission system, which 340B ESP can’t seeNDC eligibility, 340B ID access and Validation Alerts in the Submission Summary
Where results show up[7]Pharmacy or Medical Claims Details report in the Reports module (not the Claims Data modules)Submission Receipt and the Claims Data module, plus the Claims Details reports
Claim tracking[4][7]ESP ID on each processed claimESP ID on each processed claim, in the downloaded submission data

In HRSA’s rebate pilot notice, the vendor behind 340B ESP reported that more than 7,000 covered entities had submitted data through 340B ESP and that 53 TPAs could submit directly to its rebate platform on behalf of covered entities.[8]

Connecting your TPA in 340B ESP

Step 1

The TPA onboards with 340B ESP

340B ESP verifies the partner organization and issues two credentials: an access token the TPA shares with you, and a private token it keeps to sign its own requests.[3]

Step 2

You get the access token from your TPA

Ask for it in writing for each 340B ID you want covered. Some TPAs also ask you to sign an authorization first.[1][3]

Step 3

Your ESP admin adds the TPA

Settings, then TPA Permissions, then Add TPA on the right covered entity. Paste the token and choose a permission level.[2]

Step 4

Pick the right permission

Read Eligibility lets the TPA see eligibility and make SDK calls but not submit. Read and Write Submissions lets it submit claims for you. You can authorize more than one TPA.[2]

Seeing “Error Code 51”?

It means 340B ESP has no valid access token on file for the 340B ID the TPA is submitting under. The usual causes: the token was never generated or shared, it was generated for a different 340B ID, or it hasn’t been loaded into the TPA’s own submission system. Once you confirm the token on the ESP side, the fix sits with the TPA.[3]

Field by field

What goes into a pharmacy claim: 340B ESP vs. the rebate pilot

340B ESP publishes the fields it accepts for pharmacy claims. HRSA’s pilot notice limits rebate plans to a fixed list of standardized claims fields, with no purchasing records, encounter documentation or other patient-level information. ESP drops any column not on its list before submission.[1][8]

Field340B ESP pharmacy claim[1]In HRSA’s pilot field list[8]
340B ID (contracted entity ID)RequiredYes
Date of serviceRequiredYes
Date prescribedRequiredYes
NDC-11RequiredYes
QuantityRequiredYes
Rx number (hashed in ESP)RequiredYes
Service provider ID (dispensing pharmacy)RequiredYes
Prescriber IDBy manufacturerYes
Payer BINBy manufacturerYes
Payer PCNBy manufacturerYes
Fill numberOptionalYes
Wholesaler invoice numberOptionalNo
340B account numberOptionalNo
Ship-to date and locationOptionalNo
Product serialization number (hashed)OptionalNo
Encounter fields (HCPCS, diagnosis, place of service)By manufacturerNo

Medical (administered) claims use a separate layout in ESP: 340B ID, claim and line number, date of service, HCPCS code or unit of measure (one or the other), health plan name and ID, NDC-11, quantity and the NPI of the site of care.[1] Encounter fields come from Amgen’s policy, not the pilot; see Amgen’s 340B encounter data requirement.

What happens to patient data

No patient name, birth date or address is in the ESP field list. The two identifiers that could point back to a prescription are hashed before the file leaves your side.[1]

Hashed before upload
Rx number and product serialization number, using salted SHA-3. For browser uploads, this happens on your own device.[1]
De-identified data set
340B ESP says an Expert Determination found the data meets HIPAA’s de-identified standard.[1]
Encrypted
AES 256-bit at rest and TLS in transit, with two-factor sign-in available on every account.[1]
BAA on request
Second Sight Solutions offers a standard business associate agreement through support@340besp.com.[1]

Keep the ESP ID that comes back with each processed claim. It’s how you tie a de-identified claim in ESP back to the record in your own system.[7]

If this, then that

Situations that trip up submissions

A submitted claim gets reversed
Send the same claim detail again with a negative unit amount. ESP expects reversals in your regular files.[1]
A manufacturer has cut off 340B pricing at a pharmacy
You can submit qualified claims that haven’t been replenished yet. Once pricing is restored, you replenish within that manufacturer’s lookback.[1]
A new contract pharmacy isn’t showing up
ESP pulls contract pharmacies from HRSA’s OPAIS. You can’t designate, apply for an exemption or submit for a pharmacy until its HRSA begin date has arrived.[1]
You only serve uninsured patients
Register anyway and complete the attestation during registration. ESP tells you whether any manufacturer still needs your claims.[1]
Your file includes drugs outside any policy
ESP drops them automatically, and any extra columns are removed before submission. You can also pre-filter to in-scope NDCs.[1]
A manufacturer wants encounter data
ESP has Pharmacy + Encounter and Medical + Encounter submission types for manufacturers that ask for visit-level data, such as Amgen.[1][4]

Many policies also limit which contract pharmacies you can use, which is where ESP designations come in.[1] See how contract pharmacy setup works with a 340B TPA.

Who actually requires this?

Manufacturers

Claims data conditions come from each manufacturer’s own policy, and some tie access to 340B pricing at certain pharmacies to submitting.[1] In Novartis v. Johnson, the D.C. Circuit let United Therapeutics require claims data for contract pharmacy orders, pointing to HRSA’s 1994 guidance on “standard information” and noting the only record evidence called the burden “minimal.”[9]

HRSA

340B ESP notes that HRSA has not commented publicly on the platform.[1] HRSA’s rebate pilot is a separate program: it starts January 1, 2027, requires plans to accept submissions for at least 45 calendar days from dispense, and limits plans to the standardized claims fields HRSA listed.[8]

States

NCSL counts at least 16 states with their own data-submission policies, such as barring manufacturers from requiring claims data unless federal law does.[10] Vermont’s law covers claims, utilization, encounter, purchase or other data.[11] Check your state, and each manufacturer’s policy, before you change what you send.

For how ESP sits next to Beacon, Truzo and the CMS systems, read Beacon, 340B ESP and Truzo. For the pilot itself, see the 2027 340B rebate model.

How Aventi helps

One TPA feeding every platform

Real-time ESP submissions

Aventi submits qualified claims to 340B ESP in real time and connects to Truzo (Kalderos), so you don’t build or upload files by hand.

Independent TPA

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

Beacon-ready for 2027

The rebate module is Included for Aventi TPA clients, for pharmacy and medical rebate claims in Beacon. See how we handle rebate denials and reconciliation.

Audit-ready history

We keep the claim-level history behind each submission, which helps when you reconcile with a manufacturer or prepare for a HRSA audit.

FAQ

340B ESP and your TPA: common questions

340B ESP is a platform, run by Second Sight Solutions, that supports manufacturers’ contract pharmacy and in-house pharmacy policies. Covered entities use it to make contract pharmacy designations, apply for wholly owned contract pharmacy exemptions and submit 340B claims data.[1]

Yes. 340B ESP lets a third party submit on a covered entity’s behalf through its SDK. The TPA gets an access token from 340B ESP, and your account admin adds that token under TPA Permissions with the Read and Write Submissions permission.[1][2][3]

Required for every submission: 340B ID, date of service, date prescribed, NDC-11, quantity, Rx number and service provider ID. Prescriber ID, BIN and PCN may be required depending on the manufacturer. Invoice number, account number, ship-to details, serialization number and fill number are optional.[1]

340B ESP says uploaded data meets the HIPAA definition of a de-identified data set, based on an Expert Determination. The Rx number and product serialization number are hashed with a salted SHA-3 process before upload. Second Sight Solutions also offers a standard business associate agreement on request.[1]

A claim that fails one or more validation requirements under the applicable manufacturer’s policy. Issues make a claim Non-Conforming; Warnings don’t. The same check can be an Issue for one manufacturer and a Warning for another.[6]

Claims submitted through the SDK don’t appear in the Claims Data modules. Use the Pharmacy or Medical Claims Details report in the Reports module, which shows both direct and TPA submissions.[7]

340B ESP itself says HRSA has not commented publicly on the platform. Manufacturers set claims data conditions in their own policies. The D.C. Circuit allowed a claims data condition in 2024, and at least 16 states have laws on manufacturer data requirements.[1][9][10]

No. 340B ESP supports manufacturers’ contract pharmacy and in-house policies. Beacon runs the HRSA rebate model pilot from January 1, 2027, where HRSA limits data to a fixed list of standardized claims fields. Many entities will submit to both.[1][8]

Sources

  1. 340B ESP Help Center, Frequently Asked Questions (updated Oct. 8, 2026) — https://help.340besp.com/en/articles/14482537-frequently-asked-questions-faqs
  2. 340B ESP Help Center, How to Add a Partner to Your Covered Entity — https://help.340besp.com/en/articles/14482545-how-to-add-a-partner-to-your-covered-entity
  3. 340B ESP Help Center, Partner Access Tokens in 340B ESP — https://help.340besp.com/en/articles/15484180-partner-access-tokens-in-340b-esp
  4. 340B ESP Help Center, How to Submit Claims Data in 340B ESP — https://help.340besp.com/en/articles/17230435-how-to-submit-claims-data-in-340b-esp
  5. 340B ESP Help Center, Claims Submission Overview — https://help.340besp.com/en/articles/17230688-claims-submission-overview
  6. 340B ESP Help Center, Post-submission Validations — https://help.340besp.com/en/articles/16985760-post-submission-validations
  7. 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
  8. Federal Register, Notice Regarding 340B Rebate Model Pilot Program (Aug. 3, 2026), including Section VIII.D (Data) — https://www.federalregister.gov/documents/2026/08/03/2026-15633/notice-regarding-340b-rebate-model-pilot-program
  9. Novartis Pharmaceuticals Corp. v. Johnson, No. 21-5299 (D.C. Cir. May 21, 2024) — https://media.cadc.uscourts.gov/opinions/docs/2024/05/21-5299-2055423.pdf
  10. National Conference of State Legislatures, State Legislative Actions and the Federal 340B Drug Pricing Program — https://www.ncsl.org/health/state-legislative-actions-and-the-federal-340b-drug-pricing-program
  11. Vermont Statutes, 18 V.S.A. § 4682, Discrimination against 340B entities prohibited — https://legislature.vermont.gov/statutes/section/18/091/04682

Last updated November 16, 2026. This page is general information, not legal advice. 340B ESP field lists and manufacturer policies change; check 340B ESP and each manufacturer’s current notice.