What Happens When Two Systems Disagree?
When customer details differ between business applications, small mistakes can create real problems. Learn how to keep information consistent.
In this guideJump straight to what you need3 sections
A customer changes their address.
Someone updates the details in the accounting system, but the customer management spreadsheet still contains the old information.
A few weeks later, another employee prepares a delivery using the spreadsheet.
The parcel goes to the wrong place.
Nobody deliberately made a mistake. Both employees used the information available to them.
The difficulty was that the business had two different versions of the same customer record, and nobody knew which one was correct.
It's a small example of a problem that can develop whenever information is maintained separately across multiple systems.
Duplicate records create uncertainty
Imagine a hypothetical Wellington equipment supplier using separate applications for customer enquiries, orders and invoicing.
Each system contains customer contact details.
When someone changes their phone number or delivery address, employees must remember to update every relevant application.
Occasionally, one gets missed.
Now the business has several records describing the same customer, but they don't agree.
This creates more than an administrative inconvenience.
Employees may waste time checking details, contacting colleagues or asking customers to confirm information they've already provided.
Reports can also become confusing when customer names or records are inconsistent.
The underlying problem isn't necessarily that the business has too many applications.
It's that the same information is being maintained independently in several places.
Decide which system holds the correct information
When connecting business applications, an important question is which system should be treated as the authoritative source for particular information.
For example, a CRM might be responsible for customer contact details, while an accounting application manages invoice records.
An integration could then transfer relevant updates between them.
But the rules need to be clear.
If a customer changes their address in the accounting system, should that change update the CRM? Or should employees be required to make contact-detail changes in the CRM first?
What happens when two systems contain conflicting values?
These decisions depend on how the business operates and what its applications support.
Simply connecting everything in both directions can create unexpected problems if the systems repeatedly overwrite one another.
A reliable integration should also account for duplicate records, failed updates and information that doesn't match the expected format.
Automation can reduce manual entry, but only when the underlying rules make sense.
Less copying can mean greater confidence
A useful first step is to identify which pieces of information appear in more than one application.
Customer names, addresses, order numbers and job statuses are common examples.
Then examine how those details are currently updated.
Does someone manually copy changes between systems? Are employees expected to remember which applications need updating? Is there a reliable way to identify conflicting records?
Sometimes clearer procedures will solve the problem.
In other cases, a software integration may allow information to move automatically from the system responsible for maintaining it.
The aim isn't necessarily to store everything in one enormous database.
Different applications can still perform different jobs. What matters is that the information they share remains consistent enough for employees to trust.
A business that repeatedly checks whether its own records are correct is spending time compensating for an unreliable process.
Good information management isn't about having more records. It's about knowing which records you can rely on.
At Software Logic, I help New Zealand businesses explore software integrations and practical ways to reduce duplicate data entry.
If two of your business systems showed different details for the same customer tomorrow, would anyone know which one to trust?
Free practical guide
Put what you’ve read into practice
Explore practical ways to reduce repetitive work with the tools you already use. Get your free copy of Software & Automation for Small Business.
Have a question about your business? Talk to Liam.