Turn a PDF bank statement into a file QuickBooks Desktop can read. Upload your statement and BankXLSX extracts every transaction into a clean spreadsheet you map to the IIF or CSV layout QuickBooks Desktop imports, with dates, descriptions, and amounts in the right columns. Start free, no credit card.
Last updated June 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 IIF, upload the PDF to BankXLSX and it reads every transaction into a structured table with date, description, and amount columns. Export that as CSV, then map the columns to an IIF transaction layout (the tab-delimited !TRNS / !SPL records QuickBooks Desktop reads) or import the CSV directly through your third-party import tool. QuickBooks Desktop cannot read a PDF, so this conversion is the step that turns months of statement pages into rows you can post against the right accounts in minutes.
QuickBooks Desktop imports lists and transactions through IIF, a tab-delimited text format, plus QBO and CSV through add-ons. A PDF is none of those, so the data has to be reshaped first. Here is what usually goes wrong.
The File, Utilities, Import menu only accepts IIF (and Web Connect QBO). A PDF bank statement has nowhere to go until you convert it into one of those formats.
Direct Connect and Web Connect feeds cover recent activity for supported banks, but fail for closed accounts, old periods, and many smaller institutions, so you fall back to the PDF.
IIF uses a strict !TRNS, !SPL, !ENDTRNS structure with tab separators. One stray comma or a missing column and QuickBooks rejects the whole file or posts to the wrong account.
Pasting a PDF table into a sheet jams date, payee, and amount into one cell, and IIF needs them cleanly separated before it will import.
Amounts copied from a PDF carry dollar signs and commas as text, but IIF needs plain signed numbers (debits negative, deposits positive) or the totals will not balance.
Typing hundreds of lines into a template by hand is slow, and a single mistyped amount throws off the QuickBooks reconciliation for hours.
Upload the PDF and the converter reads the transaction table directly, then writes clean, structured rows you turn into an IIF or CSV file QuickBooks Desktop accepts.
Every statement lands as date, description, debit, credit, and balance, the exact fields an IIF !TRNS line needs.
Download CSV or XLSX from the same upload, ready to map to an IIF template or feed a CSV import tool.
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.
256-bit encryption in transit and you can delete your uploaded files whenever you want.
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.
Save the CSV, drop the columns into an IIF !TRNS template, then import through File, Utilities, Import, IIF Files.
Tip: Create the bank account in QuickBooks first so lines post correctly.
Millions of US businesses still run QuickBooks Desktop. The clean export fits the way those teams catch up books and reconcile.
Catch up months of client transactions in Desktop without retyping a single line from the PDF.
Post historical statements for closed or unsupported accounts that no longer have a live bank feed.
Get a year of statements into QuickBooks Desktop for reconciliation and tax prep.
Move legacy statement history into a Desktop company file before a year-end close or a migration.
IIF stands for Intuit Interchange Format. It is a plain text file with tab separated columns that QuickBooks Desktop reads through File, Utilities, Import, IIF Files. Transactions live in a three line block: a !TRNS line for the main entry, one or more !SPL lines for the offsetting splits, and an !ENDTRNS line to close it. Each !TRNS line carries a transaction type, date, the bank account name, a name or payee, and a signed amount. Because the format is unforgiving about tabs and column order, the reliable path is to get clean, correctly signed rows first, then drop them into a working template.
Start from the converter output, which already separates date, description, debit, credit, and balance. For an IIF transaction line you need the date in MM/DD/YYYY, a single signed amount (money out negative, money in positive), the bank account name exactly as it appears in QuickBooks, and a payee. Here is how the converted columns line up with what an IIF line expects.
| Converted column | IIF field | Notes |
|---|---|---|
| Date | DATE | MM/DD/YYYY format |
| Description | NAME / MEMO | Use as payee and memo text |
| Debit / Credit | AMOUNT | One signed number: debits negative, deposits positive |
| (your bank) | ACCNT | Must match the QuickBooks account name exactly |
| TRNSTYPE | TRNSTYPE | Usually CHECK, DEPOSIT, or GENERAL JOURNAL |
If you would rather skip hand building the IIF and your import tool reads CSV, the PDF bank statement to CSV converter gives you the same rows in a file most QuickBooks Desktop importers accept directly.
Both land in QuickBooks Desktop, but they behave differently. IIF imports a list of transactions you control line by line, which is ideal for historical statements, closed accounts, and bulk catch-up work. QBO (Web Connect) brings transactions into the Bank Feeds center for matching, which suits ongoing reconciliation for a connected account. Pick by the job.
| Use this when you want to | IIF | QBO (Web Connect) |
|---|---|---|
| Post historical or closed-account statements | Best choice | Often blocked |
| Bulk import many transactions at once | Best choice | Works |
| Match against the bank feed for review | No | Best choice |
| Control account and split mapping by hand | Best choice | Limited |
Either way, create the bank account in QuickBooks before you import. If a transaction names an account that does not exist, QuickBooks silently creates a new one, which is the most common reason an import looks wrong afterward.
IIF is a QuickBooks Desktop format. If you run QuickBooks Online, you import a three column CSV (date, description, amount) under Transactions, Bank transactions, Upload, not an IIF file. Our walkthrough on how to convert bank statements to QuickBooks covers the Online CSV path, and you can also push a statement straight to a QuickBooks file with a dedicated bank statement to QuickBooks converter.
Upload the PDF statement to BankXLSX, which reads every transaction into clean date, description, and amount columns. Export that as CSV, then place the columns into an IIF transaction template (the tab-delimited !TRNS and !SPL records) and import it through File, Utilities, Import, IIF Files in QuickBooks Desktop. QuickBooks Desktop cannot read a PDF directly, so this conversion is the required first step.
No. QuickBooks Desktop imports transactions through IIF and Web Connect (QBO) files, not PDFs. You first convert the PDF statement into structured rows, then build an IIF file or a CSV your import tool accepts. Converting the PDF with BankXLSX gives you the clean date, description, and amount columns those formats require.
An IIF file, short for Intuit Interchange Format, is a tab-delimited text file QuickBooks Desktop uses to import and export lists and transactions. Transactions use a !TRNS line, one or more !SPL split lines, and an !ENDTRNS line. The headers tell QuickBooks which field each column maps to, so the column order and tabs must be exact.
Create the bank account in QuickBooks first, then go to File, Utilities, Import, IIF Files and select your file. For an existing PDF statement, convert it to clean rows with BankXLSX, map them to an IIF !TRNS layout (or a CSV if your importer reads CSV), and confirm the account name matches exactly so the lines post to the right register.
An IIF !TRNS line needs a transaction type (such as CHECK or DEPOSIT), a date in MM/DD/YYYY, the bank account name (ACCNT), a name or payee, and a single signed amount with debits negative and deposits positive. The matching !SPL line carries the offsetting account. BankXLSX delivers the date, description, and signed amount, so you only fill in the account mapping.
No. IIF is a tab-delimited text format for importing lists and transactions you control line by line, ideal for historical and bulk imports. QBO (Web Connect) feeds transactions into the Bank Feeds center for matching and is meant for ongoing reconciliation of a connected account. They both target QuickBooks Desktop but serve different jobs.
Bank feeds usually fail for closed accounts and old periods, so the dependable path is the PDF statement. Convert it with BankXLSX into dated, signed rows, build an IIF file (or CSV), and import it through File, Utilities, Import. This is how bookkeepers post legacy history that no live feed will pull.
It can if the same transactions already exist from a bank feed or a prior import. Import a statement only once, and for an account that also uses Bank Feeds, post historical IIF data only for periods the feed did not cover. Reviewing the register by date range before importing is the fastest way to avoid duplicates.
You can start on BankXLSX free with no credit card, which is enough to convert a real statement and test the columns before you commit. After the conversion, building the IIF file from those rows is just mapping columns into a template, so you can validate the whole workflow on one statement at no cost.
Get clean CSV rows for any importer.
Export to QuickBooks Web Connect (QBO).
Convert PDF statements to Excel.
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 |
