When Systems Disagree
Why do senior living operators still have conflicting financial and occupancy reports after integrating their software systems?
Clicks …Last reviewed
Direct answer
Integration moves values between systems; it does not decide which value governs. After integration, each system still applies its own definitions, cutoffs and purposes, so the numbers still differ — they just differ faster. Conflicts stop only when the operator writes which definition and source governs each figure and records approvals.
The executive view
Integration projects are often sold as the end of conflicting numbers, and leaders are surprised when the conflicts survive. The missing step is a decision about authority, which no interface can make on the operator’s behalf.
Why this happens
An integrated census sent to accounting can still be counted differently by accounting, because the accounting definition was never changed.
Integrations can also spread errors: a wrong move-in date entered once now appears in every connected system.
Hypothetical example: after the integration went live
EHR census (integrated)
104
Physical residents
Accounting occupancy
106
Billed units including bed holds
Interface status
Working
Values delivered correctly
Still missing
Governing rule
Which count governs owner reporting
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Hypothetical figures. The integration worked exactly as designed; the disagreement is a definition question it was never meant to answer.
The governance question
The useful question is not "which number is right?" but "which number has authority to govern this decision?" Evidence from each system is preserved, the disagreement is surfaced rather than averaged away, the operator decides which source has authority for the decision at hand, and that determination is written to an operator-controlled operating record with its lineage.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Preserve every source value instead of overwriting it.
- Detect and surface disagreements before they reach a report.
- Apply operator-approved rules about which source governs which decision.
- Record who made each determination, when, and why.
- Make every governing number traceable back to its sources.
SeniorCRE perspective
SeniorCRE is designed around this exact moment. Its Operator-Controlled Operating Record keeps the original values from each system, flags where they disagree, and records the operator’s determination of which value governs, so that every downstream report, recommendation and action reads from a number with known authority. When systems disagree, the operator governs. 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.