Xero Import Bank Statement

Every way to import a bank statement into Xero, and the lowest-effort one: the converter turns your PDF into a Xero-ready OFX or CSV file, with a single signed amount column and dates matching your Xero region, so it imports onto the reconciliation screen without errors. Free to try, online, no installation.

PDF (MAX. 10MB)

4.7/5

Xero-Ready File: The converter turns your PDF into a file Xero accepts: an OFX file that imports with no column mapping, or a clean CSV with the single signed amount column Xero expects, dates in your region's format, and header and subtotal rows already removed.
Free & Online, No Install: This tool to import a bank statement into Xero runs entirely online, free to try with no account and no card. There is nothing to install and it works the same on Windows, Mac, and Chromebook.
OFX or CSV, No Reformatting: Money received comes out positive and money spent negative in one Amount column, dates match your Xero organisation setting, and the file is UTF-8 encoded, so the import does not fail on format or throw a date error.

PDF to a Xero-ready file

Bank statement PDF converted to a Xero-ready OFX or CSV file with a single signed amount column — Left: raw PDF Xero cannot import. Right: Xero-ready OFX or CSV, single signed amount column, regional dates.

How it works

Upload a PDF bank statement to import it into Xero — Drag and drop a PDF from any bank, single or multi-page, scanned files supported.

Transactions converted into a Xero-ready OFX or CSV file — Single signed amount column, regional date format, UTF-8, subtotals removed.

Import the OFX or CSV file into Xero via Import a Statement — Accounting, Bank Accounts, Import a Statement. OFX needs no mapping; transactions hit reconciliation.

How Do You Import a Bank Statement into Xero?

Importing a bank statement into Xero is done from Accounting then Bank Accounts, selecting your account and clicking Import a Statement. Xero accepts OFX, QFX and CSV files. OFX and QFX are the lowest-effort options because the data is already structured and imports with no column mapping. CSV is the manual route: it needs a single Amount column with money received as positive and money spent as negative, three columns (date, description, amount), a date format that matches your Xero region, and blank rows or balance subtotals removed. The catch is upstream: Xero does not import a PDF, and its API cannot push statement lines either, so the only way in besides a bank feed is uploading a correctly formatted file. This converter produces exactly that. It reads your PDF statement and returns a Xero-ready OFX or CSV file, so the transactions land on your reconciliation screen with no reformatting.

Upload any PDF bank or credit-card statement and the converter returns a file Xero accepts. Choose OFX to import with no column mapping and have transactions appear on the reconciliation screen exactly like a bank feed, or CSV with the single signed Amount column Xero requires. Dates are written to match your Xero region, the file is UTF-8 encoded, and headers, the account number and subtotal rows are removed. Because everything happens online, there is nothing to install. You can import a bank statement into Xero in seconds, free to try, whether your statement is one page or eighty, current or from prior years, typed or scanned.

Why Convert First Instead of Reformatting a CSV?

Xero does not import a PDF, only OFX, QFX or CSV
Xero imports bank statements as OFX, QFX or CSV through Import a Statement, but not PDF, which is just an image of your numbers. Its API cannot push statement lines either, so a file upload is the only manual way in. Since your bank gives you a PDF, this converter produces the OFX or CSV that Xero reads directly.

OFX imports with no column mapping
A CSV makes you map columns and match a date format every time. An OFX file arrives pre-structured, so it imports into Xero with no mapping or reformatting and the transactions appear on the reconciliation screen just like a direct feed. The converter produces a clean OFX, the lowest-effort path.

One signed Amount column, the way Xero wants it
Xero's CSV import expects a single Amount column, with money received as positive and money spent as negative, not separate debit and credit columns. The converter writes exactly that single signed column, so you skip the manual step of consolidating debit and credit before upload.

Dates in your Xero region's format
A top cause of failed Xero imports is a date format that does not match your organisation setting, since Xero reads dates by region (for example DD/MM/YYYY in the UK, Australia and New Zealand). The converter writes dates in a consistent format you can match to your Xero region, so the import does not error on dates.

Clean rows and UTF-8, no manual cleanup
Xero rejects a CSV with blank rows, balance subtotals or header text mixed into the data, and encoding issues break accented characters. The converter returns only transaction rows, UTF-8 encoded, so you do not have to delete subtotals or fix encoding before uploading.

Fills bank-feed gaps and historical periods
Bank feeds miss transactions, drop out, or start after your oldest entry, and not every bank has a feed with Xero. The converter reads any date range, and scanned statements are handled with OCR, so you can backfill history, bridge the time before a feed went live, or import from a bank with no feed at all.

What This Tool to Import a Bank Statement into Xero Does

1. Xero-Ready OFX File

The converter produces a genuine OFX file that imports through Accounting, Bank Accounts, Import a Statement, with no column mapping. Transactions appear on the reconciliation screen exactly as they would from a direct bank feed.

2. CSV in Xero's Required Structure

Prefer CSV? The output uses the date, description and single Amount column Xero expects, with money in as positive and money out as negative, so the mapping step is quick and the upload does not fail on structure.

3. Regional Date Format, UTF-8 Encoded

Dates are written in a consistent format you match to your Xero organisation region, and the file is UTF-8 encoded so accented descriptions stay intact, avoiding the two errors that most often stop a Xero import.

4. Only Transaction Rows, Nothing Else

Header rows, the account number, the account holder, and bank balance subtotals are removed, exactly the cleanup Xero otherwise forces on you. What remains is clean transaction data ready to upload.

5. OFX or CSV, Your Choice

Download an OFX file for the lowest-effort, no-mapping Xero import, or a CSV if you want to review before uploading. Both carry clean Date, Description, and Amount data for every transaction.

OFX vs CSV for Xero

Xero import methods compared: raw CSV, OFX file, and PDF conversion — Raw CSV needs mapping and date fixes, an OFX file imports onto reconciliation with none of it.

CSV with the single signed amount column and regional date format Xero requires — One Amount column, positive in and negative out, dates matching your Xero region, so the upload passes.

Import a Bank Statement into Xero: Why the File Format Decides Everything

Most people who want to import a bank statement into Xero hit the same wall: Xero imports OFX, QFX or CSV through Import a Statement, but not PDF, and the majority of banks only issue PDF statements. On top of that, Xero's API cannot push statement lines, so besides a direct bank feed the only way in is uploading a correctly formatted file. A bank statement PDF is not a data table, it is an image of your numbers that Xero cannot read. The manual routes each have a catch. OFX and QFX are the smoothest, arriving pre-structured and importing with no mapping straight onto the reconciliation screen, but your bank has to offer them. CSV works everywhere but is fussy: Xero wants a single Amount column with money in positive and money out negative, not separate debit and credit columns, dates that match your organisation's regional format, UTF-8 encoding, and no blank rows or balance subtotals. Miss any of these and the upload errors out. This page exists because the format layer is where Xero imports actually break. When the converter turns your PDF into an OFX file, Xero reads it with no mapping and the transactions appear on the reconciliation screen just like a feed. When you choose CSV, it comes out with the single signed Amount column, the right regional date format, and only clean transaction rows, so the import passes. For anyone filling bank-feed gaps, backfilling history before a feed went live, or working with a bank that has no Xero feed at all, that difference compounds. It is the gap between a file that imports in seconds and one you reformat in Excel every month. The converter is engineered to produce the former, and it is free to try so you can verify the file on your own statement before importing.

Frequently Asked Questions

1. Is this tool to import a bank statement into Xero free?

It is free to try: you can convert up to 6 statements with no account and no card to check the Xero file for yourself. Create a free account and you get 10 free pages per month. Paid plans are available only if you need higher volume, and most one-off conversions cost nothing.

2. Can I import a PDF bank statement into Xero?

No. Xero imports OFX, QFX or CSV files through Import a Statement, but not PDF, and its API cannot push statement lines either. Since most banks only provide a PDF, you convert it first. This converter produces the OFX or CSV that Xero reads, so transactions land on your reconciliation screen.

3. How do I import the file into Xero?

In Xero, go to Accounting then Bank Accounts, select your bank account, and click Import a Statement. Drag in the OFX or CSV file. For OFX the transactions import with no mapping; for CSV you map Date, Description and Amount and tell Xero to skip the header row, then check the preview.

4. What CSV format does Xero need?

Xero's CSV needs a date column, a description column, and a single Amount column with money received as positive and money spent as negative, not separate debit and credit columns. Dates must match your Xero region format. The converter outputs exactly this structure, so the upload passes.

5. Why does my Xero import fail with a date error?

Xero reads dates by your organisation region, so a file in the wrong format (for example MM/DD/YYYY when your Xero is set to DD/MM/YYYY) throws an error. The converter writes dates in a consistent format you can match to your region, which removes the most common Xero import error.

6. Does it work with scanned or older PDF statements?

Yes. Scanned and photographed statements are read with OCR, and there is no date-range limit. Since bank feeds miss transactions or start late, this is how you backfill historical periods and import statements from a bank that has no Xero feed.

7. Should I use OFX or CSV for Xero?

OFX is the lowest-effort option: it is pre-structured, imports with no column mapping, and the transactions appear on the reconciliation screen like a bank feed. CSV works if you want to review or edit first, but needs the right columns and date format. The converter produces either one.

8. Which banks does it support, and is my data secure?

It detects layouts automatically across hundreds of bank and credit-card formats, so the import works whatever your bank, including regional and overseas banks with no Xero feed. Uploads are protected and removed after conversion, and no account is required to try it, so your data is not stored or shared.