Accounting & Finance
How can a senior living CFO shorten the month-end close?
Last reviewed
Direct answer
Move reconciliation out of the close. Run a day-by-day close calendar with a named owner per task, compare census to billing daily instead of at month-end, post accruals and prepaid reviews before the period ends, and keep one written definition for each reported figure. The close then confirms differences already resolved rather than discovering new ones. APQC's cross-industry benchmarks put the monthly close at about 5 to 10 days; measure your own baseline first.
The executive view
In senior housing & care, most close delay is not journal entries; it is the census-to-billing reconciliation: move-ins, move-outs, care-level changes, second-person fees and respite stays recorded on different dates in the EHR, billing and the general ledger. A CFO shortens the close by making that reconciliation a daily operating routine with written tolerances and owners, and by locking an approved occupancy and revenue figure with its cutoff before owner reporting begins. Evidence of results: SeniorCRE has no operator-production deployment and publishes no measured close-time result. The only published figures on this page are APQC's cross-industry benchmarks, not senior housing & care results; treat any vendor's close-time claim as a target until a baseline, measurement window and observed result are documented.
Why this happens
Census, billing and payroll are kept in separate systems with different cutoffs. A move-in posted in the EHR on the 28th and billed on the 2nd appears as a variance that someone must research after month-end, and these items stack up in the first days of the close.
Definitions drift between communities and between finance and operations: occupied units, billable days and deposit-held units are counted differently. Each disagreement becomes a meeting during the close, and adjustments made in spreadsheets are not retained with the report, so the same items are re-researched next month.
A practical close calendar and census-to-billing reconciliation
An educational starting point an operator can adapt; days are business days relative to period end (BD-3 is three business days before month-end, BD+1 the first business day after). These are practical steps, not SeniorCRE product controls.
Daily during the month: census-to-billing check
Compare EHR census to the billing roster each day for every community: move-ins, move-outs, transfers, hospital leaves, care-level and rate changes, second-person and respite charges. Route each difference over the written tolerance to a named owner.
Accountable owner: Business office manager
Acceptance check: A dated exception log with owner and resolution for every difference.
BD-5: lock the definitions
Confirm the approved definitions of occupied unit, billable day and care-level revenue, and any community-specific mappings, before the period ends.
Accountable owner: Controller
Acceptance check: Definition version recorded for the period.
BD-3: work ahead
Review prepaids, accruals, deferred revenue and suspense accounts; accrue known agency labor and recurring vendor invoices.
Accountable owner: Senior accountant
Acceptance check: Pre-close accrual schedule reviewed.
BD-1: census cutoff
Freeze the census cutoff time. Reconcile open move-in and move-out paperwork so billing reflects the same residents and dates as the EHR.
Accountable owner: Executive director and business office
Acceptance check: Signed cutoff roster per community; zero unexplained census-to-billing differences.
BD+1: billing and revenue
Run resident billing from the reconciled roster; post care-level changes and prorations; reconcile billed resident days to census days.
Accountable owner: Billing lead
Acceptance check: Billed days equal census days, or every difference is explained.
BD+2: payroll and labor
Reconcile payroll hours and agency invoices to the general ledger and to scheduled hours; accrue unpaid hours.
Accountable owner: Payroll and accounting
Acceptance check: Payroll-to-GL reconciliation signed.
BD+3: balance sheet reconciliations
Reconcile cash, resident trust, accounts receivable aging, security deposits and intercompany accounts.
Accountable owner: Accounting team
Acceptance check: Reconciliations prepared and reviewed with preparer and reviewer recorded.
BD+4: review and approve
Flux review against budget and prior month; approve occupancy, revenue and labor figures with their cutoff and definition version.
Accountable owner: CFO
Acceptance check: Approved figures retained with approver, time and source records.
BD+5: owner reporting
Publish owner and lender packages from the approved figures only. Record any later correction as a new, separately approved version.
Accountable owner: CFO
Acceptance check: Reported package traceable to the approved figures.
Measures to baseline before expanding
- Close cycle time in calendar days, measured the same way each month (for example trial balance to approved package)
- Census-to-billing differences open at BD+1, by community
- Post-close adjustments and owner-report restatements per quarter
- Hours spent researching variances during the close, from a documented baseline
Educational guidance. Day targets are illustrative and depend on portfolio size, entity structure and systems; no close-time reduction is promised. SeniorCRE has no measured operator result for close time.
Hypothetical example: census-to-billing reconciliation at bd+1 for one community
EHR census, last day
88 residents
Includes one move-in on the 30th
Billing roster
87 residents
Move-in not yet billed
Exception log
1 difference
Owner: business office; logged on the 30th, not discovered at close
Approved roster
88 residents
Prorated charge posted on BD+1; cutoff and approver retained
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Hypothetical figures, not a measured operator result. The difference was found the day it happened, so the close confirms it rather than researching it.
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.
Sources and scope
References support only the scope described below, not independent product validation or endorsement.
- APQC — How can you improve the month-end closing process?
Cross-industry benchmark (5 to 10 days) and practices: day-by-day checklist with owners, centralized chart of accounts, working ahead. Not senior housing & care specific.
- APQC — Cycle time in days to complete monthly financial close
Definition of the close cycle-time measure and cross-industry median.
