This article lists common error messages which may be returned from Intacct when exporting Nexonia expense receipts data.
Viewing Error Messages
Step 1: In Intacct, click Expense Receipts.
Step 2: In the Message column, click Failure or Partial Success from the most recent integration log entry.
Error: Date must be on or after XX/XX/XXXX Currently, we can't edit the transaction 'NEX-XXXX'.
The listed date was valid at the time the report was exported but it isn’t being allowed now when we try to re-save the report by exporting receipts.
Locate the report to which the receipts should get added in Intacct, edit the report and click Save without making any actual edits. When you re-trigger the export in Nexonia, it should go through successfully.
Error: javax.xml.bind.UnmarshalException - with linked exception: [org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.]
The receipts have likely already been attached to any of the listed reports in Intacct.
Check the reports listed in the error message in Intacct to see if all the receipts have been attached already. If they are there, you can click the Flag All Pending Receipts as Exported option in the Expense Receipts integration. That will flag the referenced receipts as exported and prevent the error message from generating. Note that it is recommended to set the scheduling of your receipt integration to the hourly option to prevent expenses from exporting to Intacct well ahead of receipts. This way there is less of a risk that the expenses will be closed in Intacct before the receipts have had a chance to export, which could prevent them from transferring to Intacct. To set the scheduling to happen hourly, go to the Integration tab in Nexonia > Integration Setup > Data Integrations > click Edit next to the receipt integration > click Edit next to Scheduling > check mark Activate Scheduling if not already check marked > set the drop-down menu to Hourly > check mark Everyday > OK > OK to save.