Status code 145 means the provider taxonomy code on the claim is missing or does not match what the payer expects for the provider named by the entity code. Taxonomy codes describe a provider’s type and specialty, and many payers match them against enrollment and the NPI Registry.
What does status code 145 mean?
X12 claim status code 145 reads: “Entity’s specialty/taxonomy code. Usage: This code requires use of an Entity Code.” It is published in the X12 Claim Status Codes list (opens in a new tab). The entity code says whether the billing (85) or rendering (82) provider’s taxonomy is the problem.
On the raw 277CA it appears in the STC segment, for example STC*A7:145:82: the claim status category, then the status code, then the entity code when one is required. A rejected claim never entered the payer’s claims system, so there is nothing to appeal: you fix the data and send the claim again.
Common causes
| Cause | What to check |
|---|---|
| Taxonomy missing when the payer requires it | Billing and rendering provider fields on the claim |
| Taxonomy on the claim differs from the one the provider enrolled with | Payer enrollment record |
| Taxonomy not listed for that NPI in NPPES | The NPPES NPI Registry entry |
| Group taxonomy sent for an individual, or the reverse | Which taxonomy belongs to which NPI |
How to fix it
- Read the entity code to find which provider’s taxonomy failed.
- Check the taxonomy codes listed for that NPI in the NPPES NPI Registry (opens in a new tab).
- Confirm which taxonomy the payer has on the enrollment.
- Set the matching taxonomy in the provider setup and resubmit as a new claim.
How to prevent it
- Record each provider’s enrolled taxonomy per payer.
- Keep NPPES up to date when a provider’s specialty changes.
- Have the claim scrubber flag missing taxonomy for payers that require it.
Frequently asked questions
Where is the taxonomy code on an electronic claim?
In the PRV segment for the billing provider and, when reported, for the rendering provider.
Can a provider have more than one taxonomy?
Yes, but one is primary in NPPES, and each payer may expect a specific one for your enrollment.
Related claim rejection guides
- 277CA claim acknowledgment: how to read a rejection
- Status 33: subscriber and subscriber ID not found
- Status 562: Entity’s National Provider Identifier (NPI)
- Status 116: claim submitted to incorrect payer
- Status 128: Entity’s tax ID
- Status 496: submitter not approved for electronic claims
- “This code requires use of an Entity Code”
Status code wording is quoted from the X12 Claim Status Codes list (opens in a new tab) at the time of writing. Clearinghouse reports may show the same codes with slightly different text.
Taxonomy and enrollment out of sync?
We line up NPPES, payer enrollment and your claim setup so specialty data stops causing rejections.