Xero bank statement import template (CSV)
A free Xero bank statement import template in the CSV layout Xero’s statement importer expects, with fictional example rows and an explanation of every column and the date format for your region.
The file is a UTF-8 CSV with Windows (CRLF) line endings. The example uses UK day-first dates; change them to your organisation’s format.
The Xero statement template
| Date | Amount | Payee | Description | Reference | Cheque Number |
|---|---|---|---|---|---|
| 05/01/2026 | -4.50 | Example Coffee Shop | Card purchase | ||
| 06/01/2026 | 1250.00 | Example Client Ltd | Invoice payment | INV-1001 | |
| 08/01/2026 | -900.00 | Example Property Co | Office rent January | RENT-JAN | |
| 12/01/2026 | -150.00 | Example Supplier | Cheque payment | 100234 |
What each column means
- Date (required) — the transaction date, in the date format Xero expects for your organisation’s region (see below).
- Amount (required) — one signed number: negative for money out, positive for money in. No currency symbols or thousands separators.
- Payee — who you paid or who paid you. Xero bank rules can match on it, so keep names consistent.
- Description — free text such as the bank’s narrative.
- Reference — an invoice number or payment reference; it helps match transactions when you reconcile.
- Cheque Number — only for cheque payments.
Xero needs the date, the amount and at least one of Payee, Description or Reference on each line.
Date formats by region
| Xero organisation in | Use | Example for 5 January 2026 |
|---|---|---|
| United Kingdom, Australia, New Zealand | DD/MM/YYYY | 05/01/2026 |
| United States | MM/DD/YYYY | 01/05/2026 |
| Canada | Check your organisation’s date setting | 05/01/2026 or 01/05/2026 |
Xero reads dates according to the region settings of your organisation, so a file with the wrong order puts 5 January on 1 May — or rejects dates after the 12th. Use one format for every row.
Common mistakes
- Two amount columns. Xero’s statement CSV wants one signed Amount. If your data has money in and money out separately, see combining debit and credit columns.
- Lines above the headings. The first line must be the heading row.
- Importing into the wrong account. Import from the bank account the transactions belong to.
- Overlapping periods. Importing the same dates twice creates duplicate statement lines.
Or convert your bank file directly
If you have a CSV, Excel or OFX export from your bank, the free CSV to Xero converter writes this exact layout for you, with the right date format for your region and payees in the right column — in your browser, with nothing uploaded.
How to use the template
- Download the template. Save the Xero CSV template and open it in Excel, Google Sheets or Numbers.
- Add your transactions. Replace the fictional rows with your own, keeping one signed amount per line.
- Set the date format. Use DD/MM/YYYY for UK, Australian and New Zealand organisations, or MM/DD/YYYY for US organisations, on every row.
- Save as CSV. In Excel choose File, Save As, CSV UTF-8. In Google Sheets choose File, Download, Comma-separated values.
- Import into Xero. In Xero, open the bank account, choose Manage account, Import a statement, upload the file and match the columns.
Frequently asked questions
Which columns does Xero require?
Date and Amount, plus at least one of Payee, Description or Reference on each line.
Can I use separate debit and credit columns?
Xero’s statement CSV expects one signed Amount column. Combine them first, or use the CSV to Xero converter, which does it for you.
Which date format should I use?
The format of your Xero organisation’s region: DD/MM/YYYY in the UK, Australia and New Zealand, MM/DD/YYYY in the US.
Can Xero import OFX instead of CSV?
Yes. Xero imports OFX statement files without column matching. The CSV to OFX converter can make one.
Is the template free to use?
Yes. Download it and use it as often as you like; no sign-up is needed.