Fix Xero Import Errors

Xero imports your file as statement lines — the same kind of lines a bank feed produces, ready to reconcile against your invoices and bills. That's why the column shape matters so much. Get it right once and the file slots in cleanly; get it wrong and Xero either bounces the upload or, worse, accepts a file that's quietly missing a transaction.

The error you'll actually see, and what fixes it

Xero's messages are terser than QuickBooks' and tend to point at a row or a column. Here's how the common ones map to a cause.

That last row is the dangerous one, because there's no message attached to it. We'll come back to why.

What Xero's "Import a Statement" CSV needs

Xero's bank-statement import maps to a small, fixed set of fields. You don't need every column the bank gave you — you need the ones Xero recognises:

• Date — required. Has to match the date format you select on the import screen.
• Amount — required. Either a single signed figure (out = negative, in = positive) or split across columns Xero can read as money in and money out.
• Payee — who the transaction was with. Treated as required for a usable line.
• Description — what it was for. Strongly recommended; it's what makes reconciliation against bills and invoices quick later.
• Reference — optional, but useful for matching cheque numbers or invoice references.

Everything else from the original statement — the running balance column, transaction-type codes, a second address line, blank spacer rows — should come out before you save. A statement export that's been trimmed to those fields imports far more reliably than one you've handed over whole.

Sort the date format first

The single most common Xero import error is a date mismatch, and it catches anyone working across regions. A statement printed as `06/04/2026` is the 6th of April in the UK and the 4th of June in the US — Xero can't tell which you mean, so it asks you to pick the format on the import screen.

Pick the order your file actually uses. If your CSV reads `06/04/2026` and you mean the 6th of April, choose DD/MM/YYYY. Then do the one check that saves the most grief: find a payment you remember and confirm it imported on the right date. A month out means your format selection is wrong, not your data.

Editing the file by hand? Write dates as `YYYY-MM-DD`. It's unambiguous and Xero handles it cleanly. Don't trust Excel here either — open a CSV and re-save it and it'll happily reinterpret a date column without telling you.

Get the amount column into one shape

Two separate things go wrong in the amount column, and they produce similar-looking failures.

The first is formatting inside the cell. A value like `1,240.00` reads as text because of the symbol and the comma, so Xero either zeroes it or refuses to map the column. The cell should hold `1240.00` and nothing else — no currency sign, no thousands separator.

The second is the shape of the column. Decide between one signed Amount column, where money out carries a minus (`-89.99`) and money in is positive, or columns Xero can map separately as paid-in and paid-out. Pick one. A money-out figure that loses its minus sign imports as income, and you won't notice until the account refuses to reconcile and you're hunting for the difference.

Clear the duplicate-statement warning

When Xero says a statement looks like a duplicate, it's comparing the date range against what's already on that bank account. Usually it's right — you've re-imported a month, or the range overlaps a few days you already brought in.

Import in clean, non-overlapping ranges. Know the exact last date you imported and start the next file the day after. If the warning fires and you're certain the lines are new, you can override it, but check first — once duplicate statement lines are in, you're unpicking them one at a time during reconciliation.

Why a reconciled CSV clears most of these at once

Here's the part most guides skip. Every error above is a *format* problem, and format problems at least announce themselves. The quiet one is a missing transaction. A converter can hand you a tidy CSV with perfect Date, Amount and Payee columns that imports into Xero without a single complaint and is still wrong — because one Direct Debit fell off the bottom of page three. A clean file that's incomplete is worse than an obviously broken one, because you'll trust it.

This is where the running balance earns its keep. It's a built-in checksum: opening balance, plus money in, minus money out, has to equal the printed closing balance. Recompute it line by line and the first row where your total stops matching the bank's figure is the exact line where something was dropped or misread. Reconcile before you import and you're not chasing a discrepancy through your Xero account a fortnight later.

Export Bank Statement converts the PDF — including scanned and photographed statements, via OCR — into a clean CSV or Excel file, then runs that running-balance check for you. It recomputes the totals against the printed closing balance and flags any statement that doesn't reconcile, so a missing or misread line shows up before it reaches Xero. We once watched a tidy-looking import fail the check over a single standing order clipped at a page break; the flag turned an afternoon of cross-checking into a one-line fix. It also writes the file in Xero's native bank-import CSV format, so Date, Amount, Payee and Description arrive shaped the way Xero's importer expects.

Be plain about what it is, though: convert, then import. It doesn't push transactions into Xero through a live bank-feed API, and it isn't a bookkeeping service — you decide what gets imported and reconciled. For the field-by-field detail, the Xero CSV import format explained walkthrough goes column by column, and can Xero import PDF bank statements? answers the question sitting underneath all of this. You can also browse the wider Xero guides or the UK accounting guides.