Article: COB Denials Are Different: Three Misconceptions Revenue Cycle Leaders Should Consider

A Coordination of Benefits (COB) denial occurs when responsibility for a medical claim has not been fully resolved across multiple insurance plans. The issue may involve which payer is primary, whether other coverage exists, or whether additional information is needed from the patient before the claim can be processed.

These denials create both financial and operational burdens for health systems. In an HFMA survey of 102 hospital CFOs, 22% said their organizations had increased patient-billing staff specifically to manage coordination-of-benefits issues during the prior three years.

Yet COB is often treated like a traditional eligibility or denial-management problem. Complex COB denials require something different: investigation across multiple coverage sources, payer-specific sequencing and, when necessary, informed patient engagement. These cases often result from a significant life change, such as the birth of a child, or if an accident has occurred and it is not immediately clear if a third-party insurance may be responsible for coverage.

The following three misconceptions help explain why COB requires a more specialized approach.

 #1: “Eligibility accuracy and front-end tools will prevent COB denials.” 

Better front-end eligibility verification and registration accuracy will prevent some COB denials, particularly when the problem is specific and isolated. Common mistakes at registration could be a wrong member ID, an incorrect date of birth, coverage that existed for a patient but was not retrieved, or another clean data mistake that can be identified and corrected upfront. Leveraging front-end tools will assist with simpler problems, but they cannot resolve every situation in which coverage is incomplete, or when conflicting data emerge later.

For revenue cycle leaders, resolving COB issues beyond the front end is vital for increasing the bottom line. Common reasons for COB denial include:

  • During a period of care, coverage or circumstances change for the patient after registration.
  • A second policy through a spouse, a third-party as a result of an accident, or a payer's annual coordination questionnaire may require additional action before the payer will move forward on a claim.
  • Determining which payer is primary and which is secondary can become a sequencing and adjudication problem governed by plan rules and payer requirements, even when both policies are known when the claim is made.

Revenue cycle leaders should take heed: front-end tools reduce data errors; they do not eliminate multi-payer coordination, sequencing, discovery or a patient-action requirement.

As front-end technology improves, the remaining COB inventory may shrink. But revenue cycle leaders will need to contend with more cases requiring investigation, payer-specific knowledge, judgment, and sometimes a conversation with the patient.

 Looking beyond the front end? Explore answers to common questions about resolving COB and patient-involvement denials, including where eligibility tools end and specialized investigation begins. 

 #2: “COB is just another denial category. Our normal denial workflow can handle it.” 

A COB denial enters the same queue as other denials, but the work required to resolve it follows a fundamentally different path.

Many denial categories follow a relatively repeatable sequence: identify the error, obtain the required documentation, correct or appeal the claim, and follow it through payment. COB is different because the next action depends heavily on why the payer is questioning coverage and what information is actually missing.

One COB scenario may require research into a second active policy. Another may require determining the correct order between two known payers. A third may require clinical documentation that can substitute for an accident questionnaire. Another may ultimately require the patient to confirm information that does not exist elsewhere, for example, a recent life event such as retirement or birth.

That makes COB a triage problem at the outset.

A mature approach to COB within an organization requires people who:

  • understand payer-specific forms and requirements
  • know when existing documentation can resolve the issue without involving the patient
  • recognize when additional coverage research is warranted
  • understand when to engage the patient directly

Establishing an effective process is also critical. COB accounts need to be routed to the appropriate next action: payer investigation, coverage discovery, documentation submission or patient engagement. They need payer-specific documentation, disciplined follow-up and closed-loop rebilling. When payer requirements change, there needs to be expertise within the organization or via specialty partners to address those changes.

Managing COB claims requires enough pattern recognition across payers and denial types to know not just that an account is denied, but what specific action has the highest probability of success. This complexity requires a nuanced operating principle: investigate first, involve the patient only when necessary, and approach the interaction as a resolution rather than a collection.

 COB denials can quietly drain revenue and staff resources. See why it may be time to rethink how you prioritize and resolve them . 

 #3: “If the patient needs to be involved, our normal outreach process should be sufficient.” 

This is where many otherwise sound COB processes break down.

A patient involved in a COB denial often does not owe the hospital money; however, they may hold information that the payer requires to adjudicate the claim.

Yet a generic communication chain places the burden of solving an unfamiliar insurance problem on the patient, and can feel confusing or aggressive. The context and posture of patient outreach is an important piece of caregiving in the eyes of the consumer. Because COB issues frequently arise during significant life events such as a birth or accident, the patient may not understand why an insurer has stopped processing the claim, what information is missing, or why the hospital is contacting them.

KLAS reached a similar conclusion in its 2026 research on COB and patient-involvement denials, noting that these situations require heightened sensitivity and a specialized approach, and that standard mailings and sequenced phone calls are not sufficient. The research identifies patient advocacy, engagement and satisfaction as attributes associated with a more individualized, multichannel model.

This does not mean “more outreach” or a one-size-fits-all resolution model. It may mean a portal or text for one patient, a direct call for another, a three-way conversation with the payer when the patient cannot navigate the issue alone, and in exceptional cases, an in-person visit. Just as important, the process begins by determining whether the patient needs to be contacted at all. The operating principle should be to investigate first, advocate second. Providers should resolve the issue through payer research or available documentation wherever possible, and engage the patient only when their action is genuinely required.

Patients do not generally distinguish between a hospital and the organization helping resolve an insurance issue. A respectful, low-friction process protects the relationship with the patient while helping move the claim toward payment.

Learn how to make COB resolution more patient-centered. Explore five ways health systems can improve COB and patient-involvement denials through patient centricity.

In COB, patient engagement is not the final step in a collection workflow. It is a specialized resolution capability, and how it is handled can determine whether the claim gets paid and if the patient has a satisfactory experience along the way.

Knowtion Health is a specialized post-claim revenue partner for U.S. health systems. Discover how we can help by emailing: services@knowtionhealth.com or visiting our solutions page to learn more: https://www.knowtionhealth.com/cob-patient-involvement-denials