How to Reduce Accounts Receivable Days in Nursing Homes: A 10-Step Cash Acceleration Plan

The most important question in a nursing-home A/R meeting is not: What are our AR days?

It is: Which claims are preventing cash from arriving this month, and what must happen next to release them?

A high accounts receivable days figure is not merely a finance metric. It can affect payroll planning, vendor payments, maintenance decisions, agency utilization, capital spending, and the amount of time administrators and business office leaders spend in daily escalation.

Reducing accounts receivable days in nursing homes requires more than asking the billing team to “follow up harder.” Facilities need an admission-to-payment operating system that prevents avoidable claim defects, identifies exceptions quickly, and assigns each high-risk account to a person with a due date and next action.

That discipline matters because Medicaid is the primary payer for 63% of residents in certified U.S. nursing facilities. (Read KFF’s 2025 nursing-facility payer data). When Medicaid eligibility, managed-care authorization, resident liability, claim routing, or payer follow-up breaks down, the impact can scale across a substantial portion of a facility’s census.

Key takeaway: AR days decline when a facility removes delay before claim submission, responds to payer exceptions quickly, and treats underpayments and resident balances as active collection work, not accounting cleanup.

Start With the Right Definition of AR Days

Accounts receivable days, often called AR days or days in A/R, estimate how long it takes a facility to convert delivered care into collected cash.

A common calculation is:

AR Days = Open Accounts Receivable ÷ Average Daily Net Revenue

For example, a nursing home with $1,200,000 in open A/R and average daily net revenue of $30,000 would have:

$1,200,000 ÷ $30,000 = 40 AR Days

The calculation is simple. The interpretation is not.

A facility with 40 AR days may be performing well or may have a hidden payer problem, depending on payer mix, claim aging, authorization requirements, Medicaid-pending accounts, resident balances, and the proportion of claims that are clean but still awaiting routine adjudication.

That is why leadership should not stop at total AR days. Review AR by:

• Payer and plan
• Medicaid fee-for-service versus Medicaid managed care
• Claim age
• Dollar value
• Claim status
• Denial or pend reason
• Authorization status
• Eligibility status
• Timely-filing or appeal deadline
• Assigned owner and next action

The goal is not just to lower a number. It is to make cash movement predictable.

The 10-Step Cash Acceleration Plan

Step 1: Create a clean-claim gate before submission

A claim cannot move quickly if it enters the payer system with avoidable defects.

A clean-claim gate is a short, consistent review before a claim is submitted. It should test whether essential billing information is complete and aligned.

For each claim or claim batch, confirm:

• Coverage is active for the billed dates of service.
• The payer path is correct.
• Medicaid fee-for-service and Medicaid managed care are distinguished where applicable.
• The plan assignment is current.
• Authorization is active when required.
• Authorized dates and units align with billed services where applicable.
• Required supporting documentation is available.
• Provider and facility identifiers are correct.
• Resident liability or patient-pay information is current where relevant.
• Required claim fields and payer-specific data elements are complete.

The purpose is not to create another manual bottleneck. It is to prevent predictable errors from restarting the payment clock.

Federal Medicaid rules distinguish between clean claims and claims that require additional correction or information. Under 42 CFR § 447.45, state Medicaid agencies must generally require providers to submit claims within 12 months of the date of service and meet specified timely-payment standards for qualifying clean claims. (Read the federal clean-claim timely-payment rule (42 CFR § 447.45)). The applicable workflow can still vary by state Medicaid program, MCO, payer contract, and claim circumstance.

Operational control: Track the top five causes of corrected claims each month. Update the clean-claim gate when one cause repeats.

Step 2: Reduce days from service to claim submission

Some A/R delay begins before the claim reaches a payer.

A facility may lose days because discharge information is incomplete, authorization data is not available, resident liability is not updated, charges are not finalized, or the billing team is waiting for documentation that no one has been assigned to obtain.

Every day removed between service and submission reduces the A/R cycle by roughly one day.

Create a weekly submission clock:

A daily “missing-items” queue is often more useful than repeated email requests. The queue should show the resident, payer, dollar impact, missing item, owner, due date, and escalation path.

Step 3: Reverify eligibility and payer path at defined triggers

Eligibility verification should not be treated as a one-time admission task.

Resident coverage, plan assignment, managed-care enrollment, Medicare status, and payer responsibility can change. The exact verification cadence depends on the applicable payer, state Medicaid program, resident status, and facility workflow. But relying on admission-only verification can increase the chance of billing the wrong payer or using outdated coverage information.

Use a trigger-based verification schedule:

• At admission
• At the beginning of each month, where appropriate for the payer and program
• When Medicare coverage changes or ends
• After hospital readmission
• When an MCO plan assignment changes
• When the resident’s Medicaid eligibility status changes
• When the facility receives a payer rejection, pend, or eligibility-related denial
• Before submitting high-dollar or long-stay claims where additional confirmation is appropriate

A payer-path error does more than create a denial. It can force the facility to rebill, delay payment, create duplicate work, and obscure which balance should be pursued first.

Step 4: Treat pends as a separate urgent queue

A pend is not simply a denial that has not happened yet. It is a claim waiting for an action, document, clarification, or payer decision.

If the facility does not separate pends from denials, pends can sit too long because staff assume they are awaiting normal processing when they actually require a response.

Build a dedicated pend queue with:

• Resident and claim identifier
• Payer and plan
• Date of payer request
• Pend reason
• Required document or action
• Internal owner
• Payer response deadline, if available
• Next follow-up date
• Dollar value
• Escalation status

Use a short daily or near-daily review for high-dollar and deadline-sensitive pends.

A useful operating rule is: no pend should exist without an owner, a next action, and a next follow-up date.

Step 5: Control authorization dates, units, and ownership

Authorization failures can create some of the longest A/R cycles because the facility may need to gather documentation, correct billing, request retroactive review where allowed, appeal, or absorb a noncovered balance.

Requirements vary by payer, MCO, state Medicaid program, service line, contract, and resident situation. Facilities should not assume that a process used for one plan applies to another.

A practical authorization tracker should include:

• Resident name or account identifier
• Payer and plan
• Authorization reference number
• Authorized service dates
• Authorization end date
• Approved units or days
• Units or days used
• Remaining units or days
• Required continued-stay review date
• Required documentation
• Primary owner
• Backup owner
• Escalation contact

The tracker should produce alerts before expiration, not after.

A short weekly review between admissions, clinical leadership, the authorization owner, billing, and the business office can prevent many avoidable handoff failures.

For long-term care organizations that need structured authorization support, LTCPro’s prior authorization services can help organize authorization workflows, deadlines, and follow-up responsibilities.

Step 6: Turn documentation completeness into a measurable control

“Improve documentation” is not an operating instruction.

A more useful approach is to define what complete documentation means for the highest-risk payer scenarios, then measure whether the required information is available before billing and during payer follow-up.

Create a payer- and service-specific proof packet where applicable. It may include the documentation categories needed to support billing, authorization, continued stay, or a payer request. The exact packet should be validated against the payer’s requirements, facility policies, clinical documentation standards, and applicable state or federal rules.

A workable control system can include:

• Standard templates for common high-risk events.
• A weekly admissions-to-billing review for new residents and payer changes.
• A short clinical-to-billing exception review for high-dollar claims.
• Spot audits of a small sample of submitted claims.
• A pass/fail score for documentation readiness.
• A documented escalation route when information is missing.

The objective is not to turn billing into a clinical decision-maker. It is to ensure the billing team knows when required information is missing and who must resolve the gap.

Step 7: Work denials daily through triage

Denials should not be handled randomly, once a week, or only when they reach an older A/R bucket.

A denial has at least three dimensions:

• Time: Is there a correction, reconsideration, or appeal deadline?
• Value: How much revenue is at stake?
• Cause: What workflow or payer issue led to the denial?

Organize denials by categories such as:

• Eligibility or coverage
• Payer sequencing
• Authorization
• Documentation
• Claim-format or data issue
• Timely filing
• Resident liability
• Coding or billing logic, where applicable
• Duplicate or coordination-of-benefits issue
• Payment or recoupment issue

Then apply a triage rule:

The goal is not only recovery. It is prevention.

At the end of each month, identify the denial category with the highest dollar value or highest volume. Make one specific process change to reduce it next month.

Step 8: Reconcile payments for underpayments and recoupments

Denials are visible. Underpayments are often not.

A facility may post a payment, close the claim, and move on without determining whether the payment was consistent with the expected amount. That can leave recoverable revenue unaddressed.

For meaningful payer categories, establish an expected-versus-paid review process when the necessary data is available.

Review:

• Paid amount compared with expected amount
• Dates of service
• Covered versus noncovered days
• Units billed and units paid
• Resident responsibility
• Contractual adjustment pattern
• Payer adjustment codes
• Offsets and recoupments
• Reversals and corrected remittances

Not every variance represents an underpayment. It may reflect contract terms, rate updates, payer edits, resident liability, coordination of benefits, recoupment activity, or claim-specific facts.

The operational objective is to identify exceptions promptly enough to research, correct, dispute, appeal, or reconcile them before the recovery opportunity becomes difficult to pursue.

Step 9: Separate resident balances from insurance A/R

A/R is not only payer A/R.

For Medicaid residents, patient liability changes can affect resident balances. For private-pay residents, delayed collection activity can increase A/R even when insurance billing is accurate. For Medicare and managed-care residents, coinsurance, copayments, and other resident-responsibility amounts may require separate tracking based on the applicable payer rules and resident agreements.

Treat resident A/R as its own managed workstream.

Maintain:

• Patient-liability or resident-responsibility change log
• Effective dates
• Supporting notices or documentation, where applicable
• Separate resident-balance aging
• Statement timing and follow-up cadence
• Payment-plan documentation, where applicable
• Escalation process for unresolved balances
• Distinction between collectible resident balances and balances needing correction

The facility should validate resident-liability amounts and collection practices against applicable state requirements, resident agreements, payer information, and legal guidance where appropriate.

For a wider view of administrative workflow pressure that can affect business-office operations, see LTCPro’s article on automating payroll and compliance in long-term care.

Step 10: Run a weekly AR command meeting

A/R days should not be reviewed only after cash is already tight.

A 20- to 30-minute weekly A/R command meeting can create earlier action if it focuses on exceptions rather than reading a large aging report aloud.

The meeting should answer:

• Which payer balances increased this week?
• Which high-dollar claims need action before the next meeting?
• Which pends require documentation or payer follow-up?
• Which authorizations expire in the next 14 days?
• Which denials have appeal or filing deadlines?
• Which underpayments or recoupments require review?
• Which workflow issue is recurring?
• Which owner has the next action for every material account?

Weekly dashboard

This weekly view converts “Medicaid is slow” into a more actionable statement such as: “Three managed-care authorization issues account for 28% of new 61–90 day A/R, and each has an assigned action due this week.”

A 30-60-90-Day AR Reduction Sprint

Facilities should not attempt to fix every A/R issue at once. Start with controls that reduce new leakage while working older balances systematically.

First 30 days: Stop new avoidable delay

• Implement the clean-claim gate.
• Build a separate pend queue.
• Begin denial triage by dollar value, deadline, and root cause.
• Create a trigger-based eligibility-verification schedule.
• Build or repair the authorization tracker.
• Identify every high-dollar account without an owner or next action.

Days 31–60: Improve handoffs and payment recovery

• Standardize payer-specific documentation proof packets where needed.
• Begin expected-versus-paid payment reconciliation.
• Create an underpayment and recoupment work queue.
• Reduce time from service to claim submission.
• Establish cross-functional reviews for new admissions, payer changes, and high-risk accounts.
• Separate resident A/R reporting from insurance A/R.

Days 61–90: Make the process repeatable

• Update the clean-claim gate based on the top denial causes.
• Set management thresholds for high-dollar pends, denials, and aged claims.
• Build payer-specific A/R dashboards for leadership.
• Assign ongoing prevention actions for recurring workflow failures.
• Test coverage for critical billing, authorization, and A/R responsibilities.
• Review whether the internal model has enough capacity for current census and payer complexity.

When AR Days Stay High Despite a Strong Push

If AR days remain elevated after the facility has improved clean claims, eligibility verification, authorization tracking, pend response, denial triage, payment reconciliation, and resident-balance follow-up, leadership should assess whether the issue is structural.

Possible structural causes include:

• A staffing model without enough backup coverage
• Too many workflows dependent on individual knowledge
• Inconsistent payer-specific processes across facilities
• Lack of capacity for high-dollar A/R follow-up
• Missing integration between admissions, clinical, MDS, billing, and finance
• Reporting that identifies risk after it has already aged
• Limited ability to reconcile payment variance or recurring recoupments

In those cases, the answer may be to redesign the internal operating model, centralize some revenue-cycle functions, or add specialized RCM capacity.

LTCPro helps nursing homes and SNFs organize claims, A/R, authorization, payment-posting, remittance-review, and payer-follow-up workflows around clearer ownership, deadline tracking, and reporting.

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

Frequently Asked Questions

What is a good AR days target for nursing homes?

There is no universal target that applies to every nursing home. A reasonable range depends on payer mix, Medicaid-pending volume, Medicare and managed-care exposure, state-specific rules, authorization requirements, claim complexity, and resident balances. The most useful benchmark is the facility’s own trend by payer and aging category. Rising AR days, especially in 61–90 and 90+ day buckets, should trigger a root-cause review.

Why do nursing homes have high AR days?

Common drivers include delayed claim submission, low first-pass acceptance, incorrect payer path, eligibility changes, authorization gaps, slow pend response, denial backlogs, incomplete documentation, unreviewed underpayments, recoupments, and delayed resident-responsibility collections.

How can a nursing home reduce AR days quickly?

Start by preventing new delay: use a clean-claim gate, reduce time to submission, separate pends from denials, verify eligibility at defined triggers, track authorization deadlines, and assign each high-dollar account an owner and next action. Then work payment variance and older A/R through payer-specific queues.

How quickly must Medicaid pay clean claims?

Under 42 CFR § 447.45, state Medicaid agencies must meet federal timely-payment standards for qualifying clean claims, including paying 90% of clean claims from practitioners within 30 days and 99% within 90 days. The rule includes important definitions and exceptions, and facilities should confirm how state Medicaid, MCO, and payer-specific rules apply to their claims. (Read the federal clean-claim timely-payment rule (42 CFR § 447.45)).

How quickly does Medicare pay clean claims?

Medicare’s prompt-payment standards generally require Medicare Administrative Contractors to pay clean electronic claims no earlier than the applicable payment floor and no later than the payment ceiling. CMS explains in its Medicare Claims Processing Manual that 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. Payment timing can vary based on claim status, processing requirements, and applicable Medicare rules. (Read CMS’s Medicare Claims Processing Manual).

Should nursing homes work A/R from oldest to newest?

No. Aging is important, but A/R should also be prioritized by dollar value, payer, timely-filing or appeal deadline, authorization status, pend reason, documentation dependency, likelihood of recovery, and next action. A newer high-dollar claim with an imminent deadline may require faster attention than an older account with no immediate action available.

Why are underpayments important for reducing AR days?

Underpayments matter because a claim can appear paid even when the facility has not received the amount it expected. Without expected-versus-paid reconciliation, the balance may remain unresolved, be adjusted incorrectly, or become difficult to pursue later. Facilities should validate variances against contracts, payer rules, authorizations, resident responsibility, and claim facts.

Key Takeaways

• Reducing accounts receivable days in nursing homes begins with preventing avoidable delay before claims are submitted.
• Total AR days alone is not enough; analyze A/R by payer, claim status, age, dollar value, deadline, root cause, owner, and next action.
• Medicaid is the primary payer for 63% of residents in certified U.S. nursing facilities, so Medicaid eligibility, managed-care, and payer-path controls can materially affect cash flow.
• A dedicated pend queue prevents information requests from becoming long-aged denial and A/R problems.
• Authorization trackers should include dates, units, alerts, documentation requirements, and clear ownership.
• Payment posting should trigger expected-versus-paid reconciliation for material payer categories.
• A weekly A/R command meeting helps leadership find and resolve the specific workflows blocking cash before balances age.