How to import bank statements into QuickBooks Desktop after the 2023 sunset

The short answer: importing bank statements into QuickBooks Desktop in 2026

On a supported version (Desktop Plus 2024 or Enterprise 24.0 on an active subscription), nothing has changed: connect a bank feed, or import the bank’s Web Connect (.qbo) file with Banking → Bank Feeds → Import Web Connect Files, then review the transactions in the Bank Feeds Center. On a 2023 version after May 31, 2026, Intuit says you can no longer download or upload transactions, so expect bank feeds and Web Connect files to fail. IIF import, which reads a file on your computer into the register, is not on Intuit’s list of discontinued services, and neither is typing transactions in.

What Intuit changed, and when

Three different announcements get blurred together in most coverage: a stop-sell, the end of annual releases, and the discontinuation of one version. They affect different people. Every date below comes from Intuit’s own help pages as of October 2026.

Intuit’s discontinuation page says existing Plus and Enterprise subscribers receive version 2024 (or Enterprise 24.0) at no extra cost as part of their plan, so the 2023 sunset mostly matters to copies that were never upgraded, or whose subscription ended. As of October 2026, Intuit’s pages publish no discontinuation date for 2024 or 24.0. Third-party sites quote dates for that; we could not find one on Intuit’s own pages, so treat them as unconfirmed.

Check which version you run

1. 1Open QuickBooks Desktop for Windows and press F2 (or Ctrl+1). The Product Information window opens.
2. 2Read the product name at the top: the year and edition, such as “QuickBooks Desktop Pro Plus 2023”, and the release (R number) after it.
3. 3Ignore the “Versions Used on File” list for this purpose. It records every version that has opened the company file, not the one you are running.
4. 4On a Mac, press Command+1 for the same window.

If the year is 2024 (or Enterprise 24.0) and your subscription is active, you are on a supported version and every import method below works. If it says 2023 or earlier, you are on a discontinued version, and the rest of this guide tells you what is left.

What stops working on a discontinued version

Intuit’s discontinuation policy page lists the services that end. For importing bank data, two lines matter: you will not be able to download transactions, send online payments or send online transfers, and “uploading transactions will also get discontinued”. The FAQ on the same page adds that you lose access to online bank feeds. The message you see depends on the download method, and the example Intuit gives is the one a Web Connect import shows:

QuickBooks Desktop is unable to verify the Financial Institution Information for this download.

• Bank feeds through Direct Connect or Express Web Connect stop downloading.
• Web Connect (.qbo) files are a download in Intuit’s terms, and on a current version importing one requires signing in to your Intuit Account inside QuickBooks. Expect them to be refused on a discontinued version, whether the bank or a converter made the file.
• Payroll tax calculations and forms, Desktop Payments, emailing forms and reports, Accountant Copy Transfer and live technical support also end.
• Critical security updates stop. That matters more than any import route if the computer holds client data.

Transactions you downloaded before the cutoff stay in the company file. Intuit’s pages describe services ending, not the program refusing to open.

What still imports, version by version

QuickBooks Desktop has no CSV upload into Bank Feeds, on any version. Intuit’s import and export page lists Web Connect (.qbo) files for bank data, IIF for complex data structures, and Excel or CSV for lists and general transactions. A bank CSV therefore has to become a Web Connect file, an IIF file, or (in Enterprise and Accountant) a Batch Enter paste.

Import Web Connect files on a supported version

Web Connect is still the best route on 2024 and Enterprise 24.0, because the transactions go to the Bank Feeds Center for review and each one carries an ID that QuickBooks remembers. Intuit’s “Nothing imported” article says QuickBooks will not import a transaction with the same ID more than once, which is what makes overlapping files safe.

1. 1Back up the company file.
2. 2Download the .qbo file from your bank, or convert the statement to one.
3. 3Make sure you are signed in to your Intuit Account inside QuickBooks Desktop. Otherwise the import stops with the message below.
4. 4Go to Banking → Bank Feeds → Import Web Connect Files. File → Utilities → Import → Web Connect Files opens the same import.
5. 5Select the .qbo file and select Open.
6. 6Choose Use an existing QuickBooks account and pick the account, or create a new one, then select Continue.
7. 7Select OK when QuickBooks says the data has been read, then review and add the transactions in the Bank Feeds Center.

To download and import transactions, sign in with your Intuit account.

If you are already signed in and still see it, Intuit suggests switching bank feed modes. A file that imports with nothing new in it usually means every transaction ID was already there; a file refused with “unable to verify the financial institution” on a supported version usually means its bank ID is missing or unknown to Intuit.

Import IIF files on any version

IIF (Intuit Interchange Format) is Desktop’s own tab-separated import format. It needs no bank ID, does not go through Bank Feeds, and is not among the services Intuit lists as discontinued, which makes it the practical way to keep importing statements into a 2023 copy. It also suits history older than any bank download, on any version.

1. 1Sign in to the company file as the admin.
2. 2If you are in multi-user mode, switch to single-user mode from the File menu.
3. 3Back up the company file. Intuit calls this step important, and an IIF import is hard to undo row by row.
4. 4Go to File → Utilities → Import → IIF Files, select the file and confirm.
5. 5Open the account register and check the new transactions against the statement before going any further.

• No review screen: transactions go straight into the register.
• No duplicate check: importing the same file twice records everything twice.
• No link between transactions: Intuit’s page says IIF imports don’t link transactions, so a payment will not be applied to an invoice for you.
• No help from Intuit: its page says it doesn’t offer technical support for importing IIF files; for a file made by another program, ask that program’s support.
• Account names must match: every account an IIF line names should exist in the Chart of accounts with the right type, or be declared at the top of the file.

Each bank transaction in an IIF file is a pair of lines that balance to zero: a TRNS line for the bank account and an SPL line for the other side, such as an expense or income account. A made-up example: a $245.60 payment to Riverside Office Supply is TRNS −245.60 on Checking and SPL +245.60 on Office Supplies. If you do not know the category yet, an uncategorized account on the SPL side works, and you recategorize later.

Batch Enter Transactions in Enterprise and Accountant

Intuit says only QuickBooks Enterprise and QuickBooks Accountant Desktop support batch entering transactions from Excel or CSV. Open Accountant → Batch Enter Transactions, choose the transaction type and the bank or credit card account, arrange your spreadsheet columns in the same order as the grid, copy them and paste into the first date field. Names and accounts that QuickBooks does not recognise turn red so you can add them before saving.

It is a good route for a statement already in a spreadsheet, because you see every row before it is saved. Like IIF it has no duplicate check, so keep a note of which statement periods you have entered.

Staying on a discontinued version: the trade-offs

Some firms keep a 2023 copy for a closed year, an archived client or a business that only needs a ledger. That is a choice you can make with your eyes open, and IIF plus manual entry will keep the books current. The costs are real, though.

• No security updates. Intuit says discontinued versions won’t receive critical security updates. A machine that holds bank data and stays online is the main risk here, not the import route.
• No payroll tax calculations or forms, no payments processing and no live support.
• Every statement becomes a file job. Without a feed, each month means creating and importing an IIF, or typing.
• Reconciling becomes the only check. With no Bank Feeds review step, reconcile each month to the statement straight after the import.

Switching from a bank feed to file imports without gaps

The month a feed stops is where gaps and doubles appear. The feed downloaded part of a statement period, and the file you import next covers the whole of it. The rule is the same as for any import: find the last transaction already in the register, and start the next file the day after.

• Delete the rows a file would duplicate before importing it, or trim the file to the missing days.
• Reconcile each month to the statement’s ending balance before importing the next one.
• If a reconciliation is out by exactly one transaction, look for a row imported twice at the boundary.
• If you later upgrade and the feed reconnects, choose a start date after the last transaction you imported by file.