Coordination of benefits denials don’t get nearly the attention that authorization or medical necessity denials do, which is a little strange given how frequently they show up and how avoidable they usually are once a practice understands the mechanism. Part of the reason COB denials fly under the radar is that they feel like someone else’s problem — the patient’s other insurance, the other payer’s system, information the practice never had visibility into. But a meaningful share of COB denials are preventable with the right front-end process, and the ones that aren’t preventable at intake are still very fixable once identified correctly.
What coordination of benefits actually is
When a patient has more than one insurance plan, coordination of benefits rules determine which plan pays first (the primary payer) and which pays second (the secondary payer) on any given claim. These rules aren’t arbitrary — they follow fairly standardized industry conventions such as the birthday rule for dependent children covered under both parents’ plans, specific rules for coverage under a spouse’s employer plan versus one’s own, and specific sequencing rules for Medicare relative to employer group coverage, Medicaid, and other payer types. A COB denial happens when the claim is submitted to a payer that the payer’s own records — or the correct COB sequencing rules — indicate should not be billed first.
Why this denial reason is so commonly missed or misunderstood
The practice often doesn’t know about the other coverage at all
Patients don’t always volunteer information about a second insurance plan at intake, sometimes because they forget, sometimes because they don’t realize it’s relevant to the specific visit, and sometimes because the secondary coverage is new or was added mid-year. Front desk intake forms that ask a generic “do you have other insurance?” question, rather than specifically prompting for common scenarios (a spouse’s plan, a parent’s plan for a dependent, a second job’s benefits, Medicare alongside a retiree plan), tend to catch this less reliably than a more structured intake process.
The payer’s COB information is stale
Even when a practice correctly identifies and bills the primary payer, that payer’s own internal COB records might be outdated — reflecting a previous employer’s plan, a coverage period that’s already ended, or a spouse’s plan the patient is no longer on. This produces a denial that has nothing to do with anything the practice did wrong; it requires the patient (or the practice, on the patient’s behalf) to directly update COB information with the payer, which is a process the payer generally controls and that the practice can only prompt, not perform itself.
Sequencing rules are genuinely counterintuitive in some situations
The rules determining primary versus secondary status aren’t always obvious. A common source of confusion involves Medicare beneficiaries who are still working and covered under an employer group health plan, where the sequencing depends on factors like the size of the employer, or dependents covered under divorced or separated parents’ plans, where sequencing may depend on custody arrangements or court orders rather than simple birthday-rule logic. Billing staff who don’t regularly encounter these specific scenarios can apply the wrong default assumption.
Building a front-end process that actually catches this
Ask specifically, not generically
Rather than a single yes/no question about other insurance, intake processes that specifically prompt for the common scenarios — spousal coverage, dependent coverage under both parents, Medicare alongside other coverage, recent job changes — surface COB situations far more reliably than a generic prompt that patients can answer reflexively without really considering the question.
Re-verify periodically, not just at first registration
Coverage situations change — patients get married, get divorced, change jobs, age onto Medicare, or add a spouse’s plan. A COB check that only happens once, at the patient’s very first visit, will miss changes that happen years later. Building a periodic re-verification into the registration workflow (annually, or whenever a patient’s plan information changes) catches these before a claim goes out to the wrong sequence.
Train staff on the sequencing conventions, not just the intake question
Front desk and billing staff who understand the actual sequencing logic — not just “ask if there’s other insurance” — are better positioned to ask the right follow-up questions and correctly identify which plan is primary before the claim is ever submitted, rather than finding out from a denial weeks later.
When a COB denial does come in, act on it directly rather than resubmitting blindly
A COB denial usually requires one of two corrective paths: either resubmitting to the correct primary payer identified through the denial explanation, or prompting the patient to directly contact the payer that denied the claim to update their COB information on file, since the practice generally cannot update another payer’s COB records itself. Simply resubmitting the same claim to the same payer without addressing the underlying sequencing issue typically produces the same denial again.
Why this deserves more attention than it usually gets
Because COB denials often get lumped into a generic “eligibility” or “other” denial category in internal reporting, many practices don’t have visibility into just how much of their denial volume this actually represents. Pulling COB-specific denial codes out as their own tracked category — rather than leaving them buried inside a broader eligibility bucket — tends to reveal a more significant and more addressable volume than most billing teams expect going in.
A practitioner’s note
Billers who’ve worked a lot of COB denials often mention a particular pattern: the patient is frequently annoyed at being asked, again, about other insurance they thought the practice already knew about — because from the patient’s perspective, they mentioned it once and assume it’s on file forever. Framing the re-verification question as routine and quick (“just confirming this is still your primary coverage”) rather than implying the patient did something wrong the first time tends to get a more complete and cooperative answer, and avoids the friction that makes patients less forthcoming on future visits.
Takeaway: Coordination of benefits denials are more common and more preventable than their low profile suggests — the fix starts with a more specific front-end intake question and periodic re-verification, not just a better denial workflow after the fact. Track COB denials as their own category rather than folding them into general eligibility denials, and you’ll likely find more addressable volume than expected.