LTCPro

Why Some SNFs Wait 90+ Days for Payment: Find the Claim Stuck in the System

SNF billing delay causes illustrated: eligibility, authorization, pends, and documentation gaps

A 90+ day unpaid claim is rarely one problem. It is usually the last visible result of a chain of events: a coverage change missed at admission, an authorization that expired without an alert, a payer request left in an inbox, documentation that was not available when requested, a corrected claim that was never resubmitted, […]

A 90+ day unpaid claim is rarely one problem.

It is usually the last visible result of a chain of events: a coverage change missed at admission, an authorization that expired without an alert, a payer request left in an inbox, documentation that was not available when requested, a corrected claim that was never resubmitted, or a payment posted without checking whether it was complete.

By the time the balance appears in the 90+ day A/R column, the original breakdown may be 30, 45, or 60 days old.

That is why the most effective question is not, Why is this payer so slow? It is:

At which point did this claim stop moving, who owns the next action, and how much time remains to recover it?

For qualifying clean claims, payment systems have defined expectations. Under 42 CFR § 447.45, state Medicaid agencies must generally require providers to submit claims within 12 months of service and meet federal timely-payment standards for qualifying clean claims. (Read the federal Medicaid timely-claims regulation). Medicare has separate prompt-payment requirements: clean electronic claims generally have a 14-day payment floor and a 30-day payment ceiling, while clean paper claims generally have a 29-day payment floor and a 30-day payment ceiling. (Read CMS’s Medicare Claims Processing Manual).

Those rules do not mean every SNF claim will be paid in that timeframe. Medicaid managed care, payer contracts, state-specific requirements, authorization rules, documentation issues, claim edits, and appeals can all affect payment. But they do provide a useful operating signal: when claims routinely cross 90 days, facilities should look for workflow friction—not simply accept delay as normal.

Key takeaway: A 90+ day claim needs a root-cause investigation, not another generic follow-up call. The facility should identify whether the claim is rejected, pended, denied, underpaid, incorrectly routed, awaiting documentation, or simply not assigned to a work queue.

Follow the Claim, Not the Aging Report

An A/R aging report tells you how long a balance has been open. It does not automatically explain why the balance is open.

For a 90+ day claim, reconstruct the journey from service to payment.

Claim stage Question to ask Common failure point
Admission and payer setup Was the correct payer and plan recorded? Wrong payer path or outdated plan assignment
Eligibility verification Was coverage confirmed for billed dates? Medicaid eligibility or plan change missed
Authorization Was an approval required, active and sufficient for the dates or units billed? Expired authorization or exceeded units
Documentation readiness Was the required information available when the claim or payer request was processed? Missing, incomplete, or delayed records
Claim submission Was the claim submitted cleanly and on time? Rejection, edit, missing data, or delayed release
Pend response Did the payer request information? Request not tracked, responded to, or escalated
Denial and appeal Was the denial corrected, appealed, or resubmitted before the deadline? No owner, late action, missed deadline
Payment posting Was payment compared with what the facility expected? Underpayment, recoupment, or misapplied adjustment left unresolved

This approach changes the conversation.

Instead of saying, “Medicaid is taking 90 days,” the team can say:

  • The claim was billed to an outdated managed-care plan and rebilled 18 days later.
  • The authorization ended before the last billed dates, and the appeal packet is awaiting clinical documentation.
  • The payer pended the claim for records, but the request was not assigned for 12 days.
  • The claim paid, but the remittance showed a material short payment that has not yet been reviewed.

Those statements lead to action. A total aging number does not.

The 90-Day Delay Map

The first goal is to determine which type of delay the facility is facing.

Delay Type 1: The claim never reached the payer cleanly

A claim may be rejected at the clearinghouse, edited by the payer, or routed for manual review before it enters a normal adjudication cycle.

Common triggers include:

  • Incorrect payer or plan assignment
  • Inactive coverage for billed dates
  • Missing or invalid claim data
  • Identifier mismatch
  • Overlapping dates
  • Missing required attachments
  • Incorrect coordination-of-benefits information
  • Authorization information missing where required

The operational clue is repeated claim handling.

If staff frequently says, “We resubmitted it,” the facility may be measuring payer delay when the actual issue is claim rework.

What to check

For every claim that enters 61–90 days, review:

  • Original submission date
  • Rejection or edit date
  • Correction date
  • Resubmission date
  • Number of claim touches
  • Reason for correction
  • Whether the same issue occurred on other accounts

A claim that took 12 days to correct and resubmit did not spend 12 days in normal payer processing. It spent 12 days in internal rework.

The preventive control

Build a clean-claim gate before submission.

The gate should confirm active coverage, correct payer path, authorization status where applicable, required documentation, resident responsibility data, and payer-specific claim requirements.

The goal is not perfection. It is reducing repeatable defects before they restart the payment cycle.

If your team is resubmitting claims routinely but cannot identify the most common correction reason, LTCPro can help build a clean-claim review process tied to the payer and workflow causing the defect.

Request a Clean Claim Workflow Review →

The Eligibility and Authorization Clock

Some 90+ day balances begin with information that changed before billing ever started.

A resident may move between Medicare, Medicaid fee-for-service, Medicaid managed care, commercial coverage, private pay, or another payer pathway. The facility may also need to update resident liability, plan assignment, authorization status, or continued-stay information.

These are not interchangeable workflows.

Eligibility errors restart the clock

If an SNF bills the wrong payer, it may receive a rejection, denial, pend, or payment hold. The team then verifies coverage, corrects the claim, resubmits it, and waits for a new adjudication cycle.

The original payment timeline no longer matters. The corrected claim has entered a new workflow.

A facility should verify payer information at meaningful triggers, such as:

  • Admission
  • Start of a new month, where appropriate
  • Medicare coverage ending
  • Hospital readmission
  • Payer or plan change
  • Medicaid eligibility update
  • New managed-care assignment
  • Eligibility-related rejection or denial

Exact requirements vary by state Medicaid program, MCO, payer, resident status, and service line. The facility should validate its verification workflow against the relevant payer and state guidance.

Authorization gaps create longer recovery paths

Authorization issues can be particularly time-consuming because correction may require coordination among admissions, clinical leadership, utilization review, the payer, billing, and A/R.

A claim may require:

  • Identification of the authorization gap.
  • Verification of dates, units, and covered services.
  • Supporting documentation.
  • A payer inquiry or retroactive review, where available.
  • A corrected claim or appeal.
  • Follow-up through adjudication.

That is why an authorization issue can quickly become a 90+ day balance.

The best control is not after-the-fact appeal work. It is an active authorization tracker.

Authorization control Why it matters
Start and end date Prevents billing beyond approved periods
Authorized and used units Identifies utilization risk before limits are exceeded
Continued-stay review date Creates a proactive renewal trigger
Payer and plan Keeps requirements payer-specific
Required documentation Reduces last-minute record requests
Primary and backup owner Prevents a single-person dependency
Escalation rule Brings high-risk cases to leadership before expiration

For organizations that need more formalized tracking, LTCPro’s prior authorization services can help establish authorization worklists, expiration controls, and follow-up workflows.

The Pend That Became a 90-Day Balance

A pend is often where a claim stops moving quietly.

The payer may need records, clarification, corrected information, or additional support before completing adjudication. If the request is not recognized, assigned, and answered quickly, the claim can remain unresolved for weeks.

Eventually, it may become a denial.

Why pends get missed

Pends often fall between teams:

  • The payer notice reaches a shared inbox.
  • Billing assumes clinical will provide the requested records.
  • Clinical assumes the request is administrative.
  • No one records the deadline.
  • The claim remains listed as “in process.”
  • The payer closes or denies the claim after the response window ends.

The facility does not necessarily have a payer problem. It has an exception-management problem.

Build a pend command queue

A pend queue should be distinct from both general A/R and denials.

Every pend should include:

  • Resident or account identifier
  • Payer and plan
  • Claim number
  • Pend reason
  • Date of payer request
  • Required information
  • Assigned owner
  • Payer deadline, if provided
  • Internal due date
  • Next follow-up date
  • Dollar value
  • Documentation location
  • Escalation status

The operating rule is simple:

No pend should exist without a named owner, next action, and due date.

Facilities should prioritize pends by dollar value, payer deadline, documentation dependency, authorization status, and likelihood of converting to a denial.

If pends are sitting in payer portals, emails, or general A/R reports without a documented next action, LTCPro can help implement a dedicated pend workflow for deadline-driven follow-up.

Build My Pend Management Workflow →

When Documentation Turns Into a Payment Dispute

Payment systems do not only assess whether care was delivered. They may assess whether the claim and available records support the billed service, payer requirement, authorization, or coverage determination.

That is why documentation gaps can turn a routine claim into a long-running review, pend, denial, recoupment, or appeal.

The issue is not always that the documentation is clinically inadequate. It may be that the billing team cannot locate the required support, the payer requests a specific form or record, the documentation does not match the billed date span, or the facility’s internal handoff is too slow.

CMS’s improper-payment reporting has repeatedly identified insufficient documentation as a major cause of improper payments in several Medicare and Medicaid contexts. Insufficient documentation occurs when the documentation needed to support payment is missing or insufficient to determine whether payment requirements were met. (Read the CMS FY 2025 Agency Financial Report).

That does not mean every missing-documentation issue represents an improper payment or that a facility should assume a claim will deny. It does mean documentation readiness is a revenue-cycle control.

The documentation-to-billing handoff

For high-risk payer scenarios, define:

  • What documentation billing may need
  • Where the document is stored
  • Who retrieves it
  • Who reviews completeness for the payer request
  • How quickly it must be returned
  • Who confirms submission
  • How the facility records proof of submission

A small weekly review of new admissions, payer changes, high-dollar accounts, and open documentation requests can reduce the last-minute scramble that causes payment delay.

Medicare Claims Can Also Reach 90+ Days

Medicare is often associated with shorter clean-claim processing timelines, but a Medicare claim can still age when it leaves the routine adjudication path.

CMS’s prompt-payment requirements for clean claims include a 14-day payment floor and 30-day payment ceiling for electronic clean claims. (Read CMS’s Medicare Claims Processing Manual). Those timeframes do not apply in the same way when a claim requires additional review, correction, or supporting information.

For an SNF, Medicare claims may age because of:

  • Additional documentation requests
  • Medical review activity
  • Claim overlaps
  • Billing data errors
  • Coverage or entitlement issues
  • Untimely response to a contractor request
  • Corrected claims not submitted promptly
  • Internal uncertainty about who owns the response
Treat requests for records as time-sensitive production work

Do not manage an additional documentation request through informal email alone.

Create a separate queue that includes:

  • Contractor or payer
  • Resident and claim number
  • Request date
  • Response deadline
  • Required records
  • Documentation owner
  • Billing or A/R owner
  • Submission date
  • Proof of delivery
  • Follow-up date
  • Adjudication outcome

The faster the facility responds, the less time the claim spends in a review state.

A Paid Claim Can Still Leave Revenue Behind

Not all 90+ day revenue problems appear as an unpaid balance.

Some claims are paid partially. Others include recoupments, offsets, unusual adjustment codes, or resident-responsibility amounts that do not match what the facility expected. If payment posting records the remittance and closes the claim without review, the facility may never identify the variance.

That is why payment posting should not be treated as the end of the revenue cycle.

The expected-versus-paid review

For material payer categories, compare:

  • Billed amount
  • Expected amount, where reliable data is available
  • Paid amount
  • Units or days billed and paid
  • Covered and noncovered dates
  • Authorization information
  • Resident liability
  • Adjustment codes
  • Recoupments and offsets
  • Prior payment reversals

Not every payment variance is recoverable. It may be correct under a payer contract, rate methodology, resident-liability rule, coordination-of-benefits requirement, or claim-specific adjustment.

But a variance should be visible, assigned, and researched before it is written off or lost in an adjustment account.

If your payment-posting process records payments but does not identify meaningful payment variance, LTCPro can help create an expected-versus-paid review workflow for high-value claims and payer categories.

Find My Underpayment Variances →

The Weekly 90+ Day Claim Review

A facility does not need a three-hour A/R meeting to improve payment speed. It needs a short, disciplined review of the accounts most likely to affect cash.

Hold a weekly 30-minute 90+ day claim review with the business office leader, billing or A/R owner, and relevant admissions, clinical, MDS, authorization, or finance representatives as needed.

Review only:

  • New accounts entering 61–90 days
  • High-dollar accounts already in 90+ days
  • Claims near timely-filing or appeal deadlines
  • Open pends and documentation requests
  • Authorization-related balances
  • Eligibility and payer-path issues
  • Unresolved underpayments and recoupments
  • Claims with no owner, next action, or follow-up date

Use a simple decision column for each claim:

Claim condition Action decision
Clean claim awaiting routine payment Monitor against payer processing expectations
Missing information or payer pend Obtain and submit the required item by internal due date
Correctable claim error Correct and resubmit promptly
Denial with remaining review or appeal options Assign appeal owner and deadline
Payment variance Validate expected amount and investigate
Balance likely not collectible Escalate for policy, financial, or legal review as appropriate

This turns the 90+ day report from a historical record into an operating tool.

The First 14 Days of a Payment Delay Matter Most

Facilities often focus on the 90-day point because that is when the balance becomes alarming.

But the better intervention point is earlier.

A claim that is rejected on day 3, pended on day 14, or left without authorization follow-up on day 20 has already begun its path toward older A/R. Waiting until day 61 or day 90 makes the work harder.

Create early-warning triggers:

  • Claim rejection not corrected within two business days
  • Pend without response plan within one business day
  • Authorization approaching expiration within 14 days
  • Eligibility discrepancy not resolved before the claim cycle closes
  • High-dollar claim not submitted within the facility’s internal timeframe
  • Payment variance above the facility’s defined review threshold
  • Denial without assigned owner by the next business day
  • Claim without activity for more than seven days

The exact thresholds should reflect facility size, staffing, payer mix, volume, and state- and payer-specific requirements. The principle is consistent: intervene while the claim is still recoverable and before the aging bucket becomes the primary problem.

Where LTCPro Fits in the Payment-Delay Investigation

If a facility’s claims are routinely reaching 90+ days, the immediate question is not whether to outsource every billing task. It is whether the current process has enough structure, visibility, and specialized capacity to prevent and resolve exceptions.

LTCPro can help facilities organize the operational work behind payment speed:

  • Claim-readiness controls before submission
  • Payer-specific eligibility and authorization worklists
  • Pend, denial, and appeal queues
  • High-dollar A/R prioritization
  • Payment-posting and remittance variance review
  • Reporting across admissions, clinical, MDS, billing, A/R, and finance
  • Workflow ownership, deadlines, escalation paths, and management visibility

LTCPro does not determine Medicaid eligibility, replace state Medicaid agencies, MCOs, Medicare Administrative Contractors, or other payers; make clinical determinations; provide legal advice; interpret payer contracts as legal counsel; or guarantee payment, coverage, authorization approval, compliance, or revenue recovery. Final eligibility, payer, clinical, contract, regulatory, and legal determinations should be validated with the applicable agency, payer, MCO, clinical leadership, legal counsel, or qualified advisor.

If your SNF has a growing 90+ day A/R balance and cannot explain where claims are getting stuck, LTCPro can help build a payment-delay workflow that makes each payer exception visible, owned, and actionable.

Request a 90+ Day AR Review →

Key Takeaways

  • A 90+ day unpaid SNF claim is usually the result of an earlier workflow failure, not simply slow payer processing.
  • Follow each high-dollar claim from admission through payment posting to determine whether the delay began with eligibility, authorization, documentation, submission, a pend, a denial, or a payment variance.
  • Federal Medicaid and Medicare clean-claim payment standards provide useful context, but actual timing depends on claim cleanliness, payer workflow, state requirements, managed-care rules, documentation, and follow-up.
  • Pends require their own deadline-driven work queue; they should not be buried inside general A/R or handled only after they become denials.
  • Authorization tracking must include dates, units, documentation needs, ownership, and early alerts.
  • Payment posting should be followed by expected-versus-paid reconciliation for material payer categories.
  • The most productive 90+ day A/R meeting focuses on claims with high dollars, imminent deadlines, unclear ownership, and a recoverable next action.