Separate commercial identity from legal customer identity
An account is a commercial relationship; a legal entity is a registered organization; an ERP customer is that entity in one of our companies. Model three linked identities—not one record that means all of them.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01Context
A global B2B company keeps prospects, legal entities, subsidiaries and delivery locations in one CRM account list, while each ERP numbers customers independently. Integrations map one CRM account to one ERP customer, which breaks whenever a group buys through several legal entities or from several of the company’s own subsidiaries.
02Decision drivers
- D01
Prospects exist long before legal validation
- D02
One legal entity can be a customer of several of our companies
- D03
Selling and reporting at group level
- D04
Merges must not orphan history
03Options considered
| Option | Right when | Cost / trade-off | Verdict |
|---|---|---|---|
| One record for every meaning | Single-entity customers and one ERP | Every multi-entity relationship becomes a workaround | Rejected |
| The ERP customer as the CRM account | Transaction-led businesses with little prospecting | No place for prospects or group relationships; the CRM mirrors ERP structure | Rejected |
| Three linked identities | Groups, several legal entities, several ERPs | Needs a cross-reference and governed merge rules | Selected |
Every option is right under some premises. The verdict applies to the context above.
04Decision
Model the commercial account (CRM authority), the legal entity with a canonical party ID (master-data authority) and the ERP customer per company (ERP authority) as separate, linked identities. The integration layer owns the cross-reference; no system reconstructs identity from names.
05Consequences
What this choice changes elsewhere in the system.
- Integration
Integrations route by canonical IDs through the cross-reference, so renaming or merging an account breaks no flow.
- Data model
A commercial account can link to several legal entities, and each legal entity to several ERP customers.
- Duplicates
Duplicate checks run on natural keys before creation, not after.
- Merges
A merge keeps the surviving ID, moves history and keeps retired IDs resolvable as aliases.
- Reporting
Reports roll up by commercial account or by legal entity without contradicting each other.
- Downstream authority
ERP customers are created only for a validated legal entity; downstream systems take legal identity from master data, never from the CRM account.
06Revisit when
The decision holds while its context holds. Challenge it when:
An enterprise master-data service issues party identity for every system.
The business consolidates to one ERP and one legal entity per customer.
07Where this decision is applied
The decision says why this path was chosen; each case shows how it takes part in a larger architecture.
- Systems case / 01Designing a CRM–ERP customer lifecycleA premise-led architecture: from commercial intent to a legally valid, operationally recoverable customer.
- Systems case / 03Designing customer and master-data identity across CRM and ERPSeparating commercial, legal and transactional identity—with one issuer, explicit cardinality and governed merges—and giving authority to concepts and attributes rather than whole records.
- Data case / 01Designing a governed commercial performance data modelA governed commercial performance model: orders, invoices, targets and customer context conformed at a declared grain, with explicit time, version, correction and currency semantics—so every metric is computed once and reproduces the same business meaning everywhere.
- AI case / 03Designing AI-assisted data stewardship without moving master-data authorityAI that makes stewards faster without becoming the steward: candidates found, ranked by impact and explained with evidence and differences; a governed steward queue; identity, merge and consequential classification decided by accountable people; accepted decisions executed by the system’s own processes; and outcomes that improve evaluation and rules—never the model’s permissions.
- Operating-model case / 04Designing customer ownership in a multi-subsidiary organizationOne customer relationship across several legal entities, subsidiaries and sales teams: who owns the relationship, each local transaction and the global account data—and who resolves the conflicts.
08Related decisions
Decisions this one depends on, or constrains.
- ADR / 001Make ERP customer creation asynchronousProtect the commercial workflow from ERP latency while making pending state and recovery explicit.
- ADR / 008Run reconciliation as a permanent control, not an exception processDelivery guarantees fail silently. A scheduled comparison of expected and actual populations—with an owner for every kind of difference—is part of the architecture, not cleanup.