Decomposing the Problem: Order-to-Cash Sync
Break down Harborline Software's requirements for synchronising deals, orders, and invoices between Salesforce and NetSuite. Define system-of-record ownership at the record and field levels, establish how corresponding records are matched across systems, and specify the requirements for data mapping contracts. Identify the integration constraints introduced by partial settlement and conflicting write-back updates.
We'll cover the following...
- What Harborline must agree on before promising a sync
- Who can change each part of OPP-410 and SO-920?
- Which records represent the same object
- What the QL-1 mapping contract must specify
- How SO-920 can be settled so far and still unfinished
- What breaks when Salesforce writes Complete back
- Practice: Whether SO-1044 is ready for a design discussion
Salesforce lists Harborline Software's opportunity OPP-410 as Closed Won for ten units, while NetSuite records six units shipped and an invoice with an outstanding balance. Neither system provides a complete view of the order lifecycle. Connecting these records requires an integration contract that defines system-of-record ownership, field-level authority, and record relationships. The contract provides the basis for automating order creation and giving sales access to authoritative fulfilment and receivables data.
What Harborline must agree on before promising a sync
Start by identifying who approves orders, which approved customer and item records each order references, and how order statuses are defined across systems.
Common CRM and ERP integration challenges include conflicting data ownership, inconsistent customer models, duplicate contacts, and order statuses that do not fully represent partial shipments or returns. Selecting an integration protocol or transport mechanism does not resolve conflicting business rules or data ownership.
Use the following working assumptions for Harborline, pending client confirmation:
Each order handoff references one approved bill-to customer and one accepted order.
Track fulfilment at the order-line level, including shipped and returned quantities for each item.
Use USD for all monetary amounts in this scenario, excluding taxes and shipping charges.
An approved, posted credit reduces the outstanding balance of the invoice to which it is applied.
Salesforce is the system of record for sales proposals and customer relationship data. Finance approves billing identities and financial decisions managed in NetSuite. The fulfilment owner authorises shipment and return-receipt status changes.
These assumptions apply only to the Harborline scenario and must not be treated as standard product behaviour or accounting rules. The first deliverable is an agreed definition of record ownership, business states, and their relationships.
Who can change each part of OPP-410 and SO-920?
Consider a simplified mapping rule: "Synchronise all customer fields bidirectionally and copy the latest order_status value." This rule does not establish whether sales users can modify legal billing names or whether a ...