NetSuite accounting (coming soon)
Connect a NetSuite subsidiary to an Operating company, so your invoices and credit notes go to NetSuite and their status and payments come back.
Written By Mikko Karjalainen
Last updated 4 days ago
What the NetSuite integration does
The NetSuite integration connects one Operating company to one NetSuite subsidiary. Operating sends your invoices and credit notes to NetSuite at that subsidiary, and NetSuite sends back their status and the payments applied to them.
The integration has three features. Each feature has its own page on the connection, where you turn it on and change its settings:
Tax codes and items: imports the tax codes of the subsidiary's country, which you map to Operating's tax rates, and the items the subsidiary sells as billable items.
Clients: imports the subsidiary's customers as clients, and creates in NetSuite the clients an invoice pushed to it needs.
Invoices and payments: creates Operating's invoices and credit notes in NetSuite, and brings back their status and their payments. It needs the other two features to be on.
What syncs, and in which direction
A client's name and invoicing email go each way. Addresses and VAT IDs do not.
Each feature's Data flow sets who writes each field of the records it syncs, as Who writes each field below explains. With the systems' defaults:
Items: an item follows the system where it was created. An item that Operating created from a NetSuite item is NetSuite's to change, so edit its details in NetSuite.
Clients: Operating and NetSuite both change a client's name and invoicing email, and the latest change wins.
Invoices: Operating writes the invoice, and NetSuite writes its status.
A field that only NetSuite writes is disabled in Operating. Hover over the field to see who writes it, for example "Name is written by NetSuite · Acme Ltd. Change it there."
Operating imports tax codes, items and customers when you turn a feature on. After that, it imports tax codes and items every day, and customers every 6 hours. It reads the status and payments of each invoice that is not settled yet every hour.
What you need
The Manage integrations permission in Operating to connect NetSuite and change its settings. To save an invoice to NetSuite, you need the right to edit the invoice.
A NetSuite account on SuiteTax. An account on Legacy Tax cannot be connected.
A NetSuite administrator to turn on REST Web Services and token-based authentication, and to create the role, the integration record and the access token Operating uses.
One connection for each subsidiary you invoice from.
Nothing is installed in your NetSuite account: no bundle, SuiteApp or script.
The role Operating works as needs these permissions:
Setup: Log in using Access Tokens (Full), REST Web Services (Full).
Reports: SuiteAnalytics Workbook (Edit).
Lists: Customers (Full), Items (View), Tax Records (View), Currency (View), Subsidiaries (View).
Transactions: Invoice (Full), Credit Memo (Full), Customer Payment (View), Find Transaction (View).
How to connect NetSuite
The connect dialog guides you through NetSuite, with links to the right pages in your account.
Go to Settings > Integrations and open NetSuite.
Next to the company, click Connect an account.
Enter your Account ID or NetSuite address. Your account ID is at Setup > Company > Company Information in NetSuite.
Create the role and the user for Operating, as the dialog describes.
Create the integration record, and enter its Consumer key and Consumer secret.
Create the access token, and enter its Token ID and Token secret.
Click Connect.
If the account has more than one subsidiary, choose the one for this company.
NetSuite shows the keys and the token only once, so copy each value when NetSuite shows it.
When the role cannot list the account's subsidiaries, the dialog asks for a Subsidiary ID. It is the number after id= in the address of the subsidiary's page in NetSuite.
What the connection's page shows
Under the connection's name, a line shows its status, such as Connected, followed by the Operating company and details of the subsidiary, such as its base currency and country. Click Account details to see more, such as how Operating signs in to NetSuite.
When the status is Needs reconnecting, a notice above the tabs has a link to reconnect NetSuite. When it is Suspended, Operating has stopped the connection and nothing is exchanged. Contact support to resume it.
The page has three tabs: Overview, Mapping and Issues. The Overview tab shows what needs you first, then the Features list. Each feature in the list shows the direction it moves data (Into Operating, Out of Operating or Both ways) and when it last synced. Click a feature to open its page.
When something needs fixing, Needs you lists it with a badge and the button that fixes it:
Stopped: a feature that is on cannot run until you fix what blocks it. The button opens the fix, such as Map records, Open settings or Reconnect.
Warning: the feature runs, but one of its checks needs a look.
Failed: the last import or push of a feature failed. Click Run now to run it again, or Open feature.
1 issue, 2 issues and so on: records that did not get through. Click Open issues to see them on the Issues tab.
When nothing needs you, the tab shows Everything's running and when the connection last synced. Before any feature is on, it shows Nothing is turned on yet.
How to set up and use it
On the connection's Overview tab, open Tax codes and items, turn on its switch, and click Save changes.
Click Overview to go back, and do the same for Clients.
On the Mapping tab, map the items and the customers, and click Commit decided … mappings on each tab. Operating never creates a tax rate from a tax code, so link a tax code only to a tax rate Operating already has.
Open Invoices and payments, turn it on, and click Save changes.
Open an invoice and click Save to NetSuite.
Every line of a NetSuite invoice needs a billable item that is mapped to a NetSuite item.
NetSuite works out the tax on each invoice when it saves it. So the total NetSuite books can differ from Operating's total, and the invoice page shows both.
With the default setting An invoice posted in NetSuite, Operating marks the invoice sent once NetSuite posts it. An invoice that waits for approval in NetSuite is marked sent once it is approved.
A feature that cannot be turned on yet says why on its page, under its description:
"Turn on Tax codes and items and Clients first; this feature uses what it imports." Invoices and payments needs the records the other two features import. Turn them on and save first. The message names only the features that are still off.
"Fix what blocks it before turning it on." A readiness check has not passed. Fix what the readiness checks list.
"Invoices and payments uses what this feature imports, so it stays on until Invoices and payments is turned off." Turn off Invoices and payments first.
"Operating has suspended this connection, so features can only be turned off." Contact support to resume the connection. Until then, you can turn a feature off but cannot change its settings.
A person without the Manage integrations permission sees You can view these settings. on a feature's page. That person can read the settings but cannot change them or turn the feature on or off.
Who writes each field
Once a feature is on, its page has a Data flow section. It shows when each kind of record syncs, and who writes each field. Each field has a row with three columns:
Field: the field, such as a client's name.
Who writes it: the system or systems that set the field's value.
What happens: what this means for a record created in Operating and for one created in NetSuite.
A field that NetSuite does not carry shows "Not synced. NetSuite does not carry this field."
To change who writes a field:
On the Overview tab, open the feature.
In Data flow, find the field's row.
Choose an option in Who writes it. Read What happens to check the result.
Click Save changes.
Changing the data flow needs the Manage integrations permission.
Who writes it offers these options:
Operating only: set and edited in Operating. Not read from NetSuite or sent to it.
Operating, sent to NetSuite: set and edited in Operating, and sent to NetSuite.
Operating, then NetSuite: set in Operating when created. After that, only NetSuite's changes update it.
NetSuite: read from NetSuite, new and changed. Operating doesn't set it.
Where it was created: a record created in Operating is Operating's to change. A record created in NetSuite follows NetSuite.
Latest change wins: both change it, and each change is copied to the other. Operating asks you to confirm, because the systems overwrite each other's changes.
Custom: choose separately what Operating reads from NetSuite, what it sends to NetSuite and what Operating can do with the field.
An option that a field cannot take is greyed out, and the reason replaces its description:
"Not possible: NetSuite doesn't share this field." Operating cannot read the field from NetSuite.
"Not possible: NetSuite doesn't take this field from another system." Operating cannot send the field to NetSuite.
"Not possible: it can't change once created." The field is set only when the record is created.
Some fields are fixed once NetSuite has received the first record, such as the invoice number. Their row shows a lock and a note, such as "Fixed: NetSuite has received invoices already."
When your change gives a field a new writer and some records hold a different value, Operating shows Review how current values change with the number of records that differ. Choose one, then click Save data flow changes:
Apply now: Operating takes the new source's values on its next read, so the records match it.
Follow from now on: Operating keeps the values it has and takes only what the new source changes next.
To go back to the defaults for a kind of record, click its reset button, such as Reset clients to defaults. A kind of record that uses the defaults shows Systems' defaults.
When records sync
For each kind of record, the Data flow section has a From NetSuite line and a To NetSuite line. A line can hold these options:
On request: always available. Read one record with Refresh from NetSuite on its page in Operating, or save it to NetSuite from that page.
An interval, such as Every 6 hours: Operating reads or sends the records on this schedule.
Create new clients: Operating's scheduled sending also creates the clients added in Operating. Only one connection can do this.
Tick or clear the options that have a box, then click Save changes. How often each sync runs is set by Operating. Contact support to change it.
How status and payments come back
Paid in NetSuite: Operating adds each customer payment to the invoice, and marks the invoice paid once NetSuite reads it paid in full.
Voided in NetSuite: Operating marks the invoice voided.
Deleted in NetSuite: Operating voids the invoice, with the default setting A document deleted in NetSuite.
To void an invoice that is in NetSuite, void it in NetSuite. Operating refuses the void and shows "This invoice is in NetSuite, and Operating cannot void it there. Void it in NetSuite; Operating marks it voided the next time it reads the invoice."
How to disconnect NetSuite
On the connection's Overview tab, under Danger zone, click Disconnect NetSuite.
Click Disconnect NetSuite to confirm.
Mappings and settings are kept, so connecting the same subsidiary again continues where it stopped. To stop all access from NetSuite's side, revoke the access token in NetSuite.
Common errors and how to fix them
When you connect, or when a save or an import fails, Operating shows the message. The connection's Issues tab lists every failed record with what fixes it.
"NetSuite did not accept the keys and tokens." Check the values you copied, and that the access token was made for the same integration record as the consumer key.
"This NetSuite account uses Legacy Tax." Operating connects only to accounts on SuiteTax.
"The NetSuite role Operating connects as lacks a permission this needs, such as REST Web Services." Add the permissions listed above to the role in NetSuite, then retry.
"Every line of a NetSuite invoice needs an item." Give each line a billable item mapped to a NetSuite item, then retry.
"NetSuite does not take this currency for the customer or its subsidiary." Add the currency to the customer in NetSuite, then retry.
"The NetSuite posting period of the document's date is closed or locked." Open the period in NetSuite, or change the date, then retry.
When you click Save changes on a feature's page, Operating can refuse the save. Nothing is saved, and the message starts with the feature's name:
"… already sends this company's records. Turn off the feature that does it there first." Another connection, which the message names, already sends this company's records. Turn off that feature on the other connection, then save again.
"… already creates new clients. Turn “Create new clients” off there first, or leave it there." Only one connection can create new clients. Turn off Create new clients on the connection the message names, or leave it off here.
"A schedule that sends these records needs permission to change them. Ask someone who has it." Sending records on a schedule needs the permission to change those records, such as clients. Ask someone who has that permission to make the change.
If the scheduled sending of clients fails with "More than one connection is set to create new clients, so none creates them. Turn “Create new clients” off on all but one.", leave Create new clients on for one connection and turn it off on the others.
Related articles
Was this helpful?
More in Integrations & API
AI chat (LLM) via MCPREST APIHubSpot CRMSalesforce CRMStill need help? Ask the team