The system of record is the tool that has the final say on a given type of data: when two systems hold different versions of the same customer, price or stock level, its version wins. An SME needs to decide this for every type of data, because the number of tools running side by side keeps growing: 49.5% of Italian enterprises with at least 10 employees use an ERP and 21.7% a CRM (Istat, the Italian national statistics institute, "Imprese e ICT", 2025 reference year, press release of 15 December 2025), often alongside an online store and marketing tools.
The symptom is always the same: in a meeting, two people bring two different numbers for the same thing, and both are right. Sales reads a customer's revenue in the CRM, accounts reads it in the ERP, and the two don't match. Nobody misread anything: nobody ever decided which of the two systems counts.
Choosing the system of record doesn't take new software. It's an organisational decision, written down once, that makes everything else possible: connecting the systems, building a reliable dashboard and, later on, using AI on data that holds up.
What a system of record is
The system of record is the only system allowed to create and change a given piece of data. Other systems read it, even as a copy, but don't correct it: if a change is needed, it's made in the system of record and flows out from there. The reference version of a piece of data (sometimes called the golden record) is the one held there.
Two clarifications head off the most common misunderstandings. First, the system of record is decided per type of data, sometimes per field: the ERP can own the VAT number and billing address, the CRM the contact person and communication preferences. Second, "system of record" doesn't mean "most important system": it means the one responsible for that data, with a person accountable for it.
How many systems run side by side in an Italian SME?
Every tool adopted is one more place where the same data can be written. Istat's figures show how much overlap is possible.
| Tool | SMEs (10–249 employees) | Large enterprises (250+) |
|---|---|---|
| ERP | 48.8% | 85.9% |
| CRM | 21.1% | 56.5% |
| Online sales (all enterprises with 10+ employees) | 20.1% (18.8% among 10–49 employees; 46.6% among large enterprises) | |
| Data analysis (internal or external staff) | 41.9% | 83.6% |
Source: Istat, "Imprese e ICT", 2025 reference year, press release of 15 December 2025; universe: enterprises with at least 10 employees. There is no official statistic on the share of companies that have defined a system of record for their data.
One reading, which is mine and not Istat's: half of SMEs have an ERP and one in five a CRM as well. A company with both already has two candidates for the final say on customers; add an online store and there are three. Without a rule, each keeps its own version, and that's what later surfaces as "the numbers don't add up".
Who's in charge of what? A starting map
The table below is an operational proposal, not a standard: the right choices depend on how the company works. It's a basis for discussion, one type of data at a time.
| Data | Usually in charge | What happens if nobody decides |
|---|---|---|
| Customer tax details | ERP | Invoices with details that differ from the CRM |
| Contacts and interaction history | CRM | Sales calls someone who has left the company |
| Product codes and records | ERP (online copy and images often on the online store) | The same item with two codes |
| Prices and price lists | ERP | A customer sees a price online that differs from their quote |
| Stock | ERP | You sell something you don't have |
| Source of leads and orders | CRM | Every platform claims the same sale |
| Marketing consents | CRM or email platform | An unsubscribe recorded in one system and ignored in the other |
Some rows are covered in dedicated articles: the single customer record, prices and stock between the online store and the ERP, and order sources in tracking from campaign to order.
How to choose the system of record in 5 steps
- List the data that matters. Customers, products, prices, stock, orders, sources, consents. Not every field: the ones decisions are made on or documents are issued from.
- For each, find where it's born. The system where the data is first created is nearly always the natural candidate to be its system of record.
- Choose and write it down. A one-page table: data, system of record, systems that read it, person responsible. It's the most useful document a company can have about its systems.
- Close the side doors. If a piece of data is corrected only in the system of record, that field becomes read-only in the other systems, or at least gets overwritten by the sync.
- Connect afterwards, not before. Only with the rules written down does it make sense to configure connections, as described in integrating CRM and ERP.
When "one system of record" isn't enough
This is my own assessment, not a data point. The rule works per type of data, but sometimes it has to apply per field: on the same customer, the ERP owns the tax details and the CRM the contacts, and that's fine as long as it's written down. During a migration, for a few weeks, the old system can remain the system of record even though the new one is already live: what matters is fixing the switchover date. And the simplest limit: a company with only one system doesn't need this decision, it already has it. It matters from the second system onwards.
What it costs to decide the system of record
The decision itself costs little: a few hours of work with the people who use the systems every day. The real cost is not making it, which you pay for in manual reconciliations and disputed numbers. When the decision is part of a larger project, it belongs in the diagnosis; the implementation applies the rules to the connections; the monthly review checks over time that nobody works around them. The structure of the spend is explained in what integrating an SME's systems costs.
Frequently asked questions
Does the system of record always have to be the ERP?
No. The ERP often owns prices, stock and tax details because that's where they're created and where they have accounting value. But contacts, interaction history and commercial source are created in the CRM, and that's where they should stay. The rule is simple: the system of record is, as a rule, the system where the data is born.
What happens to data that's already duplicated?
It has to be reconciled once, before connecting the systems: compare the versions, choose the correct one and move it into the system of record. From then on, the other systems receive the data instead of producing it. Without this initial clean-up, syncing spreads the errors instead of removing them.
Who should be responsible for the data?
One person per type of data, not a department. Usually whoever uses it most: accounts for tax details, the head of sales for contacts, the warehouse for stock. You don't need a new role: you need someone who knows they're accountable when the data is wrong.
Do you need master data management software?
For most SMEs, no. Master data management tools (software dedicated to managing reference versions of data) are for companies with many systems and high volumes. With two or three systems, a written table, connections configured to match and a responsible person are enough.
In summary
The system of record is the tool with the final say on a piece of data: the others read it, they don't correct it. With 49.5% of Italian enterprises using an ERP and 21.7% a CRM (Istat, 2025), many SMEs already have several candidates for the final say. Deciding who's in charge of what, in writing and with one person responsible for each type of data, is the foundation of the foundations: it makes connections possible, a credible dashboard, and later AI that works on data that holds up. With the systems aligned, marketing stops arguing about the numbers and starts using them.
If you want to build your own "who's in charge of what" map, the diagnosis described on the pricing page starts right here. To talk it through: get in touch.
Sources
Istat, "Imprese e ICT", 2025 reference year, press release of 15 December 2025 (universe: enterprises with at least 10 employees): ERP 49.5% overall, 48.8% of SMEs and 85.9% of large enterprises; CRM 21.7% overall, 21.1% of SMEs and 56.5% of large enterprises; online sales 20.1% (18.8% among 10–49 employees, 46.6% among large enterprises); data analysis with internal or external staff 41.9% of SMEs and 83.6% of large enterprises.
As far as could be verified, there is no official statistic on the share of Italian companies that have defined a system of record for their data. The "who's in charge of what" map, the steps and the cases where the rule needs adapting are the author's professional assessments, not research data.
Sergio Selvelli, 8 October 2026.