CRM changes customer name; ERP does not—invoicing and shipping trust different versions. Meetings shout "finance wins"—next week sales wins. Golden record is not technical replication—it is governance: system of record (SOR) per entity, who may request change, conflict arbitration, sync SLA. Without charter, master data projects stall in reconciliation meetings.
Golden is not "most complete"—it is the one version you can commit externally. Others are copies or request entry points.
Charter Down to Entity Level
Customer, material, supplier, account each have SOR. Sales may initiate customer rename; finance master data approves write to golden and distribute. No direct edits to key fields in copy systems. Conflict tickets have SLA—timeout escalates to data owner.
- Publish critical field list—non-critical fields may differ by system.
- Merge duplicates keep mapping—historical documents trace old codes.
- Interfaces accept golden distribution only—no bidirectional last-write-wins.
Arbitration Must Be Executable
The XYN digital intelligence system makes master data changes SOR-aware workflows—copies read-only on key fields. Charter on the data team wall is not enough—it must enter permissions and interfaces. Executable golden record—reports share one customer; non-executable, analytics runs hard on wrong customer trees.
Pick customer or material—write charter and launch arbitration for one class. Expand after it runs. Writing six at once becomes an unexecuted constitution.
