One customer record across CRM, sales, and finance
Why Cambodian businesses end up with the same customer three times, and how one account record with duplicate detection and merging fixes it.
The same shop, spelled three ways
A customer signs up through a sales rep, buys once at the counter, and later gets invoiced by finance. Unless those are the same record, you now have three: one with a phone number, one with a tax ID, one with an outstanding balance — and no single answer to "how much does this customer owe us and what have they bought?"
Why duplicates are created by good intentions
- The counter cannot find the record, so it creates one to finish the sale
- A business name is spelled differently in Khmer and English
- A branch is entered as a separate company
- A data import runs twice, or against an unclean file
How one record stays one record
Preventing duplicates is mostly about the moment of creation. Cleaning them up afterwards is possible, but it is a merge — and a merge is something you want a record of.
- 1Manager
Duplicates are surfaced before the record is saved
Creating a customer checks what already exists and shows the likely matches. Catching it here costs a second glance; catching it at the year-end statement costs an afternoon.
- 2Humaneti
The account is linked to its receivables identity
One customer record, one identity in the ledger. That link is what lets a statement cover everything the customer has done, whether it started as a CRM deal, a sales order, or a counter sale.
- 3Humaneti
Every module points at the same account
CRM opportunities, sales orders, invoices, deliveries, and counter sales all reference it rather than holding their own copy of the name. Updating an address updates it everywhere because there was only ever one address.
- 4Administrator
Merging is deliberate and leaves a trail
When duplicates do get created, merging them records what was merged into what. Without that log, a customer's history appears to change on its own and nobody can explain why the balance moved.
- 5Administrator
Imports are batched so they can be undone
A bulk import is recorded as a batch. That is the difference between a bad file being a mistake you can reverse and a bad file being three thousand duplicates you clean by hand.
- 6Finance
One statement, whatever the customer bought through
Because the account is shared, a statement or an ageing report covers the whole relationship. Segments then let you treat groups differently — pricing, terms, campaigns — from one definition of who the customer is.