CRM & Sales
What are the limitations of standard APIs when syncing senior housing CRM data with accounting software?
Last reviewed
Direct answer
A standard API moves records; it does not reconcile meaning. CRM and accounting describe different events — a signed move-in versus a billed day — on different clocks. Typical limits include missing history (only current values), field mappings that drop concession or rate detail, rate limits, one-way flows, and no record of why a value changed. Sync does not settle which system governs.
Why this happens
A move-in can be complete in the CRM days before accounting bills it, or reversed in accounting without the CRM hearing about it. A sync that overwrites one with the other hides a real business difference.
Before connecting the two, agree which system is the source for each field, how conflicts are surfaced and who resolves them. The API then carries data under rules, rather than replacing them.
Hypothetical example: unit availability on a monday
CRM
6 units available
Deposit-held units are marked reserved.
Operations
8 units available
Two units are physically empty and ready, regardless of deposits.
Maintenance
5 units available
Three units are still in turnover.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Availability is a decision, not a fact recorded in one place. It depends on which events the operator counts.
The governance question
Sales data should inform occupancy, not quietly define it. The operator decides how deposits, pending move-ins and turnover affect reported occupancy and availability, and the operator-controlled operating record keeps that rule visible.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Approved definitions for available, reserved and occupied.
- Event matching between CRM move-ins and operating move-ins.
- Visible treatment of deposits and pending move-ins.
- Reconciliation of pipeline against actual census.
- Consistent definitions across sales dashboards and executive reports.
SeniorCRE perspective
In SeniorCRE’s architecture the CRM remains authoritative for pipeline while the operator’s rules decide how pipeline events affect occupancy and availability. Differences between sales and operations are surfaced as disagreements to resolve, not hidden by a merged view. 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.