Häufig gestellte Fragen
What does Single Point of Truth (SPoT) mean?
Single Point of Truth (SPoT) refers to the principle that every piece of information in a company has exactly one organisationally and technically authoritative source from which all systems and departments obtain it. If, for example, revenue or a customer address is queried, there is exactly one definitive version instead of several contradictory versions from different tools. Other places where the information appears are considered derived views or copies that draw their value from this one source. The SPoT is primarily an organisational determination of data ownership and not necessarily a single physical database.
Is Single Source of Truth (SSoT) the same as Single Point of Truth (SPoT)?
In the professional literature, Single Source of Truth (SSoT) and Single Point of Truth (SPoT) are used largely synonymously and describe the same idea of a single authoritative data source. Single Source of Truth is the more common term in the English-speaking world, while Single Point of Truth appears more frequently in the DACH region. If one draws a finer distinction, 'Single Point of Truth' places more emphasis on the one authoritative point of access and maintenance, while 'Single Source of Truth' highlights the authoritative data source as a concept. This distinction is fluid, however, and in everyday usage both terms generally mean the same thing.
What role does the ERP system play for the Single Point of Truth?
In many companies, an ERP system is the natural Single Point of Truth for transactional data such as customers, items, prices, orders and postings, because it consolidates this data across departments. Other systems such as CRM, web shop, marketplaces or PIM then obtain their master data from the ERP via interfaces instead of keeping their own lists. For analytical data and KPIs, by contrast, a data warehouse or lakehouse typically assumes the SPoT role, because it consolidates ERP data with web tracking, CRM activities and market data. What is decisive is a clear determination of which system leads for which data object – the ERP is a candidate, but not automatically the right source for every data domain.
How does the Single Point of Truth differ from a System of Record?
A System of Record (SoR) is the authoritative source for a specific data domain, for example the CRM for customer data or the ERP for financial data, and is thus limited to one segment at a time. The Single Point of Truth aims to designate exactly one such leading system per data object and to supply the remaining systems from it. In larger architectures, a distinction is also often made between the operational System of Record and a consolidated Source of Truth for analysis and reporting that merges data from several systems. Put simply, the System of Record safeguards data integrity at the level of individual records, while the SPoT idea ensures that everyone uses the same authoritative source.
What is the connection between Master Data Management and SPoT?
Master Data Management (MDM) is a central operational implementation of the SPoT principle, because the Single Point of Truth initially describes a target state, not a specific tool. MDM defines which system is the master for which data domain, establishes governance roles such as data owner and data steward and defines maintenance workflows, often with a four-eyes principle and data quality checks. To distribute the data to dependent systems, dedicated MDM platforms or the ERP's own master data modules are used, connected via APIs or an enterprise service bus. Important is the distinction that Forrester, among others, points out: MDM is not automatically the same as a Single Source of Truth, but one of the means of achieving it.
Why is a Single Point of Truth so hard to implement in practice?
Common hurdles are historically grown best-of-breed landscapes of ERP, CRM, shop, PIM and separate Excel lists, each maintaining its own data sets. Added to this are multiple parallel ERPs resulting from mergers and acquisitions, whose consolidation often takes years, as well as a lack of master data governance when no one is clearly responsible for maintaining master data. Departmental politics around KPI definitions and the technical complexity of timely replication across many systems also complicate the endeavour. A step-by-step introduction per data domain with prior cleansing of legacy data is therefore advisable rather than a big-bang approach.
What benefit does a Single Point of Truth deliver – and is the effort justified?
A Single Point of Truth reduces coordination effort, avoids contradictory answers and increases the reliability of analyses, because everyone involved accesses the same version of the data. Without it, typical symptoms arise such as Excel sprawl, lengthy meeting discussions about whose number is correct and reports from different tools that contradict each other. Industry analyses underline its relevance: Gartner put the average cost of poor data quality at around 12.9 million US dollars per year per organisation, and according to an Experian survey around 88 percent of companies see a unified data source as a lever for better data accuracy. Overall, the effort of continually resolving inconsistencies usually exceeds the initial effort of building a SPoT architecture in the long run, even though a SPoT ensures consistent versions but not automatically factually error-free data.