Multi-System Reconciliation
How do we prevent integrations from spreading incorrect data?
Last reviewed
Direct answer
Put a governance step between receiving data and sending it on. Compare incoming values against other sources and approved rules, hold or flag values that conflict, and only pass on values that meet the authority rules. Avoid automatic overwrites of authoritative fields. Record what was held and why.
Why this happens
Point-to-point integrations copy errors as quickly as they copy correct values.
One upstream delay, such as a late termination in payroll, can spread to several systems within hours.
Example: an integration copies a stale value
Payroll
Team member: active
The termination has not yet been processed.
HR system (copied from payroll)
Team member: active
The integration copies the value as-is.
Scheduling
Team member: terminated
The manager removed them from the schedule.
- Which number governs?
- Operator Authority
- Governing Record
- SeniorCRE Intelligence
- Execution
Illustrative figures. Governance first. Intelligence second. Execution last.
Two systems agree because one copied the other. Agreement produced by copying is not verification.
The governance question
A conventional technology sequence is integrate, normalize, analyze, automate. A governing sequence is evidence, disagreement, authority, governing record, then intelligence and execution. The difference is that disagreement is surfaced and decided by the operator rather than resolved invisibly by software.
Evidence → Disagreement → Authority → Governing Record
What good operating infrastructure should do
- Detect disagreements instead of letting the last write win.
- Route conflicts to the person with authority to decide.
- Distinguish rule-based resolution from human determinations.
- Record every reconciliation decision with its lineage.
- Standardize reconciliation rules across the organization.
SeniorCRE perspective
SeniorCRE’s architecture treats integration as a source of evidence and reconciliation as a governed act. Software can apply rules the operator has approved; anything outside those rules goes to a named person, and the decision is recorded. Unified data is not governed truth. Status: the Governed Operating Record is designed and not yet implemented in any community. What has been built, validated and deployed is published on the evidence page, and nothing here should be read as a production result.