How Xero 404 differs from Xero 400 and 401: These three HTTP errors look similar but mean different things. 400 Bad Request means the request itself was malformed — wrong data format or missing required fields. 401 Unauthorised means the credentials or OAuth token are invalid — re-authentication is needed. 404 Not Found means the credentials are fine and the request is valid — but the specific resource (page, record, feed connection) does not exist at that URL. For 404, look for deleted records or broken connections — not credential problems.

Error code

404

HTTP · Not Found

Related: Xero 400 · Xero 401 · Xero 403 · Xero 500

What it means

HTTP 404 is a universal web standard meaning "Not Found." In the Xero context it means Xero's servers received a valid, authenticated request — but the specific thing being requested (a page, a record, a bank feed connection, an API endpoint) does not exist at the URL that was requested. The resource has been deleted, moved, or never existed.

Your Xero data is safe. Error 404 is a navigation or connection error — it does not modify or delete any data. The underlying Xero organisation, transactions, and records are unaffected.

Saved Bookmark Points to Deleted Record

Most common cause — a browser bookmark, saved link in an email, or browser history entry points to a Xero record (invoice, bill, contact, account) that has since been deleted or voided. The URL is valid but the record it referenced is gone.

Third-Party Integration Partially Disconnected

A connected app (payroll software, bank feed provider, POS system) was disconnected on one side only — either removed from Xero's Connected Apps list without updating the app, or disconnected in the app without removing the Xero connection. The remaining half-connection produces 404.

Bank Feed Connection No Longer Exists

Per Xero's developer documentation, a 404 response from the bank feeds API specifically means the feed connection ID referenced no longer exists in Xero — the feed was disconnected from the Accounting → Bank Accounts side without updating the bank's integration.

Stale Browser Cache or Session

The browser is serving a cached version of a Xero page URL that has since changed or been removed. This is especially common after Xero updates its internal URL structure. A hard refresh or cache clear resolves this variant.

OAuth Token Expired or Interrupted

An integration connection to Xero was established but the OAuth authorisation process was interrupted (browser closed, timeout, user cancelled). The partial token causes 404 when the app tries to connect to a Xero organisation resource that was never fully authorised.

Wrong Xero Organisation Selected

A URL points to a record in one Xero organisation but the user is currently logged into a different organisation. The record does not exist in the active organisation — producing a 404. Common for accountants and bookkeepers with multiple Xero organisations.

METHOD 1 Clear Browser Cache and Hard Refresh — Then Navigate from the Menu Stale URL in browser — do this first

Browser cache is the fastest fix for 404 errors that appear randomly inside Xero. The browser may be serving an outdated URL — a hard refresh or cache clear forces it to load the current Xero page structure.

METHOD 2 Check You Are in the Correct Xero Organisation Multi-org user — record exists in a different org

If you manage multiple Xero organisations, a URL from one organisation will produce a 404 when you are logged into a different one — the record doesn't exist in the current org.

METHOD 3 Reconnect the Bank Feed From Accounting → Bank Accounts Bank feed returning 404 — connection no longer exists

Xero's bank feeds API returns 404 when the feed connection ID no longer exists — the bank feed was disconnected from the Xero side. Reconnecting the bank feed creates a new valid connection.

METHOD 4 Disconnect and Fully Reconnect the Third-Party Integration App showing 404 when connecting to Xero

When a third-party app (payroll software, bank feed provider, POS) returns a 404 connecting to Xero, the OAuth connection is broken or incomplete. A full disconnect on both sides followed by a fresh reauthorisation resolves this.

METHOD 5 Check Xero Status Page for Known Outages Multiple users affected — possible Xero-side issue

If 404 errors appear across multiple areas of Xero or affect multiple users simultaneously, the issue may be on Xero's side — a platform outage, maintenance, or deployment affecting specific features.

METHOD 6 Locate Deleted Records via Xero's Archived or Voided Views Record was deleted — need to find or restore it

If the 404 is from a saved bookmark pointing to a deleted record — the record is archived or voided in Xero. It may be recoverable.

How is Xero Error 404 different from Error 400 and Error 401?

All three are HTTP status errors but they identify different failure types. Error 400 Bad Request means the request was malformed — data was missing, in the wrong format, or contained invalid values. This is typically an API or integration configuration issue. Error 401 Unauthorised means the request reached Xero's server but the authentication token or credentials were rejected — the session has expired, the OAuth token is invalid, or permissions have changed. Error 404 Not Found means authentication was fine and the request was valid — but the specific resource being requested does not exist at that URL. For 404, look for deleted records or broken connections. For 401, reconnect or log in again. For 400, check the data or integration configuration.

Can I recover a deleted Xero invoice or contact that is causing a 404?

It depends on how it was removed. Voided invoices can be found under Accounting → Invoices → change the filter to Voided — and can be restored or edited. Archived contacts appear under Contacts → filter to Archived — and can be unarchived. Permanently deleted records cannot be recovered from Xero's interface. If a record was deleted and is not in the Voided or Archived views, it is gone. You would need to recreate the record and update any saved bookmarks, email links, or integration references to point to the new record.

My payroll software keeps getting a 404 error when syncing to Xero. What causes this and how do I fix it permanently?

Recurring 404 errors from payroll software syncing to Xero almost always trace to an expired or corrupted OAuth token. Xero's OAuth tokens have a limited lifetime and must be periodically refreshed. If the token refresh fails — due to an interrupted session, a Xero account password change, or a change in the payroll app's access permissions — the next sync attempt produces a 404 because the session resource no longer exists. The permanent fix is a full disconnect and reconnect (Method 4). After reconnecting, check whether the payroll app has a setting to refresh the token automatically — enabling this prevents the same error from recurring after the next token expiry.