Skip to main content

November, 11 2026: Entity Access Validation for Claims Submissions

340B ESP now validates user access to 340B IDs during claims submissions to ensure claims are submitted only for authorized covered entities.

Entity Access Validation for Claims Submissions

During the claims submission process, 340B ESP now checks whether the submitting user has access to each 340B ID associated with the claims being submitted.

Claims associated with 340B IDs the user is not authorized to access will be:

  • Excluded from the Selected Row count in the Submission Summary.

  • Excluded from the claims submission.

This validation helps prevent claims from being submitted for covered entities without the appropriate access permissions.

What do I need to do?

Please continue to reviewing your organization's access to ensure claims can be submitted without interruption.

  • Review your entity access: Navigate to your Entity Profile to confirm you have access to all applicable 340B IDs.

  • Review team permissions: Confirm that the appropriate users are registered to each entity. If necessary, use Invite New User to grant additional team members access.

Need access to an additional 340B ID?

If a 340B ID is missing from your Entity Profile, select Enroll New Entity to begin registering the entity in 340B ESP.

If the entity is already registered, you'll need to request access from an existing Admin associated with that entity.

Learn: For additional instructions, see How to Enroll Additional Entities in 340B ESP.


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 the in-app messenger

Did this answer your question?