NetSuite Salesforce
integration.
Turn won opportunities into NetSuite sales orders, and show invoices, payments and fulfilments back on the Salesforce account.
NetSuite Salesforce integration links Oracle NetSuite, the ERP, with Salesforce, the CRM, so a won opportunity becomes a sales order and invoices, payments and fulfilments appear on the account. Oracle documents its own Salesforce Connector SuiteApp for this. MuleSoft connectors and custom builds on the NetSuite and Salesforce APIs are the other routes.
How it works
What do you need for Oracle's Salesforce Connector?
Oracle says the NetSuite account must be a OneWorld account with at least one subsidiary, with the NetSuite Connector Platform SuiteApp installed first. On the Salesforce side you create an API-only integration user and, except on Professional Edition, an External Client App.
The connector
Orders in NetSuite. Context in Salesforce.
Techila Global Services is a Salesforce Summit Partner. We connect NetSuite and Salesforce so sales can see order, invoice and payment status without asking finance, and finance gets clean orders without re-keying. Our Salesforce vs NetSuite comparison explains what each system is built to own.
We start with Oracle's own connector where its syncs fit your process, and use middleware or a custom build where they do not.
NetSuite Salesforce connectors compared: what are the ways to connect them?
| Option | What it moves | Limits from the official page |
|---|---|---|
| Oracle's Salesforce Connector SuiteApp | Subsidiaries, items and products, opportunities to sales orders, fulfilments, invoices, payments, cash sales, customers and accounts, contacts | Needs a OneWorld account with at least one subsidiary and the NetSuite Connector Platform SuiteApp. Invoices and payments arrive in Salesforce as read-only Financial records. |
| MuleSoft NetSuite REST connector | Any record your Mule application maps, through the NetSuite REST Record Web Services API and the SuiteQL query service | Uses OAuth 2.0 client credentials with a JWT bearer assertion. Needs MuleSoft developers. |
| Custom build on both APIs | Whatever you design | You own the code, monitoring and upgrades. |
We help you choose the option, then build, test and support it as part of our Salesforce integration services. See Salesforce integrations, or talk to us about your setup.
What does Oracle's Salesforce Connector sync?
Oracle's documentation lists these syncs. The direction is taken from each sync's name.
| Sync | Direction |
|---|---|
| Subsidiary | NetSuite to Salesforce |
| Item to Product | NetSuite to Salesforce |
| Product to Item | Salesforce to NetSuite |
| Opportunity to Sales Order | Salesforce to NetSuite |
| Sales Order to Order | NetSuite to Salesforce |
| Fulfillment | NetSuite to Salesforce |
| Invoice to Financial record | NetSuite to Salesforce |
| Payment to Financial record | NetSuite to Salesforce |
| Cash Sale | NetSuite to Salesforce |
| Customer to Account | NetSuite to Salesforce |
| Account to Customer | Salesforce to NetSuite |
| Contacts | Not stated on the overview page |
Which way does each NetSuite sync go?
- Accounts and customers (both ways)
- Products and items (both ways)
- Opportunities to sales orders (from Salesforce to Oracle NetSuite)
- Sales orders to orders (from Oracle NetSuite to Salesforce)
- Fulfilments (from Oracle NetSuite to Salesforce)
- Invoices and payments (from Oracle NetSuite to Salesforce)
- Subsidiaries (from Oracle NetSuite to Salesforce)
Oracle says NetSuite is the source of truth for invoices. Invoices and payments sync only when they come from a sales order that started as a Salesforce opportunity; records created in NetSuite for other sales orders are not synced.
NetSuite Salesforce integration step by step
Oracle's setup guide for its Salesforce Connector lists these tasks in this order. A MuleSoft or custom build follows a different path, but the Salesforce integration user and the historical load still apply.
- Verify required features. Enable the features and set the preferences Oracle lists in both NetSuite and Salesforce. The NetSuite account must be a OneWorld account with at least one subsidiary.
- Install the NetSuite Connector Platform SuiteApp in your NetSuite production or sandbox account.
- Create an API-only integration user in Salesforce. Oracle notes this user cannot log in to the Salesforce user interface.
- Create and configure an External Client App in Salesforce. Professional Edition users skip this and use a different connection process.
- Set up the dashboard portlets on the NetSuite Connector Platform dashboard. Only a user with the Administrator role can see the Connector Platform tab.
- Run the Salesforce Connector setup wizard in NetSuite, choosing the correct Salesforce edition in the Create Connection step. The wizard then opens the Manage Lookups page for lookups and preferences.
- Configure page layouts in Salesforce so users see the synced records.
- Assign permission sets to the Salesforce integration user.
- Load historical data: sync existing item data from NetSuite to Salesforce before users start quoting.
Test each sync in a NetSuite sandbox and a Salesforce sandbox before production, starting with items and customers, because opportunities cannot become sales orders until the products and accounts on them match.
How does quote-to-cash work between Salesforce and NetSuite?
Sales owns the deal in Salesforce, and finance owns the order, the invoice and the cash in NetSuite. With Oracle's connector, the hand-off happens when an opportunity becomes a sales order.
Quote-to-cash flow between Salesforce and NetSuite
- OpportunitySales works the deal on the Salesforce account, using products synced from NetSuite items.In Salesforce
- QuotePrices and quantities are agreed on the opportunity before it closes.In Salesforce
- Sales orderThe Opportunity to Sales Order sync creates the order; Sales Order to Order shows it back in Salesforce.Salesforce to NetSuite, then back
- InvoiceNetSuite is the source of truth; the invoice syncs as a read-only Financial record.NetSuite to Salesforce
- PaymentPayments sync as read-only Financial records, so the account shows what has been paid.NetSuite to Salesforce
Oracle says invoices and payments sync only when they come from a sales order that started as a Salesforce opportunity. Orders keyed directly in NetSuite stay in NetSuite, so agree with finance which orders must start in Salesforce.
What goes wrong in NetSuite Salesforce integrations?
- Account type. Oracle's connector needs a OneWorld NetSuite account with at least one subsidiary; check this before planning around it.
- Salesforce edition. Oracle notes Professional Edition has no API access by default and uses a different connection process.
- Products not loaded first. Opportunities cannot become clean sales orders until NetSuite items exist as Salesforce products.
- Expecting to edit invoices in Salesforce. Invoices and payments arrive as read-only Financial records; changes happen in NetSuite.
- Orders keyed in NetSuite. Only sales orders that started as Salesforce opportunities send invoices and payments back.
- A personal user for the sync. Oracle's setup uses an API-only integration user with its own permission sets; keep it that way.
Should the integration be real-time or batch?
Salesforce's architects describe six integration patterns, including fire and forget, batch data synchronization and data virtualization. Order creation usually suits an event sent when the opportunity closes. Product and price lists often suit a scheduled batch. Showing long invoice histories may not need copies in Salesforce at all.
To choose a pattern for each flow, talk to us.
Architecture
How does data move between NetSuite and Salesforce?
Salesforce
Connector or middleware
Oracle NetSuite
What's included
What does a NetSuite Salesforce integration project cover?
Looking for delivered work? See case studies
FAQ
Frequently asked questions.
What architects ask before commissioning a Techila integration.
Yes. Oracle documents a Salesforce Connector SuiteApp, installed on top of the NetSuite Connector Platform SuiteApp. It syncs items, opportunities to sales orders, fulfilments, invoices, payments, cash sales, customers and contacts.
Oracle lists Enterprise Edition, Developer Edition, and Professional Edition with or without an API license. It notes that Professional Edition does not have API access by default and uses a different connection process.
Not with Oracle's connector. Invoices and payments arrive in Salesforce as read-only Financial records, and Oracle says NetSuite is the source of truth for invoices.
For Oracle's Salesforce Connector, yes: Oracle says every NetSuite account using it must be a OneWorld account with at least one subsidiary. A MuleSoft or custom API build does not have that requirement on Oracle's connector page.
Oracle lists nine tasks: verify required features, install the NetSuite Connector Platform SuiteApp, create an API-only integration user in Salesforce, create an External Client App (except on Professional Edition), set up dashboard portlets, run the setup wizard, configure Salesforce page layouts, assign permission sets to the integration user, and load historical item data.
When NetSuite is one of several systems sharing customer and order data, or when you need flows the connector does not include. MuleSoft's NetSuite REST connector reaches the REST Record Web Services API and SuiteQL.
Sources
Last reviewed:
- Oracle NetSuite, Salesforce Connector setup (read 10 November 2026)
- Oracle NetSuite, Salesforce Connector syncs (read 10 November 2026)
- Oracle NetSuite, NetSuite invoice sync to Salesforce Financial record (read 10 November 2026)
- Oracle NetSuite, NetSuite payment sync to Salesforce Financial record (read 10 November 2026)
- MuleSoft, NetSuite REST Connector 1.0 (read 10 November 2026)
- Salesforce Architects, Integration patterns (read 10 November 2026)
Talk to an expert about NetSuite Salesforce integration
Tell us what you need. We reply within 1 business day.
Let's plan your next Salesforce program.
We reply within 1 business day · +1 617-777-9873
See case studies