Accounting & Finance
How can senior living operators reconcile census, payroll, and general ledger exports using operator-approved definitions?
Clicks …Last reviewed
Direct answer
Agree the definitions first — resident day, billable day, worked hour, paid hour and the period cutoff — then reconcile the three exports to those definitions rather than to each other. Record each difference with its cause, resolve it under a written rule, and have finance approve the governing figures before they reach owners.
The executive view
When census, payroll and the GL disagree at month-end, the team usually reconciles by adjusting until totals match. That produces a number but not a rule, so the same work repeats next month. Reconciling to approved definitions turns each month’s fixes into standing rules.
Why this happens
Census exports count residents or days; payroll counts paid and worked hours across pay periods that rarely align with the month; the GL records accruals and reclasses. Each is correct for its own purpose.
Without shared definitions, labor per resident day and revenue per occupied unit can each be calculated several valid ways, and different reports quietly use different ones.
Hypothetical example: month-end labor ratio for one community
Census export
2,610 resident days
Clinical days, excludes bed holds
Payroll export
12,140 paid hours
Two pay periods, one crossing month-end
General ledger
$341,800 labor
Includes an accrual for the split pay period
Governed ratio
4.4 worked hours per resident day
Approved definitions: worked hours, billable days
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Hypothetical figures. Each export was accurate. The governed ratio is the one finance approved because its inputs follow written definitions, and the same definitions apply next month.
The governance question
Finance needs to know not only the number but its authority: which source it came from, which definition applies, what was adjusted, and who approved the adjustment. That is provenance, and it should be inspectable before the number is used.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Provenance for every operating number finance consumes.
- Documented adjustments with original values preserved.
- Shared, approved definitions between operations and finance.
- Continuous reconciliation instead of month-end spreadsheet work.
- A clear marker of which KPIs rest on governed data.
SeniorCRE perspective
SeniorCRE is designed to give finance a governing number with its lineage attached: sources, definition, adjustments and the approving authority. The aim is to reconcile once under governed rules and stop re-reconciling downstream. 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.