A dual eligible SNF resident is enrolled in both Medicare and Medicaid. For skilled nursing care under Part A, Medicare is the primary payer for the first 100 days of each benefit period. Medicaid covers cost-sharing (coinsurance, deductibles, copays) but only under specific conditions tied to the resident’s Medicare Savings Program category. That category is not a detail to confirm after admission. It is the billing decision. It determines whether Medicaid covers the daily coinsurance, whether crossover will pay anything at all, and whether federal law prohibits the facility from collecting any cost-sharing from the resident, even if Medicaid never sends a payment.
Most SNF billing teams confirm that a resident is dual eligible before admission. Most do not confirm which Medicare Savings Program category that resident falls into. Those are not the same verification. One tells you the resident has both programs. The other tells you what your billing team can and cannot do.
What Dual Eligible Actually Means in SNF Billing Terms
Medicare Primary, Medicaid Secondary: The Baseline Rule
For Medicare Part A skilled nursing care, the payment sequence works like this: Medicare pays first, Medicaid covers cost-sharing second. The first 20 days of each benefit period carry no coinsurance. Days 21 through 100 carry a daily coinsurance of $217 in 2026 (Source: Federal Register, CY 2026 Medicare Part A Coinsurance). Medicaid steps in to cover that coinsurance for qualifying residents.
Once Medicare Part A benefits are exhausted, after 100 days or when skilled care is no longer medically necessary, Medicaid becomes the primary payer for long-term custodial care. At that point the billing sequence inverts entirely. The facility bills Medicaid directly, not Medicare.
Why Dual Eligible Is Not a Single Status
There are four Medicare Savings Program categories. Each covers a different set of Medicare cost-sharing components. Two of the four cover SNF coinsurance. Two do not.
Billing teams that treat all dual-eligible residents identically, assuming Medicaid crossover will handle cost-sharing for every one of them, produce three types of errors: denied crossover claims for residents whose MSP category never covered SNF coinsurance, uncollected revenue from secondary payments that should have come through but were never pursued correctly, and federal compliance violations when QMB residents are billed for cost-sharing they cannot legally be charged. The MSP category check belongs at pre-admission verification, not at the point when the first Remittance Advice posts.
The Medicare Savings Program Categories: What Each One Requires From Your Billing Team
Four MSP categories exist under federal law. Each carries a different billing obligation.
|
MSP Category
|
What Medicaid Covers
|
SNF Coinsurance Covered?
|
Balance Billing Prohibited?
|
|---|---|---|---|
|
QMB (Qualified Medicare Beneficiary)
|
Part A/B premiums, deductibles, coinsurance
|
||
Source: CMS Medicare Savings Programs – QMB Program Page
Only QMB residents have their SNF coinsurance fully covered by Medicaid. SLMB, QI, and QDWI residents have Medicaid covering Medicare premiums, not SNF cost-sharing. A facility that assumes crossover will handle coinsurance for any dual-eligible resident, without first confirming the MSP category, is running an incomplete verification and making a billing decision based on an assumption it has not tested.
How to Verify Dual Eligible Status Before Admission: The Two-Track Requirement
Every dual-eligible referral requires two parallel verification tracks. Running them sequentially, Medicare first and Medicaid second, means the billing team does not have complete information when the admissions decision is made. At that point the bed has been offered and the family has been called. The verification result can no longer change the decision it was supposed to inform.
Track 1: Confirm Traditional Medicare vs. Medicare Advantage Enrollment
Start with HETS or the Medicare portal. Confirm Part A enrollment status, benefit period, and days remaining. Then confirm enrollment type: Traditional Medicare or Medicare Advantage.
This step is not a formality. A dual-eligible resident enrolled in a Dual Eligible Special Needs Plan (D-SNP) has a Medicare Advantage plan as their primary payer, not Traditional Medicare. The entire billing sequence changes. Prior authorization through the MA plan is required before admission. Billing Traditional Medicare for a D-SNP admission produces a denial with no self-evident cause and no retroactive fix.
For Part A enrollment verification and benefit period mechanics, see the Medicare Part A enrollment verification guide.
Track 2: Confirm Medicaid Enrollment, Managed Care Assignment, and MSP Category
Pull the resident’s Medicaid status through the state portal. Confirm three things in sequence: active Medicaid enrollment, managed care assignment, and MSP category.
Active Medicaid enrollment is the starting point, not the ending point. A resident with active Medicaid FFS enrollment may have been auto-assigned to a managed care organization. When that happens, the crossover claim goes to the MCO, not the state agency. Billing the state directly when a managed care plan owns the Medicaid coverage produces a denial with no obvious explanation on the RA.
MSP category lookup is the last step in Track 2, and the one most billing teams skip. Confirm whether the resident is QMB, SLMB, QI, or QDWI. If QMB, flag the status in the admissions intake record immediately, before any discussion of cost-sharing happens with the resident or responsible party.
For Medicaid enrollment verification and managed care assignment, see the Medicaid enrollment and managed care assignment guide.
Why Both Tracks Must Complete Before the Bed Is Offered
The Medicaid MSP category determines whether any cost-sharing can be collected from the resident. That is an admissions decision, not something billing resolves later. By the time the first RA posts, the resident has been in the building for two to three weeks. A copay collected from a QMB resident at intake is already a compliance violation. Nothing in the billing cycle corrects it retroactively.
For the complete pre-admission verification sequence across all payer types, see the pre-admission verification sequence guide.
QMB Status: The Billing Prohibition Most SNFs Violate Without Knowing It
QMB is the highest-stakes MSP category in SNF billing. It is also the most commonly mishandled, not because billing teams do not know the rules, but because the violation happens before billing is involved at all.
Federal law prohibits billing a QMB resident for any Medicare cost-sharing: deductibles, coinsurance, or copays. The prohibition is absolute. If Medicaid crossover fails and the state never pays the coinsurance balance, the facility absorbs the loss. Billing the QMB resident for that unpaid balance is a federal violation, regardless of whether Medicaid paid, regardless of whether COBA failed, and regardless of what the resident’s financial agreement says. This prohibition is established under Section 1902(n)(3)(B) of the Social Security Act. The OIG has Civil Monetary Penalty enforcement authority for QMB balance billing violations. This is not a denial to correct. It is a compliance event.
The QMB Mistake Most SNF Billing Teams Make
Most facilities know not to balance bill QMB residents. The failure happens at admission, in the financial intake workflow, before the billing team is in the room.
Here is the sequence: a dual-eligible resident arrives. The admissions coordinator processes intake. Copay collection runs automatically as part of the financial workflow, because it runs for every resident. QMB status was confirmed during pre-admission verification. But it was not flagged in the admissions record, not communicated to the intake coordinator, and not connected to the cost-sharing discussion with the responsible party. The charge goes to the resident. Three weeks later, the billing team sees QMB on the RA and has to reverse a copay that should never have been collected.
QMB is framed as a billing prohibition. It is actually an admissions intake requirement. The moment QMB status is confirmed during pre-admission verification, that status must be flagged in the resident’s intake record and visible to whoever handles the financial intake conversation, before the resident arrives. Facilities without a QMB flag in their admissions workflow do not have a billing compliance gap. They have an admissions process gap that produces billing compliance violations on a recurring basis.
LTC Apps Admissions tracks required documentation per resident from the point of referral, so a QMB status confirmed at pre-admission verification is documented in the intake record and visible before any cost-sharing conversation happens. See admissions intake documentation for how that workflow is structured.
How COBA Works and What to Do When Crossover Fails
The Coordination of Benefits Agreement (COBA) is the mechanism CMS uses to automatically forward a Medicare claim balance to the state Medicaid agency after Medicare processes its payment. When it functions correctly, the facility submits one claim to Medicare and Medicaid receives the crossover without any manual action from the billing team.
The Automatic Crossover (MA18)
When the patient’s name, date of birth, MBI, and Medicaid ID are correctly aligned across both Medicare and Medicaid records, Medicare transmits the claim balance to Medicaid automatically. The RA will show reason code MA18, confirming the crossover was sent. The facility waits for the secondary Medicaid payment. No further action is required unless that payment does not arrive.
When Crossover Fails (MA07)
MA07 on the RA means COBA crossover failed. Medicare did not transmit the balance to Medicaid. The most common cause is a record mismatch, such as a name spelling, date of birth, or identifier discrepancy between Medicare and Medicaid systems.
When MA07 appears, the billing team must bill Medicaid manually: submit the Medicare RA with the secondary claim to the state Medicaid agency, or to the resident’s Medicaid MCO if managed care is involved. Confirm managed care assignment before submitting. Billing the state agency directly when an MCO owns the Medicaid coverage produces a second denial on top of the failed crossover.
Document the MA07, the manual submission date, and the secondary payer contact. If the claim is questioned later, the billing team needs a documented sequence showing correct action was taken after the automatic crossover failed.
The QMB COBA Failure Trap
When a QMB resident’s crossover fails and Medicaid does not pay, the facility absorbs the loss. No collection action against the resident is permissible. The balance billing prohibition holds regardless of whether Medicaid paid. QMB residents with a history of Medicare-Medicaid record mismatches are a predictable accounts receivable exposure, not a collections opportunity.
The fix is upstream: verify that Medicare and Medicaid records match on name, date of birth, and identifiers before admission. A mismatch identified at pre-admission verification can be corrected before the claim is submitted. The same mismatch identified after MA07 posts triggers a manual billing process that may still produce no payment, leaving the facility with an unrecoverable balance and no legal recourse against the resident.
D-SNP Residents: When Dual Eligible Billing Is Not Medicare Plus Medicaid
The fastest-growing segment of the dual-eligible population is not enrolled in Traditional Medicare.
Dual Eligible Special Needs Plans (D-SNPs) are Medicare Advantage plans built specifically for residents enrolled in both Medicare and Medicaid. As of 2023, 5.2 million dual-eligible individuals were enrolled in a D-SNP, nearly triple the share enrolled in 2010, with enrollment growing by 159,400 new enrollees between 2024 and 2025 (Source: KFF, 10 Things to Know About Medicare Advantage Dual-Eligible Special Needs Plans). When a dual-eligible resident is D-SNP enrolled, the primary payer is the MA plan, not Traditional Medicare. The facility bills the D-SNP plan. Prior authorization through the plan’s UM department is required before admission. In-network status must be confirmed. The plan’s concurrent review requirements apply throughout the stay.
A D-SNP resident looks identical to a Traditional Medicare plus Medicaid dual eligible on a referral form. Both have Medicare. Both have Medicaid. The difference only appears when the billing team checks MA enrollment type during pre-admission verification.
Facilities that do not confirm MA plan type for every dual-eligible referral will eventually admit a D-SNP resident, bill Traditional Medicare, and receive a denial with no self-evident cause. The prior authorization gap cannot be corrected after the fact. The facility billed the wrong primary payer for a stay that required a different verification process before day one of care.
For the complete two-step verification process for D-SNP and all Medicare Advantage admissions, see the D-SNP prior authorization requirements guide. For dual-eligible residents confirmed on Traditional Medicare, eligibility verification through LTC Apps lets billing teams run Medicare and Medicaid checks in the same platform, with no separate portal, no extra login, and every result stored with the resident’s record.
The Dual Eligible Pre-Admission Verification Checklist
Every dual-eligible referral requires the following steps before the bed is confirmed. These steps are sequential. No step substitutes for the one before it.
- Confirm Medicare Part A enrollment and benefit period days remaining (HETS or Medicare portal)
- Confirm enrollment type: Traditional Medicare or Medicare Advantage
- If Medicare Advantage: confirm plan type (HMO, PPO, D-SNP, C-SNP)
- If D-SNP: initiate MA plan prior authorization before admission; do not bill Traditional Medicare
- Confirm Medicaid enrollment status: FFS or managed care assignment
- Identify MSP category: QMB, SLMB, QI, or QDWI
- If QMB: flag immediately in the admissions intake record; no cost-sharing may be collected at any stage
- Verify Medicare and Medicaid records match on name, date of birth, and identifiers before the claim is submitted
- Document verification source, reference number, and verifier name and timestamp for each completed step
Steps 5 and 6 are where most dual-eligible billing workflows break. Medicaid enrollment is confirmed. MSP category is not checked. The billing team assumes crossover will cover coinsurance and discovers at claim time that the resident’s Medicaid category never included SNF cost-sharing, or that QMB status required a compliance step that was skipped at intake three weeks earlier. Neither error has a clean correction. Both were preventable at pre-admission.
Who This Is For
LTC Apps is the right fit if:
- You operate a skilled nursing facility handling dual-eligible admissions and want Medicare and Medicaid verification connected to the admissions intake record in one platform, not across separate portals
- Your billing team is confirming enrollment but not MSP category, and you have had QMB compliance issues or unexpected COBA failures as a result
- You want a documented verification trail per resident (source, reference number, verifier, timestamp) for every dual-eligible admission
This is not the right fit if:
- You need a full revenue cycle management or claims submission platform
- You require automated D-SNP prior authorization through a direct payer network
What Happens After You Request a Demo
- A member of the LTC Apps team reaches out within one business day to schedule a call
- We run a 30-minute live walkthrough of the modules most relevant to your facility, typically Eligibility Verification and Admissions together for dual-eligible workflow questions
- You receive pricing specific to your facility size and module selection
Most facilities have a clear picture of fit and pricing within one week of reaching out.
Common Questions Before Booking
- No minimum facility size: single-facility operators and small regional groups are LTC Apps’ primary customers
- No long implementation timeline: most facilities are live on their first module within two to four weeks
- If you are mid-contract with another vendor, a parallel evaluation now means you are ready to switch at contract end without making a rushed decision under time pressure
Frequently Asked Questions
A dual-eligible SNF resident is enrolled in both Medicare and Medicaid. Medicare is the primary payer for skilled nursing care under Part A for the first 100 days of each benefit period. Medicaid covers cost-sharing depending on the resident's Medicare Savings Program category. Dual eligibility is not a single billing status. The MSP category determines what Medicaid covers and whether the facility can legally collect any cost-sharing from the resident at all.
Medicare pays first for skilled nursing care under Part A. Medicaid pays second, covering cost-sharing such as the daily coinsurance for days 21 through 100, but only for residents whose MSP category includes SNF coinsurance coverage. QMB residents have full cost-sharing covered. SLMB, QI, and QDWI residents do not have SNF coinsurance covered through their Medicaid category.
QMB stands for Qualified Medicare Beneficiary. It is an MSP category covering Medicare Part A and B premiums, deductibles, and coinsurance in full. Federal law prohibits billing a QMB resident for any Medicare cost-sharing. That prohibition applies even when COBA crossover fails and the coinsurance balance is never paid by Medicaid. SNFs that collect copays or coinsurance from QMB residents face Civil Monetary Penalty exposure under OIG enforcement authority.
QMB covers Medicare Part A and B premiums, deductibles, and coinsurance, including SNF daily coinsurance for days 21 through 100. Balance billing QMB residents is federally prohibited. SLMB covers only the Medicare Part B premium. SLMB residents' SNF coinsurance is not covered by their Medicaid category, and the balance billing prohibition that applies to QMB residents does not apply to SLMB residents. Treating them identically at intake produces both missed revenue and compliance risk.
A D-SNP (Dual Eligible Special Needs Plan) is a Medicare Advantage plan for residents enrolled in both Medicare and Medicaid. When a dual-eligible resident is D-SNP enrolled, the MA plan is the primary payer, not Traditional Medicare. The facility must obtain prior authorization through the plan's UM department before admission, confirm in-network status, and manage concurrent review throughout the stay. Billing Traditional Medicare for a D-SNP admission produces a denial that cannot be corrected retroactively.
COBA crossover failure appears as reason code MA07 on the Medicare Remittance Advice. When MA07 appears, the facility must manually submit the secondary claim to Medicaid, either to the state agency or to the resident's Medicaid MCO if managed care is involved. If the resident is QMB and the crossover fails, the facility absorbs the unpaid cost-sharing balance. Billing a QMB resident for an unrecovered COBA balance is a federal violation regardless of whether Medicaid paid.
Ready to Stop Managing Dual Eligible Verification Across Separate Portals?
Dual-eligible admissions are among the most complex billing events a skilled nursing facility handles. Running Medicare and Medicaid verification across separate systems, with no documented link between the verification result and the admissions intake record, is where QMB flags get missed, D-SNP residents get billed to the wrong primary payer, and COBA mismatches go undetected until the first RA posts and the damage is already done.
LTC Apps Eligibility Verification runs Medicare and Medicaid checks in the same platform: no separate portal, no extra login, every verification stored with the resident record and searchable by reference number and status. Combined with the Admissions module, the verification result connects directly to the intake record before the resident arrives, so QMB flags, MSP categories, and managed care assignments are visible to the intake team before any cost-sharing conversation happens.
If you operate a skilled nursing facility handling dual-eligible admissions and want verification connected to your intake workflow, LTC Apps was built for exactly this.
