Secondary Claims
A secondary claim tells the second payer what the first one did. Most secondary denials are carry-forward failures presenting as coding problems.
The Dependency Chain
The information lives in the primary's 835 remittance (paid amounts, CARC adjustments, patient responsibility) and must be carried accurately into the secondary 837 claim. A secondary claim cannot be correct unless the primary 835 was parsed correctly, the adjustments were mapped correctly, and the COB (coordination of benefits) order was right in the first place. Three upstream dependencies, each of which fails silently.
This is why secondary AR ages differently from primary AR, and why organizations often cannot explain their own secondary denial rate.
The Symptom and the Fix
Why It Presents as a Coding Denial
The second payer rejects on what it can see: amounts that do not reconcile, adjustment codes that do not make sense against the billed amount, or missing prior-payer information. The rejection message describes the symptom. The cause is upstream, in the 835 parse, the adjustment mapping, or the COB determination. Working the rejection at face value produces a resubmission that fails the same way.
What Good Looks Like
Deterministic mapping from the primary 835's adjustment detail into the secondary 837's COB segments, with the mapping auditable and the failure surfaced before submission rather than discovered as a denial. PNT validates secondary claim construction against the implementation guide at the boundary. Payer-specific secondary requirements vary and are maintained per payer.
Frequently Asked Questions
Why do secondary claims get denied after the primary paid?
Usually because the primary's payment and adjustment data from the 835 was not carried forward accurately into the secondary 837. The second payer rejects on what it sees, amounts that don't reconcile or adjustment codes that don't make sense, so the denial presents as a coding problem while the cause is a data carry-forward failure.
What data does a secondary claim need from the primary?
Paid amounts, CARC adjustment detail, and patient responsibility from the primary's 835, mapped into the secondary 837's COB segments. If the primary 835 was parsed incorrectly, or the COB order was wrong to begin with, the secondary claim cannot be correct regardless of coding.
Why does secondary AR age differently?
Because secondary claims have three silent upstream dependencies, the 835 parse, the adjustment mapping, and the COB determination, each of which fails without an obvious signal. The denial appears far from its cause, so resubmission at face value tends to fail the same way.
Transactions and Industries
837 Claims
Where clean claims actually come from: front-end validation and the acknowledgment chain.
835 ERA Processing
Reassociation is the hard part: matching the money to the explanation.
Revenue Cycle Companies
Multi-client processing with per-client provenance and no PHI retained across your book of business.
Ready to talk through your use case?
Talk to a Post-n-Track specialist about your data challenges. A direct conversation, starting with what you need.