Your bank gave you a file built for accounting software, and you wanted a spreadsheet. Drop the .qbo, .ofx or .qfx and take the transactions as CSV — read here, on your computer, and never uploaded.
| Date | Description | Amount |
|---|
Date, description, amount, type, cheque number and the transaction id the file carried. Dates are written YYYY-MM-DD, which no spreadsheet can read the wrong way round.
It is a document of tagged text, not a table — and that is before the name confuses anyone.
It is a Web Connect download: a statement your bank wrote for accounting software to import. QuickBooks keeps its own books in .qbw and .qbb files, which hold a whole company rather than a list of transactions and are not what this page reads. The extension and the product share three letters and nothing else.
Open the file as it is and every line arrives in column A as <STMTTRN> and <TRNAMT>, because there are no commas to split on. Renaming it .csv changes nothing — the tags are still there. Something has to read the tags and lay the fields out in columns, which is what happens above.
.qbo, .qfx and plain .ofx are the same document with a couple of branding tags between them, and each exists in two dialects: OFX 1.x is SGML whose tags are never closed, OFX 2.x is ordinary XML (a real file, tag by tag). All of it reads the same here. A strict XML parser fails on exactly the files banks hand out most often, so this page does not use one.
Investment OFX records trades, positions and income in blocks of its own and carries no bank transactions at all. It opens here and gives nothing back. If the page says the file holds no transactions, that is usually why.
Six columns, and the one place a spreadsheet can still spoil them.
Date, Description, Amount, Type, Cheque, Id. Type is the word the file itself used — DEBIT, CREDIT, CHECK, XFER, POS — and Id is the transaction id the bank issued. Nothing is added, renamed or reordered on the way through, and rows come out oldest first whatever order the file wrote them in.
Money out is negative and money in positive, in a single Amount column, exactly as the file has it. The column sums to the net movement and a pivot by month needs no second step. There is no balance column, because a running balance is not in the file: it states a closing figure once, and a column repeating that on every row would look like a balance without being one. When you need balances to check against, the PDF statement is where they live.
The file keeps two description fields and a spreadsheet has one. When both are present and say different things they are joined with an em dash, so nothing the bank wrote is quietly dropped on the way into a single cell.
A transaction id is often a long run of digits, and Excel opening a CSV by double-click turns that into 1.2E+15 and keeps the rounded number. Import it instead with Data → From Text/CSV and set the Id column to Text, or take the same file as a workbook, where the id is already text and any zeros in front of it survive.
Something else? Write to support@ocrsnip.com.
Yes. No row limit, no trial, no account, and nothing is added to the file. The $4.99 pass on this site is for reading PDF statements, which is the part that takes real work; this page is not a sample of it.
In the account's download menu it usually sits next to the CSV option, called Web Connect, “download for Quicken”, or simply QFX. Banks differ in how far back they will export, but what they hand out is this same document whichever of the three extensions they put on the end of it.
No. The institution, account number, type and currency belong to the statement rather than to any one transaction, so they are shown above the table and not repeated down a column; the closing figure is read from the file and left out for the same reason. Copy what you need from the line above the table.
Two things do that. An investment or brokerage OFX holds trades rather than bank transactions, and there is nothing here to list. Or the statement really is empty — open the file in any text editor and search for STMTTRN; no such tag means no transactions in it.
Yes, and it is free as well: CSV to QBO writes the file QuickBooks and Quicken import, and Excel to QBO does the same from a workbook. Sending a file out through one page and back through the other is also a reasonable way to correct one bad field.
Yes — QBO to Excel is the same reader with a workbook at the end, where amounts are numbers that sum and a transaction id keeps its leading zeros. This page stays CSV-only so that a visitor who wants a comma-separated file never downloads a spreadsheet library to get one.
Different page, same reader: OFX to QBO takes the .ofx or .qfx and writes it back out as the .qbo QuickBooks Desktop will open, with the bank id it checks for before reading a single row. The transactions and their ids are untouched.
No. It is read in this tab and the CSV is written here too. The network panel stays empty while you convert.