Understanding Intacct Accounts Payable Integration Error Messages

This article lists common error messages which may be returned from Intacct when exporting data from Nexonia Accounts Payable module to the Intacct Accounts Payable modules.

In Nexonia, view these error messages from Intacct* tab > Accounts Payable> 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. 

*May be labelled differently in your configuration 

Accounts Payable Export Errors

Error:

Date must be on or after MM/DD/YY.

OR

Your transaction date (Bill’s invoice date) is within a period that’s been closed. You can add, modify, or delete a transaction only if the date of that transaction is within a period that’s open. <br><br>Enter a date that occurs on or after the date of the relevant entity (listed below). Note that different entities may have different dates:

Could not create GLBatch record!

Reason:

The GL Posting Date of the expenses being exported is prior to the start date of the oldest open accounting period in Intacct.

Solution:

To resolve this error message, see the article "Controlling the Intacct GL Posting Date of Exported Accounts Payable Bills".

To access the GL Posting Date settings, navigate to the Intacct tab > Integration Setup > go to Configuration Data and click Edit Parameters.

In the Configuration Parameters window, go to the Accounts Payable tab and scroll to the setting Bill Batch Date / GL Posting Date

• Bill Creation Date sets the GL Posting Date to be the date on which the user created the expense report in Nexonia (this is the least selected option)
• Export Date sets the GL Posting Date to be the date on which the export from Nexonia to Intacct took place

• Invoice Date sets the GL Posting Date to be the date which the user inputs into the Invoice Date field at the Bill's header-level

• Oldest Exported Entry Date sets the GL Posting Date to the oldest line item transaction date in the Nexonia expense report
• Latest Exported Entry Date sets the Batch date to the newest line item transaction date in the Nexonia expense report

Error:

The use of an empty Location is invalid. A valid Multi-Entity Location must be specified. Currently, we can’t create the transaction ‘xxxxx’.

Reason:

Nexonia is attempting to export to the top-level without a Location value, which isn’t possible due the Intacct configuration.

Solution:

If you want to keep exporting to the top-level, select a Location for the bill in Nexonia,

OR

If you don’t want to export the bill to the top-level, choose a different Entity (instead of the top-level) to export the Bill to by going to Edit Parameters > Accounts Payable > Entity Type > choose a different option than No Entity.

Error:

The Vendor ‘V-0660’ is invalid. Currently, we can’t create the transaction ’001’.

Reason:

V-0660 is the Vendor ID and 001 is the invoice number.

Nexonia is attempting to export this bill into an Entity that the Vendor is not configured in. For example, Vendor V-0660’ is created in Entity: France but we are attempting to export to Entity: Canada.

Solution:

To determine which Entity the Bill is being exported to, navigate to Integration Setup > Data Integration for Accounts Payable > Edit > Parameters > Entity.

If this is not set to 'Default', then the listed Entity is the one that Nexonia is attempting to export to. If it’s set to 'Default', navigate to Edit Parameters > Accounts Payable > Entity Type.

If it's set to User Entity there is a mismatch between the User and Vendor Entity.

If it's set to Bill Entity there is a mismatch between the Bill and Vendor Entity.

The Vendor Entity can be accessed by going to the Payables tab > Manage Vendors > choose a Vendor > Edit > Currency (if it's set to 'Region', navigate to Settings > Regions > Currency).

Error:

The Location ‘YYY’ is invalid. Currently, we can’t create the transaction ZZZ’.

Reason:

YYY is the Location and ZZZ is the invoice number.

Nexonia is attempting to export this bill into an Entity that the selected Location is not configured in.

Solution:

In Intacct, configure the selected Location in the Entity that we are attempting to export to,

OR

Change the Location in Nexonia to a Location that is configured in the Entity that we are exporting to.

To determine which Entity the Bill is being exported to, navigate to the Intacct tab > Integration Setup > Data Integration for Accounts Payable > Edit > Parameters > Entity.

If not set to 'Default', then the listed Entity is the one that Nexonia is attempting to export to. If set to 'Default', navigate to Edit Parameters > Accounts Payable > Entity Type.

If this is set to 'User Entity', there is a mismatch between the User (User level home region) and the Location's Entity. 

If set to 'Vendor Entity', there is a mismatch between the Vendor entity and the Location's Entity.

If set to 'Project Entity', there is a mismatch between the Project entity and the Location's Entity.

If set to 'Bill Entity', there is a mismatch between the Bill entity and the Location's Entity.