System of Record
A System of Record (SOR) is an information system or application that acts as the authoritative data source for a given business object, dataset, or process across an enterprise.
Expanded Explanation
1. Technical Function and Core Characteristics
A SOR maintains the authoritative data for specific entities such as customers, products, employees, financial transactions, or assets. It enforces data integrity, applies validation rules, and preserves a consistent representation of those entities over time.
It typically provides transactional capabilities, audit trails, and access controls so users and integrated systems can create, update, and query records in a controlled manner. It also logs changes to support traceability and compliance requirements.
2. Enterprise Usage and Architectural Context
Enterprises designate systems of record within an architecture to avoid conflicting versions of core data across applications, analytics platforms, and business processes. Other systems consume data from the SOR through integration interfaces, replication, or data pipelines.
In practice, an organization can have different systems of record for distinct domains, such as human resources, finance, or customer relationship management. Architects document these designations in enterprise data models, reference architectures, and governance policies.
3. Related or Adjacent Technologies
Systems of record interact with systems of engagement, which focus on user-facing interactions, and with systems of insight, which focus on analytical processing and decision support. Data from systems of record often feeds data warehouses, data lakes, and master data management platforms.
They can run on relational databases, mainframe platforms, or modern cloud data stores, but their role is defined by governance and usage rather than only by technology. Integration platforms, APIs, and event streams distribute SOR data to other enterprise applications.
4. Business and Operational Significance
Organizations rely on systems of record to support regulatory reporting, financial statements, customer obligations, and operational processes because these systems hold the authoritative version of relevant data. Governance frameworks often reference these systems in data ownership and stewardship models.
Security, privacy, and resilience controls focus on systems of record because unauthorized changes or data loss can affect compliance and business operations. Business continuity, backup, and Disaster Recovery (DR) plans usually treat these systems as high-priority assets.