Connect Salesforce to NetSuite

Sales lives in Salesforce, finance lives in NetSuite, and the handoff between them is usually a spreadsheet, a nightly export, or a person rekeying orders. That gap is where revenue leaks and month-end slows down.

• Closed-won deals become NetSuite sales orders without manual re-entry, so fulfillment starts the same day
• Customers and items are matched, not duplicated, using external IDs on both sides
• Invoice, payment, and fulfillment status flows back to Salesforce, so reps stop asking finance for updates
• Every sync is a run you can inspect, so a disputed order has a record of what moved and when

The order-to-cash flow most teams turn on first.

Closed-won Opportunity to NetSuite Sales Order, status back to Salesforce

Started when an Opportunity reaches Closed Won, with a human approval step for any order above a threshold.

1. 1
   Trigger: Salesforce New or updated opportunity, polled on the schedule you set, with a Filter that continues only when StageName = Closed Won. For an immediate start, use a Live stream trigger on Change Data Capture instead.
2. 2
   Resolve customer: NetSuite Upsert by external id on Customer, keyed on the Salesforce Account.Id, from the Account fields.
3. 3
   Resolve items: read the OpportunityLineItem rows with a SOQL query, and match each NetSuite Item by Product2.ProductCode → itemId.
4. 4
   Approval: if Amount > 50,000, a Wait for form step sends finance an approval task by email link. Otherwise continue.
5. 5
   Write order: NetSuite Upsert by external id on SalesOrder, keyed on the Opportunity ID, mapping the fields in the table below.
6. 6
   Write back: a Salesforce update on the Opportunity, setting NetSuite_SO_Number__c and Order_Status__c = Submitted.
7. 7
   Ongoing: a second flow polls NetSuite invoices and item fulfillments with the Record Created or Changed trigger and updates Order_Status__c on the Opportunity.

The starting map for the Opportunity to Sales Order step. Adjust to your NetSuite form and Salesforce customizations.

• Orders and customers. Closed-won opportunities become sales orders. New accounts become customers. Quote revisions update the open order. (Salesforce to NetSuite)
• Billing and fulfillment status. New invoices, payments, and shipments picked up by polling update order status and paid-through date on the Opportunity. (NetSuite to Salesforce)
• Financial account fields. Credit hold, payment terms, and account balance sync onto the Salesforce Account so reps see risk before they quote. (NetSuite to Salesforce)
• Product and price book. New items and price changes keep the Salesforce price book and NetSuite item list aligned. (Either direction)

The same controls apply to this sync as to every other Neblex workload.

• Run history. Every sync is a run with step-level status and errors. A failed run can be replayed from the step that failed; steps that already succeeded are not repeated.
• Approval steps. Add a Wait for form step wherever a person should decide: large orders, credit holds, or first orders for a new customer.
• Scoped access. The connection uses a service account with only the objects this sync needs, not broad admin access.
• Environments. Build and test against a Salesforce sandbox and a NetSuite sandbox account, then promote the same flow to production.