How to import bank transactions into QuickBooks Desktop after bank feeds stopped (2026)

If your QuickBooks Desktop bank feed stopped working this year, you're not imagining it. Intuit discontinued QuickBooks Desktop 2023 after May 31, 2026, and that switched off both bank feed downloads and the old workaround of importing a .QBO Web Connect file. The software still opens and your data is intact. You just need a way to get transactions in that doesn't go through Intuit's servers. For most people that's an IIF import.

What changed on May 31, 2026

Intuit retires each QuickBooks Desktop version about three years after release. For QuickBooks Desktop Pro Plus, Premier Plus, Mac Plus and Enterprise Solutions 23.0, that date was May 31, 2026. Intuit's discontinuation notice lists what stops, including online banking: you can't download transactions, send online payments or transfers, and it adds that "uploading transactions will also get discontinued."

That last line is the one that catches people out. For years the fix for a broken bank connection was to download a .QBO (Web Connect) file from your bank and import it through the Bank Feeds Center. Web Connect is part of the same online banking service, so on a discontinued version that route is closed too. Typical errors say QuickBooks "is unable to verify the Financial Institution Information for this download."

Your options, compared

IIF (Intuit Interchange Format) is a tab-separated text file that QuickBooks Desktop has read for decades. It's unforgiving about details, but it's free, needs no internet connection, and keeps working on any version.

Step by step: import transactions with an IIF file

1. Get the transactions out of your bank

Download the activity as a CSV or Excel file from your bank's website if you can. Most banks let you pick a date range, though how far back you can go varies. For older months, closed accounts or statements a client sent you, you'll only have the PDF statement. Convert it to rows first, and check the total against the statement's ending balance before you go further (more on that below).

2. Decide which accounts the other side goes to

Every IIF transaction has two lines that must add up to zero: one for the bank (or credit card) account and one for the account on the other side. If you don't want to categorize in the spreadsheet, send everything to Uncategorized Expense (money out) and Uncategorized Income (money in), then reclassify inside QuickBooks. Open Lists > Chart of Accounts and copy the exact name of your bank account. If an account name in the file doesn't match, QuickBooks quietly creates a new account with that name.

3. Build the IIF file

Each transaction is a TRNS line (the bank side), one or more SPL lines (the other side) and an ENDTRNS line. Use these transaction types:

• Bank account: CHECK for money out (negative amount on the bank line), DEPOSIT for money in (positive).
• Credit card account: CREDIT CARD for charges (negative on the card line), CCARD REFUND for payments and refunds (positive).

Dates must match the date format in your Windows regional settings (MM/DD/YYYY in the US). Fields are separated by tabs, not commas. If you build the file in Excel, save as "Text (Tab delimited)" and rename the extension to .iif.

4. Back up, then import

1. File > Back Up Company. Don't skip this: an IIF import can't be undone in one click.
2. Switch to single-user mode.
3. File > Utilities > Import > IIF Files, then choose your file. Newer versions show a review step that flags problems before anything is posted. Read it.
4. Open the bank register and check that the first and last transactions and the ending balance look right.

5. Reconcile against the statement

IIF transactions post straight to the register. They don't appear in the Bank Feeds Center for matching, so QuickBooks won't warn you about duplicates. Run Banking > Reconcile with the statement's ending balance. If you reconcile to zero, the import is right.

A sample IIF file you can copy

Two bank transactions: a $4.50 card purchase and a $2,000 deposit. The gaps between fields are tabs. The empty field is NAME: leave it blank unless the payee already exists in your lists, or QuickBooks will add every new description as a name.

!TRNS	TRNSTYPE	DATE	ACCNT	NAME	AMOUNT	MEMO
!SPL	TRNSTYPE	DATE	ACCNT	NAME	AMOUNT	MEMO
!ENDTRNS
TRNS	CHECK	08/03/2026	Checking		-4.50	STARBUCKS #12
SPL	CHECK	08/03/2026	Uncategorized Expense		4.50	STARBUCKS #12
ENDTRNS
TRNS	DEPOSIT	08/04/2026	Checking		2000.00	ACME PAYROLL
SPL	DEPOSIT	08/04/2026	Uncategorized Income		-2000.00	ACME PAYROLL
ENDTRNS

A credit card charge looks the same with CREDIT CARD as the type and your card account (for example American Express) on the TRNS line.

Mistakes that create a mess

• Importing overlapping dates. There's no duplicate check. Start the file the day after the last transaction already in the register.
• Account name typos. "Checking" and "Checking " (trailing space) are different accounts to QuickBooks. You'll find a new, empty-looking account with all your transactions in it.
• Commas instead of tabs. A CSV renamed to .iif won't import. Save as tab-delimited text.
• Wrong signs. On the bank line, money out is negative. If every transaction lands the wrong way round, flip the signs in the whole file, not row by row.
• Not checking the source first. If a PDF-to-spreadsheet step dropped a row, IIF will import the gap faithfully. Before importing, check that opening balance + sum of transactions = closing balance.
• Payees as names. Filling the NAME column with raw bank descriptions ("SQ *COFFEE 4471") fills your Vendor and Other Names lists with junk. Keep descriptions in MEMO.

If you have only a few transactions a month, typing them in is fine. If you're catching up on a year of statements or doing this for clients, IIF is the reliable route until you upgrade.

FAQ

Related guides

• How to convert a credit card statement PDF to Excel
• QBO vs IIF vs QIF: which file QuickBooks and Quicken actually need