NetSuite guide
Software Setup
To acquire your own NetSuite instance, you must purchase a NetSuite license by going to NetSuite's website and contacting their sales team.
Rutter can also help you get access to one of our sandbox instances for development purposes. These instances come with pre-existing data. Please contact your Rutter success manager to learn more.
Developer Account Setup
No additional developer account setup is needed.
Rutter Link
The NetSuite authentication flow consists of a few steps, which are outlined below. These steps must be followed correctly to successfully connect a new NetSuite instance through Rutter Link.
Step 1: Install the AccountLink NetSuite Bundle
Click Install

If there are any conflicts on the Bundle Installation page, the safe solution would be to 'Add and Rename'.
Note: The Rutter integration will use the permissions of the user who is installing the bundle. For this reason, we strongly recommend the user has Admin permissions so Rutter has access to perform all necessary actions. More information on NetSuite permissions can be found in the Permissions section.
Step 2: Enable SuiteCloud features
Open the NetSuite Enable Features Page
Navigate to the SuiteCloud tab inside your setup page
Enable the following features:
SuiteScript
- CLIENT SUITESCRIPT
- SERVER SUITESCRIPT

SuiteTalk (Web Services)
- REST WEB SERVICES
- SOAP WEB SERVICES

Both are required for a complete integration.
Manage Authentication
- TOKEN-BASED AUTHENTICATION

Click Save
Step 3: Confirm Setup
Please confirm that you have successfully completed the following steps:
- Ensure that the 'AccountLink' Bundle (ID: 451666) has finished installation (Check the Installed Bundles Page and wait for there to be a green checkmark under Status).

- Ensure that the required SuiteCloud features have been enabled.
Reference
FAQ
Is there a limit for NetSuite access tokens?
Yes, NetSuite has a limited number of access tokens for each NetSuite user. After the limit, NetSuite will throw an error: "This user has exceeded the number of active access tokens for this role." When this happens, you can delete the existing access tokens from the NetSuite user interface.
How does a user revoke access to Rutter through NetSuite?
They can revoke the token created following this article.
Naming Conventions
Accounting platforms can refer to Rutter objects by different names internally.
Expenses
NetSuite uses multiple objects to represent a Rutter expense: Credit Card Charges and Journal Entries.
Permissions
For a full list of NetSuite permissions and their associated Rutter function, see the table below:
| Tab | Permissions | Function |
|---|---|---|
| List | Documents and Files (Full) | Remotely updating Rutter resources, also required for Attachment Uploads |
| List | Media Folders (Full) | Remotely updating Rutter resources, also required for Attachment Uploads |
| List | Website (External) publisher (Full) | Remotely updating Rutter resources, also required for Attachment Uploads |
| Setup | Allow JS / HTML Uploader (Full) | Remotely updating Rutter resources, also required for Attachment Uploads |
| Setup | Log in using Access Token (Full) | Authentication |
| Setup | Access Token Management (Full) | Authentication |
| Setup | REST Web Services (Full) | Rutter integration is powered by this |
| Setup | SuiteScript (Edit) | Rutter integration is powered by this |
| Setup | SOAP Web Services (Full) | Rutter integration is powered by this |
| Setup | Deleted Records (Edit) | Lets Rutter detect records deleted in NetSuite and mirror the deletion |
| Reports | SuiteAnalytics Workbook (Edit) | Rutter integration is powered by this |
| Transactions | Find Transaction (Edit) | Allows for transaction queries |
| Transactions | Bills (Full) | Handles the AP workflow |
| Transactions | Bill Payments (Full) | Handles the AP workflow |
| Transactions | Pay Bills (Full) | Handles the AP workflow |
| Transactions | Enter Vendor Credits (Full) | Handles the AP workflow |
| Transactions | Purchase Order (Full) | Handles the AP workflow |
| List | Vendors (Edit) | Handles the AP workflow — Edit is required because Rutter can create and update vendors |
| Transactions | Journal Entries (Full) | Handles all workflows |
| Transactions | Advanced Intercompany Journal Entry (Full) | Handles all workflows on OneWorld accounts |
| Transactions | Deposit (Edit) | Handles all workflows — Edit is required because Rutter can create and update bank deposits |
| Transactions | Transfer (Edit) | Handles all workflows |
| Transactions | Checks (Full) | Handles all workflows — check payments and check-based expenses |
| Transactions | Invoice (Full) | Handles the AR workflow |
| Transactions | Invoice Sales Orders (Full) | Handles the AR workflow |
| Transactions | Credit Memo (Full) | Handles the AR workflow |
| Transactions | Sales Orders (Full) | Handles the AR workflow |
| Transactions | Accept Customer Payments (Full) | Handles the AR workflow — customer payments and their application to invoices |
| Transactions | Customer Refund (Full) | Handles the AR workflow |
| Transactions | Cash Sale (Full) | Handles the AR workflow — surfaced as Rutter sales receipts |
| List | Customers (Full) | Handles the AR workflow |
| List | Projects (Full) | Handles the AR workflow |
| List | Jobs (Full) | Handles the AR workflow |
| Transactions | Credit Card Charge (Full) | Handles the EM workflow |
| Transactions | Credit Card Refund (Full) | Handles the EM workflow |
| Reports | Tax (View) | Permissions required to support secondary workflows |
| Reports | Transaction Detail (View) | Permissions required to support secondary workflows |
| Reports | Inventory (View) | Permissions required to support secondary workflows |
| Reports | Sales (View) | Permissions required to support secondary workflows |
| List | Currency (Full) | These entities support all transactions — Full is required to read consolidated exchange rates |
| List | Classes (Edit) | These entities support all transactions |
| List | Items (Full) | These entities support all transactions — Full is required because Rutter can create, update, and delete items |
| List | Locations (Edit) | These entities support all transactions |
| List | Other Names (Edit) | These entities support all transactions |
| List | Departments (Edit) | These entities support all transactions |
| List | Accounts (Edit) | These entities support all transactions — Edit is required because Rutter can create and update accounts |
| List | Subsidiaries (Edit) | These entities support all transactions — required on OneWorld accounts, including per-subsidiary balances |
| Setup | Custom Fields (Edit) | These entities support all transactions |
| Setup | Accounting Lists (Full) | These entities support all transactions — payment methods and payment terms; Full is required because Rutter can create and delete payment terms |
| Setup | Tax Items (Edit) | These entities support all transactions — tax rates and tax groups |
| Setup | Tax Records (Edit) | These entities support all transactions — tax rates and tax groups |
| List | Subscription Plan (Edit) | These entities support all transactions — SuiteBilling accounts only, returned alongside items |
| Setup | Accounting Preferences (Edit) | Read to determine how the account is configured (Rutter preferences) |
| Setup | Manage Accounting Periods (Edit) | Read to determine how the account is configured (Rutter preferences) |
| Setup | Company Information (Edit) | Read to determine how the account is configured (Rutter preferences) |
| Setup | Set Up Company (Edit) | Read to determine how the account is configured (Rutter preferences) |
| Setup | Financial Institution Records (Full) | Required for Rutter Bank Feeds — financial institution records and format profiles |
| List | Custom Record Entries (Full) | Required for the custom record the AccountLink bundle installs — Full is required because Rutter creates and deletes these records. Alternatively, grant access on that record type's own Permissions subtab instead of granting this account-wide permission |
Note: This is not an exhaustive list and we will continue growing this list as we implement new features