10 Common Medicaid Billing Errors in Nursing Homes: A Claim Failure Case File

A Medicaid claim can look perfectly ordinary on the day a resident is admitted.

The resident has coverage. The facility records the payer. Care begins. The business office expects the account to move through the normal billing cycle.

Then the claim starts to drift.

The resident’s plan assignment changes. A patient-liability notice arrives but is not posted. An authorization reaches its end date. A payer requests records, but the request sits between clinical and billing. The claim is submitted with an identifier mismatch. Payment eventually arrives, but it is short—and no one reviews the remittance closely enough to spot the variance.

By the time the account appears in the denial queue or 90+ day A/R report, it may contain several Medicaid billing errors, not one.

That is why nursing homes should not manage Medicaid errors as a list of isolated denials. They should manage them as failures that enter the claim at specific handoffs: admission, coverage verification, authorization, clinical documentation, billing, payment posting, and A/R follow-up.

The financial exposure is substantial. Medicaid is the primary payer for 63% of residents in certified U.S. nursing facilities (Read KFF’s 2025 nursing-facility payer-source data). When a small process error repeats across a significant Medicaid census, it becomes a cash-flow and margin issue.

CMS reported an estimated Medicaid improper-payment rate of 6.12% for FY 2025, and that insufficient documentation represented about 77% of estimated Medicaid improper payments in the 2025 review year (Read CMS’s FY 2025 Medicaid improper-payment reporting). CMS states that insufficient documentation findings generally do not indicate fraud or abuse. For nursing-home operators, the operational message is clear: payment can be disrupted when the facility cannot produce the information needed to support a claim, even when care was properly delivered.

The central lesson: Medicaid billing errors are rarely solved permanently in the denial queue. They are prevented where the information first enters, changes or disappears from the facility’s workflow.

This piece focuses on Medicaid-specific failures. For a broader look at where nursing homes lose money across the entire billing cycle, see our Top 10 SNF revenue cycle mistakes.

Case File: How a Medicaid Claim Breaks Down

The claim below is illustrative. It does not represent a specific facility, state Medicaid program, payer, MCO, resident, or denial determination.

A resident is admitted to a skilled nursing facility after a hospital stay. The resident is believed to have Medicaid coverage. The admission team enters payer information. The resident’s Medicare coverage later ends. A Medicaid managed-care assignment becomes effective. The authorization status is unclear. A patient-liability update is received later in the month. The claim is billed, pended, then denied. When the payment is eventually reviewed, the facility identifies an additional short-payment issue.

No single employee caused the entire problem.

The failure occurred because the facility lacked a reliable process for:

• Verifying and preserving payer-path information.
• Detecting payer and eligibility changes.
• Tracking authorization deadlines and units.
• Updating resident liability.
• Retrieving documentation requested by the payer.
• Separating payer pends from denials.
• Reviewing remittances for payment variance.

The 10 common Medicaid billing errors below appear in that claim journey.

Failure Zone One: The Resident Entered With Incomplete Financial Facts

The first cluster of errors occurs before the claim is created. These errors begin at admission, during payer discovery, and whenever coverage changes.

1. Wrong payer path

The resident is Medicaid eligible, but the claim is sent to the wrong payer channel: fee-for-service rather than managed care, the wrong MCO, an outdated plan, or a payer that is no longer responsible.

This error often produces front-end rejections, payer denials, delayed rebilling, and A/R aging.

What to inspect first

• Admission payer record.
• Eligibility verification result.
• Plan assignment effective date.
• Billing-path decision.
• Claim submission history.
• Proof of verification for the billed month.

The prevention step

Create one verified payer source of truth. It should include payer type, plan name, member identifier, effective dates, verification source, verification date, verified-by owner, and the designated claim-submission path.

The field should not be changed casually. It should be updated only after the applicable payer information has been checked and documented.

2. Eligibility treated as a one-time event

A resident’s coverage and plan information can change after admission. If the facility verifies eligibility only on move-in day, it may bill a payer arrangement that no longer applies.

The result may be a denial, a pend, a payment hold, or a rebilling cycle that makes the facility believe “Medicaid is slow.”

What to inspect first

• Last eligibility-verification date.
• Billed dates of service.
• Coverage effective dates.
• Recent hospital readmission, Medicare exhaustion, or plan changes.
• Eligibility-related rejection or denial messages.

The prevention step

Use trigger-based eligibility verification rather than relying only on admission verification.

Common triggers may include:

• Admission.
• A defined monthly review point.
• Medicare coverage ending.
• Hospital readmission.
• New managed-care assignment.
• Eligibility-related payer response.
• High-dollar or extended billing span, where an additional check is appropriate.

Requirements vary by state Medicaid program, payer, MCO, provider type, resident circumstance, and service line. The facility should validate its own verification frequency and evidence requirements against applicable guidance.

3. Patient liability changed, but the account did not

Patient liability, resident pay, or share-of-cost information can affect the payer balance and resident balance. If the amount or effective date is not updated promptly, the facility’s books begin to drift.

The problem can create under-collection, over-collection, resident disputes, refund work, inaccurate statements, and staff time spent untangling balances later.

What to inspect first

• Notice date.
• Effective date of the liability change.
• Prior and updated resident-responsibility amount.
• Billing-system update date.
• Resident account ledger.
• Supporting document location.

The prevention step

Create a patient-liability change ledger. The ledger should identify the resident, notice date, effective date, previous amount, updated amount, posting owner, documentation location, and reconciliation completion date.

A simple performance measure is:

Liability Update Compliance = Liability Changes Posted on Time ÷ Liability Changes Received × 100

This is a billing control, but it is also a resident-finance control. Facilities should validate resident-liability practices against the applicable state rules, resident agreements, payer information, and legal guidance where appropriate.

Failure Zone Two: Coverage Was Valid, but the Claim Was Not Ready to Bill

The second cluster occurs between payer verification and claim submission. The resident may be eligible, but the facility may not yet have the authorization, proof, or claim data necessary for payment.

4. Authorization dates or units were not controlled

Managed Medicaid plans may require authorizations, continued-stay reviews, defined units, or payer-specific documentation. Some state Medicaid or waiver-related programs may also include service, date, unit, or level-of-care requirements.

The specific rules differ. The failure pattern does not.

Services continue, but the authorization record does not.

What to inspect first

• Authorization number.
• Start and end date.
• Approved units or days.
• Units or days billed.
• Remaining units.
• Continued-stay review date.
• Payer correspondence.
• Ownership and backup coverage.

The prevention step

Treat authorizations as expiring financial controls, not static documents.

A 15-minute weekly authorization huddle can be more valuable than a lengthy monthly report. Review only items nearing expiration, approaching unit limits, missing documentation, or awaiting payer response.

For facilities that need structured workflow support, LTCPro’s prior authorization services can help organize deadlines, worklists, follow-up, and escalation.

5. Documentation was available somewhere—but not available for payment

The nursing home may have delivered appropriate care, but the billing team may not be able to locate the records, notice, authorization, or supporting information needed when the payer asks.

That distinction is important.

CMS’s FY 2025 Medicaid improper-payment materials report that insufficient documentation accounted for approximately 77% of estimated Medicaid improper payments in the 2025 review year (Read CMS’s FY 2025 Medicaid improper-payment data). CMS also makes clear that insufficient documentation findings generally do not indicate fraud or abuse.

For a facility, the practical question is not, “Did we document anything?” It is:

“Can we produce the required support for this claim, payer request, or appeal within the available response window?”

What to inspect first

• The payer’s request.
• Required documentation list.
• Document-storage location.
• Date the request was received.
• Person assigned to retrieve the documentation.
• Date the materials were sent.
• Proof of submission.

The prevention step

Build a payer-specific proof packet for high-risk claims and frequent payer requests.

The packet should not become a generic clinical checklist. It should identify the information the facility may need to retrieve for a specific payer, service, authorization, claim, or appeal scenario.

Assign a documentation owner, a billing or A/R owner, and an internal deadline. If the record is missing, escalate the exception early rather than waiting until the payer closes the claim.

6. Basic clean-claim controls were skipped

Some denials are not caused by complex Medicaid policy. They arise from missing claim fields, incorrect dates, invalid identifiers, duplicate claims, missing attachments, or payer-specific formatting requirements.

These defects create rework before the claim reaches ordinary adjudication.

What to inspect first

• Clearinghouse rejection report.
• Payer front-end edit.
• Claim correction history.
• Number of claim touches.
• Original and resubmission dates.
• Repeat error categories.

The prevention step

Use a clean-claim gate before submission.

Confirm:

• Coverage is active for billed dates.
• The claim is routed to the correct payer and plan.
• Authorization is active where required.
• Required documentation is available.
• Facility, provider, NPI, taxonomy, and other identifiers are correct where applicable.
• Resident liability is updated where relevant.
• Claim dates, units, and required attachments align with the source record.

Under 42 CFR § 447.45, state Medicaid agencies generally must require providers to submit claims within 12 months of service and meet specified timely-payment standards for qualifying clean claims (Read the 42 CFR § 447.45 regulation text). State Medicaid and MCO rules may include additional requirements, so facilities should build payer-specific claim-readiness checks.

Failure Zone Three: The Claim Could Not Be Paid Until the Facility Proved or Corrected Something

The third cluster happens after claim submission. The facility may assume the claim is “in process,” but the payer may actually be waiting for information or rejecting the billing path.

7. Provider enrollment, taxonomy, or revalidation was not maintained

Provider enrollment information can affect payment even when the resident, documentation, and claim are otherwise correct.

42 CFR § 455.414 requires state Medicaid agencies to revalidate the enrollment of all Medicaid providers, regardless of provider type, at least every five years (Read the 42 CFR § 455.414 regulation text). States may impose more frequent revalidation or additional requirements.

A facility may also need to maintain accurate NPI, taxonomy, address, ownership, licensure, credentialing, and MCO contracting information, depending on the payer and provider arrangement.

What to inspect first

• State Medicaid enrollment status.
• Revalidation due date and notice history.
• NPI and taxonomy on the claim.
• Facility location and organizational information.
• MCO contracting or credentialing status, if applicable.
• Recent ownership, location, banking, or entity changes.

The prevention step

Maintain a provider-data calendar owned by a named role, with a backup.

The calendar should track revalidation dates, enrollment notices, NPI and taxonomy data, licensure or credentialing deadlines where relevant, location changes, ownership updates, MCO status, and the evidence needed to confirm completion.

Quarterly review is usually more reliable than waiting for a claim problem to expose a missing update.

8. Third-party liability was discovered after Medicaid was billed

Medicaid is generally the payer of last resort. When another liable payer exists, the facility may need to identify and address that coverage before, during, or after Medicaid billing, depending on the applicable rules and exceptions.

Medicaid generally pays for covered items and services only when there is no other liable third party for the same items or services (Read Medicaid.gov’s third-party-liability guidance). State-specific operational rules and exceptions matter, so facilities should verify the applicable process before billing or appealing.

What to inspect first

• Other known insurance coverage.
• Coverage effective dates.
• Primary-payer claim activity.
• Explanation of benefits or denial.
• Medicaid claim status.
• Resident account information.
• Prior coordination-of-benefits documentation.

The prevention step

Create a third-party-liability work queue rather than leaving TPL issues in general A/R.

Each TPL account needs:

• Other-insurance source.
• Effective dates.
• Verification date.
• Primary-payer billing status.
• Supporting EOB or payer response.
• Medicaid billing status.
• Next action.
• Owner.
• Filing or appeal deadline.
• Escalation status.

A TPL issue often requires persistence, documentation, and payer-history reconstruction. It should be visible as its own work type.

9. The denial was worked after the recovery window narrowed

A denial is not a single event. It has a dollar value, reason, payer rule, history, owner, and deadline.

When nursing homes review denials only weekly, monthly, or at the end of a billing cycle, they may lose time needed to correct, resubmit, request reconsideration, or appeal.

What to inspect first

• Denial date.
• Payer reason code.
• Dollar value.
• Filing, correction, reconsideration, or appeal deadline.
• Claim submission history.
• Required documentation.
• Current owner.
• Last activity date.

The prevention step

Use denial triage.

Work new denials each business day and rank them by:

• Deadline risk.
• Dollar value.
• Likelihood of correction or recovery.
• Documentation dependency.
• Whether the error is recurring across multiple residents.

A denial without a category, owner, next action, and due date is not being managed. It is aging.

Failure Zone Four: The Claim Was Marked “Paid,” but the Facility Still Did Not Receive What It Expected

The final cluster is often missed because the claim may no longer appear in the denial queue.

10. Payments were posted, but underpayments and recoupments were not reconciled

Denials are visible. Underpayments are quieter.

A facility may receive a payment, post the remittance, close the claim, and move on without determining whether the amount paid aligns with the available contract, authorization, rate, billing, resident-liability, and claim information.

The result is revenue that disappears into adjustments, unexplained partial payments, or recoupments that are never investigated.

What to inspect first

• Billed amount.
• Expected amount, where supportable.
• Paid amount.
• Paid dates and units.
• Authorization record.
• Adjustment and reason codes.
• Resident-liability application.
• Recoupments or offsets.
• Prior payment reversals.
• Original claim and remittance history.

The prevention step

Establish expected-versus-paid reconciliation for material payer categories.

Not every variance is an underpayment. It may be correct under the payer contract, state Medicaid rate methodology, authorization record, resident responsibility, coordination-of-benefits rule, or specific claim facts.

But every material variance should be visible early enough to research and address.

What the Denial Is Really Telling You

A denial reason is often a symptom. The facility needs to find the upstream workflow that allowed it to occur.

This table should be used in a weekly Medicaid control meeting—not saved as a policy document and forgotten.

The 15-Minute Medicaid Control Meeting

The goal is not to add another meeting. It is to stop errors from becoming A/R crises.

Hold the meeting weekly with only the people needed to resolve current exceptions: business office leader, billing/A/R owner, admissions or eligibility owner, authorization owner, and clinical or MDS representation when documentation issues require their involvement.

Use this fixed agenda:

Minute 1–3: New risk entering the system

Review:

• Medicaid admissions.
• Payer or plan changes.
• Medicaid-pending accounts.
• New patient-liability notices.
• Other-insurance discoveries.
• Provider enrollment or revalidation deadlines.

Minute 4–7: Coverage and authorization exposure

Review:

• Authorizations expiring within 14 days.
• Unit or day limits nearing exhaustion.
• Pending continued-stay reviews.
• Eligibility verification exceptions.
• Missing payer evidence.

Minute 8–11: Pends and documentation requests

Review:

• New payer requests.
• Pends without a response.
• Documentation requests with deadlines.
• High-dollar claims waiting for records.
• Claims approaching denial risk.

Minute 12–15: Denial and payment variance trends

Review:

• New high-dollar denials.
• Denials close to appeal or filing deadlines.
• Repeat denial category.
• Significant underpayments.
• Recoupments or offsets requiring investigation.

End with one question:

What must be completed before the next meeting to prevent a current claim from becoming aged Medicaid A/R?

Each action needs one owner and one due date.

The 30-Day Medicaid Billing Safety Net

The following implementation board helps a nursing home build prevention controls without trying to redesign every process at once.

At the end of the 30 days, leadership should be able to answer:

• Which Medicaid error type is occurring most often?
• Which error type has the largest dollar impact?
• Which handoff creates the most delay?
• Which payer or plan creates the most repeat work?
• Which errors can be prevented through clearer ownership, better evidence, or a changed checklist?

If the facility cannot answer those questions, it may have data, but it does not yet have operational control.

If the Problem Is Not Effort

Some nursing homes do not have a knowledge problem. They have a capacity and coordination problem.

The team may understand the rules but lack enough structured follow-up, backup coverage, payer-level reporting, or cross-functional visibility to prevent errors from recurring.

If that is the finding, LTCPro’s revenue cycle management team can support the operational redesign: payer and eligibility worklists, authorization tracking claims readiness, pend and denial queues, high-dollar Medicaid A/R prioritization, remittance variance review, and reporting across admissions, clinical, MDS, billing, A/R, and finance.

LTCPro does not determine Medicaid eligibility, replace state Medicaid agencies or MCOs, make clinical determinations, provide legal advice, interpret payer contracts as legal counsel, or guarantee payment, compliance, authorization approval, or denial reversal. Final eligibility, clinical, payer, contract, legal, and regulatory determinations should be confirmed with the applicable state agency, MCO, payer, clinical leadership, legal counsel, or qualified advisor.

Before the Next Medicaid Claim Cycle

Use this final check before the next billing run:

• Is the payer path verified for the dates being billed?
• Is eligibility current based on the facility’s defined trigger schedule?
• Has patient liability been updated with the correct effective date?
• Are authorization dates, units, and continued-stay requirements current?
• Can billing access the documentation required for the billed claim?
• Is provider enrollment, taxonomy, and revalidation information current?
• Has other insurance or TPL activity been reviewed?
• Does every pend and denial have an owner, deadline, and next action?
• Are high-value payments checked for underpayment, adjustment, or recoupment variance?

The best Medicaid billing process is not the one that handles denials most heroically. It is the one that makes routine errors difficult to repeat.