Coordination of Benefits Agreement explained
Under COBA, Medicare's Benefits Coordination & Recovery Center sends adjudicated Medicare claim data to the supplemental insurer automatically, so the provider doesn't need to file the secondary claim separately. The 835 indicates when a claim has been crossed over.
Crossovers do fail, for example when the patient's supplemental ID is out of date. Practices should monitor crossed-over claims for secondary payment and file directly when a crossover doesn't arrive.
Where Coordination of Benefits Agreement fits in the revenue cycle
Coordination of Benefits Agreement sits within the payer landscape the revenue cycle operates within. It identifies a type of payer or coverage program whose rules shape how claims must be billed.
Coordination of Benefits Agreement is also referred to as COBA. You'll encounter it on payer communications, billing reports, and in conversations between front-office, coding, and accounts-receivable teams.
Why Coordination of Benefits Agreement matters for your practice
Every payer and program has its own rules, fee schedules, and filing requirements. Knowing the differences between Medicare, Medicaid, commercial, and specialized programs is fundamental to billing each claim correctly the first time and coordinating benefits when a patient has more than one coverage.
- Identifies a payer or coverage program and its rules
- Each program has distinct billing and filing requirements
- Critical for correct coordination of benefits
- Rules differ across Medicare, Medicaid, and commercial plans
Coordination of Benefits Agreement in practice
Knowing what Coordination of Benefits Agreement means is only useful if it changes what your team does. In a modern revenue cycle, that means catching issues related to payer & Program Types earlier, documenting and coding them correctly, and using technology to flag exceptions automatically rather than discovering them after a claim is denied.
This is exactly where a specialty-built revenue cycle platform earns its keep: by encoding the rules behind terms like Coordination of Benefits Agreement directly into the workflow, so clean claims go out the first time and your team works by exception instead of chasing problems after the fact.
