QuickBooks Desktop bank feeds discontinued: you can still import a file
Intuit retires the online services on each QuickBooks Desktop version about three years after it ships, and bank feeds go with them. When that date passes the automatic download stops for good: there is no patch, no workaround and no support call that brings it back. What does still work is the file route — File → Utilities → Import → Web Connect Files — and that is the part most of the panic leaves out.
🔒 Turn your CSV into a .QBO file — free, runs in your browser, nothing uploaded.
Why people think file import died too
Intuit's discontinuation notices say that you will no longer be able to download transactions, send online payments or transfers, and that uploading transactions is discontinued as well. Read quickly, that last clause sounds like every route into the program is closed, including importing a file by hand.
It is not. The services that end are the connected ones — the feed that reaches out to your bank, and the upload path that goes back through Intuit. Opening a .QBO Web Connect file from your own disk is a local operation, and firms running sunset versions report that it keeps working, as do the vendors who sell converters for exactly this situation.
Is my version affected?
The pattern reported across the accounting press is a three-year cycle, with each version's services ending on 31 May:
| Version | Online services ended |
|---|---|
| Desktop 2021 | 31 May 2024 |
| Desktop 2022 | 31 May 2025 |
| Desktop 2023 | 31 May 2026 |
| Desktop 2024 | Still supported, no end date announced |
Desktop 2024 is described by Intuit as the latest and last annual release. Dates do move, and we cannot read Intuit's own support pages from our server, so treat the table as orientation and confirm your own version against Intuit's current notice before you plan around it.
A discontinued version is not locked: the company file still opens, the data is intact, and you can keep entering transactions and running reports. Only the connected services are gone.
What to do instead, in order of least work
- Check whether your bank still offers a Web Connect download. Many banks publish
.QBO,.OFXor.QFXfiles from their own site, quite separately from the QuickBooks feed. If yours does, download it and import it directly — nothing needs converting. - If the bank only gives you CSV or Excel, which is the common case, convert it to
.QBOand import that. This is what QBOKit does, in the browser, without the statement leaving your machine. - If the bank only gives you PDF statements, extract the rows first, then convert. Expect to check the columns by hand: PDF layouts vary far more than CSV ones.
The two errors you will probably hit next
Both of these come from the file rather than from the discontinuation, and both have their own page here:
- "QuickBooks cannot verify the financial institution." A converted file needs the
FIDandINTU.BIDcodes that identify your bank to QuickBooks. Get them wrong and the import is refused outright. See cannot verify the financial institution. - The import runs but nothing appears, or QuickBooks says the file is already up to date. QuickBooks remembers transaction ids and silently skips anything it has seen before. See QuickBooks will not re-import a Web Connect file.
If you look after clients on old versions
This lands hardest on bookkeepers. Once a client's version sunsets, every transaction that used to arrive on its own has to be keyed in or brought in through a file, every month, for as long as that client stays put. Converting a CSV takes a few seconds per account; re-keying a month of transactions does not. If the upgrade is coming anyway but not this quarter, the file route is what carries the client until then.
Sources
- Bank not supported — QuickBooks Community.
- Import a QBO file into QuickBooks Desktop — ProperSoft support, on the Web Connect file path.
- How to import Web Connect banking data into QuickBooks Desktop — Gentle Frog.