Coordination of benefits is among the most administratively complex workflows in healthcare billing. When a patient has coverage under two insurance plans, both payers need to receive the claim, and the primary payer’s determination needs to be documented and transmitted before the secondary payer can process its portion. Every step of that process generates documentation that moves between the provider, the primary payer, and the secondary payer, and fax is the channel that carries a significant portion of that documentation in most markets.
The coordination of benefits process is not just administratively complex. It is financially consequential. Errors in COB sequencing, missing documentation, or failed transmissions between payers and providers result in delayed payments, underpayments, and in some cases claim denials that require full appeals to resolve.
How the COB Documentation Workflow Operates
The coordination of benefits process begins when the provider identifies that a patient has dual coverage and determines which plan is primary. That determination is governed by rules that vary based on the type of coverage involved: commercial group plans follow birthday rule or employment status rules, Medicare secondary payer rules apply when Medicare is involved alongside an employer plan, Medicaid always pays last, and coordination between two commercial plans follows the plan’s own COB provisions.
Once the primary payer has processed the claim and issued an explanation of benefits, that EOB needs to be transmitted to the secondary payer along with the original claim for secondary adjudication. In most markets, that EOB transmission happens by fax because the primary and secondary payers are separate organizations that do not share a common claims exchange platform capable of handling every payer combination in a provider’s patient population.
A billing team managing COB claims needs to submit to the primary payer, receive the EOB, transmit the EOB and original claim to the secondary payer, and track the secondary payer’s adjudication, all with documented records of each step in case either payer questions the sequencing or the documentation at any point in the process.
Where Fax Failures Create Revenue Cycle Risk
The COB workflow is particularly vulnerable to the kind of silent fax failure that creates revenue cycle risk without immediate visibility. A secondary payer claim submission that fails to transmit and goes undetected sits as an unpaid balance on the patient’s account until someone investigates why the secondary claim was never processed. By the time the billing team identifies the issue, the secondary payer’s timely filing deadline may have passed, converting a recoverable balance into a write-off.
Passport’s automatic retry logic and failure alerting eliminate that silent failure scenario. When a secondary claim submission fails on the first attempt, the platform retries automatically. If the transmission fails after all retry attempts, the failure surfaces in the Enterprise Status Manager immediately so the billing team can address it before the timely filing window closes.
That proactive failure visibility is the operational difference between a fax platform that supports revenue cycle integrity and one that introduces risk into the COB workflow without the billing team realizing it.
EOB Documentation and Secondary Payer Submission
The explanation of benefits from the primary payer is the foundational document for secondary claim submission. It shows the amount billed, the amount allowed, the amount paid by the primary payer, and the patient responsibility, all of which the secondary payer needs to calculate its own adjudication.
When the primary payer’s EOB arrives by fax, it needs to reach the billing team member responsible for COB claims rather than sitting in a general fax queue where it may be overlooked or misrouted. Passport’s workgroup routing allows billing operations to configure a dedicated queue for inbound EOB documentation, so that primary payer responses route directly to the COB billing team without manual sorting.
For organizations managing COB claims across multiple provider clients or multiple billing departments, routing rules can be configured at the client or department level so that each team sees the EOBs relevant to their assigned accounts.
Medicare Secondary Payer Compliance
Medicare secondary payer rules are among the most compliance-sensitive aspects of COB billing. When Medicare is the secondary payer, the provider must submit the primary payer’s EOB with the Medicare claim to demonstrate that the primary payer has already adjudicated the claim. Failure to follow MSP rules can result in Medicare claim denials and, in cases of systematic non-compliance, potential False Claims Act exposure.
The documentation of MSP submissions, including the record of when the primary EOB was received and when the Medicare secondary claim was transmitted, is a compliance record that providers need to be able to produce during a Medicare audit. Passport’s audit trail provides that documentation for every transmission in the MSP submission workflow, with timestamps and delivery confirmations that support the provider’s compliance posture.
The FAQ Friday post on fax security and privacy covers the full audit record that Passport maintains, which applies to COB and MSP documentation workflows the same way it applies to clinical fax transmissions.
Managing COB Workflows Across High-Volume Billing Operations
For billing operations managing a high volume of COB claims, the combination of dedicated routing queues, delivery confirmation, failure alerting, and centralized audit logging creates a fax infrastructure that supports the COB workflow rather than creating risk within it.
The post on how medical billing companies use fax to support multi-provider clients covers the broader multi-client billing context, and the COB workflow sits within that same operational framework for billing organizations managing dual-coverage claims across a large provider client base.
Schedule a strategy call with the Lane team to discuss how Passport supports coordination of benefits and revenue cycle fax workflows at your organization.
