CSV vs Excel vs QBO vs OFX: which bank statement format should you use?
Four file types turn up whenever bank data moves between systems. They are not interchangeable, and picking the wrong one is behind many failed imports. Here is what each one is, and a simple way to choose.
By Muhammad Sharif · October 2026 · 8 min read
Banks, accounting packages and spreadsheet programs all speak slightly different dialects of the same idea: a list of dated, described, signed amounts. The differences between formats are about how much structure travels with the list, and how forgiving the receiving software is. Knowing them lets you pick the format that makes the import boring, which is the goal.
CSV: the plain-text common denominator
A CSV (comma-separated values) file is plain text. Each line is a row and commas separate the columns. A statement CSV typically looks like this:
Date,Description,Amount,Balance2026-03-01,PAYROLL DEPOSIT,2450.00,5120.332026-03-02,GROCERY STORE #212,-84.17,5036.16
Strengths: opens everywhere, easy to inspect and edit in a text editor, accepted by nearly every spreadsheet and accounting program, small file size.
Weaknesses: no standard. Column order, date style, sign conventions and header names differ between banks and software, and nothing in the file states which is which. A CSV also carries no account identity, no currency and no transaction ID, so duplicates are hard to detect. Excel can also quietly reformat a CSV when you open it, converting dates, stripping leading zeros and turning long numbers into scientific notation, so open it as text if precision matters.
Excel (XLSX): a spreadsheet, not an interchange format
An XLSX file is a zipped bundle of XML that stores cell values, types, formulas, formatting and multiple sheets. It is the best format for people who want to work with the data: sorting, filtering, pivot tables, categorisation, charts.
Strengths: values keep their types, so a date is a date and a number is a number, with no re-interpretation on opening. Formulas and notes can live beside the data, which is ideal for the balance check described in our reconciliation guide.
Weaknesses: most accounting software does not accept XLSX for bank imports, or only accepts it in a strict template. Treat it as a working format, then export a CSV for import.
OFX: the structured bank format
OFX (Open Financial Exchange) is a standard for financial data, used by banks for downloads and by software for imports. An OFX file declares the account, the currency, the date range and, importantly, gives each transaction a unique ID (FITID). Related files you may meet are QFX, Intuit's flavour of OFX used with Quicken, and QBO.
Strengths: no column mapping, explicit signs and dates, and unique transaction IDs, so accounting software can detect that a line was already imported.
Weaknesses: not human-friendly, strict about syntax, and software varies in which versions it will read. A malformed file produces a vague error.
QBO: OFX for QuickBooks
QBO is the file extension QuickBooks uses for Web Connect: an OFX file with the identifiers QuickBooks expects. It imports in one click and is a staple for people who work in QuickBooks Online. Our dedicated article on what a QBO file is explains the structure.
One caveat applies to QBO files created from a converted PDF rather than directly by a bank. The file cannot know your real bank identifier or account number, so it carries placeholder values, and QuickBooks will ask you which account to import into. For accounts in a currency other than the one the file declares, or for a credit card, it is often safer to use CSV and the mapping screen. After importing several months, also check whether QuickBooks marked any lines as duplicates, because duplicate detection relies on the transaction IDs inside the file.
Side by side
| CSV | XLSX | OFX / QFX | QBO | |
|---|---|---|---|---|
| Human readable | Yes | In Excel | Barely | Barely |
| Carries account identity | No | No | Yes | Yes |
| Transaction IDs | No | No | Yes | Yes |
| Column mapping at import | Yes | Rarely accepted | No | No |
| Best for | Xero, QuickBooks, Sheets, Wave and most others | Analysis, checks, reporting | Xero, Quicken and tools that read OFX | QuickBooks Online and Desktop |
How to choose
- You want to analyse or check the data yourself: XLSX. Keep the original PDF next to it.
- You are importing into Xero, Wave, Zoho, FreeAgent or most other packages: CSV, in the layout that package documents. See the Xero guide for an example of how strict that can be.
- You use QuickBooks Online and the account is a plain checking account: QBO is the quickest, CSV is the most controllable.
- You are loading into Google Sheets: CSV or XLSX both work; our Sheets guide covers the details.
- You are a bookkeeper working with many banks: keep one clean XLSX per statement as your source of truth, and generate the import file from it.
Frequently asked questions
Is QBO the same as OFX?
They share the same underlying structure, but QBO adds Intuit-specific identification so that QuickBooks recognises it as a Web Connect file. Software that reads OFX may or may not accept a QBO file, and vice versa.
Why does Excel change my CSV dates?
Excel converts text that looks like a date into a real date using your computer's regional settings, and may reorder day and month in the process. Import the CSV through Data → From Text/CSV and set the date column to Text if you need to protect the original.
Which format keeps the most information from the statement?
XLSX with extra columns (balance, notes, category, source page) keeps the most for people. OFX keeps the most for software, because it adds IDs and account details.
