Medicaid Pending Residents Accounting Treatment in SNFs
Medicaid pending status creates accounting uncertainty that affects revenue, receivables.

Medicaid pending status sits at the center of one of the trickiest accounting problems in skilled nursing: a facility delivers care today against a payment outcome that won't be known for weeks or months. That gap between service and determination touches revenue recognition, receivables, allowances, and audit exposure all at once. This piece walks through how that gap gets accounted for, from the moment a resident's application goes in to the audits that later test whether the estimates held up.
Why the three possible outcomes, approval, denial, and continued pending, each produce a different financial result
An application enters pending status the day it's filed and stays there until the state acts, and federal rules give states 45 days to decide on a standard application, 90 days if a disability determination is required. States take extensions often enough that pending periods stretching four, five, six months aren't unusual. During all of that time, the facility gets nothing from the state Medicaid agency. Payment is, for practical purposes, frozen.
Three things can happen once a decision comes down, and each one changes the math differently.
Approval means the state pays retroactively to the application date, but at the Medicaid per diem rate, not whatever the facility would have charged a private-pay resident for those same days. The state also nets out the resident's accumulated share of cost before cutting a check. So even a "win" on the application produces a receivable smaller than the gross charges on the books.
Denial means no Medicaid payment at all. The facility now has to chase the full private-pay rate from the resident or family, a receivable that behaves nothing like a Medicaid claim and, historically, collects far worse.
And then there's the outcome that isn't really a resolution: continued pending, often stretching into an appeal. Facilities can't evict during that appeal window, so the exposure just keeps growing while nobody knows whether it will ever convert into cash.
One detail trips up a lot of families and, downstream, a lot of finance departments: if the family pays the full bill while the application sits pending, some states count that as income to the applicant. Pushing the applicant over the $2,982/month income eligibility threshold can flip an approval that looked probable into a denial. That's a bad outcome for the resident, obviously, but it's also a bad outcome for the facility's own recovery, since it just converted a government-program receivable into a private-pay collection problem. Facilities that do accept family payments during the pending window may also owe reimbursement to the family once Medicaid approves retroactively, and recovering money already disbursed back out of a family's pocket is, in practice, difficult.
None of this is theoretical for accounting purposes. A reclassification from "probable approval" to "probable denial" is a revenue measurement revision. It's a revenue measurement revision, because the rate itself changes along with the collectibility. Not every SNF accepts Medicaid pending residents. Those that do are taking on a defined financial risk, and that risk needs to appear in the accounting policy rather than being absorbed quietly into the numbers.
How ASC 606 frames revenue recognition for pending residents before any determination is made
ASC 606 asks how much consideration the entity actually expects to collect for what it delivered. For a Medicaid pending resident, that question doesn't have a clean answer at the time care is given, and the standard has to account for that.
Start with what counts as "the contract." Under AICPA guidance, the contract with the customer is the arrangement with the resident. Medicaid, like any third-party payer, informs how much money is likely to come in, but it isn't itself the customer relationship. Facilities generally disaggregate their revenue by payer class for exactly this reason, and a Medicaid pending resident is its own class, distinct from an approved Medicaid resident, distinct from private pay, with a collection profile that has to be estimated separately.
That estimation is where variable consideration comes in. At the point service is delivered, the facility genuinely does not know if it will collect the Medicaid rate, the private-pay rate, or nothing. ASC 606 permits the expected-value method for estimating that kind of uncertain payment, and it also allows a portfolio approach as a practical expedient, grouping similar contracts together and applying historical collection experience rather than predicting each resident's outcome individually. For a cohort of pending residents, portfolio-level estimation is really the only workable method; predicting any single application's outcome with precision isn't realistic, but a facility's historical approval and denial rates across hundreds of applications are.
The accounting shifted meaningfully from the old model here. Before ASC 606, unpaid amounts a facility didn't expect to collect were recorded as bad debt expense. Under 606, those amounts are estimated up front, at the portfolio level, as implicit price concessions, and they reduce revenue directly rather than appearing later as an expense line. Any amount the facility anticipates having to return to a government payer gets excluded from the transaction price from the start.
And estimates change. When new information comes in, whether that's a Medicaid approval landing at a lower rate than assumed or an outright denial, ASC 606-10-32-14 requires the revision to hit the period in which it occurs. There's no going back and restating prior periods. GA8 Tenants, a multi-facility SNF operator whose financials are filed with the federal securities regulator, illustrates the mechanics: it applies the portfolio approach as a practical expedient, grouping contracts with similar characteristics across its Medicaid, Medicare, private-pay, and other payer classes as a practical expedient.
For finance teams building out policy, the 2019 AICPA Audit and Accounting Guide on Revenue Recognition, produced out of the AICPA's industry task forces including the Health Care Entities Revenue Recognition Task Force, remains a useful (if nonauthoritative) reference for applying ASC 606 and ASC 340-40 specifically to healthcare arrangements.
Recording the receivable and the contractual adjustment during the pending period
Every day of care produces a gross charge on the books. For a pending resident, that gross figure is close to fiction, since it's unlikely to match what actually gets recognized as revenue no matter which of the three outcomes eventually plays out.
The gap between the gross charge and the amount the facility expects to collect, assuming approval looks probable, gets recorded as a contractual adjustment, a reduction to revenue rather than a bad-debt charge, consistent with the implicit-price-concession treatment ASC 606 calls for. That distinction matters on the income statement. A contractual adjustment shrinks revenue at the point of recognition. Bad debt expense, by contrast, is recorded after recognition rather than reducing revenue at the point of service, which doesn't accurately reflect the uncertainty present from the moment care is delivered.
Patient liability income, the resident's share of cost after the Personal Needs Allowance and any allowable deductions, deserves separate tracking. It's more certain than the eventual Medicaid portion (the resident either has the income or doesn't, and state formulas are precise about how much gets protected), so it should be recognized as it's received or becomes due, and classified apart from the Medicaid receivable itself.
What happens when the facility genuinely can't say which is more likely, approval or denial? The transaction price in that case should reflect a probability-weighted expected collection, a number that comes in lower than either "assume approval" or "assume the full private-pay rate." That's a conservative constraint by design: when the outcome is a coin flip, the revenue recognized should look like a coin flip.
Once a determination lands, the books catch up. Approval triggers reclassification from pending to Medicaid, a true-up of the contractual adjustment to the actual approved rate, and a reconciliation of whatever patient liability payments have accumulated against the approved share of cost. Denial triggers a different reclassification, from pending to private-pay/self-pay, and a reassessment of the implicit price concession against private-pay collection history, which tends to run worse than Medicaid collection rates. That reassessment can mean reducing revenue in the period the denial hits, not spreading the hit backward.
None of this works without consistency. Payer-class accounting policies need to be written down and applied the same way across every pending resident, so that internal finance staff and outside auditors alike can reproduce the estimate from the documented policy rather than from institutional memory when checking the numbers at period-end.
Estimating the allowance for doubtful accounts for pending receivables on the balance sheet
The allowance for doubtful accounts exists to state receivables at what a facility actually expects to collect, not at face value. For Medicaid pending receivables specifically, that allowance has to capture two separate layers of risk stacked on top of each other.
First, there's the rate haircut: even on approval, Medicaid pays less than gross charges. Second, there's the collection risk on denial: once a pending resident converts to self-pay, the facility is now chasing a receivable type with historically weaker collection odds. Both layers need to be reflected, and since no one knows in advance which pending residents will land in which bucket, the estimation has to happen at the portfolio level using historical approval rates, historical denial rates, and the facility's own post-denial collection experience, not resident-by-resident guessing.
Consider how that plays out numerically. If a facility's historical data shows it collects around 20% of charges from self-pay patients, a figure consistent with portfolio-level collection experience, and some share of pending residents historically end up converting to self-pay after denial, that 20% collection rate becomes a direct input into the allowance calculation for the denial-risk slice of the pending cohort. The allowance isn't static either. Every reporting period, new approvals and denials on previously pending cases feed back into the historical rates used for whatever's left in the cohort.
Scale matters here, and GA8 Tenants offers a concrete reference point: across eight skilled nursing facilities, its SEC-filed financials as of December 31, 2023 showed an allowance for doubtful accounts of $2,094,463 against accounts receivable of $13,073,080. That's a meaningful share of gross receivables reserved against, a useful benchmark for gauging whether a facility's own allowance is in a reasonable range relative to its receivable base.
Implicit price concessions baked into that allowance won't appear as a separate line on the face of the financials, and AICPA guidance suggests facilities think about whether footnote disclosure of aggregate price concessions would actually help financial statement readers, Medicaid auditors among them, who specifically look for uncompensated care and bad debt figures when they review a facility's books.
Writing an account off against the allowance should happen only once collection efforts have substantially stopped, not simply at the moment of denial. Denial ends the Medicaid path. It doesn't end the facility's obligation to actually try to collect from the resident or family before that receivable gets written off.
How the SNF VBP rate environment and FY 2026 payment updates affect pending-period estimates
The Medicaid per diem used in a contractual adjustment comes from the state plan, not from CMS, so a facility can't simply borrow a Medicare rate assumption and apply it to a Medicaid pending calculation. But the broader Medicare rate environment still matters, because it shapes total facility revenue and shifts how much weight Medicaid pending residents carry within the overall payer mix.
CMS finalized the FY 2026 SNF PPS rule on July 31, 2025 (published in the Federal Register on August 4, 2025), raising SNF PPS Medicare rates by 3.2%, worth about $1.16 billion in additional payments nationally compared to FY 2025. That figure comes from a 3.3% market basket increase, a 0.6% forecast error adjustment, and a 0.7% productivity cut netted against each other.
Layered on top of that is a separate incentive program for skilled nursing facilities, which withholds 2% of Medicare Part A fee-for-service payments and redistributes between 50% and 70% of that pool back to facilities as incentive payments based on performance. Facilities on the losing end of that redistribution have to factor the net withhold into revenue projections, and while that's a Medicare mechanism, not a Medicaid one, it affects the cash flow planning that in turn shapes how much cushion a facility can afford to build into its Medicaid pending allowance. Facilities that miss SNF Quality Reporting Program requirements face a separate 2-percentage-point cut to their Annual Payment Update, another rate contingency that belongs in the same revenue model.
Dual-eligible residents complicate the pending-period math further. If a pending applicant is also a Medicare beneficiary, Medicaid functions as a secondary payer once approved, a different payment structure than a resident whose only coverage is Medicaid, and the contractual adjustment and patient liability calculations need to reflect that sequencing.
And rate changes mid-pending-period aren't rare. If a state adjusts its Medicaid rate while a resident's application sits open, ASC 606-10-32-14 requires the facility to update its transaction price estimate in the period the rate change happens, as a cumulative catch-up adjustment, rather than waiting for the final determination to true everything up at once.
Audit scrutiny on Medicaid pending receivables
Financial statement auditors treat the Medicaid pending allowance as a place where judgment can go wrong quietly, and they test it accordingly. Expect scrutiny on the documentation behind the payer-class estimation policy, its consistent application period over period, and the supportability of the historical approval and denial rates behind the portfolio estimate with actual data rather than assumption.
Internal controls matter as much as the estimate itself. Credit policies, segregation of duties, and ongoing monitoring of allowance adequacy are the mechanisms auditors expect to see supporting the reliability of the whole allowance-estimation process, not just the final number.
Regulatory audit activity adds another layer of pressure. Year-end 2025 guidance points to elevated OMIG audit activity, including property audits, claims reviews, MDS audits, payment integrity audits, and dropped-services reviews, any of which can reveal a liability that then needs to be reserved and disclosed. Dropped services are a particular risk: if a facility kept billing for services it had actually stopped providing during a pending period, an OMIG finding could create a retroactive liability that has to be evaluated for disclosure, or recorded outright, once it's both probable and estimable.
Statutory Minimum Direct Resident Care Spending requirements, the so-called 70/40 Rule with its 5% profit cap, are now in effect and worth watching closely for facilities carrying large Medicaid pending cohorts, since those cohorts affect the underlying cost structure the rule measures against. Where non-compliance and any related penalty are both known and can be estimated, that calls for a contingency disclosure or an outright liability, not silence.
Related-party transactions draw separate scrutiny. More than three-quarters of nursing facilities nationally report payments to related parties, and the contractors that process Medicare claims on the government's behalf don't review those related-party costs as part of standard oversight, even though those costs flow directly into cost reports and can inflate the payments a facility receives. Auditors reviewing a facility with meaningful Medicaid pending exposure should expect related-party disclosures to get the same level of attention as the receivables themselves.
Beyond OMIG specifically, year-end 2025 audit priorities include Cash Receipts Assessment reconciliations, quality pool adjustments, shifts in state budgets, public health law compliance, and pending litigation, all items identified as capable of materially moving the numbers. Medicaid pending receivables touch several of these at once. They tend to draw more audit attention than a single balance-sheet line might suggest it deserves.
Where Medicaid pending receivables sit within the HUD Section 232 audit layer
Facilities financed through HUD's Section 232 program face a second, distinct audit obligation layered on top of everything above. The program insures more than 3,600 loans nationally, with an unpaid principal balance north of $32 billion, so this isn't a niche corner of SNF financing. Annual audited financial statements are required within 90 days of fiscal year close, under 24 CFR 5.801 and 200.36, and the current Section 232 Handbook carries provisions that take effect January 5, 2026.
The structural wrinkle that matters most for Medicaid pending accounting is who's actually being audited. HUD's scrutiny centers on the borrower, the property-owning entity, while Medicaid pending receivables live on the operator's books. When the operator and the borrower are separate entities, which is common in SNF real estate structures, the operator's statements may only be operator-certified rather than independently audited. Once the operator and the borrower are the same entity, though, a full audit is required, and that audit has to capture the whole receivables picture, pending-period estimates, allowances, and all, since there's no longer a separate entity to draw the line around.
HUD-required escrow accounts, things like replacement reserves, property tax escrows, and insurance escrows, sometimes end up recorded on the operating company's books instead of the borrower or property company's, a reclassification finding that appears more often than most in Section 232 audits. That's a structural error, not one tied to a single payer program, but it has the same effect as a misstated receivable: it obscures how much cash is actually available to service the debt HUD insured in the first place. For a facility already managing the layered uncertainty of Medicaid pending accounting, getting that entity-level separation right is one more place where precision at the outset saves a much harder correction later.

