How to convert a QFX file to QBO for QuickBooks
Your bank's download page offers a file for Quicken — .qfx — and QuickBooks Desktop's Web Connect import will not take it. The two files are almost the same thing inside, which is why renaming one is the first thing everybody tries, and why it usually fails anyway. Here is what actually has to change, and how to do it in about ten seconds without the statement leaving your computer.
🔒 Drop your QFX file into the converter — free, runs in your browser, the file is never uploaded.
First, which QuickBooks?
This matters, and most pages on the subject skip it.
- QuickBooks Desktop. Web Connect requires a
.qbofile. That is the case this page is about. - QuickBooks Online. Intuit's own instructions for Upload from file are not consistent about QFX: some versions of the article list
.csv,.txt,.qboand.ofx, and others say you can also upload a Quicken QFX. So try your QFX as it is first — Transactions → Bank transactions → Link account dropdown → Upload from file — and only convert it if the upload is refused. Online also caps an upload at 1,000 transactions, which a long statement will exceed whatever the format.
Why QuickBooks Desktop refuses a QFX file
This is not a bug or a missing setting. Asked directly in Intuit's own community how to get a bank's QFX file into QuickBooks, an Intuit moderator answered: ".QBO files are required. There are work arounds to make a .QFX file work but they are unsupported." (How to get a QFX file from my bank into QuickBooks?, QuickBooks Community.)
The reason the two formats exist at all is product branding, not technology. .qfx, .qbo and plain .ofx are all OFX — Open Financial Exchange — underneath. A .qfx carries the extra tags Quicken looks for, a .qbo carries the ones QuickBooks looks for, and a plain .ofx carries neither, which is why Xero, GnuCash and most other software is happy with it.
What is actually different inside the two files
Open either one in Notepad or TextEdit and you will see readable text. The transaction blocks are identical. The difference is a few lines near the top, in the sign-on block:
<FI>
<ORG>B1
<FID>10898
</FI>
<INTU.BID>2002
<INTU.USERID>you@example.comINTU.BID is the Intuit institution id, and each Intuit product validates it against its own list of institutions. A QFX file's id is one Quicken recognises. QuickBooks checks the id against the institution directory it ships with, and when the id is not in that directory it refuses the file with a generic message rather than telling you which tag it disliked. A .qfx may also carry INTU.USERID, which has no meaning in QuickBooks at all.
So why does renaming .qfx to .qbo not work?
Two separate obstacles, and people usually only hear about the first:
- The file picker filters by extension. Web Connect's dialog lists
.qbofiles, so a.qfxis invisible until you rename it. This is the part renaming does fix. - The institution id inside is still Quicken's. Nothing about renaming a file changes a byte of its contents, so QuickBooks reads an
INTU.BIDit does not know and rejects the import — most often as "QuickBooks is unable to verify the Financial Institution information for this download". That is the same error people hit with a hand-built QBO, and it has its own guide here.
Occasionally a rename does work, because the bank happened to use an id both products accept. That is luck, not a method, and it is why the advice you find in forums is contradictory: it worked for the person writing it.
Convert it properly, in three steps
- Open the converter and drop the
.qfxfile on it. It is read by JavaScript running on your own machine — nothing is uploaded, so you are not sending a bank statement to a stranger's server to have four lines of a header rewritten. - Check the preview. You will see Date, Description, Amount, Type, Check number, Memo and FITID recovered from the file, with dates shown as YYYY-MM-DD so there is no day-versus-month ambiguity to misread. If the file holds more than one account, an Account column appears instead of the accounts being silently merged.
- Choose .QBO — QuickBooks Desktop or Online and download. The file is written fresh, with a QuickBooks institution id rather than Quicken's. If QuickBooks still refuses it, set the institution explicitly — the search box on the bank code directory covers all 8,448 institutions in Intuit's own QuickBooks list, so you can paste in the right
FIDandINTU.BIDfor your bank.
Then import it the normal way: File → Utilities → Import → Web Connect Files in QuickBooks Desktop.
What survives the conversion, and what does not
Worth knowing before you rely on it, because no converter will tell you this on its sales page:
- Kept: the posting date, the amount and sign, and the full description. Descriptions longer than 32 characters continue into the memo field rather than being cut off, because the OFX name field is capped at 32 characters.
- Not carried into the QBO: the cheque number and the bank's separate memo line. Both are recovered from your QFX and both are visible in the preview, so if you need them, convert the same file a second time as Spreadsheet CSV — every column, exactly as read and keep that alongside.
- Transaction ids are rewritten. The
FITIDin the new file is computed from the transaction's own date, amount and description, not copied from the QFX. It is stable: converting the same statement twice gives the same ids, so QuickBooks will recognise a duplicate and skip it. If you actually want a second import of transactions QuickBooks has already seen — after deleting a bad import, say — tick "Re-importing a statement QuickBooks has already seen?" and every id changes. Why that is necessary at all.
Going the other way: QBO to QFX
This tool does not write .qfx files, and the reason is worth stating plainly rather than leaving you to discover it. Quicken validates INTU.BID against the institutions currently licensed for Quicken, and converters that fill it with whichever id the developer found to work produce files Quicken rejects — which is exactly why the Quicken community is full of threads about "Quicken is currently unable to verify the financial institution information" on converted files. We would rather not ship a one-click button whose output depends on a list we cannot see. If your goal is to get transactions into Quicken, a .QIF export is the honest route for the account types Quicken still accepts it for.
Is it safe to put a bank file into a web page?
A fair question, and the honest answer is to check rather than take our word for it. The conversion happens in your browser. Open your browser's developer tools, go to the Network tab, and convert a file: you will see no upload. The only request the page makes by itself is a small anonymous counter ping carrying counts and yes-or-no flags — how many rows, whether the columns were detected — and never a cell value, a header name or a file name. Block it and the converter still works.
Want to see it work before you use your own statement? Try the sample.
Sources
- How to get a QFX file from my bank into QuickBooks? — QuickBooks Community, including the Intuit moderator reply that .QBO files are required and QFX workarounds are unsupported.
- Re-import Web Connect file issue — QuickBooks Community, on the unique identifier that blocks a second import of the same file.