System of Record

Short answer: In practice, naming a system of record settles which copy wins when two systems disagree. If the order system is the system of record for orders, then the order in that system is the official version. Copies in other tools count as secondary. A company usually has several systems of record, each responsible for different data. Examples include employee records, customer contacts, the product catalog and stock levels.

The idea is related to, but distinct from, a single source of truth. A system of record is where staff officially create and maintain a given piece of data. A single source of truth is the wider goal that everyone uses one agreed version of information. A reporting database can be a single source of truth for analysis without being the system of record for anything. That is because nobody creates or changes data there. Naming systems of record is usually the first step toward a single source of truth.

For each important type of data, the company names one system of record and a business owner responsible for it. Staff make changes in that system. Other systems receive updates through connections instead of separate edits. Sometimes data is legitimately split between systems. In that case, the company assigns ownership field by field. For example, the sales system may own contact names and phone numbers. The finance and operations system may own billing and delivery addresses. Rules for resolving conflicts keep the arrangement working. So do regular checks that compare each copy against the system of record.

A company keeps customer delivery addresses in both its sales system and its finance and operations system, and staff edit either one. A check of 3,000 customers finds 240 mismatched addresses, or 8%, which cause failed deliveries. The company makes the finance and operations system the system of record for delivery addresses. It locks that field in the sales system and copies changes across each night. A monthly check then compares both systems, so the team can trace new mismatches and correct them at the source.

Without clear systems of record, teams argue over which number is right, reports disagree and automation spreads errors between tools. Naming systems of record costs little in itself, although enforcing it may need integration work. It supports reliable reporting and cleaner integrations. It also shows which systems are critical to protect and back up, and which data matters most during a migration.

Designating a system of record does not by itself make its data accurate. It should come with data quality checks and a named owner. People sometimes use the term loosely for any important system, which blurs accountability. The company should revisit the arrangement when it adds, replaces or acquires systems. Otherwise the designated source can quietly drift out of date.