How to Open a QFX, QBO or OFX File in Excel Without Quicken or QuickBooks

What these files are

The first three differ only in their extension and a handful of fields that describe the bank, not the transactions. Every transaction in them — date, amount, payee, memo, the bank's own transaction ID — is written the same way. QIF is a different, older format with the same purpose.

What Excel shows when you open one

We opened real test files from open-source projects directly in Excel — the 2007 version on our test machine — to see what comes out.

None of these can be sorted by date or added up. The tags are the file's structure, not its content, and Excel has no importer that knows which tag is the amount. Newer versions of Excel open plain text the same way; we have not tested their XML import.

Renaming the file does not help either: .qfx, .qbo and .ofx are the same text, and Excel showed the same 83 rows for all three.

First, check whether your bank offers CSV

If you are downloading from your bank right now, look for a CSV or Excel option next to Quicken, QuickBooks or Web Connect. Many banks offer one, and it opens in Excel without any conversion. A QFX or QBO is still worth converting when:

• the bank offers only Quicken or QuickBooks downloads, or only for older periods
• the file came from a client, an accountant or an old archive, and the bank is no longer there to ask
• the bank's CSV leaves out the transaction ID, which is the reliable way to remove duplicates when combining downloads
• you have QIF exports from an old copy of Quicken or Microsoft Money

How to convert QFX, QBO, OFX or QIF to Excel

1. Open the page for your file: QFX to Excel, QBO to Excel, OFX to Excel or QIF to Excel. The three OFX pages accept all three extensions
2. Drop the file in, or click to choose it
3. Download the spreadsheet: one row per transaction, one sheet per account

For another program rather than a spreadsheet — a budgeting app, an accounting import, your own script — use the CSV versions instead: QFX to CSV, QBO to CSV, OFX to CSV, QIF to CSV.

A bank statement is the kind of file you should not have to upload to a stranger's server. Here nothing is: the file is read and the spreadsheet written inside the page, and you can watch your browser's network panel while converting to check that nothing carrying the file goes out.

Five things to check in the result

1. Dates that moved by a day

OFX timestamps carry a time zone, such as 20240131000000[+10:AEST]. A converter that turns that into UTC first moves midnight on the 31st in Sydney to the 30th, and the row no longer matches the statement. In our tests one widely used reader did exactly that to a brokerage file whose trades were stamped 8:20 pm US Eastern time, moving every trade to the next day. The converter here keeps the day the bank wrote and drops the time.

2. Day and month the wrong way round

QIF does not say whether 03/04/2024 is the 3rd of April or the 4th of March. The converter reads the whole file first: one date like 23/10/2013 proves it is day-first, one like 10/23/2013 proves it month-first, and a file with neither is read month-first, as Quicken writes. If your file is the exception, set "Dates in the file" before converting. In the result every date is written 2024-01-31, which no program misreads.

3. Amounts with a decimal comma

Some European banks write -12,50, and QIF exports can contain 1.234,56. Both are read as numbers — -12.50 and 1234.56 — so the Amount column adds up. If you open the CSV in Excel set up for Germany, France or most of continental Europe, choose the semicolon layout: that Excel expects semicolons between cells and opens a comma-separated file as a single column.

4. Duplicates when you combine downloads

Download January to March and then March to May, and March appears twice. Two rows with the same date and amount can be two real purchases — two coffees on the same day — so do not de-duplicate on those. Use the Transaction ID column: it is the bank's own identifier for each transaction, unique within the account.

5. A payee that turns into a formula

A CSV is plain text, and Excel treats a cell that starts with = as a formula. Payees are written by merchants, and in our test a payee written as =1+1, opened in Excel as a CSV, showed 2; one written as =HYPERLINK(...) becomes a live link. The converter puts an invisible tab character in front of any text that starts with = or @, or with + or - when it is not a number, so Excel shows it as text; we checked in Excel that it no longer runs. Amounts are left alone and stay numbers.

How well it reads real files, measured

We collected 85 OFX files and 25 QIF files from the test suites of eight open-source projects — checking, card and brokerage statements, some labelled as coming from Fidelity, Vanguard, American Express and Nubank — and compared what this converter read with three Python libraries, ofxparse, ofxtools and quiffen.

The files the libraries refused are the ones banks really produce: a missing header, a list of transactions never closed, payees wrapped in CDATA, an empty balance. The differences are explained on each converter's page. Measured on 25 October 2026; converting 10,000 transactions in Chrome took 0.4 to 0.7 seconds from dropping the file to the download being ready.

What it does not do

• It does not go back the other way. Turning a spreadsheet into a QFX or QBO that Quicken or QuickBooks accepts needs an Intuit bank identifier, and a wrong one gets the file refused on import. We have not built that, rather than offer a file that fails.
• It does not categorise. Category, cleared mark and splits are copied from a QIF as written; nothing is guessed for an OFX.
• It does not add a running balance. An OFX states the balance once, at the end, not after each transaction, so the sheet holds transactions only.
• It does not read PDF statements. A PDF has no transactions in it, only text placed on a page; that is a different problem.
• A file with holdings but no transactions is reported as such rather than turned into an empty table.