Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
---
title: NS0029 Export Error in NetSuite Integration
description: Learn what the NS0029 export error means in NetSuite and how to resolve connection-related issues.
keywords: NS0029, NetSuite export error, unable to export report NetSuite, NetSuite connection issue, Expensify NetSuite export error, Workspace Admin
internalScope: Audience is Workspace Admins using the NetSuite integration. Covers resolving the NS0029 export error caused by connection issues. Does not cover other NetSuite error codes.
---

# NS0029 Export Error in NetSuite Integration

If you see the error:

NS0029: Unable to export this report due to an error.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Readability violation: The error message text (NS0029: Unable to export this report...) is rendered as a plain paragraph, making it hard to scan and distinguish from explanatory text. Consider formatting error messages as a blockquote or code block so they stand out visually. This pattern applies across all 87 files in this PR.

For example:

> NS0029: Unable to export this report due to an error.


This means there is a connection issue between Expensify and NetSuite preventing the report from exporting.

---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Readability violation: Excessive use of horizontal rules (---) between every section reduces scannability rather than improving it. Horizontal rules should be used sparingly for major section breaks, not between every heading. This pattern is consistent across all 87 files. Consider removing horizontal rules between subsections and keeping them only before the # FAQ section.


## Why the NS0029 Export Error Happens in NetSuite

The NS0029 error typically indicates:

- A temporary communication issue between Expensify and NetSuite.
- An authentication or permission-related problem.
- A configuration mismatch in the NetSuite integration settings.
- A backend or token-related issue.

This error requires additional review to determine the specific cause.

---

## How to Fix the NS0029 Export Error

This issue requires review by Concierge.

Please reach out to **Concierge** and provide:

- The Workspace name.
- The report ID that failed to export.
- The approximate time of the failed export.
- Any recent changes made to NetSuite roles, tokens, or permissions.

Concierge will review the integration logs and identify the root cause.

---

# FAQ

## Can I Retry the Export?

You can attempt to retry the export. If the error persists, contact Concierge for further review.

## Does NS0029 Mean My Data Is Lost?

No. This error indicates the report was not exported successfully. The report remains in Expensify until the issue is resolved.
Original file line number Diff line number Diff line change
@@ -0,0 +1,78 @@
---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Readiness / Content duplication concern: This file is an exact duplicate of Connection-errors/NS0109-Sync-Error.md and Sync-Errors/NS0109-Sync-Error.md (identical content, same blob hash). Having the same article in 3 locations creates SEO/search confusion and maintenance burden.

The following files are exact triplicates across Authentication-and-Login-errors, Connection-errors, and Sync-Errors folders:

  • NS0109-Sync-Error.md (3 identical copies)
  • NS0593-Sync-Error.md (3 identical copies)
  • NS0942-Sync-Error.md (3 identical copies)

And these are exact duplicates across 2 folders:

  • NS0318-Sync-Error.md (2 identical copies: Auth + Sync-Errors)
  • NS0739-Sync-Error.md (2 identical copies: Connection-errors + Sync-Errors)

Additionally, NS0565, NS0123, and NS0521 each appear in 3 folders with slightly different content (near-duplicates).

Consider placing each error code in a single canonical location and, if needed, using cross-references or redirects instead of duplicating files.

title: NS0109 Sync Error in NetSuite Integration
description: Learn how to fix the NS0109 sync error in NetSuite when Expensify cannot log in using admin credentials.
keywords: NS0109, NetSuite login failed, verify admin credentials NetSuite, refresh NetSuite token, NetSuite access token error, Expensify NetSuite sync error, Workspace Admin
internalScope: Audience is Workspace Admins using the NetSuite integration. Covers fixing the NS0109 sync error caused by invalid or expired admin credentials. Does not cover other NetSuite error codes.
---

# NS0109 Sync Error in NetSuite Integration

If you see the error:

NS0109: Failed to login to NetSuite. Please verify your admin credentials.

This means Expensify is unable to authenticate with NetSuite using the current admin credentials or token.

---

## Why the NS0109 Sync Error Happens in NetSuite

The NS0109 error occurs when:

- The NetSuite admin password was changed.
- The access token expired or was revoked.
- The NetSuite role permissions were modified.
- The integration credentials in Expensify are outdated.
- Multi-factor authentication or security settings were updated.

When credentials change or expire, Expensify cannot log in until the connection is refreshed.

---

## How to Fix the NS0109 Sync Error

### Step One: Confirm NetSuite Admin Credentials

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heading level violation: ### headings are too deep for HelpDot articles. Only # (article title) and ## (sections) should be used. This pattern appears across all 87 files in this PR -- every ### Step One, ### Step Two, ### Option One, etc. should be changed to ##.

For example:

Suggested change
### Step One: Confirm NetSuite Admin Credentials
## Step One: Confirm NetSuite Admin Credentials


1. Log in to NetSuite directly using the admin credentials.
2. Confirm the account is active and has the correct permissions for integration.
3. Review the NetSuite integration setup guide to ensure all required fields are correct.

If login fails in NetSuite, update the credentials before reconnecting in Expensify.

---

### Step Two: Generate a New NetSuite Access Token (If Needed)

If you are using token-based authentication:

1. Log in to NetSuite as an Admin.
2. Navigate to the **Access Token Management** section.
3. Create a new access token.
4. Copy the new token details.

---

### Step Three: Update the Connection in Expensify

1. In Expensify, go to **Settings**.
2. Select **Workspaces**.
3. Select your Workspace.
4. Click **Accounting**.
5. Open the NetSuite connection settings.
6. Enter the updated admin credentials or new access token.
7. Save the changes.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Button label violation (Expensify style): Per Expensify documentation standards, the final action in a flow should use "Confirm" rather than "Save." This file uses Save the changes at the end of a configuration flow (line 63). This pattern repeats across nearly all 87 files in this PR -- look for "Save the changes", "Save your changes", "Save the form", and "Click Save" as the last step in numbered flows.

Consider replacing with "Confirm" or removing the explicit save step if the platform auto-saves.

8. Click **Sync now**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Expensify style / consistency violation: This line uses Click **Sync now** while the vast majority of files (70+) use Click **Sync**. A few other files also use inconsistent variants: Click **Sync Now** (capitalized differently). Pick one label and use it consistently across all 87 files. The most common pattern in this PR is Click **Sync**.

Files using the variant Sync now or Sync Now:

  • Authentication-and-Login-errors/NS0109-Sync-Error.md (line 64)
  • Connection-errors/NS0109-Sync-Error.md (line 64)
  • Sync-Errors/NS0109-Sync-Error.md (line 64)
  • Export-Errors/NS0077-Export-Error.md (line 39)
  • NetSuite-FAQ.md (line 194)
  • Sync-Errors/NS0394-Sync-Error.md (lines 57, 68)


After refreshing the credentials or token, the sync should complete successfully.

---

# FAQ

## Do I Need to Disconnect the NetSuite Integration?

Not usually. Updating the admin credentials or generating a new access token typically resolves the issue.

## Does NS0109 Mean My Data Is Lost?

No. This error only indicates a login or authentication failure. Your data remains intact in both Expensify and NetSuite.
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
---
title: NS0123 Sync Error in NetSuite Integration
description: Learn how to fix the NS0123 sync error in NetSuite when the Expensify integration is not enabled.
keywords: NS0123, NetSuite integration not enabled, enable Expensify integration NetSuite, manage integrations NetSuite, Expensify NetSuite sync error, Workspace Admin
internalScope: Audience is Workspace Admins using the NetSuite integration. Covers fixing the NS0123 sync error caused by the Expensify integration being disabled in NetSuite. Does not cover other NetSuite error codes.
---

# NS0123 Sync Error in NetSuite Integration

If you see the error:

NS0123: The Expensify integration is not enabled in NetSuite. Please enable it under Setup > Integrations > Manage Integrations in NetSuite.

This means the Expensify integration is currently disabled in your NetSuite account.

---

## Why the NS0123 Sync Error Happens in NetSuite

The NS0123 error occurs when:

- The Expensify integration is not enabled in NetSuite.
- The integration was previously disabled.
- Integration permissions were modified.
- A NetSuite account configuration change removed integration access.

Expensify cannot sync with NetSuite unless the integration is enabled.

---

## How to Fix the NS0123 Sync Error

### Step One: Enable the Expensify Integration in NetSuite

1. Log in to **NetSuite** as an Administrator.
2. Go to **Setup**.
3. Select **Integrations**.
4. Click **Manage Integrations**.
5. Locate the **Expensify Integration**.
6. Ensure the integration is enabled.
7. Save your changes.

---

### Step Two: Sync the Workspace in Expensify

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

Once the integration is enabled in NetSuite and the Workspace is synced in Expensify, the connection should complete successfully.

---

# FAQ

## Do I Need to Reconnect the Integration?

Not usually. Enabling the integration in NetSuite and running **Sync** in Expensify typically resolves the issue.

## Does NS0123 Mean My Data Is Lost?

No. This error only indicates that the integration is disabled. Your data remains intact in both Expensify and NetSuite.
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
---
title: NS0318 Sync Error in NetSuite Integration
description: Learn how to fix the NS0318 sync error in NetSuite when the Expensify Connect bundle is out of date or missing permissions.
keywords: NS0318, NetSuite permissions error, could not import items NetSuite, Expensify Connect bundle update, SuiteBundler update NetSuite, Expensify NetSuite sync error, Workspace Admin
internalScope: Audience is Workspace Admins using the NetSuite integration. Covers fixing the NS0318 sync error caused by an outdated Expensify Connect bundle or permissions issue. Does not cover other NetSuite error codes.
---

# NS0318 Sync Error in NetSuite Integration

If you see the error:

NS0318: Could not import items due to permissions error. Please update your NetSuite bundle version.

This means the Expensify Connect bundle in NetSuite is out of date or missing required permissions.

---

## Why the NS0318 Sync Error Happens in NetSuite

The NS0318 error occurs when:

- The **Expensify Connect** bundle in NetSuite is outdated.
- The NetSuite account does not have the correct permissions configured.
- An invoice is being exported from Expensify and the bundle version does not support the required functionality.

This error most commonly occurs when exporting invoices.

---

## How to Fix the NS0318 Sync Error

### Step One: Confirm the Export Type in Expensify

1. In Expensify, confirm whether you are exporting:
- An **Invoice**, or
- An **Expense Report**.

If exporting an **Expense Report**:

- You can ignore the error.
- Manually refresh the page to confirm the Workspace synced successfully.

If exporting an **Invoice**, continue to Step Two.

---

### Step Two: Update the Expensify Connect Bundle in NetSuite

1. Log in to **NetSuite** as an Administrator.
2. Go to **Customization**.
3. Select **SuiteBundler**.
4. Click **Search & Install Bundles**.
5. Go to the **List** tab.
6. Locate the **Expensify Connect** bundle.
7. Update it to the latest available version.

After updating the bundle, return to Expensify and retry the sync or export.

---

### Step Three: Reconfirm the NetSuite Connection (If Needed)

If the bundle is already up to date:

1. Review the NetSuite connection steps in Expensify.
2. Confirm each setup step was completed correctly.
3. Reconnect the integration if necessary.
4. Retry the sync.

---

# FAQ

## Does NS0318 Only Affect Invoice Exports?

Yes. This error most commonly occurs when exporting invoices and the Expensify Connect bundle is outdated.

## Do I Need to Disconnect the Integration?

Not usually. Updating the Expensify Connect bundle typically resolves the issue.
Original file line number Diff line number Diff line change
@@ -0,0 +1,87 @@
---
title: NS0510 Export Error in NetSuite Integration
description: Learn how to fix the NS0510 export error in NetSuite when your role lacks access to required records or token permissions.
keywords: NS0510, NetSuite role access error, Expensify Connect bundle update, NetSuite token permissions, Access Token Management permission, User Access Tokens permission, multi-currency NetSuite restriction, Expensify NetSuite export error, Workspace Admin
internalScope: Audience is Workspace Admins using the NetSuite integration. Covers fixing the NS0510 export error caused by outdated bundles or insufficient role/token permissions. Does not cover other NetSuite error codes.
---

# NS0510 Export Error in NetSuite Integration

If you see the error:

NS0510: Your NetSuite role doesn’t have access to this record. Please ensure the Expensify bundle is up to date and that your role has the required token permissions.

This means the NetSuite role connected to Expensify does not have sufficient permissions to access required records.

---

## Why the NS0510 Export Error Happens in NetSuite

The NS0510 error occurs when:

- The **Expensify Connect** bundle in NetSuite is outdated.
- The NetSuite role used for the connection lacks required token permissions.
- Access Token Management permissions are missing.
- Multi-Currency settings restrict required permissions.
- The integration token does not have access to specific record types.

This error is typically related to role configuration or bundle version.

---

## How to Fix the NS0510 Export Error

### Option One: Update the Expensify Connect Bundle

1. Log in to **NetSuite** as an Administrator.
2. Go to **Customization**.
3. Select **SuiteBundler**.
4. Click **Search & Install Bundles**.
5. Open the **List** tab.
6. Locate the **Expensify Connect** bundle.
7. Update it to the latest available version.

After updating the bundle:

1. In Expensify, go to **Settings**.
2. Select **Workspaces**.
3. Select your Workspace.
4. Click **Accounting**.
5. Click **Sync**.
6. Retry exporting the report.

---

### Option Two: Update NetSuite Role Permissions

If the bundle is already up to date, review the role permissions.

1. In NetSuite, go to **Setup** > **Users/Roles** > **Manage Roles**.
2. Select the role used for the Expensify integration.
3. Go to the **Permissions** tab.
4. Under the **Setup** subtab, confirm the following permissions are added:
- **Access Token Management**
- **User Access Tokens**

Note: These permissions can only be added if **Multi-Currency** is not enabled.

After updating permissions:

1. In Expensify, go to **Settings**.
2. Select **Workspaces**.
3. Select your Workspace.
4. Click **Accounting**.
5. Click **Sync**.
6. Retry exporting the report.

---

# FAQ

## Does NS0510 Mean My Integration Is Broken?

No. This error indicates a permission or bundle configuration issue in NetSuite.

## Does Multi-Currency Affect Token Permissions?

Yes. If Multi-Currency is enabled in NetSuite, certain token-related permissions may be restricted. You may need to review your role configuration carefully.
Loading
Loading