Salesforce

NS90: Integrate:

Salesforce and NetSuite

Salesforce and NetSuite, with sync status visible on every record.

NS90: Integrate connects Salesforce to NetSuite through MHI's integration service on NSIP. Accounts, contacts and Salesforce-based apps flow into NetSuite through an Oracle data hub, and every Salesforce record shows whether it synced, its NetSuite ID and any error.

Plan my Salesforce integration

See supported flows

System

Salesforce, including Salesforce-based apps

Direction

Both ways: CRM masters in, NetSuite IDs, status and credit data back

API

Salesforce REST API with SOQL; OAuth

Run mode

Scheduled, near real-time: every 10–15 minutes

Platform

NSIP + NSAW

Delivered

7 delivered · 6 prebuilt

WHY NOW

6 prebuilt flows

Reps sell in Salesforce, finance closes in NetSuite, and both need the same numbers

NS90: Integrate's prebuilt Salesforce flows turn closed-won opportunities into NetSuite sales orders, then send back what happens next: fulfillments with serial numbers, invoices, payments and credits, and item prices by price level. Reps answer customers without asking finance, and finance stops re-keying orders.

Prebuilt flows, ready for deployment: see Supported flows below.

//Supported flows

Salesforce flows delivered on NS90: Integrate

Each solid dot is a client project where MHI built the flow on NSIP. Diamond markers are prebuilt flows. Arrows show direction relative to NetSuite.

Master data

Transactions

Financial & reconciliation

Master data

NETSUITE

Accounts to customers

Salesforce account (or app record) → NetSuite customer

10 – 15 min

Contacts

Salesforce contact → NetSuite contact or individual customer

10 – 15 min

Products and price books

NetSuite item and price levels → Salesforce product and price book entries

15 min · Prebuilt

Transactions

NETSUITE

Closed-won opportunities

Salesforce opportunity and line items → NetSuite sales order

10 min · Prebuilt

Sales order status

NetSuite sales order → Salesforce opportunity or order

Scheduled · Prebuilt

Fulfillments to Salesforce

NetSuite item fulfillment and lines → Salesforce fulfillment record on the opportunity, with assets for serialized items

15 min · Prebuilt

Invoices, cash sales and credit memos to Salesforce

NetSuite invoice, cash sale and credit memo → Salesforce financial record on the account and opportunity

Hourly · Prebuilt

Payments, deposits and refunds to Salesforce

NetSuite customer payment, customer deposit, customer refund and cash refund → Salesforce financial record

Hourly · Prebuilt

Financial & reconciliation

NETSUITE

Credit status and limits

NetSuite customer credit status, limit and terms → every linked Salesforce account

10 – 15 min

Invoices and credit memos from Salesforce

Receivable in a Salesforce-based app → NetSuite invoice or credit memo

10 – 15 min

How it runs

Every Salesforce run is counted, checked and recoverable

Records land in the NS90 data hub in Oracle Autonomous Data Warehouse before they reach NetSuite, so each one can be checked, retried and traced.

Balance and Control

Checks before and after posting

Every record marked ready in Salesforce ends as Success, with its NetSuite ID and link, or as Failure, with the error.

Source and target record counts are written to a job audit for every run.

Parent accounts load before child accounts, and transactions wait until their customer or vendor exists.

Self-healing

Record-level reprocessing

Failed records retry automatically up to five times a day.

Users fix a record in Salesforce and set it back to ready, and it re-syncs on the next run.

Large extracts page through results, so big loads finish without timeouts.

Alerts and visibility

Dashboards and monitoring

Sync status, error, NetSuite ID and last sync time sit on the Salesforce record, so users see integration state without leaving Salesforce.

A business observability dashboard in NetSuite Analytics Warehouse shows each data domain end-to-end flow with its sync status.

What we’ve learned

6 lessons from Salesforce projects on NS90: Integrate

Sync on a business event, not every edit

A Salesforce flow that marks a record ready when something meaningful happens, such as a deal won or a document approved, keeps NetSuite clean and API usage low.

Name an owner for duplicate matching

When several CRM accounts roll up to one billing customer, someone has to own the match. A defined match step, with the NetSuite ID stored back in Salesforce, keeps it consistent.

Agree which system owns each field

After the first sync, decide which fields Salesforce keeps updating and which are maintained in NetSuite, such as credit terms. It avoids each system overwriting the other.

Send back only what started in Salesforce

Fulfillments sync to Salesforce only when their sales order came from Salesforce, so orders entered directly in NetSuite don't clutter the opportunity.

Key price book entries by item and price level

One Salesforce price book entry per NetSuite item and price level keeps prices in step when a level changes, instead of overwriting a single list price.

Agree what Closed Won means

Orders are created when an opportunity reaches the agreed stage. Renamed stages, extra stages or validation rules on that update can stop orders silently, so lock the trigger stage down with sales operations.

How we deliver

Six steps from assessment to steady state