NS0739 Sync Error in NetSuite Integration

If you see the error:

NS0739: Unexpected error when logging in with tokens. This usually means the tokens were created with incorrect permissions or are not formatted properly.

This means the NetSuite access tokens used for the Expensify integration were created with incorrect permissions or are improperly formatted.

Why the NS0739 Sync Error Happens in NetSuite

The NS0739 error occurs when:

• The NetSuite access token does not have the required permissions.
• The SOAP Web Services permission is not set to Full.
• The token is incorrectly formatted.
• A Sandbox token is not properly capitalized.
• The role assigned to the token is missing required permissions.

Expensify relies on properly configured token-based authentication to connect to NetSuite.

How to Fix the NS0739 Sync Error

Step One: Confirm SOAP Web Services Permission

1. Log in to NetSuite as an Administrator.
2. Go to Setup > Users/Roles > Manage Users.
3. Locate and edit the user associated with the Expensify Integration Role.
4. Click the Permissions tab.
5. Scroll to the Setup section.
6. Confirm SOAP Web Services is set to Full.
7. Save your changes.

Step Two: Confirm Token Formatting (Sandbox Environments)

If you are connected to a NetSuite Sandbox environment, confirm the token is formatted correctly.

Correct format example:

• 12345678_SB1

Incorrect format example:

• 12345678-sb1

Sandbox identifiers must use an underscore and proper capitalization.

Step Three: Retry the Sync in Expensify

1. In Expensify, go to Settings.
2. Select Workspaces.
3. Select your Workspace.
4. Click Accounting.
5. Click Sync.

After correcting permissions and token formatting, the sync should complete successfully.

FAQ

Do I Need to Create a New Token?

If the token permissions or formatting are incorrect, it may be easier to generate a new access token after confirming the correct role permissions.

Does NS0739 Mean My Integration Is Broken?

No. This error typically indicates a token configuration or permission issue, not a full integration failure.