Designing a CRM–ERP customer lifecycle.
A premise-led architecture. Creating a customer is not a system call: it is a transfer of authority across identities, decisions and states—designed so the business always knows what is true, and every unresolved state has an owner.
The case in brief
Current reality
A global B2B company wants CRM to “create customers in ERP.” The phrase hides three identities, a transfer of authority between systems and an outcome that can stay unknown—any of which can stop a first order.
What must become true
Turn approved commercial intent into an orderable legal and transactional customer—without duplicate identity, without coupling sellers to ERP availability, without hiding uncertain outcomes and without making technical retries a user’s job.
Design question
When does the CRM stop owning the customer—and what does the user see while the ERP decides?
01Reality & premises
“Create the customer in ERP” is not one requirement.
“Create the customer in ERP.”
- Identity
- Which customer: the relationship, the legal organization or the number that can be invoiced?
- Authority
- Which system may author each part of it, before and after creation?
- Approval
- Who confirms the request is commercially ready—and what exactly did they approve?
- State
- What is true while ERP has not answered yet?
- Availability
- What happens to the seller when ERP is slow or unavailable?
- Idempotency
- Can the same approved request ever create two ERP customers?
- Recovery
- When the outcome is unclear, how is it settled without a duplicate?
- Operational ownership
- Who acts on each state nobody planned for?
State what must be true before choosing.
The recommendation is valid only for this premise set. Change the premises and the answer should be allowed to change.
- 01Global operation
Several subsidiaries can share one commercial relationship but transact through different legal and transactional contexts.
- 02Financial control
ERP validation is mandatory before ordering; it may reject tax, credit or company-code data.
- 03Variable availability
ERP response time and availability cannot be assumed deterministic: planned maintenance and regional latency are normal.
- 04Human accountability
A commercial approver confirms readiness explicitly; unresolved identity and integration exceptions have named owners.
02Identity & authority
One relationship. Several identities. Different authorities.
“Customer” names three different things. They come into existence at different moments, through different decisions—and they do not map one to one.
Account
The relationship: context, pipeline and commercial intent.
- Comes into existence
- Exists from the first conversation, in CRM
- Cardinality
- One per commercial relationship
Party
The registered legal organization and its tax identity.
- Comes into existence
- Validated by ERP before anything can be invoiced
- Cardinality
- One or more per relationship—a group may buy through several legal entities
Customer
The number that can be ordered against and invoiced, in one company-code and sales-area context.
- Comes into existence
- Issued by ERP when creation succeeds
- Cardinality
- One or more per party—one for each valid selling context
One commercial relationship is not one legal customer number. Identity is not the same as record location.
“ERP owns the customer.”
“Source of truth” is too coarse at system level. ERP is authoritative for the legal and transactional identity; CRM still owns the relationship, the commercial lifecycle and the readiness decision. Authority belongs to concepts, attributes and lifecycle states—not to applications.
Authority by concept
For this capability, one system owns each concept. The others act on it, move it, consume it or derive from it—and some concepts change hands at creation.
03Business state
What exists before, during and after ERP creation?
The states come before the mechanism. Each one says what the business may believe right now, and which action is allowed next.
Select a state to see what the business believes, what happens next and who owns it.
Potential customer
- What the business believes
- A commercial relationship exists. No legal or transactional customer does.
- What is allowed next
- Sell, qualify and prepare the creation data.
- Who acts
- Seller
- Can move to
- Ready for creation
Ready for creation
- What the business believes
- The approver has confirmed readiness; the approved data is frozen.
- What is allowed next
- Send the creation command—once.
- Who acts
- Commercial approver
- Can move to
- Creation pending
- Reached from
- Potential customer
Creation pending
- What the business believes
- ERP has the request and has not answered yet. Nothing has failed.
- What is allowed next
- Commercial work continues; order entry waits.
- Who acts
- Platform operations, once it ages
- Can move to
- Ready to order
- Rejected — repair required · ERP decides no
- Outcome unknown — reconciling · No answer in time
- Reached from
- Ready for creation
Ready to order
- What the business believes
- ERP issued the canonical customer number, and CRM holds the reference.
- What is allowed next
- Order entry opens.
- Who acts
- Seller
- Reached from
- Creation pending, Outcome unknown — reconciling
Rejected — repair required
- What the business believes
- ERP decided no, for a stable business reason.
- What is allowed next
- Correct the governed data and resubmit: a corrected request, not a replay.
- Who acts
- Master data / Finance, with the seller
- Reached from
- Creation pending
Outcome unknown — reconciling
- What the business believes
- Nobody knows yet whether ERP committed. The customer may already exist.
- What is allowed next
- Reconcile by the request identity. Never press Create again.
- Who acts
- Platform operations
- Can move to
- Ready to order · Reconciliation finds it
- Intervention required · Still unclear
- Reached from
- Creation pending
Intervention required
- What the business believes
- Reconciliation or matching could not settle the outcome on its own.
- What is allowed next
- A named operator resolves it under the same request identity.
- Who acts
- Platform operations or Master data / Finance, by cause
- Reached from
- Outcome unknown — reconciling
Compare all 7 in one table
| State | What the business believes | What is allowed next | Who acts |
|---|---|---|---|
| Potential customer | A commercial relationship exists. No legal or transactional customer does. | Sell, qualify and prepare the creation data. | Seller |
| Ready for creation | The approver has confirmed readiness; the approved data is frozen. | Send the creation command—once. | Commercial approver |
| Creation pending | ERP has the request and has not answered yet. Nothing has failed. | Commercial work continues; order entry waits. | Platform operations, once it ages |
| Ready to order | ERP issued the canonical customer number, and CRM holds the reference. | Order entry opens. | Seller |
| Rejected — repair required | ERP decided no, for a stable business reason. | Correct the governed data and resubmit: a corrected request, not a replay. | Master data / Finance, with the seller |
| Outcome unknown — reconciling | Nobody knows yet whether ERP committed. The customer may already exist. | Reconcile by the request identity. Never press Create again. | Platform operations |
| Intervention required | Reconciliation or matching could not settle the outcome on its own. | A named operator resolves it under the same request identity. | Platform operations or Master data / Finance, by cause |
Four distinctions the states protect
- Pending is not failureWaiting is a state, not an error.
- Rejected is not technical failureERP decided; nothing is broken.
- Unknown is not safe to retryERP may already have committed.
- Created is not reply receivedERP can succeed before CRM hears about it.
Commercial work never waits for ERP: the approval is acknowledged at once and the relationship moves on. Order entry is different—it stays gated until the canonical ERP customer exists. CRM may confirm business progress; it must never claim the customer is ready to transact.
What must always remain true
- 01One approved creation request can never create two ERP customers.
- 02A timeout is never treated as proof that ERP did not create the customer.
- 03Only the canonical ERP outcome makes a customer ready to order.
- 04A seller never repairs an uncertain outcome by pressing Create again.
- 05Every pending, unknown or intervention state has a named operational owner.
- 06Every state a user sees traces back to a durable business or integration state.
04Design decision
Synchronous, asynchronous or batch?
Three interaction architectures can create a customer. None is better in general. The question is which one these premises can live with.
Compare the three on four dimensions
| Dimension | Synchronous API | Asynchronous command | Scheduled batch |
|---|---|---|---|
| User wait | Blocks on ERP | Approval completes | Approval completes |
| Failure recovery | User retries | Managed reconciliation and replay | Next batch |
| Consistency | Immediate | Eventual, and visible | Delayed |
| Operational load | Low while ERP behaves | Explicit ownership of unresolved states | Reconciliation-heavy |
Design decision
Put an asynchronous boundary between commercial approval and legal creation: freeze the approved intent under one request identity, show its business state in CRM, reconcile before any replay, accept only the canonical ERP outcome as ready to order, send business rejections to governed repair and unresolved outcomes to named operators.
Why it fits these premises
- Commercial approval should not wait on ERP latency.
- Legal creation is still mandatory before any order.
- ERP availability varies across regions and maintenance windows.
- Uncertain outcomes must be recoverable without a duplicate.
- The business needs a visible state while creation completes.
Asynchrony does not remove the ERP dependency. It turns waiting into an explicit state the operating model can own.
05Architecture
Acknowledge the intent. Reconcile the outcome.
The selected design, system by system. Each system has one job at this boundary—and a list of things it deliberately does not own.
Hover or focus a system to see what it owns, what it does not, and which flows it takes part in.
What each system owns—and does not
| System | Owns | Does not own |
|---|---|---|
| CRM |
|
|
| Integration layer |
|
|
| ERP |
|
|
| Data platform |
|
|
ERP controls legal and transactional customer creation. CRM owns the commercial lifecycle. The integration layer owns delivery state. No integration component owns business truth merely because it moves it.
- 01Commercial approval
- 02Creation command
- 03ERP validation
- 04Outcome event
- 05Ready to order
- Freeze the approved intent.
On approval, CRM records the request exactly as approved and gives it one request identity, scoped to its legal context.
- Acknowledge receipt, not completion.
The integration boundary confirms durable receipt. CRM moves to
Creation pending—no premature success. - Reconcile before any replay.
After a timeout, ask ERP by the request identity first. A late success must never become a duplicate.
- Publish a business-readable outcome.
Success carries the canonical identifiers. Rejection carries a stable reason and a repair owner—not a stack trace.
06Contract
What crosses the boundary—and what does not?
A semantic contract, not API documentation: what each message must mean for the business to trust it.
Creation command
- One request identity, used for correlation end to end
- The source commercial identity: the CRM account
- The legal and transactional context required for creation
- The approved data, frozen at approval
- The contract version it was written against
Outcome
- The same request identity
- The business result: created, rejected or intervention required
- The canonical ERP identifiers, on success
- A stable rejection or intervention reason
- Enough context for CRM to reconcile its state
- Edits made in CRM after approval
- Retry counters and transport errors as business data
- Stack traces in place of reasons
- ERP-internal keys beyond the canonical identifiers
Why the approved intent is frozen
Approval is a decision about specific data. If the account is edited while the command is in flight, the integration must not quietly create something different from what was approved. The frozen request is the evidence of that decision—and the contract carries it unchanged.
One creation intent, at most one ERP customer
The business rule comes first: one approved intent can produce at most one ERP customer, however often the message is delivered. The mechanism follows: ERP keeps the request identity as an external key and treats a repeat as the same request. In technical terms, the command is idempotent.
07Failure & recovery
Unknown is not failed.
Timeout is not failure
A timeout means the caller does not know the outcome. It does not mean ERP did not create the customer.
Reconcile before retry.
Five ways creation can go off the happy path. They are classified by what they mean, because the meaning decides the recovery.
Select a failure class to trace it from what happened to who owns the recovery.
01Business rejection
Validation rejection
- 01What it meansERP decided no.
- 02System responseRecord the stable reason; never retry.
- 03What the user seesRejected, with the reason and who repairs it.
- 04Who repairs itMaster data / Finance, with the seller
02Unknown outcome
Timeout
- 01What it meansNobody knows yet whether ERP committed.
- 02System responseReconcile by the request identity before any replay.
- 03What the user seesStill pending, with the time of the last check.
- 04Who repairs itPlatform operations
03Transport failure
ERP or integration unavailable
- 01What it meansThe command has not crossed the boundary.
- 02System responseHold the command durably; back off, retry, then dead-letter.
- 03What the user seesStill pending. Nothing to repeat.
- 04Who repairs itPlatform operations
04Identity conflict
Duplicate candidate
- 01What it meansA legal identity may already exist.
- 02System responsePause for deterministic matching, then human review.
- 03What the user seesWaiting on identity review.
- 04Who repairs itMaster data / Finance
05Return-path failure
CRM callback failure
- 01What it meansERP succeeded; CRM has not received the outcome yet.
- 02System responseReplay the outcome under the same request identity.
- 03What the user seesThe ERP number appears after recovery.
- 04Who repairs itPlatform operations
Compare all 5 in one table
| Class | What it means | System response | What the user sees | Who repairs it |
|---|---|---|---|---|
| Business rejectionValidation rejection | ERP decided no. | Record the stable reason; never retry. | Rejected, with the reason and who repairs it. | Master data / Finance, with the seller |
| Unknown outcomeTimeout | Nobody knows yet whether ERP committed. | Reconcile by the request identity before any replay. | Still pending, with the time of the last check. | Platform operations |
| Transport failureERP or integration unavailable | The command has not crossed the boundary. | Hold the command durably; back off, retry, then dead-letter. | Still pending. Nothing to repeat. | Platform operations |
| Identity conflictDuplicate candidate | A legal identity may already exist. | Pause for deterministic matching, then human review. | Waiting on identity review. | Master data / Finance |
| Return-path failureCRM callback failure | ERP succeeded; CRM has not received the outcome yet. | Replay the outcome under the same request identity. | The ERP number appears after recovery. | Platform operations |
Reconcile before retry
- A timeout or a lost replyAsk ERP for the request identity.
- ERP has itAdopt the canonical customer number: ready to order.
- ERP never received itResend the same request—same identity, same frozen data.
- Still unclearIntervention required: a named operator decides, under the same request identity.
Never ask a user to resolve an uncertain distributed-system outcome by pressing “Create” again.
08Operating model
Who owns each state, decision and exception?
The architecture is incomplete until every unresolved state has an owner and a permitted action.
Commercial operations
- Commercial readiness and approval policy
- Communication with sellers
- Business-process questions
Master data / Finance
- Legal validation rules
- Duplicate resolution
- Governed transactional attributes
Platform operations
- Integration and transport health
- Correlation and replay
- Technical recovery
Capability owner
- Changes to the customer-creation design and its policies
Who may do what with an exception
| Role | May | May not |
|---|---|---|
| Seller | Correct commercial inputs before approval | Retry an unknown outcome, or edit the approved request |
| Commercial approver | Confirm commercial readiness | Override legal or financial validation |
| Master data / Finance | Resolve legal data and duplicate candidates | Change the commercial intent that was approved |
| Platform operations | Reconcile and replay under the same request identity | Create a new business request to “fix” a failure |
From design to operable boundary
The write path is enabled last, not first.
- 01
Define identity
Agree what Account, Party and Customer mean.
- 02
Assign authority
Make authority explicit per concept and attribute.
- 03
Define states
Give pending, created, rejected, unknown and intervention a business meaning.
- 04
Define the contract
A frozen request, a durable request identity, stable outcomes.
- 05
Test failure first
Prove timeout after commit, duplicate candidates, lost replies and ERP outage.
- 06
Name the operators
Every unresolved state has an owner and a permitted action.
- 07
Enable the write path
Only once identity, state, recovery and support are proven.
09Observability
Measure business state, not only integration health.
Observe business state, not only infrastructure. A green queue means little if new customers are blocked before their first order.
Technical observability
- Delivery failures
- Retries and dead-lettered commands
- Outcome replies and their delay
- Correlation gaps
- Queue and endpoint health
Business observability
- Creation requests pending, by age
- Rejections by stable business reason
- Unknown outcomes awaiting reconciliation
- Interventions by owner and age
- Duplicate candidates awaiting resolution
- Customers created in ERP but not yet ready in CRM
Architecture-health measures
| Measure | Why it matters | Owner and response |
|---|---|---|
| Pending requests by age | Shows where approved customers wait before their first order | Platform operations: reconcile or escalate |
| Rejections by stable reason | Repeated reasons point to data captured wrongly upstream | Master data with Commercial operations: fix the capture, not each request |
| Unknown outcomes awaiting reconciliation | Each one may already be a customer | Platform operations: reconcile before replay |
| Interventions by owner and age | Unowned exceptions are where revenue stalls | The named owner: resolve or reassign |
| Duplicate candidates awaiting resolution | Each one blocks a legal identity decision | Master data / Finance: match or reject |
| Outcomes recovered on the return path | Shows how often CRM lags behind ERP | Platform operations: fix the reply path |
| Time from approval to ready to order | The business view of the whole boundary | Capability owner: revisit the design when it drifts |
10When context changes
When would the architecture change?
The recommendation follows the premises. These are the conditions under which it should change.
When ERP creation is deterministic, highly available, safe to repeat and fast—and users cannot proceed meaningfully without the immediate result.
When same-day creation is unnecessary, volumes are high and the operating model already works in controlled master-data windows.
When a governed enterprise master-data service becomes the authoritative issuer of legal identity across CRM and ERP.
When legal customer creation is itself a governed human process—a reviewer decides each case—rather than an automated system operation.
The integration is not the architecture.
The command flow is one implementation layer. The architecture is what “customer” means, which identities exist, which system may author each concept, what moves authority, what is true while the outcome is unknown—and who repairs it.
Do not model system availability as business truth. Model intent, progress and outcome separately.
11Second layer & outputs
Questions that change the architecture—and what the work produced.
The second layer
Identity
- What exists before an ERP customer number?
- Can one commercial relationship map to several transactional customers?
Authority
- Which system may change each concept after creation?
- Which event moves authority from CRM to ERP?
State & failure
- Does a timeout mean failure—or an unknown outcome?
- Who may recover an uncertain outcome without creating a duplicate?
What the work produced
- 01Customer identity model
- 02Concept and attribute authority matrix
- 03Customer-creation state model
- 04Interaction decision
- 05Creation command and outcome contract
- 06Failure and recovery model
- 07Operational ownership model
- 08Business observability model