Step-by-Step Guide: How to Set Up the Navan NetSuite Integration

You've decided to integrate Navan with NetSuite. Good decision. The combination of Navan's travel and expense automation with NetSuite's financial engine eliminates one of the most persistent manual processes in any growing business and when set up correctly, it runs seamlessly in the background while your team focuses on the work that matters. 

But setting it up correctly is the operative phrase. 

This guide walks you through the complete technical setup of the Navan NetSuite integration step by step, including the configurations most guides skip, the common mistakes that cause problems down the line, and one critical limitation you need to know before you start. 

Before You Begin: What You Need in Place 

Before touching a single setting in either platform, make sure the following prerequisites are confirmed: 

In NetSuite: 

• Administrator-level access to your NetSuite production account 

• SuiteCloud features enabled (REST Web Services, Token-Based Authentication, OAuth 2.0) 

• A dedicated integration user account created specifically for Navan should never use a general admin's credentials for integrations 

In Navan: 

• A fully active Navan account with expense management enabled 

• Admin-level access within the Navan platform 

• Your chart of accounts and expense category structure is documented and ready for mapping 

One critical thing to know before you start: 

⚠️ Navan does not have a Sandbox or test environment. 

This is not a minor footnote; it is a significant constraint that shapes how the entire setup process needs to be approached. 

Unlike most enterprise software integrations, where you configure and test everything in a safe sandbox environment before touching your live data, Navan operates exclusively in a production environment. There is no staging, no sandbox, no test instance. 

This means every configuration you make, every mapping you set, and every test transaction you run during setup goes through your live NetSuite account. The practical implication is straightforward: you need to be more deliberate and precise during the configuration phase than you would with a sandboxed integration. 

This is one of the primary reasons we recommend having an experienced NetSuite partner involved in this setup. The absence of a test environment significantly raises the cost of getting things wrong. 

Step 1: Enable the Required Features in NetSuite 

Log in to your NetSuite account with Administrator access and navigate to: 

Setup → Company → Enable Features → SuiteCloud tab 

Enable the following features: 

• REST Web Services required for API-based data transfer 

• Token-Based Authentication (TBA) for secure machine-to-machine connection 

• OAuth 2.0 Navan uses this for authentication 

Click Save once all three are enabled. 

Step 2: Create a Dedicated Integration User in NetSuite 

This is the step most companies skip, and it causes significant security and troubleshooting problems later. 

Never authenticate an integration using a real employee's NetSuite credentials. If that employee changes their password, enables 2FA, or leaves the company, your integration breaks instantly. 

Create a dedicated integration user: 

1. Go to Lists → Employees → New 

2. Create a user named something clear, like "Navan Integration User" 

3. Assign this user a custom role (see Step 3) 

4. Set the user's access to Web Services Only this user should not have interactive login permissions 

Step 3: Create a Custom Role for the Navan Integration 

Navigate to Setup → Users/Roles → Manage Roles → New 

This role needs precisely the permissions Navan requires, no more, no less. Over-permissioned integration roles are a security risk. 

The role should include permissions across these categories: 

Transactions: 

• Expense Reports View, Create, Edit 

• Journal Entries View, Create 

• Vendor Bills View (if applicable) 

Lists: 

• Accounts View 

• Employees View 

• Departments View 

• Classes / Locations View (if used in your chart of accounts) 

• Expense Categories View, Create 

Setup: 

• User Access Tokens Full 

• Web Services Full 

Once the role is created, assign it to your Navan integration user from Step 2. 

Step 4: Create the NetSuite Integration Record 

Navigate to Setup → Integration → Manage Integrations → New 

Fill in the details: 

• Name: Navan Integration (or similar) 

• State: Enabled 

• Authentication: Select Token-Based Authentication and/or OAuth 2.0 

After saving, NetSuite will generate your Consumer Key and Consumer Secret. 

Step 5: Generate an Access Token 

Navigate to Setup → Users/Roles → Access Tokens → New 

Select: 

• Integration Record: The Navan integration record you just created 

• User: Your dedicated Navan integration user 

• Role: The custom role you created in Step 3 

After saving, NetSuite will generate a Token ID and Token Secret. 

You now have four values you will need for the Navan configuration: 

1. Consumer Key 

2. Consumer Secret 

3. Token ID 

4. Token Secret 

Step 6: Configure the NetSuite Integration in Navan 

Log in to your Navan admin account and navigate to: 

Settings → Integrations → NetSuite 

Select NetSuite from the available ERP integrations and enter the four credentials generated in Steps 4 and 5: 

• Consumer Key 

• Consumer Secret 

• Token ID 

• Token Secret 

You will also need to enter your NetSuite Account ID, which can be found under Setup → Company → Company Information in NetSuite.

Once entered, Navan will authenticate against NetSuite and establish the connection. If authentication fails, the most common causes are incorrect credential entry, insufficient role permissions, or the integration record not having Token-Based Authentication properly enabled. 

Step 7: Sync Your NetSuite Data into Navan 

Once connected, Navan will pull your NetSuite financial structure into the integration interface. This includes: 

• Chart of Accounts / General Ledger Accounts 

• Departments 

• Classes 

• Locations 

• Subsidiaries (if running NetSuite OneWorld) 

• Employees (for expense assignment) 

• Expense Categories 

Review each of these carefully. The data that Navan pulls from NetSuite forms the foundation of all your expense mapping so any errors in your NetSuite account structure will surface here. 

Step 8: Map Expense Categories to GL Accounts 

This is the most consequential step in the entire setup and the one that requires the most careful attention. 

In Navan, navigate to the Expense Categories mapping section within the NetSuite integration settings. For each Navan expense category, you need to assign the corresponding NetSuite General Ledger account. 

For example: 

Work through every expense category in Navan and ensure it maps to the correct account in your NetSuite chart of accounts. Unmapped categories will cause sync failures or unposted transactions, which defeats the purpose of the integration entirely. 

If your business uses Departments, Classes, or Locations in NetSuite for cost centre reporting, configure these mappings in Navan as well so expense data lands in the right segment when it syncs. 

Step 9: Configure Sync Settings & Reimbursement Preferences 

Before going live, configure the following in Navan's NetSuite integration settings: 

Sync Frequency: Navan supports both real-time and scheduled sync. For most businesses, a daily automated sync is the right balance of real-time visibility, without overwhelming NetSuite with constant API calls. 

Transaction Type: Decide how Navan expense reports should appear in NetSuite: 

• As Expense Reports (matched to individual employees) 

• As Journal Entries (for consolidated posting) 

• As Vendor Bills (if reimbursements are handled through accounts payable) 

Reimbursement Method: Configure whether employee reimbursements are processed through NetSuite's payroll/AP module or handled directly via Navan. 

Subsidiary Mapping (OneWorld only): If you are on NetSuite OneWorld, map each Navan entity or cost centre to the corresponding NetSuite subsidiary. Without this, expense data will fail to post or land in the wrong entity. 

Step 10: Run a Live Test Carefully 

Remember: Navan has no sandbox environment. This means your test transactions will go directly into your live NetSuite account. 

To manage this responsibly: 

1. Create a dedicated test expense category in NetSuite, mapped to a clearly labelled test GL account (e.g., "9999 Integration Testing") so test entries are easy to identify and reverse 

2. Submit a small number of test expenses in Navan, ideally covering different categories, departments, and employees 

3. Trigger a manual sync in Navan and verify the results in NetSuite, check that transactions are posted to the correct GL accounts, correct departments, and correct subsidiaries 

4. Review any sync error logs in Navan's integration dashboard, address mapping, or permission errors before proceeding 

5. Once verified, manually reverse or void the test transactions in NetSuite before going live with real data 

This deliberate approach to testing in a live environment is essential given the absence of a Navan sandbox. Rushing this step is how businesses end up with duplicate transactions, miscategorised expenses, or unposted entries that take hours to unpick. 

Step 11: Train Your Team and Go Live 

Before switching your entire team to the integrated workflow, brief the relevant stakeholders: 

• Finance team: Understand how synced data will appear in NetSuite, how to handle sync errors, and what the reconciliation workflow looks like 

• Employees: Understand how to correctly submit expenses in Navan. Accurate coding at submission reduces downstream correction work significantly 

• Administrators: Know how to access sync logs, resolve mapping errors, and update the integration as the business evolves 

Once training is complete and your test validation is confirmed, you are live. 

Ongoing Maintenance: What to Watch After Go-Live 

The integration does not run perfectly forever without attention. Here is what to monitor regularly: 

Sync Error Logs: Check Navan's integration dashboard for failed syncs. Common causes include deleted GL accounts in NetSuite, new expense categories without mappings, and subsidiary changes. 

Credential Rotation: If your NetSuite integration record or access tokens are regenerated for any reason, update the credentials in Navan immediately. 

Chart of Accounts Changes: Any time you add, rename, or deactivate GL accounts in NetSuite, review your Navan expense category mappings to ensure nothing is broken. 

Employee Provisioning: When new employees join or leave, ensure their records are correctly synchronised between Navan and NetSuite to avoid unattributed expense submissions. 

Policy Updates: As your company's travel and expense policies change, update the enforcement rules in Navan to keep compliant data flowing into NetSuite. 

Common Issues and How to Fix Them 

Don't Want to Do This Yourself? 

Given the technical complexity of this setup and especially given that Navan has no sandbox environment, meaning every mistake happens in your live financial data, many businesses choose to have a certified NetSuite partner handle the integration correctly from the start. 

At Versich, we are NetSuite implementation and integration specialists operating across the USA and UK. We handle the full Navan NetSuite integration setup, including authentication configuration, GL mapping, subsidiary structure, sync testing, and post-go-live support so you can be confident the integration works exactly as it should from day one. 

What Versich delivers: 

• Full Navan NetSuite integration setup and configuration  

• Custom role and integration user creation in NetSuite  

• Complete expense category to GL account mapping  

• Subsidiary and multi-entity configuration (OneWorld)  

• Live environment testing with controlled reversal process  

• Team training and handover documentation  

• Ongoing NetSuite managed services and support 

No guesswork. No live data mistakes. No months of troubleshooting.