If you want to skip coding transactions one by one in reconciliation, you need to create a precoded import file for Xero — a CSV where every line already carries its account code and tax rate, so it imports already classified. The hard part isn’t importing it; Xero handles that fine. The hard part is building the file, especially when your starting point is a PDF bank statement. Here’s what a precoded import file actually is and how to produce one.
What a Xero precoded import file is
A Xero precoded import file is a CSV with the usual bank columns — date, amount, description — plus columns Xero reads for the account code and tax rate of each transaction. Because the coding is baked into the file, the transactions arrive in Xero already assigned to the right accounts, rather than landing uncoded in the reconciliation screen.
That’s the whole point: a plain statement import gets the data in; a precoded import gets the data in and coded.
Step 1 — Turn the PDF into structured rows
You can’t go straight from a pdf bank statement to xero precoded import in one click with Xero alone, because Xero doesn’t read PDFs. First you need the transactions as structured data — one row per transaction with clean date, description, and amount fields. Converting the PDF (rather than copy-pasting) keeps the columns intact.
Step 2 — Assign an account code and tax rate to each line
This is the step that makes it “precoded.” Each transaction needs:
- the account code from your Xero chart of accounts, and
- the tax rate Xero should apply.
Doing this by hand for hundreds of lines is exactly the work the precoded file is supposed to save — so the value depends entirely on how you assign the codes.
Step 3 — Format it as a CSV Xero accepts and import
Arrange the columns so Xero can map account code and tax rate alongside date/amount/description, save as a xero precoded import csv, and import it through the account’s import option. Xero brings the transactions in coded; you review and reconcile.
The shortcut: let AI code it
The bottleneck in creating a precoded import file is the coding, not the formatting. This is what 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 every transaction, assigns the account and tax treatment, and exports a Xero-ready precoded import file. You go straight from a pdf bank statement to xero precoded import without hand-coding each line — just review the exceptions and import. It works from the statement itself, so closed accounts and old history are no problem.
For how the import side works in detail, see how to import bank transactions into Xero from a CSV.
Frequently asked questions
What makes an import file “precoded” in Xero? It includes the account code and tax rate for each transaction, so the lines import already coded instead of needing classification in reconciliation.
Can Xero create a precoded file from a PDF automatically? Not on its own — Xero imports CSV bank data, not PDFs. You convert and code the PDF into a precoded CSV first, then import that.
Do I still reconcile after a precoded import? Yes, but it’s far faster — you’re confirming already-coded transactions rather than classifying each one from scratch.
What columns does a Xero precoded import file need? Date, amount, and description, plus the account code and tax rate columns Xero maps during import.
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 →
Leave a Reply