Accounting & Finance
How should census from a clinical system such as MatrixCare be reconciled with the general ledger?
Last reviewed
Direct answer
Compare resident days from the clinical census with billed and posted resident days for the same community and period, list every difference, and decide in writing which source governs each reporting purpose. Clinical census usually governs care and staffing measures; the billing sub-ledger and general ledger usually govern revenue. Review each exception with a named owner before close.
The executive view
Census and the ledger disagree for ordinary reasons: admissions and discharges posted on different dates, hospital leave, respite stays, second-occupant days and billing holds. The risk is not the gap itself but reporting a figure without saying which source produced it. Assigning authority by purpose, and recording each exception, makes the number defensible to a board, lender or owner.
Why this happens
Each system can be correct for its own purpose: the clinical record counts who was in the building, billing counts who was charged, and the ledger records what was posted.
Without a named governing source, occupancy, revenue per occupied unit and labor ratios are calculated from different denominators across reports.
Census-to-ledger reconciliation for one month
Educational guidance, not an implemented SeniorCRE workflow. SeniorCRE is designed, not yet implemented in any community, and named-vendor connectors (including MatrixCare) are roadmap.
Pull the same period from each source
Export resident days by community from the clinical census, the billing sub-ledger and the general ledger for one closed month.
Accountable owner: Controller
Acceptance check: Three totals per community for the same dates.
Classify every difference
Assign each gap to a reason: timing, leave, respite, second occupant, billing hold or error.
Accountable owner: Controller with the business office manager
Acceptance check: No unexplained difference above an agreed threshold.
Assign authority by purpose
Record which source governs care and staffing measures and which governs revenue and occupancy reporting.
Accountable owner: CFO with clinical leadership
Acceptance check: A written definition and named source per reporting purpose.
Review and close exceptions
Give each true error an owner and correction date; carry timing items forward to next month.
Accountable owner: Controller
Acceptance check: An exception log reviewed before close.
Measures to baseline before expanding
- Communities where all three totals are explained
- Exceptions with a named owner and resolution date
- Reports that state their governing source
Governance checks only; they are not accounting or audit advice and imply no measured outcome.
Hypothetical example: one synthetic month for one community
Clinical census
2,790 resident days
Counts hospital-leave days while the bed is held.
Billing sub-ledger
2,760 resident days
Two late admissions billed from the following month.
General ledger
2,745 resident days
A respite stay posted to other revenue, not resident days.
Governed revenue figure
2,760 resident days
CFO rules billing governs revenue reporting; the 30-day and 15-day gaps are logged as exceptions with owners.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Illustrative synthetic educational example, not data from any operator, system or measured outcome.
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.
Product names are trademarks of their owners and are used only to identify systems operators run. No claim is made about any vendor’s capabilities; confirm what your configuration provides with that vendor.