Most SNF billing teams think they have an eligibility verification problem. What they have is a timing problem.The verification is running. It is just running a day too late to change anything.
By the time a billing coordinator confirms that a resident’s Medicare Advantage plan requires prior authorization, the resident is already in the bed. The family has signed the admission agreement. The discharge planner at the referring hospital has closed the referral and moved to the next case. Correcting the payer at that point is not a billing task. It is a relationship management crisis that most facilities absorb quietly and repeatedly.
The SNF eligibility verification workflow is a three-stage process: a pre-admission check at the referral stage, a mid-stay recheck triggered by coverage milestones and authorization deadlines, and a post-denial recovery process when a claim returns with an eligibility failure code. Each stage involves different staff, different systems, and a different response window. Running all three correctly is what separates facilities that prevent eligibility denials from facilities that spend their billing staff’s time appealing them.
Eligibility and benefits issues are among the most common reasons for claim denials across all payer types. In skilled nursing, where Medicare and Medicaid margins are already compressed, a single preventable denial on a high-acuity resident can represent thousands of dollars in delayed or lost reimbursement. (Source: AHCA/NCAL or OIG Reports.)
This guide covers all three stages: what staff do at each step, which systems they use, where errors enter the process, and what changes when the workflow is automated.
Why Eligibility Verification Is a Three-Stage Workflow, Not a One-Time Check
The most expensive assumption in SNF billing is that eligibility verification is a billing department task. It is not. It is an admissions decision, and it has to be treated as one from the moment a referral comes in.
The Mistake Most SNFs Make
Here is what actually happens in facilities that treat verification as a single event: the admissions coordinator receives a referral, clinical reviews the hospital records, a bed is offered, and the family is contacted. Somewhere in that sequence, usually after the bed offer, sometimes after the family has started packing, someone runs the eligibility check.
If it comes back clean, nothing changes. If it comes back with a problem, coverage lapsed, authorization required, three-day qualifying stay not met, the facility is now managing a clinical problem, a financial problem, and a referral relationship problem simultaneously. The resident cannot easily be turned away. The discharge planner cannot easily be told the bed offer was premature. The family cannot easily be told that coverage was assumed before it was confirmed.
This is not a verification failure. The check ran. It is a sequencing failure. The check happened after the point at which its results could have changed the decision.
The entire workflow below is built on one principle: verification results must be available before the bed is offered. Not after.
What the Three Stages Are and Why Each Exists
Stage 1 is pre-admission verification, confirming coverage at the referral stage, before clinical acceptance and before the bed offer. This is where the most revenue is protected and where the most errors currently occur in most facilities.
Stage 2 is mid-stay recheck, monitoring coverage changes during the stay, catching authorization expirations, benefit period exhaustion, and Medicaid status transitions before they create billing gaps. Most facilities have no formal process for this stage. They find out about coverage changes when the remittance comes back.
Stage 3 is post-denial recovery, the structured response when a claim returns with an eligibility-related denial code. This stage should be shrinking in every facility that runs Stages 1 and 2 correctly. In facilities without a formal workflow, it is where most of the billing staff’s time goes.
LTC Apps’ eligibility verification software built for SNFs is designed around this three-stage model, automating the pre-admission check, surfacing mid-stay recheck triggers before they become billing gaps, and giving billing coordinators a documented audit trail for post-denial recovery.
Stage 1: Pre-Admission Eligibility Verification
Pre-admission verification is the highest-stakes stage of the workflow. It is also the stage most commonly run too late, with incomplete information, or without a clear protocol for what to do when the result is not clean.
2025 reality: Over 95% of UnitedHealthcare, Humana, Anthem, Aetna, and Cigna plans return full benefit detail via 270/271 — more than Medicare and far more than Medicaid. When you have automation, you never log into another portal again.
Payer-by-Payer Verification Guide – The Big 5 in 2026
When This Check Must Happen
The trigger for Stage 1 is referral contact, the moment a hospital discharge planner, case manager, or family member reaches out about a potential admission. Not the day the resident arrives. Not after clinical review is complete. At the referral stage, before any bed offer is made.
For Medicare Part A admissions, three pieces of information are sufficient to run the check: the resident’s full legal name, date of birth, and Medicare Beneficiary Identifier. With those three fields, a 270/271 eligibility transaction through a clearinghouse or a direct query to the Noridian Medicare portal will return benefit period status and remaining covered days.
For Medicare Advantage and HMO admissions, the timeline is more compressed and less forgiving. Some plans require 72-hour prior authorization notice. A referral that arrives Friday afternoon for a Monday admission may already be inside the authorization window before anyone has picked up the phone. Managed care verification must happen within hours of referral contact, not the next business day.
The hard rule: if coverage cannot be confirmed before the bed offer, issue a conditional acceptance with a stated verification deadline. Document the condition in writing. Do not admit without confirmation.
What to Verify at This Stage
Medicare Part A
The three-day qualifying inpatient hospital stay is the most commonly misunderstood Medicare SNF eligibility requirement, and the most commonly assumed. The rule requires three consecutive days as a hospital inpatient. The discharge day does not count. Observation-status days do not count, even if the resident was physically in the hospital during that time and the discharge summary does not distinguish between them.
Verify the qualifying stay before accepting the referral. Ask the discharge planner for the admission date, the discharge date, and whether any days were classified as observation. If observation days are included in the three-day count, Medicare Part A SNF coverage does not exist, regardless of what any other documentation suggests.
Beyond the qualifying stay, confirm benefit period status and remaining covered days. Medicare covers up to 100 days per benefit period for SNF care, with coinsurance beginning on day 21. A resident who used 60 days in a prior stay has 40 days of remaining coverage. For a complete walkthrough of the Medicare Part A verification process, see our guide to verifying Medicare Part A coverage.
Medicaid
Medicaid verification requires confirming active status in the state where the facility is located, not the state where the resident previously lived or received care. Coverage does not transfer across state lines.
Medicaid pending is a separate category that requires its own documentation protocol. When a resident is Medicaid-pending at admission, the facility is extending care on the expectation that Medicaid will be approved retroactively. That expectation must be documented, the application status must be tracked weekly, and billing must be held on those dates of service until approval is received. Admitting a Medicaid-pending resident without a documented tracking protocol is how facilities end up carrying large uncollected balances on long-stay residents, often for months before anyone surfaces the problem.
For dual-eligible residents, confirm Medicaid as the secondary payer before admission. See our guide to Medicaid eligibility status for state-specific verification steps.
Medicare Advantage, HMO, and Managed Care
Confirming that a resident has a Medicare Advantage plan is not the same as confirming that your facility is covered under that plan. These are two separate verification steps. In-network status must be confirmed plan by plan. It cannot be assumed based on the plan name, the plan type, or prior admissions from the same plan.
Once in-network status is confirmed, prior authorization must be requested and received before admission. Log four data points before the resident’s move-in date: the authorization number, the approved level of care, the authorization start date, and the number of approved days. A verbal authorization without a logged authorization number is a conversation, not a coverage confirmation. It will not hold up when the claim is disputed.
For a complete walkthrough of commercial and HMO payer verification, including prior authorization submission steps, see our dedicated guide.
Who Owns This Step
The admissions coordinator owns Stage 1. This is not a billing function. It is an admissions function. The admissions coordinator is the person with the referral, the relationship with the discharge planner, and the earliest access to the information needed to run the check. Shifting verification responsibility to billing because they know the payers is how the timing failure happens. By the time the file reaches billing, the bed has already been offered.
The business office manager supports on payer-specific questions and escalates anything that cannot be resolved before the admission decision. The administrator makes the final call when coverage cannot be confirmed and a bed decision is time-sensitive. All verification documentation, the 271 response, the authorization number, the Medicaid portal printout, is filed by the business office before the move-in date.
|
Common Error
|
What Actually Happens
|
Prevention
|
|---|---|---|
|
Verification runs on admission day instead of at referral
|
Coverage problem found after bed is offered and family is notified
|
|
Stage 2: Mid-Stay Eligibility Recheck
Stage 2 is the most consistently skipped stage in SNF eligibility workflows. Most facilities assume that if coverage was confirmed at admission, the billing team will catch changes when the claim generates. This is the assumption that creates the mid-stay denial category.
What Triggers a Mid-Stay Recheck
Coverage does not stay static during a SNF stay. Several predictable events change a resident’s coverage status, and every one of them can be anticipated on a calendar.
Medicare Part A day 20 is the first threshold. Coinsurance begins on day 21. Search CMS.gov for the current Medicare SNF coinsurance daily rate. Before day 21, confirm that the resident still meets the skilled care requirement and that clinical documentation supports continued medical necessity. A resident who no longer meets skilled care criteria loses Part A coverage regardless of remaining benefit days.
Medicare Part A day 100 marks benefit period exhaustion. If a long-stay resident is approaching day 100, the transition plan, to Medicaid, Medicare Advantage, private pay, or discharge, must be operational before day 101, not assembled on it.
HMO and Medicare Advantage authorizations expire on a fixed date or at a fixed number of approved days, whichever comes first. Authorization renewal must be submitted before expiration. Most plans require five to seven business days of advance notice. Waiting until an authorization has lapsed to request renewal means billing uncovered days while the renewal is pending, and most plans will not backdate an authorization that was not submitted on time.
Medicaid pending approval received mid-stay is a billing transition event, not a routine update. When pending status converts to active, the effective date, which is frequently retroactive to the admission date, determines when Medicaid billing begins and whether previously held claims can now be released. The billing team must be notified immediately.
Who Owns the Recheck Trigger
This is where most SNF billing workflows break down at Stage 2: the assumption that the billing team will catch coverage changes when the claim generates. The claim generates after the billing period closes. At that point, the authorization has already expired, the Medicare days have already run, and the correction window on some payer types has already started closing.
The mid-stay recheck trigger must be owned by the business office manager, not discovered by the billing coordinator at month-end. This means one person, one coverage milestone calendar, reviewed weekly. Every active resident’s Medicare day thresholds, authorization expiration dates, and Medicaid pending follow-up dates on a single document, checked every week without exception.
Facilities that assign this responsibility explicitly, and hold someone accountable for the weekly review, catch mid-stay coverage changes before they become denied claims. Facilities that leave it to the billing cycle read about them in the remittance.
What to Check and How
For Medicare Part A residents approaching a coverage threshold, re-run the 270/271 transaction. Do not rely on the admission-day verification printout. A 271 response from 45 days ago tells you what coverage looked like at referral, not what it looks like today.
For managed care residents, contact the plan directly at least five business days before authorization expiration. Request renewal, confirm the new authorization number, log the approved days, and update the resident record before the current authorization period closes.
For Medicaid-pending residents, check the state portal weekly and document each check: date of access, status returned, next follow-up date. If approval is overdue, escalate to the business office manager and contact the Medicaid eligibility office directly. Weekly checks with no documentation are not a tracking system. They are a habit with no paper trail.
Stage 3: Post-Denial Recovery Workflow
Every eligibility-related denial that reaches Stage 3 is evidence of a failure in Stage 1 or Stage 2. The goal of a well-run post-denial process is not only to recover the denied claim. It is to identify which upstream step failed so it stops producing the same result.
What a Post-Denial Eligibility Failure Actually Means
Not all eligibility denials are the same. There are two types, and they require completely different responses.
Type 1 is genuine ineligibility. The resident was not covered under the billed payer at the dates of service. The Medicare benefit period had been exhausted. The Medicaid application was denied. The resident was never enrolled in the plan that was billed. The fix is to identify the correct payer, issue an Advance Beneficiary Notice if applicable, and re-bill. If no other payer exists and a valid ABN was issued at admission, the facility can bill the resident directly. If no ABN exists, that option may be legally restricted, which is precisely why ABN documentation at admission is not a formality.
Type 2 is administrative failure. Coverage existed. It was not verified correctly, not verified on time, or not documented in a form that supports the claim. This is the more common category and the more recoverable one. The correct response is a corrected claim or a formal appeal with documentation establishing coverage at the dates of service.
Filing an appeal regardless of denial type is how billing staff spend hours on claims that needed a corrected billing, not an appeal, and miss the appeal window on claims that genuinely needed one.
The Post-Denial Recovery Steps
- Pull the remittance advice and identify the denial reason code. Common eligibility-related codes: CO-27 (expenses incurred after coverage terminated), CO-29 (time limit for filing expired), CO-15 (authorization number missing or invalid), PR-96 (non-covered charges). The reason code identifies the denial type before the resident’s file is opened.
- Cross-reference against the original verification record. Was verification run before admission? When? What did the 270/271 response show? If no verification record exists, there is a Stage 1 documentation failure in addition to the billing problem, and the appeal will be harder to support.
- Determine denial type. Genuine ineligibility or administrative failure. This determination drives every subsequent step.
- For administrative failure, gather corrected eligibility documentation and submit a corrected claim or formal appeal. For Medicare, the redetermination window is generally 120 days from the remittance date. The clock starts on the remittance date, not the date the billing team gets around to reviewing it.
- For genuine ineligibility, identify the correct payer. If a valid ABN was issued, bill the resident for non-covered services. If no ABN exists, the facility’s collection options are limited. Document why and close the file with a root cause notation.
- Document the root cause. Which stage broke down: Stage 1 timing failure, Stage 1 payer-specific error, Stage 2 recheck missed? This is not a blame exercise. It is the only way to turn a single denial into a workflow correction.
The Internal Audit Step Most Facilities Skip
Every eligibility denial should trigger a brief internal audit, one question: which step in the three-stage workflow failed, and what change prevents it from failing the same way again?
Facilities that track denial root causes by stage start seeing patterns that are invisible claim by claim. Every HMO denial in a quarter came from the same Stage 1 failure: in-network status was assumed rather than confirmed. Every Medicare denial in a long-stay wing came from the same Stage 2 failure: no one owned the day-100 transition check. Once the pattern is visible, the fix is a workflow adjustment, not additional headcount, not a performance conversation, not another appeal.
Facilities that treat each denial as a standalone event fix nothing. They recover what they can from the current claim, close the file, and face the same denial on the next resident because the upstream failure was never corrected. The appeals backlog grows. The billing coordinator’s calendar fills with rework. Recovery rates decline, not because the team is working less, but because the workflow is generating the same errors at the same rate with no mechanism to surface them.
LTC Apps’ medical code analysis gives billing teams the denial pattern visibility to run this audit systematically, identifying which payers, which residents, and which workflow stages are producing the most rework, before the pattern becomes a revenue problem.
What the Workflow Looks Like When It Is Automated
Manual Workflows Are Built to Catch Errors. Automated Workflows Are Built to Prevent Them.
Every manual step in the workflow above depends on a staff member remembering to act, knowing which system to use, having time to run the check during an active admissions push, and documenting the result where the billing team can find it later.
Under normal census volume, a disciplined team can execute this. Under pressure, a census spike, a key staff departure, a survey week, the steps that get skipped are consistently Stage 1 timing and Stage 2 recheck. The two stages that prevent denials.
Automated eligibility verification reorients the workflow from reactive to preventive. The system flags any pending admission without a completed verification before the bed can be offered. It surfaces mid-stay coverage milestones automatically, not when the billing cycle closes, but when there is still time to act. It creates a timestamped verification record at the moment the 270/271 transaction runs, not reconstructed after a denial has arrived.
The post-denial recovery section of this guide exists because manual workflows need it. Facilities running automated pre-admission verification write fewer appeals, carry smaller denial backlogs, and produce cleaner audit trails when a payer or regulator asks for documentation, because the record was created by the system in real time, not assembled under pressure after the fact.
See how LTC Apps automates the pre-admission eligibility check and surfaces mid-stay recheck triggers before coverage gaps open.
Frequently Asked Questions
The SNF eligibility verification workflow has three stages: a pre-admission check confirming payer coverage before the bed is offered, a mid-stay recheck monitoring coverage changes and authorization expirations during the resident's stay, and a post-denial recovery process for claims that return with eligibility-related denial codes. Each stage has distinct staff responsibilities, system tools, and time constraints.
At the pre-admission stage, verification includes confirming the Medicare Part A three-day qualifying hospital stay and remaining benefit days; checking Medicaid active status or pending application status; and confirming in-network status and prior authorization for Medicare Advantage and HMO plans. The check runs at referral contact, before the bed offer, using a 270/271 eligibility transaction through a clearinghouse or the Noridian Medicare portal.
Medicare Part A SNF eligibility requires a three-day qualifying inpatient hospital stay, excluding the discharge day and any observation-status days. Verification confirms the qualifying stay dates, benefit period status, and remaining covered days using the HETS system via a clearinghouse 270/271 transaction or the Noridian provider portal.
Observation hours are the most common source of qualifying stay miscounts. Always confirm with the discharge planner before accepting the referral.
Mid-stay rechecks should occur at predictable coverage milestones: before Medicare Part A day 21, before day 100, at least five business days before any managed care authorization expiration, and weekly for any resident with Medicaid-pending status. A standing weekly calendar review of all active residents' coverage milestones is the operational minimum. Monthly reviews are too slow to catch an authorization expiring in ten days.
The facility assumes the full financial risk for those dates of service. If the claim is denied on eligibility grounds, the facility must appeal with retroactive documentation, identify an alternative payer, or bill the resident directly, but only if a valid Advance Beneficiary Notice was issued at admission. Without an ABN, the facility's ability to collect from the resident may be legally restricted.
Pre-admission verification is owned by the admissions coordinator. Mid-stay recheck is owned by the business office manager, who maintains the coverage milestone calendar and conducts weekly reviews. Post-denial recovery is owned by the billing coordinator, with escalation to the business office manager for high-dollar or aging denials. Root cause findings from Stage 3 flow back to the admissions coordinator to close the loop on upstream workflow failures.
Is LTC Apps the Right Fit for Your Facility?
LTC Apps is built for you if:
- You operate a skilled nursing facility or small regional SNF group and your current eligibility process is manual, inconsistent, or generating denials you are catching too late to prevent.
- You want automated pre-admission verification, mid-stay recheck alerts, and a clean audit trail for billing, without replacing your entire clinical system.
- You are evaluating modular operations software and need something built for SNF workflows, not adapted from hospital or home health platforms.
This is not the right fit if:
- You need a full clinical EHR with physician-facing charting and order management.
- Your facility is assisted living only with no skilled nursing component.
- You require an enterprise implementation contract with a dedicated project team from day one.
What happens after you request a demo:
- A member of our team contacts you within one business day to schedule a call.
- We run a 30-minute live walkthrough of the eligibility verification module and any other modules relevant to your facility’s workflow.
- 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.
Before you book, the questions we hear most often:
No long implementation timelines. Most facilities are live on their first module within two to four weeks. No minimum facility size. We work with single-facility operators and regional groups. If you are mid-contract with another vendor, we can run a parallel evaluation so you are ready to move at contract end.
Ready to Stop Losing Revenue to Preventable Eligibility Errors?
If you operate a skilled nursing facility and want to stop losing revenue to eligibility errors that were preventable at the referral stage, LTC Apps was built for exactly this.
Call us: 309-590-3455
Most facilities complete their first demo within one week of reaching out.
