> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/central/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ordereazi.com/central/order-management/integrations/accounting-system/xero/xero-sync-errors.md).

# Xero Sync Errors

What Xero's sync errors mean, and how to fix the document, contact, or product Xero refused.

Xero checks every document, contact, and product OrderEazi sends before accepting it. If Xero refuses one, OrderEazi shows you Xero's reason, in Xero's own words, so you can fix the cause. Here are the most common reasons and how to fix them.

### Before you start

You'll need the **Accounting System** permission, in the **Integrations** permission group, to see the Xero settings and sync log. If you don't have it, ask your OrderEazi administrator to add it to your role. To fix the cause, you'll often need a Xero login too.

### Where you see sync errors

A document Xero refused shows the error under it, on the project's **Documents** tab, with "Click the error for guidance on how to resolve it." Selecting the error opens the matching section below.

Errors that aren't about one document, such as a sync that stopped early, are in the **Sync log** at the top of your Xero settings.

There are two kinds of problem:

* **A refused document:** Xero refused the document itself. Once you've fixed the cause, contact OrderEazi support to have it sent again. It isn't sent again on its own.
* **A waiting document:** Xero refused something the document needs, such as its client. Once you've fixed that, the document goes across on the next sync by itself.

### Item code is not valid

Xero says "Item code '...' is not valid". The document uses a product that Xero can't find by its code, usually because the item was deleted in Xero, or its code was changed in one system.

Make sure the product exists in Xero with exactly the same code as in OrderEazi. Xero only accepts codes of up to 30 characters, so shorten longer codes to 30 characters or fewer in both systems. Then contact OrderEazi support to send the document again.

### Contact has been archived

Xero says the contact on the document is archived. The client or supplier is linked to an archived Xero contact, and Xero doesn't accept new documents for archived contacts.

Making a client or supplier inactive in OrderEazi archives its Xero contact. Make it active again in OrderEazi, or restore the contact in Xero. Then contact OrderEazi support to send the document again.

### Contact name is already in use

Xero says "The contact name ... is already assigned to another contact." OrderEazi tried to create a client or supplier in Xero, but Xero already has an active contact with that name. Contact names must be unique in Xero.

If it's the same business, archive or merge the duplicate in Xero. If they're different businesses, rename the client or supplier in OrderEazi. OrderEazi tries again on its next sync, and the documents waiting for the contact go across by themselves.

### Document is not in a valid status

Xero says "Invoice not of valid status for modification", or that the document has a payment or credit note allocated to it. The document was changed in OrderEazi after it was paid, credited, or voided in Xero, and Xero won't let it be edited.

If the change is needed, remove the payment or credit allocation in Xero first. Or record the change as a new document, such as a Credit Note, instead of editing the original. Then contact OrderEazi support to send the document again.

### Tax type cannot be used with this account code

Xero says "The TaxType code '...' cannot be used with account code '...'". The tax rate on a line isn't allowed on the account the line posts to.

In Xero, allow that tax rate on the account. Or, in your Xero settings in OrderEazi, change the default account or tax rate so lines post to an account that accepts it. Then contact OrderEazi support to send the document again.

### Waiting to sync

A document can wait because Xero refused something it depends on, such as its client or one of its products. It shows a note such as "Waiting to sync: Xero rejected the client". The document itself is fine. Fix the client, supplier, or product named in the note, and the document goes across on the next sync.

**Example:** A Tax Invoice shows "Waiting to sync: Xero rejected the client 'Acme Ltd': The contact name Acme Ltd is already assigned to another contact." In Xero, you find an old Acme Ltd contact from before you used OrderEazi, and archive it. On the next sync, OrderEazi creates the contact, and the invoice goes across.

### The Xero sync log

Select **Sync log** at the top of your Xero settings. It lists the last 30 days of syncs, newest first, with **When (UTC)**, **Sync**, **Outcome**, and **Message**. A red number on the button counts the problems.

* **Started** and **Finished:** A sync began, and completed.
* **Stopped:** A sync stopped early, with the reason.
* **Rejected:** Xero refused a client, supplier, or product.
* **Retried:** Xero asked OrderEazi to slow down, and it tried again on its own. Nothing to do.

Tick **Problems only** to see just the problems, and select **Copy all** to paste them into a support request.

### Daily limit reached

Xero limits how many requests your organisation can make in a day. If you reach it, you see "Xero's daily limit for your organisation was reached." with the time syncing resumes. Nothing is lost. Syncing carries on by itself at that time.

### Related pages

* [Xero](/central/order-management/integrations/accounting-system/xero.md): your Xero settings
* [Accounting System](/central/order-management/integrations/accounting-system.md): the main switches