Xero's direct bank feeds are brilliant when they work. Your bank sends transactions straight into Xero, and you reconcile them as they arrive.

But direct feeds don't cover everything. If your bank isn't supported, if you're dealing with an overseas account, a credit card provider that only exports PDFs, or a payment processor like Stripe or PayPal — you need another way to get that transaction data into Xero.

This guide covers three approaches: Xero's manual CSV upload, converting statements from other formats, and automated import using EntryRocket.

Why bank statements sometimes need manual importing

Xero has direct feed agreements with many major banks, but the coverage isn't universal. Common situations where you'll need to import manually include:

  • Banks in countries or regions that don't support Xero feeds
  • Credit unions and smaller financial institutions
  • Business credit card accounts from providers like Amex or Diners Club
  • Payment processor settlement reports from Stripe, PayPal, or Square
  • Older accounts or closed accounts where feeds have been disconnected
  • Multi-currency accounts held with overseas banks

In all these cases, you typically get a statement file — CSV, Excel, PDF, or OFX — that needs to get into Xero for reconciliation.

Method 1: Xero's manual CSV import

Xero lets you upload bank statement files directly to a bank account.

How to do it

Go to Accounting > Bank Accounts in Xero, select the relevant bank account, click Import a Statement, and upload your file. Xero supports CSV and OFX formats natively.

CSV format requirements

For CSV files, Xero expects a very specific structure. You need either three columns (Date, Description, Amount) or four columns (Date, Description, Debit, Credit).

The date format must match your Xero organisation's region setting — DD/MM/YYYY for UK, Australia, and New Zealand; MM/DD/YYYY for the US. This is the single most common source of import errors. If your bank exports dates as 2026-03-15 (ISO format) or 15-Mar-2026, you'll need to reformat every date before Xero will accept the file.

Amounts in the single-amount format need to be positive for money in and negative for money out. If your bank exports debits and credits in separate columns, you need to consolidate them into one column before importing.

The file must be UTF-8 encoded. Files with encoding issues will show garbled characters in transaction descriptions.

Xero recommends keeping files under 500 lines per import.

Limitations

The CSV format Xero accepts is rigid. Most bank statement exports don't match it out of the box — they have extra columns, different date formats, or a different structure. You end up spending time in Excel reformatting data before every import.

PDF statements can't be imported into Xero at all. If your bank only provides statements in PDF, you need to convert them to CSV first (manually or using an OCR tool).

OFX files generally work more smoothly than CSV, but not every bank provides OFX exports.

Method 2: Converting your statement files

If your bank statement is in a format Xero doesn't accept — PDF, Excel, or a CSV with the wrong structure — you'll need to convert it first.

PDF to CSV conversion

Several tools can extract transaction data from PDF bank statements and produce a CSV that Xero can read. This involves uploading the PDF, checking that the extracted data looks right, adjusting columns to match Xero's requirements, and downloading the CSV.

The accuracy depends on the quality of the PDF and how the tool handles your bank's specific layout. Scanned statements (images rather than digital PDFs) are harder to convert accurately.

Excel reformatting

If your statement is in Excel, you'll need to strip out extra columns, rename headers to match what Xero expects, reformat dates, and save as CSV. This is manual work, and it needs to happen every time you get a new statement.

The recurring cost of conversion

The core problem with conversion is that it's repetitive. Every week or month, the same reformatting task. The same risk of introducing errors. The same 15-30 minutes of work that feels like it should be automated.

Method 3: Automated import with EntryRocket

EntryRocket imports bank statements into Xero from any file format — CSV, Excel, PDF, OFX, XML — without requiring any reformatting.

How it works

Email your bank statement file to your dedicated @entryrocket.com address. A custom reader, built specifically for your bank's export format, maps the transaction data — dates, descriptions, amounts, references — and imports the transactions into the correct Xero bank account. They appear in Xero's reconciliation screen, ready to match.

You get a confirmation email showing what was imported and whether anything needs attention.

What this solves

You never need to reformat a file. Your bank's CSV, your Amex PDF, your Stripe settlement export — whatever the format, whatever the column structure, EntryRocket handles the mapping.

If you're importing from a payment processor like Stripe or PayPal, your reader can automatically separate processing fees from gross amounts, so the net figures in Xero match your actual bank deposits.

Multi-currency statements are handled without needing to manually adjust date or number formats.

Who this works for

  • Businesses whose bank doesn't support Xero direct feeds
  • Companies importing Stripe, PayPal, or Square settlement data
  • Finance teams dealing with overseas bank accounts or multi-currency transactions
  • Anyone who spends recurring time reformatting bank statements before uploading them to Xero

Choosing the right approach

If your bank supports Xero direct feeds — use them. They're the simplest option and work automatically.

For everything else, the choice is between manual conversion and automation. If you're importing one statement per quarter, manual conversion is manageable. If it's weekly or monthly, or involves multiple accounts, or the format requires significant reformatting — the time spent on manual work adds up quickly, and automation gives that time back.