QuickBooks Desktop refuses a perfectly good .ofx and takes the same transactions as a .qbo without a murmur. Drop the file your bank gave you, add the one number QuickBooks looks for, and download it in the format it will open. Free, and nothing is uploaded.
| Date | Description | Amount |
|---|
Less than the software selling the conversion would like you to think. OFX, QFX and
QBO are the same document: the same header, the same account block,
the same transactions in the same tags. A .qbo carries two extra lines —
INTU.BID and INTU.USERID — and a different extension. That
is the whole difference, and
what is inside one of these files shows it line by line.
So this page does not re-interpret your statement. It reads the transactions, writes them out again with the two Intuit tags in place, and names the file so that the program you are aiming at will agree to open it. Every amount, date, payee and transaction id comes through untouched — including the id, which is what stops a re-import from doubling a month you already have.
INTU.BID is an institution id: QuickBooks Desktop checks it against its
own list of banks before it reads a single transaction, and refuses the file
outright when it does not recognise the number. That is why a correct .ofx full of
correct transactions gets rejected with a message about the format, and why no
converter can invent the number for you — it belongs to your bank, not to the file.
Where to find it: the id your bank uses is printed in QuickBooks' own financial
institution directory, and a .qbo you have successfully imported before contains it
in plain text near the top. Open that older file in a text editor and copy the digits
after <INTU.BID>. If you have never had one, the bank's support
line can give it, and leaving the box empty still produces a valid .ofx and .qfx.
QuickBooks Desktop wants the .qbo, and wants the bank id in it. Quicken wants .qfx and often refuses a plain .ofx holding exactly the same rows — it checks the extension before the contents. QuickBooks Online is the forgiving one: .csv, .qbo, .qfx and .ofx are all accepted on its upload screen, so if Desktop is fighting you and the data matters more than the route, that is the quick way through. Xero, GnuCash, Wave and most everything else read the plain .ofx.
All four buttons above write the same transactions. Choosing between them is choosing which program will open the file, not which data goes in it.
Something else? Write to support@ocrsnip.com.
Yes, with no row limit and no account. It re-tags a file you already have, and every converter here that does that is free — the paid tools are the ones that read a document and check it, like a PDF statement or an MT940.
Then the bank id is wrong or missing — that is the check it runs first. A .qbo you imported successfully in the past holds the right number in plain text near the top: open it in a text editor and look for INTU.BID. Failing that, QuickBooks Online accepts the plain .ofx this page also writes, and OFX to IIF takes the same file down a route that asks for no institution id at all — at the cost of the transaction ids that stop a re-import doubling.
No. Each transaction keeps the unique id its original file gave it, and QuickBooks and Quicken both use that id to recognise a transaction they have seen before. Re-importing an overlapping month corrects rather than doubles — which is exactly what would break if a converter rewrote the ids.
That is the other direction and it is free too: QBO to Excel and QBO to CSV read .qbo, .qfx and .ofx and hand back columns.
No. Reading the file and writing the new one both happen in this tab; there is no upload step and no server on this site that receives files. The network panel of your developer tools stays empty while you convert, which is the only form of this promise worth anything.