NetSuite integration for SaaS companies
NetSuite is one of the most common ERPs among growing companies, so it's often the first integration prospects ask for. Unity connects your product to it, syncing customers, items, sales orders, invoices and payments through NetSuite's own web services, under your brand, managed by our team.
- Customers
- Orders
- Payments
- Subscriptions
- Every NetSuite release
- OneWorld subsidiaries
- Custom fields and records
- Multiple currencies
Every NetSuite account is customized differently, with its own subsidiaries, custom fields, forms and scripts, and shares a limited number of concurrent API connections across all of its integrations. Unity connects through NetSuite's own web services (SuiteTalk REST and SOAP, plus SuiteQL for reads) using token-based authentication, so there's nothing to install and no shared NetSuite password. It maps each customer's own setup and paces its calls so your integration never crowds out the others. Our team builds the integration, delivers it under your brand and keeps it running through NetSuite's twice-yearly releases.
NetSuite records Unity maps for SaaS products
Each map uses NetSuite's own records and transactions, so they land in the right subsidiary with the classification your customer's finance team expects.
| NetSuite record | Typical direction | What it's used for |
|---|---|---|
| Customers, contacts and addresses | Both ways | The accounts your app serves, with billing and shipping addresses and buyer contacts |
| Items and inventory by location | From NetSuite | Inventory, non-inventory and service items, with quantities by location |
| Price levels and customer pricing | From NetSuite | Price levels and customer-specific prices, so your app quotes what NetSuite will invoice |
| Estimates and sales orders | Both ways | Quotes and orders captured in your app, created in NetSuite with the right subsidiary, location and terms |
| Item fulfillments and tracking | Both ways | Shipped quantities, carriers and tracking numbers that keep customers and invoices current |
| Invoices, credit memos and open balances | Both ways | Invoices from your billing platform, or open balances for payments, collections and customer portals |
| Customer payments and deposits | To NetSuite | Payments collected in your app, applied to the right open invoices |
| Vendors, purchase orders and vendor bills | Both ways | Suppliers, POs and bills for procurement, AP automation and spend management |
| Journal entries | To NetSuite | Summarized revenue, fees and payouts posted with the right department, class and location |
| Custom records and fields | Both ways | The data your customer has added to NetSuite, mapped like any standard field |
NetSuite's own web services, tuned to each account
NetSuite is cloud-only, but no two accounts are set up alike. Unity adapts to each one.
Token-based authentication
Unity connects with a dedicated integration record and access tokens, so your customer never shares a password and can revoke access at any time.
Paced to the account's limits
NetSuite caps how many API calls can run at once across all of an account's integrations. Unity batches and throttles its calls so it never blocks your customer's other integrations.
Every subsidiary
NetSuite OneWorld accounts run many subsidiaries, often in different currencies. Unity assigns each record to the right subsidiary and currency.
Custom fields, forms and scripts respected
Unity maps your customer's custom fields and records, uses the right transaction forms, and works with the SuiteScripts and workflows they already run.
NetSuite problems we've already solved
These are the issues that stall do-it-yourself NetSuite integrations, and how Unity handles each one.
Calls rejected because the account is busy
When too many integrations call NetSuite at once, it rejects the extra requests. Unity queues and retries automatically, so nothing is lost and other integrations keep running.
A required custom field or script blocks the record
Mandatory custom fields and user event scripts can reject a record with their own message. Unity maps those fields up front and raises a case with NetSuite's exact error if a script still blocks it.
A customer that isn't assigned to the right subsidiary
In OneWorld, a transaction fails if its customer or item isn't available in that subsidiary. Unity checks the assignments first and creates or updates them where the customer allows.
Integrations that break after a NetSuite upgrade
NetSuite upgrades every account twice a year. Unity tests each release in the customer's sandbox where available and keeps your integration working through the change.
Which SaaS products connect to NetSuite?
Billing, subscriptions and payments
Send invoices from your billing platform to NetSuite, collect payment, and apply customer payments to the right invoices.
Transportation management (TMS)
Send sales orders from NetSuite to your TMS for load planning, then return carriers, tracking numbers and actual freight costs.
CRM, CPQ and quoting
Give reps customer balances, prices and order status, and turn quotes into NetSuite estimates or sales orders.
Ecommerce and marketplaces
Read items, prices and stock by location from NetSuite, and create sales orders the moment a customer checks out.
AP automation, procurement and spend management
Sync vendors and purchase orders, push approved vendor bills and expenses with the right department and class, and return payment status to your app.
Unity is a managed integration service for SaaS companies, built on the Intelligrate iPaaS. We build your NetSuite integration, put your brand on it, monitor it, fix errors and handle upgrades. Integration updates can even flow into your own help desk. See how Unity works for SaaS.
NetSuite integration questions
How does Unity connect to NetSuite?
Through NetSuite's own web services (SuiteTalk REST and SOAP, plus SuiteQL for reads), using token-based authentication on a dedicated integration record. There's nothing to install, and your customer can revoke access at any time.
Will Unity use up our customer's NetSuite API concurrency?
Unity paces its calls to stay within the account's concurrency limit, batching and retrying as needed, so it doesn't block your customer's other integrations.
Does Unity support NetSuite OneWorld and multiple subsidiaries?
Yes. Unity assigns each customer, item and transaction to the right subsidiary and currency, and posts with the department, class and location your customer's finance team uses.
Can Unity work with our customer's custom fields and SuiteScripts?
Yes. Unity maps custom fields and custom records like any standard field, uses the right transaction forms, and works alongside the SuiteScripts and workflows your customer already runs.
What happens when NetSuite releases an upgrade?
NetSuite upgrades every account twice a year. Unity manages those releases as part of the service, so your integration keeps working without your team testing each one.
How long does a NetSuite integration take?
A first NetSuite integration typically goes live in eight to twelve weeks. Each new customer after that is mostly configuration, since the maps are already built.
Your customers run other ERPs too
- All Unity integrations for SaaS
- SAP Business One
- All Microsoft Dynamics integrations
- Microsoft Dynamics 365 Business Central
- Microsoft Dynamics 365 Finance & Supply Chain
- Microsoft Dynamics GP
- Epicor Prophet 21
- All Epicor integrations
- Epicor Kinetic
- All Infor integrations
- Infor SyteLine / CloudSuite Industrial
- Acumatica