If a customer record appears in two places, which one is correct?
If the same company’s address is listed one way in the CRM and another way on the invoice, the problem isn’t with data entry—it’s because the record’s owner is unclear.
In most companies, a single customer’s record exists in at least two places: the list maintained by sales and the card used by accounting to issue invoices. The two are similar for a while, then diverge. No one notices when they diverge; by the time it’s noticed, the invoice has already been sent to the wrong address.
The problem isn’t a “data entry error.” The problem is that it’s unclear who owns the record.
Every record must have a SINGLE owner
If it’s clear who can edit a field, then the correct value for that field is also clear. The company name and tax ID belong to accounting; the contact person, phone number, and call history belong to sales. If both sides can modify every field, the “last one to write wins” rule applies—and that rule is accountable to no one.
Don’t copy—display
Having two modules copy the same data into their own tables is the most common solution—and the most fragile one: the copy becomes outdated when the source changes. The correct approach is to read the record from its owner. The sales screen reads the tax details from accounting; if it needs to edit them, it directs the user there.
“We do a nightly sync” is not integration
If there’s a transfer, there’s a delay. If there’s a delay, the two records remain different for a while, and during that time, an invoice might be generated from one and a quote from the other. Ask the question this way: When will the other screen show the correct information when this field changes? If the answer is “by morning,” then you have two records.
Merging is not a one-time task
Cleaning up duplicate records is a project; preventing duplicate records from being created in the first place is a design decision. Unless you make a field—such as a tax ID or email address—unique, the cleanup process will have to be repeated every year.
A team that sees the same customer in two different ways across two screens triples the problem when they open a third screen. Determining the record’s owner today makes next year’s merge project completely unnecessary.