How does SeniorCRE manage rate sheets, payer contracts, and annual increases?
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 · Internal estimate
Full annual increase realized on every line
Modeled estimate from SeniorCRE engineering. Not a result: no approved Evidence Record supports it, and business outcomes remain contributory. See Industry Findings for methodology.
Incumbents this workflow touches
Performs in-platform: Master rate sheet in Excel · Payer-contract folder on the controller’s desktop
Integrates with (Tier 3): Yardi Voyager · PointClickCare AR
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
Rate sheets live in Excel. Annual increases get applied to base rent but forgotten on care levels and ancillary charges. Payer contracts expire silently and roll over at the old rate.
How the platform runs it
Every rate — base, care level, ancillary, payer-specific — lives on the resident or contract record with effective dates. Rate changes apply prospectively across affected residents in one workflow with executive approval. Payer contracts have renewal dates that surface 90 days in advance, with negotiation notes and historical performance attached.
On the shift
On October 15, the executive team approves a 4% rate increase effective January 1. The CFO opens the rate-change workflow, applies the increase across base rent, care levels, and ancillaries, previews the per-resident impact, and routes for final approval. On January 1, every active contract, every claim header, and every billing run reflects the new rates. The renewal-date dashboard shows the two payer contracts that expire in March; negotiation prep is already on the CFO’s calendar.
What the outcome looks like
Operators capture the full annual increase across every line — a 4% increase actually yields close to 4% on the AR, not 2.5% after Excel errors. Payer contracts get renegotiated on schedule with utilization data already attached to the conversation.
What goes wrong without it
On Excel-driven rate management, the 4% increase gets applied to base rent and forgotten on care levels. The ancillary charges still bill at last year’s rate for nine months until someone notices. Payer contracts auto-renew silently because the renewal-date spreadsheet has not been updated since 2024. The realized rate increase is 2.5% on AR — and that 1.5% gap is the difference between a budgeted year and a missed year.
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.