Guides

OFX vs. QBO vs. QIF: Which Format Should You Download?

Your statement is converted and checked. Now the download page offers a row of formats — CSV, Excel, QBO, OFX, QIF — and the choice matters more than it looks. Pick the format your destination program was built to eat, and the import takes a minute. Pick another, and you inherit mapping screens, flipped signs and duplicate rows. This guide explains the three accounting formats in plain words and ends with a simple rule for choosing.

The idea they all share

All three formats carry the same cargo: a list of transactions, each with a date, a description, an amount, and — in the better formats — a unique ID. They differ in who defined them, which programs read them, and how much safety the unique ID buys you. CSV and Excel are covered by their own guides (CSV, Excel); this page is about the three formats built for accounting software.

OFX: the open standard

OFX stands for Open Financial Exchange. It is a published standard for moving financial data between banks and software, maintained openly — the full specification is a public document (linked in our sources). An OFX file is structured text: an account block, then a transaction list, each transaction carrying its date, amount, name and a unique ID (the FITID) assigned so importing programs can recognise the same transaction twice.

Who eats OFX: Quicken (its Web Connect files, .qfx, are OFX in Quicken clothing), Xero, many bookkeeping and personal-finance tools, and most bank-feed importers. If a program says 'import bank transactions' and does not name a special format, it usually means OFX. OFX is the safest general choice after CSV: open, documented, and duplicate-aware thanks to those unique IDs.

QBO: QuickBooks' own Web Connect file

A .qbo file is a Web Connect file for Intuit QuickBooks. Under the skin it is built on the same OFX family tree, tuned for QuickBooks: transactions arrive with unique IDs, account details are embedded, and QuickBooks imports it with no column mapping at all. This is the file to choose when the destination is QuickBooks — Desktop or Online. Our step-by-step for that whole path is the guide to importing statements into QuickBooks, including the matching step where duplicates are born or killed.

Two traps to know. First, a .qbo file is not a renamed CSV: changing a file extension changes nothing inside, and QuickBooks will reject a fake. Second, very large Web Connect files can hit import size limits; convert month by month (which is good practice anyway) and the problem never appears.

QIF: the old-timer

QIF — Quicken Interchange Format — is the elder of the three: a simple text format from the early days of personal finance software. Each transaction is a few short lines: a date line starting with D, an amount line starting with T, a payee line starting with P, and an exclamation mark to end the record. It is easy to read and easy to write, which kept it alive for decades.

But age shows. QIF carries no unique transaction IDs, so importing the same file twice creates true duplicates that software cannot reliably detect. And modern Quicken itself has stepped back from it: Quicken's own help (linked below) says QIF import is now limited to a small set of account types — asset, liability and cash accounts among them — and is not the route for checking, savings or credit card accounts. Choose QIF when an older program or a niche tool asks for it by name, or when a support page tells you to. Otherwise, it is the third choice, kept for compatibility.

The choosing rule

Ask one question: which program will eat this file?

• QuickBooks → QBO. No mapping, unique IDs, cleanest import.
• Quicken → OFX (delivered as Web Connect .qfx in Quicken's world; our OFX download is the same family).
• Xero and most other accounting tools → OFX.
• An old or niche program that names QIF → QIF, and import each file once, carefully.
• A human with a spreadsheet → CSV or Excel, not any of these three.
• You do not know yet → OFX. It is the most widely accepted of the three, and its IDs protect you if the file is imported twice.

On StatementConverter, QBO, OFX and QIF are part of the Starter and Pro plans, alongside the merged-batch download; CSV and Excel are free on every plan, including Free. Plans and page limits are counted by pages converted, never by downloads — so you can download the same checked statement in two formats without paying twice. That makes the choosing rule cheap to apply: when in doubt, take the format your program loves and a CSV as a spare.

One last habit, whichever you pick

The format decides how the import behaves. It cannot decide whether the rows were right. That was settled earlier, by the balance check — the rows reproducing the statement's closing balance before any file was made. A QBO file built from unreconciled rows imports its errors beautifully, with unique IDs. So keep the order this site is built around: convert, reconcile, then choose the format. If a statement will not reconcile, our guide on why statements do not balance is the place to fix it — before QuickBooks, Xero or Quicken ever see the file.

A peek inside the files

None of these formats is magic. Open an OFX or QBO file in a text editor and you will see tagged lines a human can read. Each transaction sits in a block (the tag is STMTTRN) and carries lines such as DTPOSTED for the date, TRNAMT for the amount, FITID for the unique ID, and NAME or MEMO for the text. A QIF file is even plainer: a few short lines per transaction, starting with letters — D for the date, T for the amount, P for the payee — and an exclamation mark to close each record.

Knowing this helps in one practical way: if an import ever behaves strangely, opening the file and reading one block tells you whether the data left the converter correctly. Nine times out of ten the rows are fine and the issue is a setting in the importing program — a date format, an account choice — which is much easier to fix once you know the file is honest.

How the three formats got here

QIF came first, in the early years of home finance software, when a simple text format was enough. OFX arrived in the late 1990s as a joint effort by Microsoft, Intuit and CheckFree — the banks and software makers wanted one documented way to exchange statements, and OFX became it; its specification is still published openly, and our sources link to it. QBO files came with QuickBooks' Web Connect feature: technically a dialect of the same OFX family, branded and tuned for one program. That family tree explains the table above — OFX and QBO carry IDs and structure because they were designed for machine import, while QIF carries the simplicity of an older, more trusting era.

What the unique ID really does

The FITID deserves one more moment, because it is the difference between a safe import and a risky one. When a bank (or our converter) writes a transaction, it stamps it with an ID that will be identical if the same statement is converted again. When the importing program meets that ID a second time, it knows: this row is already here. That is why re-importing an OFX or QBO file is mostly harmless, and why re-importing a QIF or CSV file demands care — without IDs, the program cannot tell a duplicate from a genuinely repeated payment, like two identical rent charges in one month.

If you ever must use an ID-less format, import each file exactly once, tick the files off a list as you go, and reconcile straight after each import. The reconciliation is your duplicate detector: a doubled month announces itself as a difference exactly equal to a real transaction.

What about QFX — and other cousins?

Quicken users will meet the .qfx extension: a Web Connect file. QFX is OFX with Quicken's partner details baked in, and Quicken accepts statement data through it. The practical point for you: OFX and QFX are the same family and carry the same transactions and IDs; if your program asks for a Web Connect file, you are in OFX territory and the conversion's OFX download is the right starting point. A handful of other extensions float around older software — all of them are dialects of these same ideas, and the choosing rule still applies: give the program the format it names in its own import menu.

Cards and investments ride the same rails

These formats were designed for more than checking accounts. OFX describes credit card statements and even investment accounts in the same framework, which is why a converted card statement can travel as OFX or QBO into the same tools as a bank statement — uploaded to the card account, not the bank account. If a statement is part bank, part card (combined documents exist), split it first: one file per account is the rule that keeps every import sane.

Format questions we hear

• 'My tool imports both OFX and CSV. Which is safer?' OFX — the unique IDs guard you against double imports, and no column mapping means no flipped signs.
• 'Can I convert the file later if I pick wrong?' Yes. The checked statement stays the source; download another format from the same conversion. Formats are packaging, not decisions.
• 'Does the format change the numbers?' Never. Date, text and amount are identical across CSV, Excel, QBO, OFX and QIF from the same conversion. Only the wrapping differs.
• 'Why does my old program only list QIF?' Because it predates the OFX era. Use QIF, import once, and reconcile immediately — the routine from our checking guide becomes your duplicate detector.

Dates and amounts inside the formats

One technical corner is worth a look, because it explains most cross-border format pain. OFX writes dates in a fixed machine order — year, month, day, then time — so 2026-04-03 means the same thing in every country, and amounts are signed decimals with a point, never a comma. QIF, born in a single country, lets dates follow local habit — which is how 03/04 becomes March in one program and April in another when a file crosses the Atlantic. If you must use QIF internationally, open the importing program's date setting before the file, not after, and verify the first and last rows against the statement once imported. OFX and QBO users can skip this worry entirely: the format leaves nothing to interpret.

Signs follow the same pattern. In OFX-family files, money out is negative and money in is positive, always, inside the file — programs display it however they like, but the data never flips. That consistency is a quiet part of why imports from these formats reconcile first time so much more often than hand-mapped spreadsheets.

If this guide leaves you with one sentence, let it be this: formats are envelopes, and the letter inside is your checked data. Choose the envelope your program opens most happily — QBO for QuickBooks, OFX for almost everything else, QIF only when an old friend insists — and spend the attention you saved on the part that cannot be automated: knowing the rows were right before they were wrapped. An elegant import of wrong numbers is still wrong numbers, arriving in style.

Choose once, choose by destination, and the format question never needs to trouble you again.

Sources and further reading

• Open Financial Exchange (OFX) specification — docs.ofx.org
• QIF data import: scope and limits — Quicken Support
• Import bank transactions using Web Connect files — Intuit QuickBooks Support

More guides

How to Convert a Bank Statement PDF to CSV · How to Convert a Bank Statement PDF to Excel · How to Import Bank Statements into QuickBooks (QBO Files) · Why a Converted Bank Statement Does Not Balance — and How to Fix It · How to Check a Converted Bank Statement Is Correct · Scanned vs. Digital Bank Statements: Why One Converts and the Other Does Not · How to Convert a Password-Protected Bank Statement PDF · How to Convert Many Bank Statements at Once (and Merge Them Cleanly) · Is It Safe to Convert Bank Statements Online? A Privacy Checklist