How to map the same customer across CRM, ERP and finance systems

The same customer often has one record in Salesforce, another in Oracle or NetSuite, and a third in the billing system, each with its own ID and spelling. Mapping them takes three things: a crosswalk that links every record to one customer, rules for parents and subsidiaries, and an owner who approves changes. Without it, customer revenue, retention and forecasts are unlikely to agree.

Why records drift apart

1. Different entry points. Sales creates the account, finance creates the billing entity, and neither checks the other.
2. Corporate structure. Parents, subsidiaries and acquisitions are modeled differently in each system.
3. Name changes. A rebrand or merger creates a new record instead of updating the old one.

How to map customers

1. Pick the system that owns the master customer ID.
2. Build a crosswalk from every other system's ID to it.
3. Write rules for parents, subsidiaries and renamed customers.
4. Have finance approve the rules that affect revenue reporting.
5. Review unmatched records every month.

How Preql helps

Preql's agents propose matches for the same customer across systems and surface conflicting records. Owners approve the mapping, and every change is versioned, so revenue and retention figures can be built on the same customer list.

FAQ

Is this the same as master data management?

It overlaps. MDM tools manage the customer records themselves. A context layer governs how finance definitions use them.

What about customer-level forecasts?

They depend on this mapping. Forecasts built on unmapped records can double count or miss customers.