This topic has 2 versions: the Brex classic experience and the Brex Empower platform. If you need help finding which you use, sign in or read this article.

When attempting to export directly to your accounting software integration from the Review & Export page, you may see the error message Unable to export.

The most common reasons for this error can be found below.

User permissions have changed since initial integration setup

Account admins, card admins, and bookkeepers can resolve this issue by following the steps outlined below.

Note: As long as you reconnect to the same account, your mapping rules will remain the same in your dashboard.

Step 1: Ensure that you have full admin access within your accounting software.

Step 2: Click the Integrations tab on the left side of your Brex dashboard.

Step 3: Click Settings in the top right corner next to Review & Export.

Step 4: Click Disconnect at the bottom of the page.

Step 5: Click Connect and follow the prompts to reconnect your integration. Details to set up each integration can be found here: QuickBooks Online Setup, NetSuite Setup, Xero Setup, Sage Intacct Setup.

One or more of the accounts or entities that transactions are mapped to is no longer active within your chart of accounts

To resolve, confirm that there haven’t been any recent changes to your chart of accounts within your accounting software. If there have been,re-enable any GL Accounts, Departments, Locations, etc. that may have been disabled.

You can also refresh the integration, which resyncs your chart of accounts. You can then remap all the transactions that were being mapped to inactive accounts or entities.

One or more fields in NetSuite are marked as mandatory

If you’re a NetSuite user, a setting may be enabled that makes Departments, Classes, or Locations mandatory. If this is the case, Brex can’t export transactions, even if each transaction is assigned a Department, Class, or Location.

To resolve, please disable this setting within NetSuite before attempting to export. You can re-enable the setting after export.

One or more required fields in NetSuite have been disabled

For Brex to export successfully, the custom fields Receipt URL and Created From should be enabled in NetSuite. To confirm that they are, follow the steps outlined below:

Step 1: In NetSuite, navigate to Customization > Forms > Transaction Forms.

Step 2: Locate your preferred journal entry form. Type will be listed as Journal and preferred will be marked in the far right column.

Step 3: On the Custom Transaction Form page, click Screen Fields > Lines.

Step 4: Find the two custom line fields named Receipt URL and Created From and select the Show checkboxes next to them.

Step 5: Click Save.

If you’re still receiving an export error, please reach out to Support.

One of your field values is not available to your NetSuite entity

If you are seeing the error Invalid location reference key, then you are likely attempting to export a transaction to NetSuite that uses a Location that is not within your entity.


This can happen when you set up a Custom Rule to apply a NetSuite Location for transactions across different entities. You can resolve this issue by deleting the Custom Rule in question.

When attempting to export directly to your accounting software integration from the Review & Export page, you may see the error message Unable to export.

The most common reasons for this error can be found below.

User permissions have changed since initial integration setup

Account admins, card admins, and bookkeepers can resolve this issue by following the steps outlined below.

Note: As long as you reconnect to the same account, your mapping rules will remain the same in your dashboard.

Step 1: Ensure that you have full admin access within your accounting software.

Step 2: Click the Accounting tab on the left side of your Brex dashboard.

Step 3: Under Export settings, click Manage [your account software].

Step 4: Click Disconnect at the bottom of the page.

Step 5: Click Connect and follow the prompts to reconnect your integration. Details to set up each integration can be found here: QuickBooks Online Setup, NetSuite Setup, Xero Setup, Sage Intacct Setup.

One or more of the accounts or entities that transactions are mapped to is no longer active within your chart of accounts

To resolve, confirm that there haven’t been any recent changes to your chart of accounts within your accounting software. If there have been, re-enable any GL Accounts, Departments, Locations, etc. that may have been disabled.

You can also refresh the integration, which resyncs your chart of accounts. You can then remap all the transactions that were being mapped to inactive accounts or entities.

One or more fields in NetSuite are marked as mandatory

If you’re a NetSuite user, a setting may be enabled that makes Departments, Classes, or Locations mandatory. If this is the case, Brex can’t export transactions, even if each transaction is assigned a Department, Class, or Location.

To resolve, please assign a NetSuite default by following these instructions: How do I set up NetSuite defaults fields?.

One or more required fields in NetSuite have been disabled

For Brex to export successfully, the custom fields Receipt URL and Created From should be enabled in NetSuite. To confirm that they are, follow the steps outlined below:

Step 1: In NetSuite, navigate to Customization > Forms > Transaction Forms.

Step 2: Locate your preferred journal entry form. Type will be listed as Journal and preferred will be marked in the far right column.

Step 3: On the Custom Transaction Form page, click Screen Fields > Lines.

Step 4: Find the two custom line fields named Receipt URL and Created From and select the Show checkboxes next to them.

Step 5: Click Save.

If you’re still receiving an export error, please reach out to Support.

One of your field values is not available to your NetSuite entity

If you are seeing the error Invalid location reference key, then you are likely attempting to export a transaction to NetSuite that uses a Location that is not within your entity.

This can happen when you set up a Custom Rule to apply a NetSuite Location for transactions across different entities. You can resolve this issue by deleting the Custom Rule in question.


Was this article helpful?

|

Still can't find what you're looking for?

Chat with us->