Single Source of Truth
A Single Source of Truth (SSOT) is the designated authoritative system for a specific business entity or metric — the one place that, when there is a conflict, wins. SSOT is not a single physical database; it is a governance designation: 'For customer billing address, the Billing System is SSOT. For customer marketing preferences, the CDP is SSOT. For employee headcount, Workday is SSOT.' All other systems are downstream consumers that must accept the SSOT's value. The discipline matters because most enterprises have 3-7 systems each claiming to be 'the truth' for the same entity, producing irreconcilable reports and conflicting decisions. SSOT is the prerequisite for trust at scale.
The Trap
The trap is declaring 'the data warehouse is our single source of truth' as if that solves anything. The warehouse is a CONSUMER of upstream operational systems; the question is which OPERATIONAL system is authoritative for each entity. If both Salesforce and the billing system can independently update a customer's address, the warehouse will faithfully reflect the chaos. The other trap is declaring SSOT in policy without enforcing it in pipelines. If marketing keeps overwriting customer attributes in their CDP because 'it's faster than a ticket', the policy SSOT is fiction. Real SSOT requires technical write-locks, not just documentation.
What to Do
For each critical business entity (customer, product, employee, account, financial transaction), produce a 'SSOT Map' that names: (1) The authoritative SYSTEM for that entity, (2) The authoritative FIELD-LEVEL source within that system (e.g., 'first_name comes from billing; preferred_name comes from CDP'), (3) The DIRECTION of data flow to other systems (one-way, no exceptions), (4) The OWNER who arbitrates exceptions. Then technically enforce: downstream systems should sync FROM the SSOT, never write back. Audit quarterly for backdoor writes.
Formula
In Practice
Stripe famously runs much of their internal operations on the principle that the Stripe ledger is the single source of truth for all financial transactions — period. Even sophisticated downstream systems (analytics, fraud, finance reporting) must defer to the ledger; if the ledger says a transaction occurred, it occurred, and other systems must reconcile to it. This discipline is operationally painful in the short term (reconciliation work) but is what allows Stripe to make audit-grade financial guarantees to customers and regulators at massive scale. Without SSOT discipline on transactions, a payments company cannot exist.
Pro Tips
- 01
Be explicit that SSOT is per-FIELD not per-entity. Example: customer's billing address SSOT = billing system; customer's marketing email SSOT = CDP; customer's support ticket history SSOT = Zendesk. Pretending one system owns 'the customer' fails because real businesses have legitimate field-level authority spread across systems.
- 02
Enforce SSOT with one-way sync, not API integration. Bi-directional sync (Salesforce ↔ billing) creates race conditions and silent data corruption. Make downstream systems read-only consumers; if they need to write, route the write to the SSOT system first via a workflow.
- 03
Audit for 'shadow SSOTs' quarterly. Marketing builds a spreadsheet of 'real' customer counts because they don't trust the dashboard; finance maintains a parallel ledger because they don't trust the warehouse. Shadow SSOTs are diagnostic of trust failure; they don't go away by being banned, only by making the official SSOT trustworthy.
Myth vs Reality
Myth
“Implementing a data warehouse creates a single source of truth”
Reality
A warehouse is a consumer of upstream systems. If the upstream systems disagree (Salesforce says 12,000 customers, billing says 11,840), the warehouse will faithfully reflect the disagreement. SSOT is upstream of architecture: it's a governance decision about which operational system is authoritative. The warehouse CONFIRMS SSOT discipline; it doesn't create it.
Myth
“SSOT means one giant system that does everything”
Reality
Effective enterprises have many SSOTs — one per critical entity or field. Trying to consolidate into one mega-system (the 'monolithic ERP' fantasy) fails for every enterprise that has tried it for 30+ years. SSOT is about CLEAR field-level authority across multiple systems, not eliminating systems.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
A retailer has Salesforce, an ecommerce platform, an ERP, and a CDP. All four can update the customer's email address. The data warehouse pulls from all four. Reports show 18% of customers have inconsistent email addresses across systems. What is the single most important fix?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Cross-System Field Consistency (Tier-1 Entities)
Customer master attributes across CRM, ERP, billing, supportExcellent (mature SSOT discipline)
≥ 98%
Good
92-97%
Average Enterprise
82-91%
Poor
70-81%
Crisis
< 70%
Source: https://www.gartner.com/en/data-analytics (Master Data Management benchmarks)
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Stripe
2011-present
Stripe operates with extreme SSOT discipline: the Stripe ledger is the absolute single source of truth for all financial transactions. Every other system (analytics, fraud detection, customer dashboards, finance reporting) must reconcile to the ledger. If the ledger says it happened, it happened — full stop. This discipline is operationally expensive (constant reconciliation work) but is foundational to making audit-grade financial guarantees at scale. A payments company without SSOT discipline on transactions cannot exist; Stripe institutionalized this from day one.
SSOT for Transactions
Stripe ledger (singular)
Other Systems' Authority
Read-only / reconcile
Reconciliation Discipline
Continuous
Outcome
Audit-grade scale
In financial systems SSOT is non-negotiable. The discipline of one authoritative source for transactions is what enables trust, scale, and regulatory compliance.
Hypothetical: 5,000-person Healthcare Network
2018-2022
A hospital system had four EHR instances (from acquired hospitals), three patient billing systems, and a 'unified' patient portal. Each could update patient demographics. By 2020, ~31% of patients had inconsistent addresses, phone numbers, or insurance details across at least two systems. Misrouted appointment reminders contributed to a measurable no-show rate increase. They eventually designated the regional EHR as SSOT for clinical data and a single billing platform as SSOT for financial — a 3-year program. Inconsistency dropped to 6% post-implementation. No-show rate fell measurably; revenue cycle metrics improved.
Pre-Program Inconsistency
31%
Post-Program Inconsistency
6%
Program Duration
3 years
Outcome
Measurable revenue cycle improvement
Multi-system SSOT consolidation is multi-year work, but the operational improvement is real and quantifiable. Healthcare M&A creates SSOT debt that must eventually be paid.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Single Source of Truth into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Single Source of Truth into a live operating decision.
Use Single Source of Truth as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.