A claim can have more than one payer. Coordination of benefits (COB) establishes which plan pays first and how another plan may consider the remaining claim. The Centers for Medicare & Medicaid Services describes COB as a way to determine each plan’s payment responsibility when a person has multiple coverages. When the primary payer has adjudicated the claim, the next submission needs to preserve that decision as evidence—not turn it into a fresh guess.
That handoff is where the primary payer’s explanation of benefits (EOB) matters. It reports how that payer processed the claim: the billed charge, allowed amount, payment, adjustments and the portion assigned to the member, among other details. A secondary payer uses prior adjudication information as part of its own review. The exact rules and fields depend on the payer, plan and transaction; an EOB does not determine the secondary benefit by itself.
CMS describes electronic COB claims as claims sent to a secondary payer with adjudication information from a prior payer. In its Medicare COB process, CMS also explains that certain Medicare-paid claims can be transmitted to supplemental insurers under an agreement, while other cases require the beneficiary to coordinate payment. The practical lesson is narrow: the record of the first decision must remain attached to the claim that asks the next payer to consider it.
CMS: Coordination of benefits transaction · CMS: Coordination of Benefits
Carry each line’s decision forward
The most useful review starts at the service line, where a payer’s amounts and reasons attach to a particular service. A claim may contain several lines with different allowed amounts, adjustments or patient responsibility. Flattening the EOB into one total can hide which decision belongs to which procedure—and make the next claim harder to reconcile.
| Primary EOB value | Use in secondary-claim preparation | If it is missing or detached |
|---|---|---|
| Claim and member identifiers | Match the EOB to the patient, coverage and claim being coordinated | A correct payment may be attached to the wrong claim or member |
| Service-line dates and procedure context | Keep each adjudication result paired with the service it describes | Amounts can be attributed to the wrong line or date |
| Billed charge and allowed amount | Show the charge submitted and the amount recognized by the primary payer | A secondary reviewer cannot see the primary payer’s pricing basis |
| Paid amount | Record what the primary payer paid for the claim or line | The next submission can overstate the amount still outstanding |
| Adjustments and reason codes | Preserve why the primary payer changed or denied an amount | A contractual adjustment or denial can look like an unexplained balance |
| Deductible, coinsurance and other member responsibility | Keep the EOB’s stated allocation visible for downstream review | Member responsibility may be mistaken for an unpaid payer balance |
This is a preparation map, not a universal billing formula. A secondary plan may apply its own benefit rules, coordination method and limits. Do not calculate a secondary payment by subtracting the primary payment from the charge, or assume that a patient-responsibility amount is automatically payable by another plan. The reviewer needs the first payer’s evidence and the second payer’s rules.
Preserve the reason, not just the amount
Two EOB lines can show the same payment and still mean different things. One may have reached the payer’s allowed amount with a contractual adjustment; another may have been reduced because a service was not covered or more information was required. The adjustment or denial explanation is part of the adjudication. Keeping the code with its explanatory text helps an operations team distinguish a priced line from a denial or an unresolved question.
The same applies to member responsibility. Deductible, coinsurance and copayment are not interchangeable labels. A value should stay linked to the category the EOB actually reports, along with the relevant line and claim. If a document gives only a claim-level amount, preserve that scope instead of allocating it across lines without evidence.
When the EOB is scanned or faxed, source citations make the extracted result reviewable. A reviewer should be able to open the source region for a paid amount, adjustment code or member responsibility and confirm that the value was read from the right line. Low-confidence, missing or inconsistent fields should be flagged for review; they should not be silently filled from a neighboring row.
Common handoff failures
- One total replaces line detail — the secondary record loses which service and decision produced each amount.
- Paid and allowed are swapped — the primary payer’s recognized amount is confused with its actual payment.
- An adjustment is treated as payment — the outstanding balance appears different from the EOB’s adjudication.
- A denial reason is dropped — the next reviewer sees a zero or reduced payment without the context needed to understand it.
- Member responsibility is relabeled — deductible or coinsurance is carried as an assumed secondary benefit.
- The claim is matched by amount alone — similar totals can belong to different members, dates or service lines.
These errors are often data-handling failures rather than difficult policy questions. A repeatable check can compare the primary EOB’s claim identity, line count, allowed amounts, payment, adjustments and member-responsibility categories with the values prepared for the secondary submission. Differences become review items; the check does not decide what the next plan owes.
Confirm payer order before carrying values forward
An EOB tells you what one payer did with a claim. It does not, on its own, establish that this payer was primary, that another plan is secondary, or that the second plan will cover the remaining amount. Payer order depends on the person’s coverage and the applicable coordination rules. CMS describes its COB process as a way to identify the plans involved and establish which one pays first; its Medicare examples also show that the order can change with circumstances such as employment coverage and other insurance.
For operations teams, that means keeping the coverage decision separate from document extraction. Confirm the relevant plans and order through the payer’s eligibility or coordination process. Then link the primary EOB to the claim being prepared for the next payer. If the member, provider, date of service or claim reference does not match, stop and resolve the mismatch before moving amounts forward. A similar total is not a safe substitute for a verified claim match.
This separation also prevents a common assumption: that the “secondary” payer simply pays whatever the first payer did not. The second plan adjudicates under its own coverage terms and coordination rules. A balance on an EOB may include a contractual write-off, a noncovered service, a deductible, coinsurance or a denial. Those categories can have different consequences. The extracted record should preserve the category and source wording so a qualified billing reviewer can apply the appropriate rule.
CMS’s electronic COB transaction overview describes a COB claim as one sent with adjudication information from a prior payer. That prior decision is relevant input, while the receiving plan remains responsible for its own determination. Keep the original EOB available alongside any normalized fields: a compact structured record speeds review, and the source document resolves questions about labels, context and exceptions.
Follow one claim across two service lines
Consider a hypothetical claim with two service lines. The primary EOB shows that the first line was processed with an allowed amount and a payment, while the second line has a separate adjustment and an explanation. A preparation workflow should retain both line results under the same claim, with each amount and reason attached to the correct service. It should not copy the first line’s payment pattern onto the second or replace both outcomes with one net total.
| Illustrative primary EOB record | What to retain for review | Question for the secondary workflow |
|---|---|---|
| Line 1: service date, procedure context, allowed amount, paid amount and member share | The complete line values, the EOB’s labels and the source region | Does the next payer require this line-level adjudication data, and is the service covered under its rules? |
| Line 2: its own service date, adjustment or denial code and explanation | The reason code and explanatory text, without substituting a neighboring line’s reason | Does the reason call for additional documentation, a corrected claim or a different review path? |
| Claim-level totals and payer reference | The total scope and identifier as printed, kept separate from individual line amounts | Do the line records and claim summary reconcile to the source, or is there an unresolved difference? |
The example is about preserving evidence, not calculating a benefit. No single subtraction reliably determines what a second plan owes across all plans and situations. A workflow can compare extracted values with the source, identify gaps and assemble the prior adjudication context. The payer’s rules and an authorized reviewer determine what to submit and how to interpret the response.
Keep the handoff record traceable
A clean handoff can be organized around a few linked records rather than a single flattened row: the member and coverage context, the claim identity, each service line, each adjudication outcome and the source document. The relationship matters as much as the values. A paid amount belongs to a payer, claim and line; an adjustment belongs to the decision that produced it; member responsibility belongs to the scope the EOB identifies.
For every extracted field, preserve the exact value, the printed label, its scope (claim or service line), the source location and any confidence or review flag the extraction system provides. Keep codes and descriptions together when both appear. If a code is present but the explanation is on another page, record that relationship rather than treating the code as a complete explanation. If the document does not state a value, represent it as absent instead of inventing zero.
Document identity should travel with the structured record. A payer claim control number, member identifier and service dates help a reviewer distinguish this EOB from another claim for the same person. Where identifiers are masked or partially redacted, retain what the document actually shows and route an uncertain match to review. Do not silently complete a number from a prior claim or infer a payer from a logo alone.
The original document remains the evidence of record for this extraction. Keep the primary EOB and the secondary submission or response connected through the organization’s approved recordkeeping process. Limit access to the people and systems that need the information, and follow the organization’s privacy and retention requirements. The article’s data examples are operational guidance, not a substitute for a payer’s transaction companion guide or an organization’s compliance review.
Make exceptions visible before submission
A useful quality check compares the prepared handoff against the EOB before it leaves the billing workflow. Start with claim identity and service-line count. Check that each date and procedure context has the corresponding primary payer outcome. Compare allowed amount, payment, adjustment, denial reason and member-responsibility fields within their stated scope. Reconcile totals only where the source defines a comparable total; do not force a balance by allocating claim-level values across lines.
- Identity mismatch — member, payer, claim number or service date does not agree across the EOB and work item.
- Missing or repeated line — a service line disappeared, appeared twice or was merged with a similar line.
- Amount outside its context — a claim total was attached to a service line, or an allowed amount was read as payment.
- Reason without evidence — an adjustment or denial code is present but the EOB’s explanation was not retained.
- Uncertain reading — an amount, code or identifier is obscured, low confidence or inconsistent with the source total.
Route these cases to a person with the original EOB open. The goal is to resolve the evidence gap or document why the claim needs a different handling path. A review flag should not be treated as approval to submit, and an automated consistency check should not overrule the payer’s adjudication.
Build a reviewable extraction
A useful EOB extraction keeps claim-level and service-line fields separate, retains the original labels and code descriptions, and points each value back to its source. It should also preserve document identity and flag totals that do not reconcile, duplicated or missing lines, and values with weak evidence. These controls make the handoff easier to inspect without claiming that document extraction performs COB adjudication.
For a workflow benchmark, test a mix of EOB layouts, multiple service lines, partial payments, adjustments, denial codes and member-responsibility categories. Check whether the result captures patient, provider, payer, claim number, service dates, billed and allowed amounts, paid amounts, adjustments and reason codes with line-level evidence. Include pages where the explanation spans a continuation sheet, and confirm that the record does not merge similar lines.
Cogneris’s EOB extraction workflow describes structured extraction for claim and service-line details, including allowed and paid amounts, adjustments, denial codes and member responsibility, with source citations and review flags. That supports preparing EOB data for an operations team to inspect. It does not claim to determine payer order, interpret a plan’s COB rules or calculate the secondary benefit.
The primary EOB is evidence for the next decision
In a coordinated claim, the first payer’s EOB explains what was submitted, what was recognized, what was paid and why the remaining amount was classified as it was. The secondary payer makes its own decision under its own rules. Keeping the original claim identity, service-line context, amounts and reasons together gives that review a defensible starting point.
For healthcare operations, the goal is not to make the first EOB answer the second payer’s question. It is to carry the first decision forward accurately enough that the next reviewer can see the evidence, identify gaps and apply the right coverage rules.