“Claim submitted to incorrect payer” means the payer that received the claim is not the one responsible for it. The claim was rejected, not denied, so the fix is to find the right payer and payer ID and send it there before the filing deadline.
What does status code 116 mean?
X12 claim status code 116 reads: “Claim submitted to incorrect payer.” It is published in the X12 Claim Status Codes list (opens in a new tab). The payer is telling you the claim belongs somewhere else.
On the raw 277CA it appears in the STC segment, for example STC*A3:116: 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 |
|---|---|
| Patient has a Medicare Advantage plan but the claim went to Original Medicare, or the reverse | Eligibility response and the current card |
| Behavioral health or another benefit is managed by a separate carve-out company | The card and the plan’s benefit information |
| Wrong payer ID selected in the clearinghouse | The clearinghouse payer list |
| Patient changed plans | Coverage on the date of service |
| Out-of-area Blue Cross Blue Shield member billed to the wrong Blue plan | BlueCard rules: usually file with your local Blue plan |
How to fix it
- Run eligibility for the date of service and note the plan that actually covers the patient.
- Check the card for a separate claims address or payer for the service type.
- Pick the correct payer ID from your clearinghouse’s current list.
- Update the patient’s insurance record and resubmit as a new claim.
How to prevent it
- Verify the payer, not just “active coverage,” at each visit.
- Keep a list of carve-out payers for the plans you see most.
- Review your clearinghouse payer ID mapping when payers merge or change IDs.
Frequently asked questions
Does a rejection for incorrect payer stop timely filing?
Usually not. Send the claim to the correct payer as soon as possible and keep the rejection report as proof of the original submission date in case it is needed.
Is status 116 the same as a coordination of benefits denial?
No. A coordination of benefits denial (CARC 22) comes on the 835 after processing. Status 116 is a rejection before processing.
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 128: Entity’s tax ID
- Status 145: Entity’s specialty/taxonomy code
- 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.
Claims bouncing between payers?
We verify the responsible payer before claims go out and fix payer mapping in your clearinghouse.