Compare the operating models
In this fictional example, CRM company A has contacts Lin/Bo. ERP has one trading account A with outlets A1/A2. Retail buyer Jo has no supplied credit account. Creating one ERP account for each CRM person would duplicate A and invent unnecessary accounts.
| Business requirement | Person-to-account copy | Entity-aware crosswalk |
|---|---|---|
| Lin/Bo at A | Two competing A accounts | Two contacts linked to one A |
| A1/A2 outlets | May duplicate payer | Delivery/trading locations beneath A |
| Retail Jo | Invented credit relationship | Retail identity only unless account needed |
Work through the chosen model
The crosswalk records source system/type/ID and target system/type/ID plus relationship purpose. Company A maps to trading buyer A; Lin and Bo map to contact relationships. Address, credit terms and contact channels have different scopes and should not be copied person-wide by default.
- Identify the source entity type
- Choose the matching trading grain
- Attach people and outlets through links
Entity-aware mapping takes more preparation but prevents account duplication.
A maps to one trading account with two contacts and two outlets. Jo remains retail without an invented credit account. The six identities in this example do not require six ERP trading accounts.
When the other model fits
Bo buys personally outside A. Must that sale use A’s terms?
Show the worked answer
No. Use the personal transaction context; contact affiliation alone does not make A the buyer.