> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://tieback.io/docs/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server. # System of Record > The system formally designated as authoritative for a defined data element or business domain, so that its value is the one relied upon when systems disagree. ## Definition A system that has been formally designated as the authority for a defined data element or business domain. Where several systems hold the same information, the designated system supplies the value that the organisation relies upon, and changes made elsewhere are treated as copies rather than as the record itself. ## Expanded Explanation The designation is administrative, not technical. Any database can physically store a product weight; a system becomes the system of record for weight when the organisation decides that its value governs, names the people accountable for maintaining it, and requires other systems to accept that value rather than compete with it. Authority is normally granted at the level of a domain or an individual attribute rather than for a whole product. A lifecycle management system may be authoritative for engineering specification and material composition, an enterprise resource planning system for commercial and logistics attributes, a laboratory or quality system for test results, and a supplier portal for declarations the supplier itself must stand behind. Each is a system of record within its own scope and a consumer everywhere else. That scoping is what makes the concept workable in practice. Attempting to nominate one enterprise-wide system of record for every product attribute usually fails, because no single system is close enough to every business process that creates the data. Attribute-level and domain-level designation records where authority actually sits rather than where an organisation wishes it sat. A system of record is a place. It is not a reconciled output. Where several systems hold competing values for the same attribute, the reconciled result produced by matching and survivorship rules is a golden record, and the system of record is one of the inputs that reconciliation relies upon. ## Why It Matters A Digital Product Passport must present a single answer per field to a reader who has no way of knowing which internal system produced it. Publishing without designated systems of record means the published value is decided by whichever integration ran last, which is not a defensible position under market surveillance. Designation also gives every field an accountable owner, so a challenged value can be traced to a system, a process and a person rather than to an export file. ## Common Misconceptions #### An organisation should have one system of record Authority is granted per domain or per attribute. Most manufacturers legitimately operate several systems of record at once, each authoritative within a defined scope and subordinate outside it. #### The most recently updated system holds the record Recency is not authority. A value edited yesterday in a spreadsheet does not displace the designated system; it usually indicates an uncontrolled change that governance should detect. ## Related Terms * [Authoritative Source](/docs/knowledge-base/glossary/authoritative-source) * [Source of Truth](/docs/knowledge-base/glossary/source-of-truth) * [Golden Record](/docs/knowledge-base/glossary/golden-record) * [Master Data Management](/docs/knowledge-base/glossary/master-data-management) * [Product Data Governance](/docs/knowledge-base/glossary/data-governance) ## Related Knowledge Base Articles * [What is a System of Record?](/docs/knowledge-base/enterprise-systems-and-data-architecture/what-is-a-system-of-record) * [What is Product Master Data?](/docs/knowledge-base/enterprise-systems-and-data-architecture/what-is-product-master-data) * [Building an Enterprise Digital Product Passport Architecture](/docs/knowledge-base/enterprise-systems-and-data-architecture/building-an-enterprise-digital-product-passport-architecture) ## Related Articles * [Authoritative Source](/docs/knowledge-base/glossary/authoritative-source) * [Product Data Governance](/docs/knowledge-base/glossary/data-governance) * [Product Data Stewardship](/docs/knowledge-base/glossary/data-stewardship) * [Source of Truth](/docs/knowledge-base/glossary/source-of-truth) * [Golden Record](/docs/knowledge-base/glossary/golden-record) * [Product Data Quality](/docs/knowledge-base/glossary/data-quality) * [Data Architecture](/docs/knowledge-base/glossary/data-architecture) * [Master Data Management](/docs/knowledge-base/glossary/master-data-management) ## See Also * [Enterprise Systems and Data Architecture](/docs/knowledge-base/enterprise-systems-and-data-architecture/overview) * [Implementation](/docs/knowledge-base/implementation/overview) ## References * Regulation (EU) 2024/1781, Official Journal of the European Union: [https://eur-lex.europa.eu/eli/reg/2024/1781/oj](https://eur-lex.europa.eu/eli/reg/2024/1781/oj) * ISO 8000, data quality: [https://www.iso.org/standard/81745.html](https://www.iso.org/standard/81745.html) ## About This Article About This Article
Last Reviewed
2026-08-09
Next Scheduled Review
2027-08-09
Article Version
1.0
tieback Knowledge is a continuously maintained reference library covering Digital Product Passports, product traceability, product compliance and related regulations. Articles are reviewed regularly as legislation, standards and implementation guidance evolve. ## Related Docs * [Enterprise Systems and Data Architecture](/docs/knowledge-base/enterprise-systems-and-data-architecture/overview) * [Implementation](/docs/knowledge-base/implementation/overview) * [Digital Product Passports](/docs/knowledge-base/digital-product-passports/overview) * [Glossary](/docs/knowledge-base/glossary/overview)