How to Build a Single Source of Truth Across Your Business Systems
Sales says the customer address is:
12 Smith Street.
Operations has:
21 Smith Street.
Accounting has an old email address.
The spreadsheet has another phone number.
Now somebody has to work out:
Which one is right?
That is what happens when several systems become responsible for the same information.
A single source of truth fixes the ownership problem.
It Does Not Mean One System for Everything
Businesses often hear:
“We need one source of truth.”
and assume that means:
“Everything needs to live in one platform.”
It does not.
Your CRM may still be best for sales.
Your job system may still be best for operations.
Your accounting platform should probably remain responsible for financial records.
The goal is deciding which system owns each type of information.
Give Every Important Field an Owner
For example:
Customer Contact Details → CRM
Job Status → Job Management
Invoice Status → Accounting
Technician Timesheets → Field System
Product Cost → Purchasing
Other systems may display that information.
But they should not independently maintain competing versions of it.
Move the Data Instead of Copying It
Suppose the CRM owns the customer's phone number.
When the customer becomes a job, that number can be transferred into the operational system.
If it changes later, the connected workflow can update the appropriate record.
You move toward:
One value → shared where needed
instead of:
Four values → manually kept in sync.
That dramatically reduces disagreement between systems.
Use Unique IDs
Names are not reliable identifiers.
You may have:
Smith Electrical
Smith Electrical Pty Ltd
Smith Electrical - Brisbane
Are those three customers?
Or one?
Connected systems should use stable references such as:
Customer ID
Job ID
Quote ID
Invoice ID
Those identifiers let automations know exactly which records belong together.
Separate Customer Data From Job Data
One customer may have ten jobs.
Their customer record might contain:
- business name,
- billing address,
- phone,
- email,
- account status.
Each job may contain:
- site address,
- scope,
- scheduled date,
- technician,
- job notes,
- materials.
Keeping those concepts separate avoids duplicating the customer's core information across every job.
Decide Which Direction Information Should Flow
Not everything needs two-way synchronisation.
For example:
CRM → Job System
Customer contact details.
Job System → Accounting
Completed job information.
Accounting → Job System
Payment status.
Each field should have a clear direction.
Two systems constantly overwriting each other is not a single source of truth.
It is a fight.
Handle Changes Properly
The real test comes when information changes.
For example:
The customer updates their phone number.
Ask:
Where should that update happen?
If the answer is:
“Anywhere, depending on who notices first.”
you do not have clear ownership.
A better model is:
Update CRM
↓
Connected systems receive the change
Now everyone sees the same information.
Make Exceptions Visible
Integrations occasionally fail.
A record may be missing.
A required ID may not exist.
Two possible matches may appear.
Do not silently guess.
Surface the exception.
For example:
Customer sync failed
Possible duplicate records found
Action required: Review customer
That protects the quality of the source data.
Stop Creating Extra Sources of Truth
Spreadsheets often become accidental databases.
Someone exports information because reporting is difficult.
Then people start updating the spreadsheet.
Soon the spreadsheet contains information that does not exist in the original system.
Now you have another source of truth.
Where possible, reporting should read from operational systems rather than create another editable copy.
Start With Five Important Fields
You do not need to redesign the entire data architecture today.
Choose five pieces of information your team regularly disagrees about.
For example:
- customer phone,
- customer email,
- site address,
- job status,
- invoice status.
For each one, ask:
Which system owns this?
Who can change it?
Which other systems need to see it?
How does the update reach them?
That exercise alone can uncover a surprising amount of operational confusion.
At 5M Consulting, we help businesses define clear ownership across their systems and connect information so teams are not constantly deciding which version to trust.
You can have several business systems.
You should still have one answer.