Understanding Bill.com Expense Integration Errors

This article lists common error messages which may be returned from Bill.com when exporting Nexonia expense data to Bill.com

In Nexonia, view these error messages from Intacct* > Expense Reports > choose the Integration from the drop-down menu if you have more than one > in the Message column on the right, click Failure or Partial Success from the most recent integration log entry.

Expense Export Errors:

Error: Can't export report for '[user name]'. as this user is not part of the integration

Reason:

This is caused by the user whose name is listed not being active in Nexonia.

Solution:

You may be integrated with an ERP from which users are synced, in which case they need to be re-activated in your ERP first to get activated in Nexonia. If your users aren't integrated from another ERP, they need to be activated in Nexonia. Go to Settings > Users > click into the applicable user profile > Edit > set Active to Yes > Apply to save.

Error: Can't export report for '[user name]'. as this user is not part of the integration

Reason:

This is caused by the user whose name is listed not being active in Nexonia.

Solution:

You may be integrated with an ERP from which users are synced, in which case they need to be re-activated in your ERP first to get activated in Nexonia. If your users aren't integrated from another ERP, they need to be activated in Nexonia. Go to Settings > Users > click into the applicable user profile > Edit > set Active to Yes > Apply to save.

Error: Category: '[category name]' is not part of the integration

Reason: This is caused by the categories that are listed with this error not being mapped for export to Bill.com.

Solution:

To resolve, go to the Integration* tab > Integration Setup > Data Integrations > click Edit next to the Bill.com expense integration > Parameters > Categories/Accounts > map the categories listed in the error to the applicable Bill.com accounts > OK to save.

Error: Department/Location/Class not found

Reason:

This is caused by one or more items in the referenced report(s) being coded to an inactive Department/Location/Class value

Solution:

If your Departments/Locations/Classes are integrated from another ERP, you can re-activate the values in your ERP and run a sync in Nexonia to activate the values in there. You can also code the affected expenses to other values that are already active.