Explain the additional subscriber, payer, adjudication, and adjustment information required after a primary payer has processed a claim.

From our workflow: When we test 837P Secondary Claims and Coordination of Benefits, we trace the value from the source claim record, the implementation guide, and the receiver’s companion guide into the exported segment and then into the acknowledgment. That is more reliable than editing the X12 text after a rejection.

For 837P Secondary Claims and Coordination of Benefits, the 837P must identify each party and service through loops, segments, qualifiers, and control numbers. The receiver cannot rely on the visual layout of a paper form.

Core 837P workflow: understand the file’s purpose, review the envelope and transaction structure, validate before transmission, and read the claim acknowledgment.

Where the data belongs

Our 837P review for 837P Secondary Claims and Coordination of Benefits begins with the business purpose of the data. We then trace the source field into the loop or segment where the receiver expects it.

Keep the source for 837P Secondary Claims and Coordination of Benefits—such as eligibility, enrollment, authorization, charge data, or the companion guide—alongside the exported value. That makes a rejection traceable without hand-editing the X12 file.

What must agree with this value

Explain the additional subscriber, payer, adjudication, and adjustment information required after a primary payer has processed a claim. The information must remain consistent with related loops and segments. A change made late in the workflow—such as changing the subscriber relationship, diagnosis order, rendering provider, or service line—can require several connected elements to be rebuilt rather than one text value being replaced.

Practical design rule: Validate relationships, not only individual fields. A valid NPI can still be wrong for the role; a valid date can still be wrong for the qualifier; a valid total can still fail when it does not equal the service lines.

A worked example

The secondary claim includes the primary payer payment and adjustment details so the next payer can understand how the remaining balance was calculated.

For 837P Secondary Claims and Coordination of Benefits, our audit trail includes the internal claim ID, destination, file name, control numbers, creation time, claim count, total charges, and every response received.

Where the process breaks down

  • Submitting a secondary claim as if it were primary
  • Sending only the primary EOB as an attachment
  • Failing to balance paid and adjusted amounts

If a receiver rejects 837P Secondary Claims and Coordination of Benefits, correct the source record, mapping, or generator that produced it. Editing the exported file may fix one transmission while leaving the defect in the software.

Edits the software should catch

  • Capture primary adjudication
  • Identify payer responsibility order
  • Balance claim and line information
  • Retain the remittance source

A useful validation message for 837P Secondary Claims and Coordination of Benefits identifies the claim or service line, shows the value involved, and explains the relationship that failed. “Invalid file” is not enough for a practical correction.

Apply this in software: Review the electronic 837P filing software for a workflow that keeps claim data, control numbers, exports, and corrections traceable. The payer companion guide and enrollment record still control the final submission.

Related reading

Official source material

Written and reviewed by

1500Software Development Team

Covers the software, printing, validation, export, and troubleshooting steps described on this page.

1500Software Claims Review Team

Reviews field placement, provider roles, source records, and practical correction steps.

Reviewed July 26, 2026. Always follow the receiving payer’s current instructions and companion guide.