Xero is one of our most popular accounting integrations. Over time we have encountered certain known issues which we have highlighted below.
- Contact Push Limitation
- The TaxType Code Cannot be used with Account Code Error
- Account Code or ID must be specified
Contact Push Limitation
The Xero API has a known limitation that does not allow 2 individual contacts with the same name to be pushed through to Xero.
Consider the following scenario:
In Xero, there exists a contact with the name 'John Doe', with the email firstname.lastname@example.org
When integrating with another system, OneSaas gets another 'John Doe' contact, however with a different email address and contact details (email@example.com)
Because of this OneSaas will treat both John Doe records as separate contacts. However, if we try to push the new John Doe into Xero, the Xero API rejects this on the basis that the name is a duplicate.
When this happens, we'll automatically append the second contact with a '-1' (John Doe-1) to send it through to Xero.
The TaxType Code Cannot be used with Account Code Error
This error is often encountered when the tax code used for the set up does not match the required tax type.
In this mapping, the configuration is looking for Expense Tax Codes but the user has selected Income Tax Codes. This is what will cause the error to occur.
This can be usually fixed by updating the configuration then reset the error and resync.
Account Code or ID Must Be Specified
This error will occur when OneSaas detects that a line item on the invoice does not have a Sales Account in Xero.
To fix this, check all the line items on the invoice and see which one has a blank Sales Account mapping. Once a Sales Account has been selected for the item, the error can be easily reset and the invoice should be synced.