A sales rep closes a big deal in Salesforce and proudly talks about it in a meeting. Three weeks later, accounting discovers the sale… when the customer sends a reminder because they are still waiting for their invoice. Meanwhile, the same rep is chasing a customer who actually has two unpaid invoices the rep knew nothing about.
Salesforce to sell, NetSuite to run the business: it is a very common pairing. But without a connection between the two, sales and finance teams each work in their own bubble, with re-keying, errors and information that arrives too late.
At SuiteVise, we connect NetSuite and Salesforce for our clients, and we also take over integrations that are not delivering. Here are the possible options, the data flows to plan and the best practices for success.
Why connect NetSuite and Salesforce, and which flows to plan
The goal is simple: a deal signed in Salesforce becomes an order and then an invoice in NetSuite, without re-keying, and sales reps can see their customers’ financial situation without leaving Salesforce. This is often called the “lead-to-cash” process, from prospect to payment.
| Flow | Usual direction | Trigger |
|---|---|---|
| Accounts → customers | Salesforce → NetSuite | First sale or conversion to customer |
| Contacts | Salesforce → NetSuite | With the account |
| Items and price lists | NetSuite → Salesforce | On every change |
| Won opportunities → orders | Salesforce → NetSuite | Move to “Closed Won” or quote approval |
| Invoices, payments and balances | NetSuite → Salesforce | Continuously or regularly |
| Order and shipment status | NetSuite → Salesforce | On every change |
| Exchange rates | NetSuite → Salesforce | Daily |
Depending on your business, other flows are added: automatic creation of a project in NetSuite for a professional services firm, or of a subscription for a software company.
The four ways to connect NetSuite and Salesforce
1. Oracle’s connector: NetSuite Connector for Salesforce
Oracle offers its own connector, available on the Salesforce AppExchange and managed from NetSuite. According to Oracle’s documentation, it is reserved for NetSuite OneWorld accounts.
Its strengths: an official solution, managed by NetSuite’s vendor.
Its limits: a newer solution than the alternatives on the market, to be assessed on your real cases, especially if your Salesforce is heavily customized.
2. A native Salesforce application, such as Breadwinner
Breadwinner installs directly in Salesforce, from the AppExchange. It displays NetSuite data (invoices, payments, orders, balances) on Salesforce records, and lets you create orders in NetSuite from Salesforce.
Its strengths: fast setup, no middleware platform, and a solution a Salesforce administrator can manage.
Its limits: an approach focused on financial flows. For broader processes or several systems, it can be limiting.
3. An integration platform (iPaaS)
Celigo offers a Salesforce–NetSuite integration app with ready-to-use flows, from customer account to invoice. Other platforms are also used: Boomi, Workato, Jitterbit, or MuleSoft, which belongs to Salesforce.
Their strengths: preconfigured flows, advanced error handling, strong customization capabilities, and the ability to connect other systems on the same platform.
Their limits: a higher cost and one more platform to master, often with the help of a specialist.
4. Custom integration
An integration developed between Salesforce’s APIs and NetSuite’s (REST or RESTlets).
Its strengths: total freedom, useful when Salesforce is heavily customized, especially with a complex quoting tool (CPQ).
Its limits: a development cost and ongoing maintenance to take on, with every change to either platform.
How to choose the right option?
A few questions to ask yourself:
- What is the real need? Giving sales reps financial visibility, automating order creation, or both?
- How customized is Salesforce (custom objects, CPQ, validation rules)?
- Is NetSuite on OneWorld, with several subsidiaries and currencies?
- Who will administer the integration: a Salesforce administrator, the NetSuite team, or a partner?
- Will other systems need to be connected in the future?
| Your situation | Option that often fits best |
|---|---|
| Sales reps mainly want to see invoices and payments in Salesforce | Native application (Breadwinner) |
| NetSuite OneWorld, preference for an Oracle solution managed from NetSuite | NetSuite Connector for Salesforce |
| Full quote-to-invoice process, with other systems to connect | iPaaS (Celigo, Boomi, Workato…) |
| Company already equipped with MuleSoft or an integration platform | That existing platform |
| Heavily customized Salesforce, complex CPQ, very specific rules | Customized iPaaS or custom integration |
The pitfalls we see most often
- Not deciding which system is the master. If a customer can be created and edited in both systems without a clear rule, duplicates and inconsistencies appear very quickly.
- A poorly chosen trigger. Creating an order in NetSuite as soon as an opportunity moves to “Closed Won”, while the contract is not signed or the information is incomplete, causes a chain of corrections.
- Catalogs that drift apart. Items and prices changed in Salesforce without going through NetSuite: orders arrive with unknown references or wrong prices.
- Underestimating CPQ. Discounts, bundles, options, subscriptions: a complex quoting tool in Salesforce requires precise mapping to NetSuite items and billing.
- Forgetting OneWorld. Subsidiaries, currencies, VAT numbers: you need to define which NetSuite subsidiary each account and each sale belongs to.
- Exposing too much financial data. Sales reps need their customers’ invoices and balances, not necessarily margins. Permissions must be designed on both sides.
- Ignoring API limits. Salesforce and NetSuite both limit the number of calls. A poorly designed integration can exhaust quotas and block other flows.
- No error monitoring. An order that does not go through is an invoice that does not go out. Errors must be visible and handled every day.
Our method for a successful integration
- Bring sales and finance to the table. The quote-to-cash process involves both teams: the rules are decided together.
- Define the master system for each piece of data. Customers, contacts, items, prices, orders, invoices: who creates, who edits, who views.
- Choose the right trigger. At exactly what point does a Salesforce deal become a NetSuite order, and with which mandatory information?
- Clean the data before connecting. Duplicate accounts, unlinked customers, obsolete items: a clean base prevents most errors.
- Choose the tool based on real needs, the complexity of Salesforce and expected changes.
- Test real scenarios. New customer, existing customer, multi-currency, discount, amendment, cancellation: each case is tested in a test environment on both sides.
- Set up monitoring and an owner for errors, then train sales reps and accountants on what changes for them.
Frequently asked questions
Does NetSuite integrate natively with Salesforce?
The two systems are not connected by default. Oracle does, however, offer its NetSuite Connector for Salesforce, and several third-party solutions exist: native Salesforce applications, integration platforms or custom developments.
What is the best NetSuite–Salesforce connector?
It depends on the need. A native application such as Breadwinner works well for quickly giving sales reps financial visibility. A platform such as Celigo is better suited to a full quote-to-invoice process or to several systems.
Which data should be synced between Salesforce and NetSuite?
Accounts and contacts, won opportunities converted into orders, items and prices, as well as invoices, payments and balances sent back to Salesforce.
How long does a NetSuite–Salesforce integration take?
From a few days for a native application with simple needs to several months for a complex integration with CPQ or custom developments.
Can Salesforce CPQ be integrated with NetSuite?
Yes, but it requires precise mapping between CPQ products, discounts and options and NetSuite items and billing rules.
In short: connect the tools, but above all the teams
Connecting NetSuite and Salesforce means bringing together two teams that have long worked separately. Oracle’s connector, a native application such as Breadwinner, a platform such as Celigo or a custom integration can all work. What makes the difference are the rules sales and finance define together: which system is the master, when a deal becomes an order, and who sees what.
Your sales reps and your accounting team don’t talk about the same figures, or your current integration generates too many errors? SuiteVise can help: process scoping, choice of solution, configuration, testing and follow-up. Let’s take 30 minutes to talk it through.