Is converting a bank statement to QIF free?

Yes, the first five pages every month are free with no signup or card. Longer statements and ongoing use are covered by affordable credit packs.

What is the difference between QIF and OFX?

OFX is a structured XML/SGML format with unambiguous dates and a transaction ID that prevents duplicate imports. QIF is an older plain-text format with no date standard, no transaction IDs, and no balance assertions. Use OFX where your app supports it; use QIF for older tools that only read it.

Why are my QIF dates importing wrong?

QIF defines no date format, so a value like 03/04 is ambiguous between US month/day and international day/month. Set the date order on import to match the file, or in GnuCash choose the date format in the import dialog. Our converter lets you confirm the order before download.

Which apps can import a QIF file?

GnuCash and MoneyDance read QIF reliably. Older and many regional Quicken editions accept it too, though newer Quicken has restricted QIF import to certain account types and may require QFX or OFX instead.

Can I convert a scanned or photographed statement?

Not yet. Scanned and image-only PDFs have no text layer to extract into transaction records, which requires OCR. Text-based PDFs, what most banks issue, convert fully today.

Bank Statement to QIF Converter, Free Tool

Q: How do I convert a bank statement PDF to QIF?

Upload the PDF to the converter above, confirm the extracted transactions in the preview, choose QIF, confirm the date order matches your software, and download. The first five pages each month are free with no account.

A bank statement PDF becomes a QIF file by extracting every posted transaction and writing it in the Quicken Interchange Format, a plain-text layout where each record uses a single-letter code for the date (D), the amount (T), and the payee (P), with a caret on its own line ending each transaction. Upload the PDF above, confirm the preview, pick QIF, and download. The first five pages each month are free with no account, and the file imports into Quicken, GnuCash, and MoneyDance.

What QIF is: the Quicken Interchange Format, a legacy plain-text format Intuit retired from newer Quicken imports but that GnuCash and MoneyDance still read well.
What you get: a .qif file with a header line declaring the account type and one transaction record per row, each terminated by a caret.
Where it imports: Quicken (older versions and many regional editions), GnuCash, and MoneyDance accept QIF directly.
The gotcha: QIF carries no timezone or locale, so a date like 03/04 is ambiguous, getting the day/month order right is the most common import problem.
Cost and privacy: 5 pages/month free, then credit packs; the PDF is parsed in memory and not stored.

What the converter writes into the file

QIF is deliberately minimal. Each transaction is a short block of lines, one field per line, each prefixed by a single-letter code: D for the date, T for the signed amount, P for the payee or description, and an optional M for a memo, with a lone caret line closing the record. There is no account block and no per-transaction ID the way OFX has.

That minimalism is why QIF imports almost anywhere old enough to support it, and also why two details decide whether the import is clean. First, the date: QIF defines no date format, so the converter writes a consistent order and you confirm it matches your software's expectation. Second, the sign: the T amount is negative for money out and positive for money in, with no separate debit and credit columns. The converter normalizes split withdrawal/deposit columns into that single signed T field so nothing gets double-counted.

Because the format is plain text, a QIF file is also the easiest export to inspect by hand if an import goes sideways. Open it in any text editor and you can read the D, T, and P lines directly, spot a malformed date, or count the carets to confirm the transaction total matches the statement. That transparency is small consolation next to OFX's automatic de-duplication, but it does make QIF the simplest format to debug when an older app rejects an import without a useful error message.

Which apps still import QIF cleanly

QIF is a legacy format, so support varies by app and version. GnuCash and MoneyDance read it reliably; modern Quicken has narrowed QIF import to certain account types, while older and some regional Quicken editions still accept it broadly.

App	How it imports QIF	Watch out for
Quicken (older / regional editions)	File > Import > QIF File, then choose the account	Newer Quicken restricts QIF import to some account types; QFX/OFX may be required instead
GnuCash	File > Import > Import QIF	Prompts for the date format on import, set it to match the file
MoneyDance	File > Import, then select the .qif file	Pick the target account; QIF has no embedded account identifier
AceMoney, Moneydance plugins	Standard QIF import	Confirm the account type header matches (Bank vs Cash)

QIF or OFX, which one should you pick?

Pick OFX when your app supports it; pick QIF only when it doesn't. OFX is structured, de-duplicates on a transaction ID, and uses an unambiguous date format. QIF is older, simpler, and survives in tools that predate OFX or never adopted it.

Format	Best for	Main tradeoff
QIF	Older Quicken, GnuCash, MoneyDance, tools without OFX support	Ambiguous dates, no de-duplication, no balance assertions
OFX	Xero, Sage, GnuCash, YNAB, MoneyDance, most current apps	Stricter spec; some banks need an institution identifier
QBO	QuickBooks Desktop and Online	QuickBooks only; uses Intuit's INTU.BID tag
CSV	Spreadsheets and custom analysis	No structure beyond columns; the destination maps fields

If your software accepts OFX, the OFX converter is the more robust choice because it de-duplicates on re-import and avoids the date ambiguity. For QuickBooks, use QBO. For analysis in a sheet, CSV is simplest. Reach for QIF when one of those older tools is the only place the data needs to land.

How a single QIF record is built, line by line

A QIF transaction is a handful of single-letter lines, and knowing them helps when an import looks off. The converter writes D for the date, T for the signed amount, and P for the payee, then closes the record with a caret on its own line; everything between two carets is one transaction.

Code	Field	What the converter puts there
!Type:Bank	Header (once at the top)	Declares the file as bank-account transactions
D	Date	The posting date in a single consistent order you confirm before download
T	Amount	One signed figure; negative for money out, positive for money in
P	Payee	The transaction description, including reference codes where present
M	Memo (optional)	Any extra detail that does not fit the payee line
^	End of record	A lone caret marking where one transaction stops and the next begins

Notably absent are a category line and a cleared-status flag. The converter leaves the L category field empty rather than guessing, because a wrong auto-category is harder to fix after import than a blank one you assign in your own software. There is also no N check-number field unless the statement clearly prints one, which keeps spurious reference numbers out of the payee column.

The QIF details that decide a clean import

No date standard. Unlike OFX's fixed YYYYMMDD, QIF never defined a date format. A US statement and a UK statement both showing "03/04" mean different days. The converter writes a consistent order and surfaces the choice so 03/04 doesn't import as April 3 when you meant March 4.
No balance assertions. QIF has no field that records the running balance as a checkpoint, so the importer cannot verify it landed on the right ending balance. Reconcile manually after import, or use OFX where the closing balance can be carried.
No transaction IDs. QIF carries no FITID, so importing the same file twice creates duplicates. Import each statement once, or switch to OFX where the transaction ID makes re-imports idempotent.
Account-type header matters. The file opens with a header like !Type:Bank. If it is wrong, some apps file the transactions under the wrong account category. The converter sets it to a bank account by default.

What we see across 500+ bank layouts

From parsing statements across hundreds of bank templates, the date-order problem is the single biggest source of QIF import errors, far more than any structural issue:

Regional date order is the top failure mode. US statements print month/day and most of the rest of the world prints day/month. Because QIF carries no locale, a converter that copies the printed string verbatim hands the importer an ambiguous value. We parse to a real date first, then write a single consistent order you can confirm.
Split debit/credit columns. Many banks print separate withdrawal and deposit columns; we merge them into one signed T amount so the QIF doesn't double-count.
Scanned statements. A photographed or scanned PDF has no text layer to read into QIF records. Those need OCR, which is on the roadmap but not yet supported, see the note below.

The fastest path from PDF to QIF

Drop the PDF on the converter above, scan the preview, choose QIF, confirm the date order matches your software, and download. Import it through your app's File or Import menu and pick the destination account, since QIF carries none. Import each statement only once to avoid duplicates, because QIF has no transaction ID to de-duplicate on. If your tool can read OFX instead, that format is more forgiving; QIF is the right call when an older app leaves you no other option. For ongoing work, credit packs keep the per-page cost below desktop converters.

Two habits prevent almost every QIF headache. Set the date order once and check the first few rows of the preview against the printed statement, if the 5th of the month and the 5th month look swapped, fix it before importing rather than after. And keep a copy of the original PDF, because without balance assertions the QIF cannot prove it imported completely; the PDF is your reference if a transaction goes missing during the import and you need to reconcile by hand. Treat QIF as the compatibility option it is: reliable in the older tools that still depend on it, but worth trading for OFX the moment your software supports the newer format.

Convert a Bank Statement PDF to QIF

Drop your bank statement PDF here