Coming in October 2026 as part of the new claims submission experience, 340B ESP will provide greater visibility into potential data issues before claims are submitted. Pre-submission validation checks evaluate attached claims files for formatting, data type, required-field, and other issues that may affect whether individual rows are available for submission.
As files are attached, 340B ESP assigns each file a file state and identifies any Validation Alerts within the data. File states help you quickly understand whether a file is ready for submission, contains issues that may require additional review, or has no rows available for submission.
Tip: For a detailed list of pre-submission validation requirements and accepted formats, check out Claims Data Requirements.
Understanding File Validation States
When a claims file is attached to 340B ESP, it is assigned one of three validation states based on its contents: Good, Validation Alert, or No Rows for Submission. Each file state appears in the Submission Summary and indicates whether the file is ready for submission, contains issues that may need review, or has no claim rows available for submission. Each file state is explained below.
Good – Files with No Validation Alerts
A Good file state indicates that the attached file contains no Validation Alerts and includes at least one valid NDC that will be included in the submission..
In the Submission Summary, the file will appear as Good. A Good file state means:
The file contains no Validation Alerts.
The file contains at least one valid NDC.
The file is using an accurate column mapping that allows the submitted data to be interpreted correctly.
The file may still contain invalid NDCs. A Good status does not mean that every NDC in the file is valid.
Only rows listed in the Rows for Submission will be included in the submission.
A Good file state does not mean that every NDC in the file is valid. The file may still contain invalid NDCs; however, as long as at least one valid NDC is identified and there are no Validation Alerts, the file will display as Good. Only claim rows with valid NDCs and no Validation Alerts will be included in the submission.
Validation Alerts
Validation Alerts identify formatting, data type, and required-field issues within attached claims files. Examples include:
Missing values in required fields.
Alphabetic characters submitted in numeric fields.
Dates submitted in an unsupported format.
Values exceeding permitted field lengths.
Decimal values where decimals are not permitted.
When these issues are identified, ESP displays a Validation Alert so users can review the affected data. Users can investigate these issues directly in the Submission Data file view or download the Validation Alerts file to review all claim rows with validation alerts.
Pre-submission validation checks help identify potential data issues before claims are submitted. Validation Alerts give users visibility into formatting and required-field issues without automatically blocking the entire submission. Once claim lines pass front-end validation, they move into subsequent back-end validation.
Note: A Validation Alert does not prevent the file from being submitted. Claims that can be submitted will continue through the submission process, while the alert remains available for review. If every row in the file contains an error in a required field, there are no rows available for submission and the file cannot be submitted.
No Rows for Submission
A file may display a No Rows for Submission file state when none of the claim rows in the file are eligible for submission.
This can occur for several reasons, including:
No valid NDCs are identified in the file.
Column mappings prevent the attached data from being interpreted correctly.
Every claim row contains a Validation Alert that prevents the row from being submitted.
When a file has No Rows for Submission, no claims from that file will be included in the submission. Review the file details, column mappings, and any available Validation Alerts to identify what needs to be corrected before reattaching the file.
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]