How to Import Bank Transactions into QuickBooks Desktop (IIF, QBO, CSV)

QuickBooks Desktop will not read a PDF bank statement, and it will not open a raw Excel export the way you might expect. It imports transactions in one of a few specific shapes: a QBO (Web Connect) file downloaded from your bank, an IIF file laid out in Intuit's exact format, or a CSV mapped to QuickBooks columns. If your statement is a PDF, or your bank's feed has stopped working, you first convert that statement into one of those formats, then import it. This guide walks through every method, the column layout each one needs, and the fastest path when Desktop bank feeds quit on an older version.

The short answer: download a .QBO Web Connect file from your bank and import it through File > Utilities > Import > Web Connect Files, or build an .IIF file with the !TRNS / !SPL structure and import it through File > Utilities > Import > IIF Files. If all you have is a PDF statement, convert it to a clean CSV or directly to an IIF or QBO file first. QuickBooks Desktop will not accept the PDF itself.

Which file formats QuickBooks Desktop accepts

QuickBooks Desktop reads three import shapes for bank activity, and each behaves differently once the data lands in your file. Knowing which one fits your situation saves a lot of cleanup later.

One point trips people up constantly: QuickBooks Desktop has no native CSV bank-import screen. That feature lives in QuickBooks Online. On Desktop you either feed it a .QBO file or an .IIF file, so a CSV or Excel statement has to be converted into one of those before it will import.

Method 1: Import a QBO (Web Connect) file

Web Connect is Intuit's recommended path for bank activity on Desktop. A .QBO file carries your transactions plus the bank routing details QuickBooks uses to match them, and imported transactions land in the Bank Feeds center where you review before they hit the register.

1. In QuickBooks Desktop, open Lists > Chart of Accounts and confirm the bank account you are importing into exists with the correct name and type.
2. If the account shows a lightning-bolt or strike icon (a live direct-connect feed), open its Bank Feed Settings and deactivate online services first, or the Web Connect import can collide with the feed.
3. Download the .QBO file from your bank's website, or convert your statement to a .QBO file if your bank does not offer one.
4. Go to File > Utilities > Import > Web Connect Files (older builds: Banking > Bank Feeds > Import Web Connect Files).
5. Select the .QBO file, pick the matching QuickBooks account, then review and accept the transactions in the Online Banking Center.

Because QBO transactions wait in the review queue, you can apply renaming rules and assign accounts as you accept them. That is the main reason newer Desktop users prefer it over IIF.

Method 2: Import an IIF file

IIF (Intuit Interchange Format) is a tab-delimited text file that posts transactions directly into the register with no review step. It is the most flexible option, works on any QuickBooks version including ones too old for Web Connect, and supports splits, classes, and memos. The trade-off is precision: every account name in the file must already exist in your Chart of Accounts and match character for character.

1. Create the bank account and any expense or income accounts you will reference, so the names already exist in QuickBooks.
2. Build the IIF with the header rows QuickBooks expects: a !TRNS line, a !SPL line, and an !ENDTRNS marker, then one TRNS/SPL/ENDTRNS block per transaction.
3. Use signed amounts: money leaving the account is negative on the TRNS line, the offsetting split is positive, and the two must net to zero per transaction.
4. Format dates as MM/DD/YYYY and keep the file tab-delimited, not comma-delimited.
5. In QuickBooks, go to File > Utilities > Import > IIF Files, choose the file, and let it post. Back up your company file first, since IIF writes straight to the register.

Hand-building IIF by hand is error-prone, which is why most people convert their PDF or CSV statement straight to a ready-to-import IIF file instead of typing the structure themselves. Our bank statement to IIF converter for QuickBooks Desktop outputs the correct !TRNS / !SPL layout with signed amounts so the import posts cleanly the first time.

Method 3: Convert a PDF or CSV statement first

Most of the time the problem is not the import screen, it is the file you are starting with. A PDF statement or a plain Excel export will not import on Desktop as-is. The reliable path is to convert the statement into a clean, structured file and then run Method 1 or Method 2.

1. Upload your PDF statement to the converter at the top of this page to extract every transaction into Date, Description, and Amount columns, with the running balance preserved.
2. Review the rows in Excel or CSV, fix any vendor names you want renamed, and split debits and credits the way QuickBooks expects (debits negative, credits positive).
3. Export the result as a QBO or IIF file, then import it with the matching method above.

This is also the only practical way to load historical activity, closed accounts, or a bank that no longer offers a Desktop feed, since none of those will stream in through Web Connect. If you are on QuickBooks Online instead, the path is different: you can import a bank statement into QuickBooks with a mapped CSV upload built into the Banking screen.

When QuickBooks Desktop bank feeds stop working

Intuit disables online banking services for QuickBooks Desktop versions older than three years, even though the software still runs locally. When that happens, the Bank Feeds connection simply stops pulling transactions, and a Web Connect import may reject the file as out of date. You do not have to upgrade to keep your books current. Convert each statement to an IIF file, which has no version cutoff, and import it through File > Utilities > Import > IIF Files. That keeps an unsupported but otherwise working copy of QuickBooks Desktop usable for as long as you need it. The same approach applies to other desktop bookkeeping tools: see how to import bank statements into Quicken for the QFX, QIF, and CSV equivalents there.

How many transactions can you import at once?

There is no hard published cap for a Desktop IIF or QBO import the way QuickBooks Online limits manual uploads to around 1,000 lines per file. In practice, very large IIF files can be slow or can fail mid-import, so it is safer to split a long history into one file per statement period or per few hundred transactions. Importing month by month also makes it far easier to reconcile and to spot a bad row if one transaction is rejected.

Frequently asked questions

Can you import bank transactions into QuickBooks Desktop?

Yes. QuickBooks Desktop imports bank transactions from a QBO (Web Connect) file through File > Utilities > Import > Web Connect Files, or from an IIF file through File > Utilities > Import > IIF Files. It does not read a PDF statement or a raw Excel file directly, so a PDF or CSV statement has to be converted to QBO or IIF first.

Can I import bank transactions into QuickBooks Desktop from Excel or CSV?

Not directly. Unlike QuickBooks Online, Desktop has no native screen for uploading a CSV or Excel bank file. You convert the spreadsheet into a QBO or IIF file, then import that. A converter that outputs the QuickBooks-ready format does this in one step and avoids hand-formatting the columns.

How do I manually import bank transactions into QuickBooks Desktop?

Download a .QBO Web Connect file from your bank, or convert your PDF statement to a .QBO or .IIF file, then import it manually under File > Utilities > Import. Manual import is the fallback whenever a live bank feed is unavailable, the account is closed, or you need older history that the feed will not provide.

What is the difference between IIF and QBO for QuickBooks Desktop?

IIF is a tab-delimited text file that posts directly into the register and works on any QuickBooks version, but it requires exact existing account names and signed amounts. QBO is an XML Web Connect file that lands in the Bank Feeds review queue so you can match and rename before accepting, but it needs a QuickBooks version no more than about three years old.

Why won't QuickBooks Desktop import my bank file?

The most common causes are a QuickBooks version too old for Web Connect, an account name in an IIF file that does not exactly match the Chart of Accounts, a comma-delimited file where IIF expects tabs, or a still-active direct-connect feed conflicting with the import. Deactivate the live feed, confirm the account names, and re-export the file in the correct format.

Does QuickBooks Desktop still support IIF imports?

Yes. QuickBooks Desktop continues to accept IIF files for transaction imports, and because IIF has no version cutoff it is often the most dependable option for older installs and for full historical data. Back up your company file before an IIF import, since the transactions post straight to the register without a review step.

Once your transactions are in, reconcile each statement period against the register so opening and closing balances match. If you also keep books in QuickBooks Online or need a .QBO file for it, you can convert a bank statement to QuickBooks (QBO) in the same way. And if you would rather work the numbers in a spreadsheet first, our bank statement converter exports clean Excel and CSV you can review before importing.