How does SeniorCRE reconcile payer remittances against expected PDPM and managed-care reimbursement?
Roadmap — not built
The platform does not yet ship a dedicated module for this workflow. The “How the platform runs it” description below reflects designed-and-planned behavior, not currently shipping code. Outcome figures are modeled targets.
Design target · Expected outcome
+0.5–2% net Medicare/MA revenue recovered
Design target modeled from workflow design. No operator community has been measured, no approved Evidence Record supports it, and business outcomes remain contributory — figures are targets, not results. See Industry Findings for methodology.
Incumbents this workflow touches
Performs in-platform: Manual 835 review against expected PDPM rate sheet
Integrates with (Tier 3): Availity · Waystar · Change Healthcare · Optum
SeniorCRE does not “replace” the EHR. Where PointClickCare, MatrixCare, Yardi, or OnShift are in place, the workflow runs on top of the existing record via integration.
The problem
When a Medicare 835 comes back at less than the expected PDPM rate — or a Medicare Advantage payer applies an undisclosed contractual adjustment — most operators post the cash and move on. The underpayment is never appealed, and the pattern is invisible until the same payer underpays the next 200 claims.
How the platform runs it
Every UB-04 claim has an expected reimbursement computed at submission from the HIPPS code, length of stay, and contracted rate. When the 835 arrives, the actual is matched line-by-line against expected. Variances above tolerance — by HIPPS, by payer, by plan — queue for appeal with supporting documentation already attached. Trend reporting shows underpayment patterns by payer plan and by month.
On the shift
The 835 from a managed-Medicaid plan posts overnight. The system matches each line against the expected reimbursement computed when the claim was submitted. Twelve lines came in below expected; eight are inside tolerance, four are queued for appeal with the original claim, the supporting documentation, and the payer’s contract rate already attached. The CFO opens the trend report — this payer has underpaid by an average of 1.4% over the past quarter, which is now a renegotiation talking point.
What the outcome looks like
SNF operators should expect to recover 0.5–2% of net Medicare and Medicare-Advantage revenue that previously aged out as silent underpayments. AL/IL private-pay portfolios should not expect this lift — the workflow is targeted at Medicare and managed-care payers.
What goes wrong without it
On most operators’ stack, the cash from the 835 is posted and the variance is invisible. The CFO finds out about the underpayment when she happens to spot-check a claim, by which time appeal windows have closed on most of them. The renegotiation conversation with the payer is anecdotal — "I think you’re underpaying us" — instead of "your last 200 PDPM payments were 1.4% below contract."
Sources for baselines cited above
Industry benchmarks referenced in the problem statement or outcome come from these third parties. SeniorCRE figures are labeled expected outcome — modeled from workflow design and benchmarks, not yet measured in a customer community.
- CMS — SNF PDPM and payment policy manual
Centers for Medicare & Medicaid Services
Show me the evidence
Operators do not buy claims. They buy proof. If anything on this page reads as aspirational, ask us to walk you through the surface in production for a community at your acuity and payer mix.
Where this connects in the platform
Every financial workflow runs on the same record. These are the feature pages, head-to-head comparisons, and pillar articles that go deeper on the surfaces this workflow touches.
Feature surfaces
Compared head-to-head
Regulatory and accounting references
Financial workflows on this page reflect CMS PDPM and PDGM payment rules, GAAP revenue recognition (ASC 606), and the state Medicaid case-mix programs that drive reimbursement.
- Patient Driven Payment Model (PDPM) — SNF Payment Methodology
CMS
Component scoring (PT, OT, SLP, Nursing, NTA) and the variable per-diem adjustments that drive Part A revenue.
- Medicaid Case-Mix Reimbursement — RUG-IV and successor systems
Medicaid.gov
State-level case-mix methodology overview; each state files its own State Plan Amendment with rate calculation detail.
- ASC 606 — Revenue from Contracts with Customers
FASB
The GAAP standard for revenue recognition; governs how room-and-board, ancillary, and Medicaid revenue is recognized over the resident stay.
- OIG Compliance Program Guidance for Nursing Facilities
HHS OIG
Federal expectations for billing integrity programs — drives audit-log requirements and segregation of duties around claims.