US Medical BillingRevenue cycle solutions

How to handle dual-eligible claims

A step-based operational guide to processing claims for beneficiaries enrolled in both Medicare and Medicaid: confirming dual status, sequencing payers correctly, working crossover claims, and preventing the coordination-of-benefits denials that stall these accounts. Rules vary by state and plan, so the guide points to authoritative sources rather than quoting figures.

8 minute read · Reviewed 2026-07-18

Understand what a dual-eligible claim is

A dual-eligible beneficiary is a person enrolled in both Medicare and Medicaid. Medicare covers the beneficiary as a federal program, while Medicaid, administered by each state, coordinates behind it. Because Medicaid is generally the payer of last resort, the sequencing of these payers — and how much each pays — is the core of what makes these claims distinct from single-payer Medicaid claims.

Dual status is not uniform. Some beneficiaries are 'full-benefit' duals who receive the complete Medicaid benefit package, while others are 'partial' duals whose Medicaid coverage is limited to help with Medicare premiums and cost-sharing through the Medicare Savings Programs. The category assigned to a beneficiary determines what, if anything, Medicaid is obligated to pay after Medicare adjudicates. These categories and their exact benefits are defined by federal rules and implemented differently by each state, so the applicable specifics should be confirmed with the state Medicaid agency and Medicaid.gov.

Getting the category right at the front end shapes every downstream decision: which payer is billed first, whether a secondary claim is warranted, and how patient responsibility is handled. Misreading the category is one of the most common root causes of misrouted dual-eligible claims.

  1. 1Confirm the beneficiary is enrolled in both Medicare and Medicaid, not one program alone.
  2. 2Identify whether the person is a full-benefit or partial-benefit dual, since this drives Medicaid's payment obligation.
  3. 3Note the specific Medicare Savings Program category where applicable, as it defines which cost-sharing Medicaid may cover.
  4. 4Document the source and date of the status check so the file reflects coverage as of the date of service.

Verify coverage and establish payer order

Before a service is billed, both coverages must be verified independently. Medicare eligibility is confirmed through the Medicare eligibility systems, and Medicaid eligibility is confirmed through the state's Medicaid verification channel. Coverage can change month to month, so verification should reflect the actual date of service rather than a prior check. Strong eligibility verification is the single most effective control against dual-eligible denials.

Payer sequencing follows from the coverage picture. For services covered by Medicare, Medicare is billed first and Medicaid is considered only after Medicare has adjudicated. Where a beneficiary is enrolled in a Medicare Advantage plan rather than Original Medicare, that plan takes Medicare's place as the first payer, which changes where the primary claim is sent. The principle that Medicaid pays after other coverage is structural; the exact amount Medicaid pays after Medicare is governed by state policy and should not be assumed.

Provider enrollment underpins all of this. To be paid by either program, the rendering provider generally must be enrolled with Medicare and with the relevant state Medicaid program. Enrollment gaps on either side are a frequent, avoidable cause of dual-eligible claim failures.

  1. 1Verify active Medicare (or Medicare Advantage) coverage for the date of service through the appropriate eligibility channel.
  2. 2Verify active Medicaid coverage for the same date through the state Medicaid verification tool.
  3. 3Determine the primary payer — Original Medicare, a Medicare Advantage plan, or another liable third party — before submitting anything.
  4. 4Confirm the provider is enrolled with both the primary payer and the state Medicaid program.
  5. 5Capture coordination-of-benefits details so the secondary claim can be built from accurate primary payment data.

Submit and work the crossover claim

Once Medicare adjudicates, the remaining balance flows to Medicaid as a secondary, or 'crossover,' claim. In many cases the primary payer transmits the claim to Medicaid automatically through an established crossover process, and no separate submission is required. In other cases the secondary claim must be filed directly with the state Medicaid program using the primary payer's remittance advice as support. Whether crossover is automatic depends on the payers and the state, so this should be confirmed rather than assumed for each payer relationship.

When a secondary claim is filed directly, it is built on the professional or institutional claim format appropriate to the service and must carry the primary payer's adjudication details — allowed amount, paid amount, and adjustment reasons from the remittance advice. Accurate coordination-of-benefits data is what allows Medicaid to calculate any secondary liability correctly. Timely filing clocks still apply on the Medicaid side, and those limits are set by each state, so the applicable deadline should be checked with the state agency.

Because dual-eligible cost-sharing is complex, it is important to respect the rules that protect these beneficiaries. Balance-billing a dual-eligible beneficiary for Medicare cost-sharing is restricted under federal law for many dual categories; the specifics should be confirmed against CMS guidance and state policy rather than handled ad hoc.

  1. 1Determine whether the primary payer auto-crosses the claim to Medicaid or whether direct secondary submission is required.
  2. 2If filing directly, build the secondary claim with the primary remittance advice attached or its adjudication data reported.
  3. 3Report allowed, paid, and adjustment amounts from the primary payer accurately so Medicaid can compute secondary liability.
  4. 4File within the state Medicaid timely-filing window, tracking from the correct trigger date.
  5. 5Avoid billing the beneficiary for protected Medicare cost-sharing; verify the applicable protection before any patient balance is pursued.

Resolve and prevent common denials

Dual-eligible denials cluster around a few predictable causes: the claim was sent to the wrong payer first, coordination-of-benefits information was missing or mismatched, the beneficiary's coverage had lapsed on the date of service, or the provider was not enrolled with one of the programs. Reading the remittance advice carefully — the specific reason and remark codes — tells the biller which of these applies before any rework begins.

Effective resolution starts with the root cause rather than resubmitting blindly. A sequencing error is corrected by billing the true primary payer first; a coordination-of-benefits mismatch is corrected by aligning the secondary claim with the primary's actual adjudication; a coverage-date problem is corrected by re-verifying eligibility for the exact service date. Where medical necessity or authorization drove the denial on the primary side, that issue must be cleared with the primary payer before Medicaid will consider the balance.

Prevention is more durable than appeals. A front-end workflow that verifies both coverages, confirms dual category, checks provider enrollment, and captures coordination-of-benefits data at registration eliminates the majority of these denials before a claim is ever built. Tracking denial reasons over time reveals which control is failing and where to focus.

  1. 1Read the remittance advice and isolate the specific denial reason before taking any action.
  2. 2Match the denial to its root cause: sequencing, coordination of benefits, coverage dates, or enrollment.
  3. 3Correct the underlying issue — rebill the true primary, align secondary data, or re-verify eligibility — rather than resubmitting unchanged.
  4. 4Resolve any primary-payer authorization or medical-necessity problem before pursuing the Medicaid balance.
  5. 5Feed recurring denial reasons back into the front-end workflow to prevent repeat failures.

Authoritative sources

Related Knowledge