Skip to main contentSkip to navigation
SeniorCRE Logo

Census & Occupancy

Why doesn't our EHR census match accounting?

Last reviewed

Direct answer

The EHR census and the accounting census usually measure different things. The EHR counts residents in care, often including hospital leave and bed holds. Accounting counts billable resident days under payer and contract rules. Timing adds to the gap: admissions, discharges and level-of-care changes reach accounting after they reach the floor. A mismatch is expected until the two definitions are written down and reconciled.

Videos that answer this question

Why this happens

Clinical systems are designed around care: who needs care, documentation and orders today. Accounting is designed around revenue recognition and the close. Both are right for their purpose.

Without a daily comparison at the resident level, the gap is found at month-end as one total, when it is hardest to explain and most expensive to correct.

Hypothetical example: census at 11:00 p.m. on the last day of the month

  • EHR census

    92

    Includes a resident on a bed-hold hospital stay.

  • Accounting census

    90

    Excludes the bed hold and a move-in whose agreement is not yet countersigned.

  • CRM occupancy

    91 of 100 units

    Counts units, not residents, and treats a deposit-held unit as occupied.

  1. Evidence
  2. Disagreement
  3. Authority
  4. Operator-Controlled Operating Record
  5. Intelligence
  6. Execution

Illustrative figures. Coherence before Intelligence.

Residents, billable days and occupied units are three different measures. Calling all three "census" is what makes them look contradictory.

The governance question

Before reconciling census, an operator has to decide which census governs which decision: staffing, billing, investor reporting and sales availability can legitimately use different definitions. The governance step is to approve those definitions, assign source authority for each, and record the determination when sources disagree.

Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution

What good operating infrastructure should do

  • Hold an approved, written definition for each census and occupancy measure.
  • Compare census across systems daily, not only at month-end.
  • Show the specific residents or units behind a census difference.
  • Record which source governs each census measure and why.
  • Keep the original system values alongside the governing number.

SeniorCRE perspective

In SeniorCRE’s architecture, census is a governed measure: each definition is approved by the operator, each source’s value is preserved, and daily differences are surfaced with the residents behind them before month-end. The operator’s determination, not a model, sets the census that staffing, finance and reporting read. Status: the Operator-Controlled Operating Record is designed and not yet implemented in any community. Current capability states and production-entry gates are published in the Evidence Record at the Trust Center; nothing here should be read as a production result.

See the evidence record

All Census & Occupancy questions

Request a 30-Minute AssessmentReview the Evidence Record

Stay up to date

The Senior Housing Journal, in your inbox

Perspectives on operator-governed operating information, capital and operating developments across senior housing & care, and platform updates from SeniorCRE.

By subscribing, you agree to receive the Senior Housing Journal newsletter. Unsubscribe at any time. See our Privacy Policy.