Home › Guides › Fix Xero Bank Statement Import Errors: Dates, Amounts and CSV Rows
Fix Xero Bank Statement Import Errors: Dates, Amounts and CSV Rows
For a Xero bank statement CSV import error, check that the file contains transaction rows with a valid Date and signed Amount, uses a supported date format, and maps to the intended bank account. Remove balance columns, account numbers and empty rows from the import copy. Inspect existing imports before retrying a period.
Updated November 6, 2026
Check the import type before changing the data
A bank statement CSV belongs in the bank account's Import a Statement workflow. Invoice, contact and other CSV importers expect different templates. If a valid-looking file produces “no valid data” or similar wording, begin by checking the workflow, required fields and mapping; the wording alone does not establish one specific cause.
Xero supports several bank statement formats. This page focuses on CSV preparation. PDF import availability and file restrictions are separate, and can vary by country and plan.
Use this diagnostic checklist
| Symptom | Check | Correction to try |
|---|---|---|
| No usable rows recognised | Real CSV content, mapped Date/Amount and rows below the header | Prepare a small transaction-only copy and remap the fields |
| Dates rejected or interpreted incorrectly | Mixed formats or ambiguous dates such as 04/05/2026 | Use one supported format and confirm a known date |
| Amounts rejected | Separate Debit/Credit fields, decimal commas or currency text | Use a single signed Amount with a decimal point |
| CSV too long | More than 100,000 rows, including empty trailing rows | Remove empty rows or use smaller non-overlapping batches |
| Unexpected statement balance | Missing rows, wrong signs, overlap or wrong destination account | Compare with the original statement before further imports |
1. Make the rows unambiguous
Xero's statement CSV requires Date and Amount. If you include headings, put them in row 1 and make every name unique. Remove cover text, repeated page headers, account numbers, balance columns and empty rows from the import copy. Do not remove those details from your original evidence copy.
Each row should describe one transaction. A statement summary such as “total withdrawals” is not an extra transaction. If a description wraps over multiple PDF lines, review the extraction so it does not become several incomplete CSV rows.
2. Check date and amount interpretation
Xero supports DD/MM/YYYY, MM/DD/YYYY and YYYY/MM/DD, among other documented formats. Choose one convention for the whole file. A date with a day above 12 is useful for confirming which interpretation is being used. If the saved CSV differs from the spreadsheet display, correct the saved text, not just the workbook formatting.
For amounts, put income and expenses in the same column. Income is positive; an expense can use a minus sign or brackets. Xero says not to use commas as decimal separators. Do not globally delete punctuation: a minus sign and decimal point carry essential meaning. A reliable review includes a known receipt and a known payment.
3. Retry without duplicating a successful attempt
First check whether the prior import completed, partially progressed or only showed a preview. Inspect the correct account's existing statement lines and date range. Do not assume a warning means nothing was imported. Keep a record of which source files and periods have already been used.
Once the working copy is corrected, use Import a Statement, map the fields and review the data before completion. After import, reconcile the statement lines. If errors remain, keep the exact message and a description of the step where it occurred for Xero support; avoid posting private bank data in a public discussion.
If you are importing a PDF instead
Xero's current PDF import help limits that feature to organisations in Canada and the United States and excludes the Xero Ledger plan. Its documented PDF requirements include English text, no password protection, at most 100 pages and a size of 35 MB or less. Check the current regional help before assuming your organisation has PDF import. A reviewed CSV can be an alternative workflow when direct PDF import is unavailable; it still needs the checks above.
From a PDF to reviewed transaction data
If you need to extract a PDF into statement rows, use the Xero CSV converter and review both the row details and statement balance before importing.
Open the converter → · Plans and limits · How balance checks work
Conversion runs in your browser; statement files are not uploaded to CSVLedger. A balance check helps identify extraction issues, but does not replace review or accounting reconciliation.
Frequently asked questions
What are the minimum Xero statement CSV fields?
Date and Amount. Additional detail helps matching and reconciliation.
Does a bank statement CSV automatically categorise transactions?
No. Importing statement lines and reconciling them to accounting transactions are separate steps.
Can every Xero organisation import a PDF directly?
No. The current Xero help restricts PDF statement imports by country and plan, with additional file requirements. Check the official article for your organisation.
Related guides
- Xero Bank Statement CSV Template: Required Columns and Examples
- Complete Xero import walkthrough
- Fix QuickBooks CSV Date Format Errors Before Importing
Sources and scope
Based on official help documentation reviewed through search results on November 6, 2026. Menus, regional availability and product requirements can change; use the current official instructions if your screen differs. Examples are fictional. These instructions are documentation-based, not a claim of a completed live import test.