QIF is the legacy interchange format older software and Quicken for Windows read, and it starts with clean transaction data a PDF will not give you. BankXLSX reads your statement and writes every line into date, description, and amount columns as CSV or Excel. Quicken for Mac imports that CSV directly, and for Quicken for Windows, which wants QIF or QFX, you run the same CSV through a dedicated QIF utility. No retyping, no jammed columns. Start free, no credit card.
Last updated July 2026
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
To convert a bank statement to QIF, upload the PDF to BankXLSX and it reads every transaction into a structured table with date, description, and amount columns, then export it as CSV. BankXLSX does not emit a native .qif file, and it does not need to: it produces the clean, accurate transaction data a QIF import is built from, which is the step a PDF blocks. Quicken for Mac imports that CSV directly. For Quicken for Windows, which needs QIF or QFX rather than a transaction CSV, you pass the same CSV through a dedicated QIF or QFX utility to produce the file it accepts. Either way the converter removes the retyping, and Quicken cannot read a PDF at all.
Quicken imports transactions through QFX (Web Connect) and QIF, plus a transaction CSV on Quicken for Mac. A PDF is none of those, and bank feeds do not reach everything, so the data has to be reshaped first. Here is where it usually breaks.
Quicken imports QFX and QIF, and a CSV on the Mac version. A PDF bank statement has nowhere to go until you convert it into structured rows first.
Direct Connect and Web Connect cover recent activity for supported banks, but fail for closed accounts, old periods, and many smaller institutions, so you fall back to the PDF.
QIF uses tagged lines (D for date, T for amount, P for payee, M for memo) under a !Type header. One malformed record and the import skips transactions or posts them wrong.
Pasting a PDF table into a sheet jams date, payee, and amount into one cell, and both QIF and Quicken CSV need them cleanly separated before import.
Amounts copied from a PDF carry dollar signs and commas as text, but the import needs plain signed numbers (money out negative, money in positive) or the register will not balance.
Typing hundreds of lines into a template by hand is slow, and one mistyped amount throws off the Quicken reconciliation for hours.
Upload the PDF and the converter reads the transaction table directly, then writes clean, structured rows you import into Quicken or turn into a QIF file.
Every statement lands as date, description, debit, credit, and running balance, the exact fields a QIF record or a Quicken CSV needs.
Download CSV or XLSX from the same upload. Quicken for Mac imports the CSV directly; on Quicken for Windows you convert it to QIF or QFX with a utility first.
The Mint-layout CSV that Quicken for Mac reads can carry a category column, so your coding lands with the transactions instead of starting from a blank register.
OCR pulls transactions from scanned PDFs and phone photos in JPG, PNG, HEIC, and TIFF, not just digital PDFs.
Upload a full statement or a year of them and the converter stitches every page into one continuous transaction list.
Templates tuned to how Chase, Bank of America, Wells Fargo, and dozens of other US banks print their statements.
No software to install and no credit card to start.
Drag your PDF, scanned statement, or photo into the box above. Password-protected PDFs work too.
Tip: Multi-page and multi-month files are fine.
The AI reads every transaction into clean date, description, and amount columns you can export.
Tip: Most statements finish in under a minute.
On Quicken for Mac, import the CSV into the account directly. On Quicken for Windows, convert the CSV to QIF or QFX with a dedicated utility first, then import that.
Tip: Create the account in Quicken first so lines post correctly.
Long-time Quicken users, rental owners, and bookkeepers all hit the same wall: the account they need is a PDF, not a feed.
Tracking a property account in Quicken when the bank feed drops or the account is at a small institution that never connected.
Bringing years of history into Quicken from statements the online feed will not backfill.
Catching up a client on Quicken from a stack of monthly PDFs instead of a live connection.
Keeping a business account in Quicken clean for tax time without retyping every transaction.
BankXLSX exports clean transaction data as CSV and Excel, not a native .qif file. That is deliberate. Quicken for Mac imports the CSV directly, so on a Mac you rarely need QIF at all. Quicken for Windows does need a QIF or QFX file, and since BankXLSX does not write those formats, you run the converted CSV through a dedicated QIF utility, which takes a couple of minutes because the hard part, getting accurate date, payee, and amount data out of the PDF, is already done. What the converter removes is the retyping and the jammed columns, which is the actual blocker.
QIF (Quicken Interchange Format) is a plain-text format that Intuit created for moving transactions between financial programs. Each transaction is a set of tagged lines under a type header: D for the date, T for the amount, P for the payee, M for a memo, and a caret to end the record. It is old and loosely specified, which is why imports fail on small formatting differences, and why Quicken itself has steered users toward QFX and CSV. It still shows up because a lot of legacy software and some banks only speak QIF.
The right target depends on your Quicken version. The table lays out the trade-offs.
| Format | Best for | Watch out for |
|---|---|---|
| CSV | Quicken for Mac (2015+), which imports a Mint-layout transaction CSV directly | Quicken for Windows CSV import only updates security prices, not transactions |
| QFX | Quicken for Windows register imports (Web Connect) that skip duplicates | Quicken wants the Intuit-branded QFX flavor; BankXLSX does not write QFX, so use a utility |
| QIF | Legacy software and Quicken for Windows; can carry categories and tags | Quicken for Windows limits QIF import to cash, asset, and liability accounts, not bank accounts |
The practical read: on Quicken for Mac, import the CSV directly. On Quicken for Windows, take the same CSV through a dedicated QIF or QFX utility, because Windows will not import a transaction CSV and BankXLSX does not write QFX or QIF itself. Reach for QIF specifically when the destination requires it, keeping in mind Quicken for Windows limits QIF import to cash, asset, and liability accounts rather than bank accounts.
Quicken for Mac reads a CSV in the Mint layout, using the transaction date, a payee, and a signed amount with MM/DD/YYYY dates and plain numbers, no dollar signs or commas, money out negative and money in positive. BankXLSX exports in that clean shape, so on a Mac the file is close to import-ready. On Quicken for Windows you convert that same CSV to QIF or QFX with a utility first, since Windows does not import a transaction CSV. For a step-by-step walkthrough, see how to import bank statements into Quicken, and the Quicken bank statement converter covers the whole workflow. Importing into QuickBooks instead? Use the QuickBooks bank statement converter or the desktop IIF converter.
To be precise: BankXLSX converts the statement and keeps the numbers exact. It gives you CSV and Excel, not a finished .qif or .qfx, and it does not decide which account a line belongs to or how to categorize it. Those are yours. What it removes is the part with no judgment in it, which is turning a stack of PDF pages into accurate rows ready for a Quicken import.
No. BankXLSX exports clean transaction data as CSV and Excel, not a native .qif file. Quicken for Mac imports the CSV directly, so on a Mac QIF is rarely needed. Quicken for Windows needs a QIF or QFX file, which you make by running the converted CSV through a dedicated utility. Either way the accurate date, payee, and amount data is already extracted from the PDF, which is the step that actually blocks the import.
Upload the PDF to BankXLSX, which reads every transaction into date, description, and amount columns, and export the CSV. On Quicken for Mac you import that CSV directly. On Quicken for Windows you convert the CSV to a QIF or QFX file with a dedicated utility, since BankXLSX does not write those formats. There is no retyping, and the converter handles scanned statements and password-protected PDFs as well as digital ones.
Not as a PDF. Quicken imports QFX (Web Connect) and QIF, plus a transaction CSV on the Mac version, but it cannot read a PDF statement. For accounts the bank feed will not reach, such as closed accounts or older periods, you convert the PDF to a clean CSV first, then import that on Mac or turn it into QIF or QFX for Windows.
It depends on your version. Quicken for Mac imports a Mint-layout transaction CSV directly, so use the CSV there. Quicken for Windows will not import a transaction CSV (its CSV import only updates security prices), so on Windows you need QIF or QFX. Keep in mind Quicken for Windows also limits QIF import to cash, asset, and liability accounts rather than bank accounts.
QIF (Quicken Interchange Format) is a plain-text format Intuit created for moving transactions between financial programs. Each transaction is a set of tagged lines under a type header, using D for date, T for amount, P for payee, and M for memo. It is loosely specified, which is why imports fail on small formatting differences, and why newer software prefers QFX and CSV.
Yes. Every converted row carries the running balance printed on the statement, alongside the date, description, and amount. That makes it easy to confirm nothing was dropped in conversion before you import, even though the balance column itself is not part of a QIF or Quicken transaction import.
The full workflow for converting statements for Quicken.
Export OFX for other accounting software.
The CSV Quicken for Mac imports directly.
Importing into QuickBooks instead of Quicken.
From the same family of tools
Get started converting bank statements to spreadsheets.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
