NS0844 Sync Error
NS0844 Sync Error in NetSuite Integration
If you see the error:
NS0844: Permission error querying NetSuite for ‘Vendor’. Please ensure the connected role has access to this record type in NetSuite.
This means the NetSuite role associated with the Expensify access token does not have permission to access Vendor records.
Why the NS0844 Sync Error Happens in NetSuite
The NS0844 error occurs when:
- The NetSuite access token is assigned to the wrong role.
- The Expensify Integration role does not have Vendor permissions.
- The role’s List permissions were modified after the token was created.
- The token is tied to a user-role combination that lacks access to Vendor records.
Access tokens in NetSuite are linked to both a User and a Role. If the role lacks required permissions, the sync will fail.
How to Fix the NS0844 Sync Error
Step One: Confirm the Token Is Assigned to the Expensify Integration Role
- Log in to NetSuite as an Administrator.
- Search for Access Tokens.
- Click View next to the token used for the Expensify integration.
- Confirm the token is assigned to the Expensify Integration role.
If the token is not assigned to the correct role, create a new token tied to the correct user and role, then reconnect in Expensify.
Step Two: Update Vendor Permissions on the Expensify Integration Role
- In NetSuite, go to Setup.
- Select Users/Roles.
- Click Manage Roles.
- Select Expensify Integration.
- Click Edit.
- Scroll to Permissions.
- Open the Lists tab.
- Locate Vendors.
- Set the permission level to Full.
- Click Save.
Step Three: Sync the Workspace in Expensify
- In Expensify, go to Settings.
- Select Workspaces.
- Select your Workspace.
- Click Accounting.
- Click Sync.
Step Four: Retry the Sync or Export
Once the Vendor permission is set to Full and the Workspace is synced, the sync should complete successfully.
FAQ
Does NS0844 Mean My Vendor Records Are Missing?
No. This error indicates a role permission issue, not missing vendor records.
Do I Need to Reconnect NetSuite?
Not usually. Updating the role permissions and running Sync is typically sufficient unless the token is tied to the wrong role.