Skip to content
English
More support Customer portal
Contact us
  • There are no suggestions because the search field is empty.

Troubleshooting Medicaid COB Denials for Medicare Crossovers

This article explains documented, concrete reasons why Medicaid may deny secondary claims as coordination-of-benefits (COB) denials related to Medicare crossover payments, and gives practical steps to verify and troubleshoot those causes.

What immediate reasons have been observed for Medicaid denying secondary claims as coordination-of-benefits?

Medicaid denial messages stating “care may be covered by another payer as per coordination of benefits” have been observed when the primary payer is a Medicare or Medicare Advantage plan (examples: Aetna, United Healthcare, Fidelis, BlueCross Medicare). These denials occur even after the primary Medicare/Medicare Advantage claim was billed, paid, autoposted, and transmitted to Medicaid as a secondary.

Why might a correctly billed Medicare primary still lead to a Medicaid COB denial?

Three operational causes have been documented:

  • System processing for multiple EOBs: processing logic that handles multiple EOBs can malfunction, causing secondary transmissions or status updates not to be recognized by Medicaid.
  • Secondary claim not available to attach to the secondary payment: when the Medicare crossover/secondary payment posts, the corresponding secondary claim record may not be present or available for matching/attachment, producing a COB denial.
  • Autoposting out-of-balance: autoposted payments or adjustments that leave account balances inconsistent can contribute to denial outcomes when Medicaid evaluates coordination of benefits.
What should you do first to verify the situation?
  1. Confirm the primary Medicare or Medicare Advantage claim was billed and shows as paid.
  2. Verify the primary EOB was autoposted and that the system transmitted the claim/payment to Medicaid as a secondary.
  3. Check that a secondary claim record exists and is in a state where it can be matched to the incoming Medicare crossover payment before posting the payment.
How should you post Medicare EOBs to avoid issues?
  • Post Medicare EOBs following your standard posting workflow. Before posting, confirm the steps in the "What should you do first to verify the situation?" section above — specifically that the secondary claim record exists and is available for matching — so Populate's EMR can recognize the payment as a secondary crossover and transmit it to Medicaid correctly.
What troubleshooting steps can reduce the chance of a COB denial?
  1. Reconcile the primary payment posting and ensure the autopost did not leave an out-of-balance condition.
  2. Confirm the secondary claim was created/transmitted to Medicaid prior to or available at the time the crossover payment posts.
  3. If multiple EOBs are involved, review processing logs or status for all related EOBs to ensure none failed or remained unprocessed.
  4. If a denial occurs, include information about the primary payer (Medicare Advantage plan name), dates of service, and whether the primary payment was autoposted when escalating.
When should this be escalated to engineering or support?

Escalate to engineering or support when normal reconciliation steps cannot resolve the denial. Specific conditions that require escalation include:

  • A Medicaid COB denial persists after you have confirmed the primary payment was made, the secondary claim was transmitted, and the autopost balance is correct.Multiple related EOBs show processing errors or inconsistent status.
  • Secondary claims are not available to attach when crossover payments arrive.
  • Autoposting produced account imbalances that you cannot resolve through normal reconciliation.