If your completed Unleashed transactions are failing to export to Xero or if there have been any syncing issues for your Supplier and Customer records, use the Connection Log and Failed Exports pages to identify and fix common errors that can occur.
Review failed exports to Xero
There are two ways to review the errors that can occur when data fails to sync successfully between Xero and Unleashed:
Review the Xero integration's Connection Log.
Click on the View Failed Exports link at the bottom of your Unleashed page.
Xero's Connection Log
You can review the Connection Log tab in your Xero integration to further investigate and resolve any issues that may have occurred whilst Unleashed attempted to export your transactions or sync your Suppliers and Customers with Xero.
From the main menu, navigate to Integration > Integration Store > Xero.
Select the Connection Log tab.
All sync updates from the previous 7 days will be listed in date order (newest first) in the grid below.
Filter the connection log's grid using the following filter options:
Log Level: Use the drop-down menu to filter the grid's log by type: All, Error, or Info.
Search: A free text field that will filter the log's details by the specific text entered.
View Failed Exports
When a transaction or record fails to export or sync with Xero, it will be highlighted in the blue "Xero Export Queue" banner that displays at the bottom of your Unleashed pages:
Click on the View Failed Exports link, available in the "Xero Export Queue" banner.
You will be redirected to the Manage Xero Queue page, which will display:
Current Xero Queue: A list of exports currently in process of exporting to Xero.
Failed Xero Exports: A list of exports that have failed to sync.
Within the Failed Xero Exports grid, each listed item will display the following information:
Failed Export: A description of the type of transaction or record attempting to export.
Exported Item: The transaction's, Customer's or Supplier's reference number (e.g. the transaction's order number or the customer's name).
Export Error: A description explaining why the transaction or record failed to export successfully.
Action Required: A description of the steps needed to resolve the error.
Export: A hyperlink that can be selected to re-attempt exporting the failed item.
Delete: A hyperlink that will remove the failed export from the queue.
Alternatively, click the Export All or Delete All hyperlinks to bulk export or delete items from the failed export list.
Resolving common Xero integration errors
When working with Unleashed and Xero integration, you may occasionally encounter errors that prevent transactions or data from exporting correctly to Xero. This section provides common troubleshooting steps to resolve such issues efficiently. If you continue to experience errors after following these steps, contact the support team.
Error message | Cause | Solution |
"The document date cannot be before the period lock date, currently set at XX-XXX-20XX The document date cannot be before the end of year lock date, currently set at XX-XX-20XX" | The date the transaction is attempting to export is after the End of Year Lock Date set in Xero. | You will need to refer back to your Xero account and unlock the End of Year Lock Date, then re-export from Unleashed. This error cannot be resolved in Unleashed directly. |
"Response status code does not indicate success: 500 (Internal Server Error)." | The number if transactions and/or records attempting to export and sync with Xero has exceeded its daily rate limit of 5000 requests. | The daily rate limit is a limitation set by Xero's API and cannot be extended by Unleashed. To resolve, wait 24 hours, until the daily limit has reset and then re-attempt exporting them from Unleashed. For more details on Xero's integration limits, please see Xero Rate limits. |
"Account Code XXX is not a valid Code for this document" "Account code or ID must be specified" | The account may have been archived or no longer exists in Xero. | Contact the Unleashed Support team, and they will be able to re-map the account code to an existing account.
|
"Account must be valid, Tax Rate must be valid" | One of the product line OR the sum total value of the exporting journal transaction is less than 0.005. | There is no straight fix for this error, as Xero is only able to import journals with a value of 0.01 or greater. As such, for journals with a value of 0.005 or less, they are rounded to a value of 0.00 and therefore negligible to Xero's accounts. We therefore suggest deleting the error from your Failed Exports Queue. OR, If you have multiple product lines with value on the same order needing exporting to Xero, you could credit the whole sales order and raise a new one. If you need to include the product which triggered the error you would need to adjust its decimal value and/or discount it 100% if it's not something the customer pays for (i.e. freight). Please note - This workaround may not be suitable for all businesses. |
"The Account Number already exists. Please enter a different Account Number." | The Customer Code already exists as an Account Number in Xero but the contact details don't match. |
|
"Export of XXX to Xero Invoices API failed - Details: [TaxCode XXX] is not mapped to an accounting tax." | The Tax Code on the transaction is not mapped with a Tax set up in Xero. | Xero taxes are for either Purchase or Sales, while Unleashed allows the creation of taxes for Sales and Purchases. Review the Unleashed Setting > System > Taxes page. All taxes should have a selected Accounting Tax and either Purchase or Sales selected for all non-obsolete taxes. Please note - To update the invalid taxes on completed transactions, please contact our Support team. |
"Export of XXX to Xero Contacts API failed - Details: Xero validation error:" | The Customer or Supplier's GST/VAT Number is invalid | Update the Customer or Supplier's GST/VAT Number in Unleashed and ensure it's in a valid format, matching the country specified in the contact's setting in Xero, then re-export from Unleashed. |
"The specified contact details matched an archived contact. Archived contacts cannot currently be edited via the API" | The previously mapped contact in Xero has been deleted, merged or archived in Xero, disrupting it's sync with Unleashed. |
|
"API failed - Details: * Email address must be valid." | The email address for the Supplier or Customer contact is not given in a valid format in Unleashed. | Update the Supplier or Customer contact in Unleashed to ensure:
|
"The contact name XXXX is already assigned to another contact. The contact name must be unique across all active contacts" | The email address for the contact already exists under another contact in Xero. | All mapped contacts from Unleashed must be unique across all contacts (both Suppliers and Customers) in Xero. To resolve the error:
|