Accounts / A73 / external key ERP-73
Account synchronization acceptance
Map one external account. Protect sales ownership. Retain the applied event.
Current CRM revision7
Source-owned fields2
Retained event receipts0
Field ownership map
A message is not permission to overwrite every field
The external system maintains two values; sales assignment stays with the CRM.
| Field / owner | CRM at revision 7 | Incoming value | Expected action |
|---|---|---|---|
| Account nameExternal source | Harbour Parts | Harbour Supply | Update |
| SegmentExternal source | Retail | Wholesale | Update |
| Sales teamCRM owned | Team West | Team East | Keep Team West |
Trace one accepted event
EVT-73 → ERP-73 → A73. Apply two changes once, then distinguish an identical retry from a changed replay.
Acceptance stops
- Identity mismatchNo implicit creation or fuzzy match
- Stale record revisionRe-read before applying a new change
- Changed replaySame event key with different values conflicts
- Applying authorityIntegration operator plus acknowledgement
Monthly delivery checkpoint
Agree the mapping, replay behavior and staging evidence with the first integration task.
Prepare an account update without writing it
Inspect the incoming event and projected changes
Not prepared
Prepare the message to see allowed changes and the protected field.
Current CRM record
Revision check and field ownership are part of this acceptance model.
Operator handoff
Preparing does not change the account. Review the accepted message and apply it from the receipt screen.
Apply the accepted message once
Operator application and event receipt
Prepare a valid account message first.
No event receipt retained.
CRM record after application
- Same key, same payloadReturn the existing receipt; do not write again
- Same key, changed payloadStop as a conflicting replay
- New message, stale revisionRefresh the record before preparing
Synthetic values remain in this tab. Reset starts the original account again.