OFX vs QFX vs QBO vs QIF: Which File Format Does QuickBooks Accept?

QuickBooks Online accepts CSV, QBO, QFX, and OFX files for bank transaction uploads. It does not accept QIF. QBO is the format it was built around, so a Web Connect .qbo file is the cleanest import. QFX and OFX work too. QIF is the odd one out: it predates the whole OFX family, shares none of its structure, and every current Intuit product has stopped taking it for bank transactions. If you are holding a QIF, the file has to be converted before anything will read it.

That one paragraph resolves most of the confusion, but the four extensions look interchangeable and are not, which is why people rename files and watch the import fail anyway. This guide explains what each format actually is, why some of them are the same thing wearing different hats, and what to do with the file you have.

Last updated July 2026.

The four formats at a glance

What each format can actually carry

The at-a-glance table above answers "which one imports". This one answers "what is inside the file", which is what decides whether your categories, memos and running balance survive the trip.

Read the two rows that trip people up. QIF is the only one of the four that carries categories and splits, which is why a Quicken user feels like they are losing detail by converting. They are, and it is unavoidable: QuickBooks does not read categories out of a bank file in any format, because a bank feed never had them. QIF is also the only one with no FITID, so QuickBooks has nothing to deduplicate against. A good converter generates a stable FITID for every row from the date, amount and description, so re-importing the same file does not create a second copy of every transaction.

Why do QBO, QFX, and OFX look so similar?

Because underneath, they are the same document. OFX is the open standard for moving bank transactions between institutions and software. QFX and QBO are both OFX files that Intuit has stamped with an extra header identifying which of its products the file is meant for, and which financial institution it came from. Open all three in a text editor and you will see the same OFX elements: a signon block, an account block, and a run of STMTTRN transaction records.

The header is the difference that matters. A QBO file carries QuickBooks Web Connect headers; a QFX file carries Quicken's INTU.BID bank identifier. That header is what the receiving program checks first, and it is why the same transactions in the wrong wrapper get rejected by a program that could otherwise read every byte of the file.

Why is QIF different from the other three?

QIF is not an OFX file and never was. It predates the standard entirely. Instead of nested elements, it stores each field on its own line behind a single-letter tag: D for date, T for amount, P for payee, M for memo, with a caret closing each transaction. There is no header, no account block, no schema, and, importantly, no declaration of what date format the file uses. It is a different format that happens to hold the same kind of data. That is the whole reason QIF cannot be renamed into any of the others.

Can I just rename a QIF file to .QBO?

No. Renaming changes the extension and nothing else. QuickBooks opens the file, looks for the OFX header block that every Web Connect file starts with, finds tagged Quicken text instead, and refuses it. The same is true renaming QIF to QFX or OFX. To go from QIF to any of them, the transactions have to be parsed out of the QIF tags and rewritten as a genuine OFX document, which is what the QIF to QBO converter does.

Why does QuickBooks say my file has to be .ofx, .qfx, .qbo, or .csv?

Because QuickBooks checks the file extension before it tries to read the contents, and it is telling you which extensions it is willing to open. The check is on the name, not the data, which leads to two surprises. A file you renamed will clear the extension check and then fail at the parse step, because the bytes inside are still the old format. And a .qif can pass the name check in products that list it, yet still not import as bank transactions into QuickBooks Online. If you are hitting this with a file that already has an accepted extension, the usual cause is a renamed file, or an export that is really a PDF or a spreadsheet wearing the wrong suffix. Converting the source file properly is the fix. Note that the CSV in that list applies to QuickBooks Online only. QuickBooks Desktop will not take a bank CSV at all, so on Desktop the file has to be converted from CSV to a Web Connect .qbo before it will import.

Which format should I actually use for QuickBooks?

Use QBO if you can. It is the format QuickBooks was designed around, it lands directly in the banking review queue as a normal bank feed, and it preserves the transaction structure and the signs without you configuring anything. QFX and OFX are reasonable fallbacks that QuickBooks Online will accept. CSV is the last resort: it works, but QuickBooks Online enforces strict column rules on manual CSV uploads, and you lose the bank-feed behavior along with anything the CSV could not carry.

Which format should I use for Quicken?

QFX. Current Quicken takes QFX for downloading transactions into a checking, savings, or credit card account, and that is the format your bank hands you when you click Download to Quicken. QIF will not do it: Quicken's QIF import covers only asset, liability, and cash accounts, and is not available for checking, savings, credit card, or brokerage accounts. If what you have is a QIF, converting it to QFX is the step that makes it importable.

Does the file format affect my numbers?

The format itself does not, but the conversion between formats absolutely can. Two things go wrong most often. Splits: one charge divided across three categories is written as several lines in a QIF, and a parser that reads only the amount tag will double count or drop them. Dates: QIF carries no date-format declaration, so 03/04/2026 is March 4 or April 3 depending on who wrote the file, and Quicken's apostrophe years like D01/15'26 break naive parsers outright. A converter worth using resolves the date format across the whole file, sums splits into one signed amount, and reconciles the parsed total against the source before it exports anything.

What if my bank only gives me a PDF?

Then none of these four formats is in play yet, and the job is a different one: getting structured transactions out of a document. Convert the statement to a spreadsheet or a QBO file first, and then you are back on the path above. Once the transactions are in the books and reconciled, generating the P&L and balance sheet from that bookkeeping export is the next step most people need anyway.

Quick decision guide

If you have a QIF and need QuickBooks, convert to QBO. If you have a QIF and need Quicken, convert to QFX. If you have a QIF and need to review the data in Excel, convert to CSV or XLSX. If you have a QFX or OFX and need QuickBooks, upload it as is, because QuickBooks Online will take it. And if renaming a file is the plan, it is not a plan: the extension is not the format.

The converter at the top of this page takes a .qif and produces all of them from a single upload: a Web Connect .qbo, a QFX or OFX file, and Excel and CSV copies, with the totals reconciled against your source file before you download anything.

Is a QFX file the same as a QBO file?

Almost, but not interchangeably. Both are Web Connect files built on the same OFX standard, and both hold identical transaction data. The difference is the Intuit branding block in the header: a QFX names Quicken, a QBO names QuickBooks. Each program checks for its own and rejects the other, so a QFX will not import into QuickBooks no matter what you rename it.

What does a QBO file look like?

Open one in a text editor and you see plain text, not a spreadsheet. It starts with an OFX header block (OFXHEADER, DATA, VERSION), then an Intuit branding section with an INTU.BID number, then a STMTTRN tag for each transaction holding TRNTYPE, DTPOSTED, TRNAMT, FITID and NAME or MEMO. That readable structure is why a corrupt QBO can often be diagnosed by eye.

Can I open an OFX or QBO file to read it?

Yes. OFX, QFX and QBO are all text files, so Notepad, TextEdit or any code editor opens them and shows the transactions. You do not need a dedicated OFX file viewer. What you cannot do is edit one casually: change an amount and the totals in the closing balance tags no longer agree, and QuickBooks may reject the file or import numbers that will never reconcile.

What is a QBA file in QuickBooks?

A QBA file is a QuickBooks Accountant copy working file, and it has nothing to do with bank imports. It is the version an accountant edits while the client keeps working in the QBW company file. People land on it searching for QBO because the extensions look alike. If you are trying to import transactions, QBO is the file you want.

Which format holds up best for bookkeeping at volume?

QBO, by a clear margin, because of the FITID. When a bookkeeper imports twelve months of catch-up work across several accounts, the thing that breaks a close is duplicated transactions, and only the OFX family carries the ID QuickBooks needs to spot them. CSV has no ID either, and it adds column mapping and a file size cap on top. If you are running QIF exports from client to client every month, converting each one to QBO first is what keeps the register clean. The comparison of QIF to QBO converter software covers how the main tools differ on exactly that, and the Quicken file converter hub lists which Quicken export each one starts from.

Related reading: what a QIF file is, what a QBO file is, Direct Connect vs Web Connect, fixing a QuickBooks Web Connect import error, and importing QIF data into QuickBooks Online.