Loading...
Loading...
Most Xero bank statement CSV errors come from four root causes: the date format does not match your organization's region, amounts have the wrong sign or non-numeric characters, the file has blank rows or non-UTF-8 encoding, or the column layout does not match one of the two accepted formats.
Xero's error messages are usually vague ("No valid statement data", "Unable to import"), so the fix is to go through the common causes below in order.
Fast answer: verify your Xero region, normalize the date format to match it, use positive amounts for money in and negative for money out, save as UTF-8, and delete blank rows.
You export a bank CSV, upload it to Xero, and get a generic error with no row number and no specifics. This guide walks through the seven reasons Xero rejects statement files and exactly what to check for each one. Fixes are ordered by how often they are the cause, highest first.
This is the most common cause by a wide margin. Xero's date parser follows your organization's country setting.
| Xero region | Expected date format | Example |
|---|---|---|
| United States | MM/DD/YYYY | 03/15/2026 |
| United Kingdom | DD/MM/YYYY | 15/03/2026 |
| Australia | DD/MM/YYYY | 15/03/2026 |
| New Zealand | DD/MM/YYYY | 15/03/2026 |
Fix:check your region in Settings > General Settings and reformat every date to match. Watch out for the silent failure mode where dates with day-of-month 12 or lower parse successfully but in the wrong order.
ISO format caution:many bank CSVs export dates as 2026-03-15. Xero does not accept ISO format directly. Convert every date to your region's format before uploading.
In Xero's single-amount CSV format, the sign determines direction:
These common patterns cause Xero to reject the row:
$1,234.56 currency symbol and thousand separator1234.56 CR credit suffix (common on Australian banks)(1234.56) accounting-style negatives in parenthesesFix: strip amounts down to a plain number with an optional minus sign. If your bank uses CR/DR suffixes, convert to signed values: money in stays positive, money out becomes negative.
This error typically means one of these three things:
Fix: open the CSV in a plain text editor (VS Code, Notepad, TextEdit), save as UTF-8, and remove any empty rows. Do not fix this in Excel. Excel often introduces the encoding problem by re-saving the file.
Xero accepts two bank statement CSV layouts:
| Format | Minimum columns | Optional columns |
|---|---|---|
| Single-amount | Date, Amount | Payee, Description, Reference |
| Debit/Credit | Date, Debit, Credit | Payee, Description, Reference |
Fix: delete extra columns (running balance, branch, account number, etc.) that are not in either accepted layout. Keep the columns you do need in any order, with the header names Xero maps on (Date, Amount, Debit, Credit, Payee, Description, Reference).
Excel silently rewrites CSV files on save. The most common damage:
Fix: re-download the CSV from your bank and edit it in a plain text editor instead. If you need to make bulk edits, a converter keeps the file outside of Excel entirely.
Xero flags duplicate statement lines during reconciliation. If you upload the same month twice (for example, because the first upload appeared to fail but actually partially succeeded), you end up with every transaction listed twice in the statement lines view.
Fix: go to the Bank accounts page, open the Statement lines view, and delete the duplicate import. Xero keeps each upload as a separate statement you can remove without affecting reconciled transactions.
If you are uploading a precoded CSV with AccountCode, TaxType, or ContactName columns, every value has to match your Xero organization exactly:
Fix: pull the full list of AccountCode and TaxType values from your Xero settings, then validate every row in the CSV against those lists before uploading.
The free Xero CSV converter reshapes any bank or card export into Xero's accepted layout. Pick your date format to match your organization's region, map the columns once, and download a clean CSV. The file never leaves your browser.
Once the statement is in Xero, every line has to be reconciled against an account. On a busy month that can mean hundreds of decisions.
The Bulk Categorizer groups transactions by category and Schedule C bucket, which makes it faster to assign each group to a Xero AccountCode during reconciliation, especially when the same merchants appear on every statement.
That error usually means one of three things: the file has blank rows inside the data range, the date format does not match your Xero region, or the CSV has hidden characters from a non-UTF-8 encoding. Fix by saving as UTF-8 in a plain text editor and removing empty rows.
Xero follows your organization's regional setting. US organizations expect MM/DD/YYYY. UK and Australian organizations expect DD/MM/YYYY. If your CSV is in ISO format (2026-03-15) or day-month-short-year (15-Mar-26), Xero rejects the file.
Positive numbers for money in (deposits), negative numbers for money out (withdrawals), in the single-amount format. Use a period as the decimal separator for English-language regions. No currency symbols, no commas for thousands, no CR or DR suffixes.
If your Xero organization is set to a US region but your CSV uses DD/MM/YYYY, dates where the day is 12 or below will be misinterpreted (March 2 vs February 3). Either switch the CSV to MM/DD/YYYY or check your organization's region in Settings > General.
Not if you can avoid it. Excel silently reinterprets dates based on the system locale and can strip leading zeros from reference numbers. Use a plain text editor like VS Code, Notepad, or TextEdit. Or run the file through a converter that outputs a clean Xero-compatible CSV directly.