NetSuite is available in our Premium and Pro plans.
What you'll need
To integrate with NetSuite, you will need to provide the following information:
- Client ID
- Client Secret
To get them, you will need a NetSuite user with Administrator access.
In NetSuite
Log in to your NetSuite account with the Administrator role.
Step 1: Enable SuiteCloud features
- Open the NetSuite Enable Features page.
- Under SuiteCloud, check the following boxes and click Save:
- Server SuiteScript
- REST Web Services
- OAuth 2.0
Step 2: Create an integration record to obtain Client ID and Secret
-
Navigate to Integration and create an integration with the following details:
Name CledaraConcurrency limit Leave blankRedirect URLhttps://app.cledara.com/register?netsuite=trueCheck the following boxes:
- Authorization Code Grant
- RESTlets
- REST Web Services
- Client Credentials (Machine To Machine) Grant
Reviewing your concurrency limit
As a part of this process, review your Integration Governance settings (navigate to Setup / Integration / Integration Governance) to understand your account's available concurrency and how it is allocated across your integrations.
If your settings show an Unallocated Concurrency Limit of less than three, we suggest reviewing other integrations to determine where your concurrency is allocated.
If you want to allocate some concurrency limit anyway, we suggest a minimum of 3.
If you can't allocate at least 3, contact Cledara support before you connect. We can switch your account to a slower sync that works within a lower limit.
-
Once you click Save, copy the Client ID and Client Secret and store them in a safe place.
They will only be shown once, and you will need to enter them later in Cledara.
Step 3: Deploy RESTlet script for uploading files
NetSuite currently does not support a native way of uploading files to your account. For that, you need to deploy a script that will give Cledara access to this operation.
-
Download the script file.
- Navigate to File Cabinet, go to the SuiteScripts folder, add a new file and select the downloaded script file.
-
Navigate to Scripts, create a script record by selecting the uploaded file and fill in the following details:
Type RESTletName Cledara File UploadID_cledara_file_upload -
Make sure the script ID matches
customscript_cledara_file_uploadand under the Scripts subtab, the POST Function option is enabled. -
Click the Deploy Script button and set the following:
Title Cledara File UploadStatus ReleasedLog level ErrorDeployed EnabledInternal roles Enable Select All
Before moving on to Cledara, you should have:
- The Client ID and Client Secret saved somewhere safe
- The Cledara File Upload script deployed with the status Released
In Cledara
Once you have obtained the client credentials from the NetSuite step 2 above, head to Settings / Integrations as an Admin or a Finance user in Cledara to activate the integration.
Enter your client credentials
Click Connect and provide the Client ID and Secret to authenticate your account.
Authorise Cledara in NetSuite
You will be taken to NetSuite to log in. You will be asked to authorise Cledara to connect to your account.
Select the subsidiary
Once your NetSuite account is connected, select the NetSuite subsidiary to connect. In most cases, this should match the entity your Cledara workspace is created for.
Set up each account
Click the toggle and customise the invoice folder, bank account, and reward category. You can only find the bank accounts that are created under the subsidiary selected and under the same currency as your Cledara account.
If you have both EUR and GBP accounts, you can customise each separately.
Depending on your account, you may also see these settings:
- NetSuite reward category
Shown for your main Cledara accounts only, not for Spend accounts.
- Push classification fields in the bill body
Pushes classification fields (class and department) in the vendor bill and payment body.
- Default settings (Spend accounts)
Choose what is pushed to NetSuite for each expense by default: the bank statement, the vendor bill, vendor payments, and attached receipts. Vendor payments and receipts can only be pushed when the vendor bill is pushed. The bank statement option only appears if bank feeds are turned on for your account.
Once confirmed, you will see the linked account(s) toggled on.
You can now customise what to push and where to push to in the NetSuite Settings under each application. Find more information here.
Common issues
- You see "Currency EUR not found in Netsuite. Please add it."
The currency of the Cledara account you're setting up doesn't exist in your NetSuite account. Add the currency in NetSuite, then turn the toggle on again. The message shows whichever currency is missing.
- The bank account you want isn't in the list
Only bank accounts under the connected subsidiary and in the same currency as the Cledara account are listed. Check the account's subsidiary and currency in NetSuite.
FAQ
How do I change the NetSuite invoice folder, bank account, or reward category connected?
Click Edit next to the account connection (EUR, GBP) and change the invoice folder, bank account, or reward category.
How do I change the NetSuite subsidiary connected?
To switch the NetSuite subsidiary connected, you will have to disconnect the NetSuite integration and reconnect again. You can use the same credentials from your original setup to perform the reconnection.
Do note that if you switch NetSuite subsidiaries, all existing NetSuite settings for your Cledara applications will be reset.
If I switch these NetSuite configurations, will the changes be applied to previously pushed transactions?
They will not be applied to retroactively change what has been pushed. The new configuration will only be applied to new transactions from there on.
How do I push custom fields?
Currently, we do not yet support custom fields. If your custom fields are mandatory, your transactions will not be pushed to NetSuite. These will be supported in an upcoming release.