OFX & QFX Converter: From PDF Statement to Quicken

Search for an ofx converter and you'll find dozens of tools built for one narrow job: turning a bank statement into the .ofx or .qfx file that older accounting software still insists on. If that sounds like an odd thing to need in 2026, you're not alone — most people assume file formats from the 1990s died out long ago. They didn't. Quicken still requires a qfx converter for anything that isn't a direct bank feed, and plenty of legacy bookkeeping tools quietly rely on the same standard. Here's what OFX and QFX actually are, why they refuse to disappear, and how to produce one from a plain PDF statement.

What is an OFX file, exactly?

Open Financial Exchange — OFX for short — is a file format built for one job: moving transaction data between a bank and personal finance or accounting software without anyone re-typing it by hand. Microsoft, Intuit and CheckFree agreed the specification in January 1997, and it has quietly been the plumbing behind bank downloads ever since. An OFX file isn't a picture of a statement the way a PDF is — it's structured data: account number, statement period, opening and closing balances, and every transaction with its date, amount and description, laid out so any OFX-compliant application can read it without guessing. The Open Financial Exchange standard is one of the oldest open banking data formats still in daily use, nearly three decades after it was announced.

QFX: Intuit's Quicken-only variant

QFX looks like a small variation on OFX, and technically it is — but the difference matters enormously if Quicken is the software you're feeding. A QFX file follows the same OFX structure with one addition: an INTU.BID tag identifying the financial institution to Intuit. Quicken checks for that tag on import, and if it's missing — because the file is a plain .ofx rather than a .qfx — Quicken simply won't accept it. Quicken's own documentation on importing files from a bank confirms as much: Quicken imports the Quicken Transfer Format (.QFX), not generic OFX. So while every QFX file is a kind of OFX file underneath, Quicken users specifically need the QFX variant, and a general ofx converter that skips Intuit's identifier will produce a file that fails a Quicken import.

Why formats built in the 1990s still matter

It would be easy to assume these formats died with dial-up modems. They didn't, for two practical reasons. First, Quicken is still actively used — by people who've tracked decades of spending in one file and see no reason to migrate — and Quicken import remains QFX-only. Second, plenty of older accounting software never moved past OFX either: certain desktop bookkeeping tools, older Sage installs, and various regional banking add-ons still expect it as their only structured import option, alongside newer formats like CSV and QBO. Meanwhile, banks have been quietly removing the direct-download button. A bank that offered one-click OFX downloads five years ago may now only offer a PDF statement, or a CSV missing half the fields Quicken expects — which pushes the conversion step back onto the customer.

Martin, a retired quantity surveyor, has entered every transaction into Quicken since 1998 — decades of category history he has no intention of abandoning. When his building society migrated to a new online banking platform last winter, the OFX download link vanished from the statements page; all that remained was a PDF. He didn't need new software or a new habit, just one converted file: a PDF turned into a QFX file Quicken would actually import, INTU.BID tag and all. That situation is more common than it sounds — anyone who's used Quicken for personal or small-business bookkeeping for more than a few years has usually built up records they don't want to lose by switching platforms.

"Most people don't actually want an OFX file — they want their fifteen years of Quicken history to keep working without a gap." — Priya Shah, Head of Product at Ledgerary

How to convert a bank statement PDF into OFX or QFX

When a bank stops offering a direct OFX or QFX download, or never offered one to begin with, the statement is usually still available as a PDF — and that PDF contains everything a converter needs, provided it can extract every field accurately.

1. Get a complete transaction list out of the PDF first, rather than hand-typing figures into Quicken's register. Every row needs a date, description, amount and running balance — Quicken can't reconcile against a file that's missing rows.
2. Check the totals before converting anything. Opening balance, plus total money in, minus total money out, should equal the closing balance printed on the statement itself. A converter that runs this check catches a misread line before it reaches Quicken, not after.
3. Convert into the format your software actually needs — QFX for Quicken, with the INTU.BID identifier included, OFX for other OFX-compliant tools, or CSV if you're importing into Excel, Xero or Sage instead.
4. Import and review. Quicken will try to auto-match incoming transactions against anything already in the register; check anything it flags as uncertain before accepting the batch.

Ledgerary handles the extraction and verification stage of that process. Upload a statement PDF and it returns a clean transaction list — balance-checked against the statement's own totals — exportable as Excel, CSV, JSON, or a ready-made QuickBooks, Xero or Sage file. That CSV is exactly the input a csv to ofx conversion step needs, since most CSV-to-OFX tools require the same clean date, description and amount structure Quicken's import expects. Files are deleted after processing, and the whole extraction is callable through a single-key API or MCP server if you'd rather script the conversion than click through it by hand. If QuickBooks rather than Quicken is the destination, importing a bank statement into QuickBooks walks through the equivalent QBO-flavoured route, and reconciling the result against your books is worth doing regardless of which format you land on.

OFX vs QFX vs CSV vs QBO: picking the right format

Once you know your software's required format, the choice is straightforward — but it's easy to convert into the wrong one and only find out when the import fails silently. Here's how the four formats compare in practice.

CSV is the safest default when you're not sure what your software expects, or when you're comparing several tools — it's the format the best QBO converter tools tend to fall back on when a bank doesn't offer a native export. But if Quicken import is genuinely the goal, only QFX will do; feeding it a plain OFX file, or a CSV renamed with a .qfx extension, produces an import that either fails outright or silently drops the fields Quicken needs to auto-match transactions.

Frequently asked questions

What is an OFX file?

An OFX file is a structured data file — not a PDF or scanned image — built on the Open Financial Exchange standard for exchanging transaction data between banks and finance software. It holds account details, statement dates, balances and every transaction, formatted so compliant software can import it directly.

What's the difference between QFX and OFX?

QFX is Intuit's own variant of OFX, built specifically for Quicken. It follows the same underlying structure but adds an INTU.BID tag identifying the bank to Intuit. Quicken only accepts QFX files for import; it won't open a plain .ofx file, even though the two formats are closely related.

How do I convert a bank statement to OFX?

Start from a clean, verified transaction list rather than the PDF itself. Extract every date, description, amount and balance, check the totals against the statement's own opening and closing balance, then run that data through an OFX or QFX converter. Converting the PDF text directly, without that verification step, is how rows go missing.

Can I convert a CSV to OFX?

Yes — CSV to OFX conversion is one of the most common routes, since most banks still offer CSV even after dropping direct OFX downloads. The CSV needs consistent date formatting and a single signed amount column (or separate debit/credit columns) for a converter to map it accurately into OFX's transaction structure.