Coordination of Benefits Denials: When the Payer Thinks Another Plan Is Primary

When a patient has more than one plan, only one is primary — billed first and adjudicating as though no other coverage existed — and the rest are billed in order behind it. Which plan is primary is set by rule, not by anyone's preference. A coordination-of-benefits denial is what a payer returns when the claim it received does not fit the position it believes it holds in that order: either it thinks it is not first and another plan should pay before it, or it accepts that it is secondary but has nothing from the primary to coordinate against.

The distinction that matters most is that this is a coverage-order problem, not a content problem. The payer is not questioning whether the service was necessary or whether the codes were right; it is questioning who should be paying, and in what order. That is why re-coding a COB denial or arguing the merits of the care does nothing — the claim never reached the question the coding would answer. On the remittance it typically arrives as CARC 22, the code for a service that may be the responsibility of another payer under coordination of benefits, or as CARC 109 when the payer is saying the claim as a whole belongs to a different payer or contractor entirely.

Almost every COB denial is one of two situations, and reading the remittance to tell which is the single most useful thing to do before touching the claim, because the response to each is the opposite of the other.

The reason the two are worth separating so firmly is that they send the claim to different places. The missing-information denial is finished inside the billing office: retrieve the primary's remittance and resubmit the secondary claim carrying it. The coverage-order denial usually cannot be — it turns on a record the payer holds and the practice does not, which is the subject of the next section.

Before working the denial, settle who owns the balance, because the instinct to move an unpaid amount to the patient is exactly wrong here. As everywhere in this cluster, it is the group code, not the reason code, that assigns responsibility. The same CARC 22 can appear as CO-22 or PR-22, and the prefix is the whole difference: a contractual-obligation code makes the amount the practice's to pursue, while a patient-responsibility code assigns it to the patient.

The structural difficulty behind coverage-order denials is an asymmetry of information. The payer maintains a record of the patient's other coverage and its position in the order; the practice does not, and cannot see it directly. A front desk can ask every right question and get honest answers, verify each plan, and submit in good faith — and the claim can still be denied because the payer's own record says something different, or says nothing, because it was never updated when the patient's coverage changed.

That is why so many coverage-order denials are resolved not in the billing office but by the patient. The record lives with the plan, and the plan generally will not change it on a provider's say-so; the subscriber has to contact the plan and correct it — confirm that other coverage has ended, or that this plan is in fact primary — before the payer will reprocess. Until that happens, the claim can keep denying no matter how it is resubmitted, because nothing about the claim is what the payer is objecting to.

Medicare — the Benefits Coordination & Recovery Center (BCRC)

For Medicare, other-coverage information is held centrally by the Benefits Coordination & Recovery Center under the Coordination of Benefits & Recovery program, and it drives whether Medicare pays primary or secondary under the Medicare Secondary Payer rules. When a claim denies because Medicare's record shows another payer as primary, the beneficiary generally has to resolve it with the BCRC. The MSP framework itself — when Medicare is secondary, and to what — is the subject of Medicare Secondary Payer billing.

Commercial plans — the plan's own COB record

Private plans keep their own coordination-of-benefits records and periodically ask members to confirm whether they have other coverage. A denial can trace to nothing more than an unanswered COB verification, which the plan reads as unresolved and holds claims against. The member updating that record with the plan is usually what releases the claim.

1. 01

   Read the remittance to identify which denial it is

   Start with the reason and remark codes and the group-code prefix. A missing-primary-information denial (CARC 16 with RARC MA04 or N4) and a coverage-order denial (CARC 22 or 109) look similar at a glance and take opposite responses, so this read comes before anything else.
2. 02

   If the primary's information is missing, complete the claim

   This is not an appeal and not a coverage dispute. Retrieve the primary payer's remittance, and resubmit the secondary claim carrying the primary's allowed amount, payment, and adjustments — the detail the secondary needs to coordinate. The mechanics of building that claim, and why line-level posting of the primary is what makes it possible, are covered in secondary billing.
3. 03

   If another plan is genuinely primary, bill that plan first

   Where the payer is right that a primary plan was missed, the fix is to bill the correct plan first and then submit to this one as secondary. The order is set by rule, and confirming it belongs to the registration work described in identifying primary and secondary coverage — the point at which the missed plan should have been caught.
4. 04

   If the payer's record is wrong, get it corrected

   Where there is no other primary — the other coverage has ended, or this plan really is first — the claim will keep denying until the payer's record is fixed. That generally means the patient contacting the plan (or the BCRC, for Medicare) to correct it, or supplying proof such as a termination letter, after which the payer reprocesses. Resubmitting an unchanged claim against an unchanged record only repeats the denial.
5. 05

   Watch the filing clock while the record is corrected

   COB back-and-forth is slow, and the timely filing window keeps running while it happens — which is how a resolvable COB denial turns into an unappealable timely-filing denial. Keep dated proof of each submission and each contact with the payer and patient, so an eventual filing-limit exception can be argued from a record.

An actual appeal is the last resort here, not the first move, because most COB denials are resolved by completing the claim or correcting a record rather than by disputing a decision. Where the payer will not reprocess despite a corrected record or an attached primary remittance, the question of whether and how to appeal — and what governs the deadline — is set out in appealing a denial, and what to assemble first is in the denial appeal readiness checklist.

Like most of the front-end denials, COB denials are produced before the claim is ever built — at registration, where the patient's full set of coverage and its order is either captured or missed. Prevention lives there rather than in the billing office.

A second plan was never captured

The most common source: the patient presented one card, and the other coverage — a spouse's plan, Medicare alongside a group plan, an injury carrier — was never asked about. Making “any other coverage?” a standard registration prompt is what catches it.

The order was captured but out of date

Coverage order changes — a job changes, a plan ends, Medicare begins — and a patient seen before is not the same patient this visit. Re-verifying recurring patients is what keeps the order current.

The payer's COB record was stale on its side

The one the practice cannot prevent. Even a perfectly captured claim denies when the payer's own record is wrong, and the only fix is the correction described above. Anticipating it — knowing the denial for what it is and routing it to the patient quickly — is the realistic control.

Coordination of benefits is one of the recurring categories mapped in why claims get denied, and the front-end controls that reduce it are the ones set out in preventing denials. The rest of this cluster is indexed on the Denials & Appeals pillar.