How to Convert a Bank Statement PDF to QIF
QIF is the oldest way to move transactions between finance programs, and it is still the only format some desktop software will accept. The problem is that banks stopped offering QIF downloads years ago, so a PDF statement is usually the only source left. This guide shows how to convert a bank statement PDF to QIF with a bank statement converter: what the file looks like, how to check it balances before you import it, and what to do when your software refuses it — because current Quicken, for one, does not accept QIF for ordinary bank accounts at all.
What a QIF file is — and why it still exists
QIF stands for Quicken Interchange Format. It dates from the early days of personal finance software, when programs needed a plain, human-readable way to hand transactions to each other. A QIF file is just text: one block per transaction, each line starting with a single-letter code for the date, the amount, or the payee, and a caret (^) marking the end of the record. There is no bank ID, no account number, and no enrolment of any kind — which is exactly why it still works. GnuCash, Moneydance, older versions of Quicken, and several long-lived accounting packages still read it, and it is often the only import format shared by tools that otherwise agree on nothing.
QIF survives for a practical reason: it is the format of last resort for old data. A bank that closed your account, a statement from five years ago, a year of history you need inside GnuCash — none of these come with a QFX download link. The PDF is the only copy, and QIF is the bridge from that PDF to the program. Newer formats carry more detail, but when the software on the other end only speaks QIF, there is no newer option to choose.
- Your software lists QIF as an import format and nothing newer fits — GnuCash and Moneydance are the usual cases.
- You are rebuilding history: months or years of statements that the bank no longer offers as downloads.
- You are moving data between two desktop programs and want a file you can open in a text editor and inspect by eye.
- You need one file per account, in plain text, with no bank connection and no account credentials involved.
What a QIF file looks like
Open a QIF file and there is nothing to decode. The first line names the account type, then each transaction is a short block of coded lines. Dates are written month first (MM/DD/YYYY), amounts are signed in a single column — money out as a negative number, money in as positive — and the payee is plain text, cut to 255 characters. A credit card file uses the same shape with a different header, !Type:CCard instead of !Type:Bank. Here is one transaction, line by line:
| Line | What it means | From the statement |
|---|---|---|
| !Type:Bank | Header: these are bank account transactions | Written once at the top of the file |
| D03/01/2026 | Transaction date, month first | The date column on the statement |
| T-54.20 | Amount: negative, so money out | The debit column, merged into one signed amount |
| PGrocery Mart | Payee | The description or narrative on the statement line |
| ^ | End of this transaction | Marks where the next record begins |
Two details in that table cause most of the trouble people have with QIF. The first is the date order: month first, always, with no setting to change it. A statement dated 03/04/2026 means 4 March, not 3 April, and a file converted from a day-first statement has to be reordered before import, not after. The second is the single signed amount. A statement with separate debit and credit columns has to merge them into one column, with withdrawals flipped negative. Get either wrong and the import still succeeds — with the wrong dates or signs, which is worse than failing loudly.
Before you convert: QIF, QFX or CSV?
QIF is the right file only when the software on the other end asks for it. Pick the format by the destination, not by habit, because each one carries different information and different traps. QFX (the Quicken Web Connect flavour of OFX) carries bank and account identifiers and is what current Quicken expects for checking, savings and credit card accounts. CSV is the format for spreadsheets and for accounting systems that want you to map columns by hand. Our comparison of OFX, QBO and QIF formats works through the three in full; the short version is below.
| Format | Best for | What to watch |
|---|---|---|
| QIF | GnuCash, Moneydance, older desktop software, moving old history | No bank or account ID; dates are month-first; current Quicken Windows will not take it for bank or card accounts |
| QFX / OFX | Current Quicken, QuickBooks imports, monthly imports of live accounts | Needs a bank ID; a paid export on this site |
| CSV | Excel, Google Sheets, accounting systems with column mapping | You map the columns yourself; signs and dates need shaping first — see our guide to converting a bank statement PDF to CSV |
The Quicken limit deserves spelling out, because it is the most common reason a QIF conversion feels like a failure. Quicken for Windows now accepts QIF import only for cash, asset and liability accounts — not for checking, savings or credit card accounts, where it recommends Web Connect (.QFX) files instead. Quicken for Mac covers QIF only for moving data from Banktivity or Moneydance into a new data file, and does not support incremental QIF imports. If your destination is a Quicken bank account, convert to QFX instead. If it is GnuCash or Moneydance, QIF is exactly right.
How to Convert a Bank Statement PDF to QIF, Step by Step
- Get the digital PDF from your bank. Download the statement from online banking rather than scanning a paper copy: a digital PDF carries a real text layer, and a scan has to be read by OCR, which misreads digits more often than words. Our guide to scanned vs digital bank statements shows how to tell which kind you have in ten seconds.
- Open the bank statement converter and drop in the PDF. One account and one statement period per file — never mix two accounts in one QIF, because the file has no way to say which transaction belongs to which account.
- Review every row against the PDF page before you download anything. Look for a missed line, a doubled line, and any amount that does not match the page. Do this now, while the PDF is still open beside the preview.
- Choose QIF as the output. The file is typed Bank for a checking or savings statement and CCard for a credit card statement, and dates are written month first. QIF is a paid export on this site (Starter and Pro); CSV and Excel are free on every plan.
- Download the .qif file and open it in a text editor for a ten-second look. The first line should read !Type:Bank or !Type:CCard, and each transaction should end with a caret (^). If the file opens as one long line or shows odd characters, do not import it — re-download it first.
- Back up the program you are importing into. QIF imports usually cannot be rolled back in one step, so copy your Quicken, GnuCash or Moneydance data file before the first import. This takes a minute and saves an afternoon.
- Import one statement first, then check the ending balance in your software against the closing balance printed on the PDF. Only when that one month agrees should you import the rest.
Three cases need a word of their own. If the PDF is a scan, confirm the converter read it with OCR and check the figures, not just the dates. If the PDF is password-protected, unlock it once for the conversion; the password opens the file and is never stored — see our guide to password-protected bank statement PDFs. And if you have a year of statements, convert them in batches and import month by month; our guide to converting multiple bank statements at once shows how to keep the batch organised so a mistake stays small.
Check the file before you import it
Here is the step most people skip, and the step that matters most. Once a QIF file is inside your finance program, finding one misread amount among hundreds of imported transactions is miserable. Check first, while the file is still just text. Every statement prints two numbers that let you test the work: the opening balance and the closing balance. The test is simple: opening balance, plus money in, minus money out, should equal the closing balance printed on the statement.
- Add the signed amounts in the QIF file and compare the total with the statement: opening balance plus the sum of the file should equal the closing balance.
- Scan the dates: every date should fall inside the statement period, and none should be a month and day swapped by the month-first format.
- Check the first and last transactions against the PDF — a missing first or last line is the most common gap.
- Count the records: the number of caret (^) marks is the number of transactions, and it should match the transaction count on the statement.
If the numbers refuse to agree, do not import and hope. Our guide on how to check a bank statement conversion explains the full checking routine, and our guide to why a bank statement does not balance lists the six usual causes — a split transaction, a wrapped description read as two lines, a fee the bank printed outside the table — and how to hunt each one down.
Import the QIF file into your software
GnuCash
In GnuCash, choose File, then Import, then Import QIF, and select the .qif file. The QIF importer walks you through matching the file to an account and mapping payees to GnuCash accounts; take the mapping screen slowly on the first import, because the choices it remembers will shape every later one. GnuCash also lets you set the date format during import — leave it on month-first (MM/DD/YYYY) to match the file. Import one month, open the account, and confirm the ending balance before importing the next.
Moneydance
In Moneydance, choose File, then Import, and pick the QIF file and the account the transactions belong to. Moneydance reads the !Type header to decide the account kind, so a card file typed CCard lands in a card account and a Bank file in a bank account. As with GnuCash, import one statement first and compare the ending balance with the paper statement before doing the rest.
Quicken — read the limits first
In Quicken for Windows the menu is File, then File Import, then QIF File. But before you use it, check what your version allows: current Quicken for Windows accepts QIF only for cash, asset and liability accounts, not for checking, savings or credit card accounts. For those, import a QFX file instead — our guide to importing bank statements into QuickBooks follows the same pattern of a balance-checked file first, even though the destination format differs. On Quicken for Mac, QIF exists only to move data from Banktivity or Moneydance into a new data file; it does not support importing more QIF into an existing file month by month.
When the import goes wrong
| Problem | Likely cause | What to do |
|---|---|---|
| Quicken refuses the file | Current Quicken Windows does not accept QIF for bank or card accounts | Convert the same statement to QFX instead; keep QIF for GnuCash or Moneydance |
| Dates land a month and day swapped | QIF dates are month-first; the statement was day-first | Reorder the dates to MM/DD/YYYY in the file and re-import; check the first few dates before importing the rest |
| Money out shows as money in | Signs were not flipped when debit and credit columns merged | Make withdrawals negative and deposits positive, then re-import — delete the bad import first |
| The ending balance is off by one row | A line was missed or read twice in the conversion | Compare the file total with the statement; find the missing or doubled row in the preview and re-convert |
| Payees are cut short or garbled | Description over 255 characters, or a wrapped line split in two | Shorten the payee in the file, or join the wrapped lines and re-convert |
| The same lines appear twice | The period overlaps a previous import | Start the next file the day after the last transaction already in the program |
| The file will not open in a text editor | A damaged download, or the wrong file was saved | Re-download the .qif file and check the first line reads !Type:Bank or !Type:CCard |
The pattern behind most of these is the same: the file was imported before it was checked. A QIF file is plain text, so every one of these problems can be seen — and fixed — in a text editor before the file touches your books. When in doubt, fix the file, delete the bad import, and import again. Re-importing a corrected file takes a minute; untangling hundreds of wrong lines inside your program takes far longer.
A short decision rule
If your software takes QIF and the history you need exists only as PDFs, convert the PDF to QIF, check it against the statement balance, and import one month at a time. If your destination is a current Quicken bank or card account, choose QFX instead — QIF will be refused, and no reformatting changes that. If the destination is a spreadsheet, a CSV is the better file: it keeps the running balance and the separate debit and credit columns QIF throws away. The format is a means, not the goal: the right file is the one that gets your books to add up with the least repair work.
Sources and further reading
- How do I import data into Quicken for Windows? — Quicken Support
- QIF Import — GnuCash Wiki
- Quicken Interchange Format — Wikipedia
Put it into practice
Convert a statement now and watch the balance check run on your own file. The first 10 pages each month are free, and exports are never cut short.
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) · OFX vs. QBO vs. QIF: Which Format Should You Download? · 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 · How to Import Bank Statements into Xero · How to Reconcile a Bank Statement in Excel After Converting PDF to CSV · How to Import Bank Statements into Sage from a PDF · How to Import Bank Statements into FreeAgent from a PDF · How to Import Bank Statements into Zoho Books from a PDF · How to Import Bank Statements into Wave from a PDF · How to Convert a Credit Card Statement to CSV (From a PDF)