How to Import Bank Transactions into Xero from a CSV (Precoded Import File)

If you need to import bank transactions into Xero from a CSV, there are actually two very different ways to do it — and knowing which one you’re using changes how much manual work you’re signing up for. A plain statement import drops raw lines into Xero that you still have to code one by one. A precoded import file brings each transaction in with its account and tax rate already assigned. Here’s how both work, and how to produce the precoded version.

Two kinds of CSV import in Xero

Xero accepts two flavours of bank data via CSV:

Most people who search for how to import bank transactions into Xero from a CSV only know about the first one. The second is where the time savings live.

Step 1 — Get a clean CSV out of the statement

Whether you want a plain or precoded import, you first need the transactions in a structured CSV. If you’re starting from a PDF statement, you’ll need to convert it — copy-paste almost never preserves the columns. The goal is a file with one row per transaction and consistent Date, Description, and Amount columns.

Step 2 — Import a plain statement (the manual route)

In Xero, go to Accounting → Bank accounts, pick the account, then Manage account → Import a statement. Map your columns to Date, Amount, and Description, and import. Xero loads the lines into the reconciliation screen — but every transaction is uncoded, so you still sit in reconciliation assigning an account to each one. For a few transactions that’s fine. For a catch-up client with months of history, it’s the whole job.

Step 3 — Build a precoded import file instead

A Xero precoded import file is a CSV that already contains the account code and tax rate for each line, so the transactions import already coded. The format adds columns Xero recognises for the account and tax treatment alongside the usual date/amount/description. When you import it, the coding work is essentially done — you review and reconcile rather than classify from scratch.

The catch is building that xero precoded import csv in the first place. Assigning the right code to hundreds of lines by hand defeats the purpose. This is the exact gap I built Bookmonstic for. (Disclosure: I’m a CPA and Bookmonstic is my own tool.) You drop in a PDF, CSV, or Excel statement, the AI reads and categorises every transaction, and it exports a Xero-ready precoded import file — so you convert bank statement to xero import file and code it in one pass, no rules to set up and no bank feed required. You review the exceptions and import a clean, coded file.

Which should you use?

• A handful of transactions, going forward → a plain statement import (or the bank feed) is quick enough.
• Catch-up, cleanup, closed accounts, or high volume → a precoded import file, so you’re not hand-coding line by line.

For the QuickBooks equivalent of this workflow, see how to convert a PDF bank statement to QuickBooks Online.

Frequently asked questions

What format does Xero need to import bank transactions from a CSV? At minimum, columns for Date, Amount, and Description. A precoded import file adds account code and tax rate columns so the transactions import already coded.

What is a precoded import file in Xero? A CSV where each transaction already carries its account code and tax rate, so it imports coded instead of landing uncoded in the reconciliation screen.

Can I import a PDF bank statement straight into Xero? No — Xero imports CSV (and OFX/QIF) bank data, not raw PDFs. You convert the PDF into a CSV (ideally a precoded one) first.

Will a CSV statement import categorize transactions for me? A plain statement import won’t — you code each line in reconciliation. A precoded import file does, because the codes are already in the file.

Written by the founder of Bookmonstic, a practicing CPA. Bookmonstic turns PDF/CSV/Excel bank statements into AI-categorized, import-ready files for QuickBooks and Xero — no rules to build, no API. Try it free →