Skip to main content

Pharmacy Claims Submission Requirements

Streamline data processes with ESP's data requirements table

What are Pharmacy Claims?

Pharmacy claims are records for prescription drugs dispensed through a pharmacy and submitted to 340B ESP to meet applicable manufacturer claims data requirements.

Submit pharmacy claims when the drug or NDC is supported for pharmacy claims submission in 340B ESP and the applicable manufacturer requires claims data for the covered entity or pharmacy relationship.

Before submitting, confirm that the NDC is included in the pharmacy NDC list and review any applicable manufacturer requirements.


Pharmacy Claim Field Requirements

The following fields are collected when submitting pharmacy claims data to 340B ESP. Required fields are indicated with an asterisk. Any additional data elements included in a data file selected for upload will automatically be removed prior to data submission.

Download the Pharmacy Claims Data Template here:

Field

Data Type

Description

Date of Service*

Date

The date on which the prescription was filled by the dispensing pharmacy.

Date Prescribed*

Date

The date on which the prescription was written by the prescribing healthcare provider.

Rx Number*

Numeric

The native (unmodified) prescription number for the prescription as generated by the pharmacy.

Fill Number

Numeric (0-99)

Indicates the number of times the prescription has been filled as of the current fill. For example, a value of "0" indicates that the prescription has not been filled previously and the current fill is the first one. The first refill would have a value of "1".

NDC*

Numeric (11 Digits)

The 11-digit National Drug Code (NDC) identifying the manufacturer, drug product, and package size of the medication dispensed.

Quantity*

Numeric

Number of units dispensed to the patient. Appropriate Units of Measure for each product will be provided within the NDC list.

Prescriber ID**

Numeric (10 Digits)

The unique public ID for the prescribing physician. Accepted IDs include the NPI and DEA ID.

Service Provider ID*

Numeric (10 Digits), no leading zeros.

The unique identifier of the pharmacy that dispensed the prescription.

Contracted Entity ID*

Alphanumeric, may contain dashes – starts with 2 or 3 letters

HRSA assigned identifier of the 340B covered entity that designated the dispense as 340B. If the 340B ID contains a suffix, this must be included.

Payer BIN**

Alpha numeric, may contain leading zeros

The bank identification number of the primary payer on the prescription.

Payer PCN**

Alphanumeric

Processor Control Number. Identifier used to determine which processor will handle a prescription drug claim.

Prescriber ID Qualifier**

Numeric

Indicates the type of unique ID provided. A value of "01" indicates NPI, "12" indicates DEA.

Service Provider ID Qualifier**

Numeric

The type of unique ID provider. "01" for NPI, "05" for Medicaid, "07" for NCPDP, and "12" for DEA.

Wholesaler Invoice Number

Numeric

The invoice number assigned by the wholesaler for the replenishment order made by the 340B covered entity. For claims with multiple invoice numbers, submit each invoice number as a separate claim line.

Ship to Date

Standard Date Formats

Date when the drug was shipped to the Ship To location.

Ship to Location

Numeric

NPI, DEA, or NCPDP of the pharmacy where the drug was physically shipped.

340B Account Number

Alpha numeric

Account number assigned by the wholesaler and used for the purchase.

Product Serialization Number

Numeric

Unique ID assigned to the package shipped from the manufacturer to the wholesaler.


​*Indicates a required field for all 340B ESP submissions regardless of NDC.
**Indicates a field that may be required depending on the manufacturer. Please review the manufacturer policies in the Resources page to learn more.


Still have questions?

If you have questions or need additional help, our team is here for you — please feel free to reach out using any of the contact options below:

Chat: Available via in-app messenger
​Email: [email protected]

Did this answer your question?