Bank No Longer Supports QuickBooks Download? How to Keep Importing
No account needed for your first 3 conversions. We never store your bank login.
Short answer: If your bank no longer supports a QuickBooks download, export your transactions as a CSV or Excel file from the bank's website and convert that file to a .qbo, which QuickBooks Desktop and Online both import. Most notices about a dropped QuickBooks connection refer to Direct Connect, which Intuit retires on October 30, 2026, not to your ability to import a file. A converted CSV keeps the exact same import step working.
Two different things get reported as "my bank stopped working with QuickBooks," and the fix depends on which one you have. One is the Direct Connect retirement. The other is a bank that simply never offered a .qbo download in the first place. Both end at the same place: a CSV you convert to a .qbo.
Why did my bank stop supporting QuickBooks?
In most 2026 cases the bank did not drop QuickBooks, it dropped Direct Connect. Intuit is retiring Direct Connect on October 30, 2026, and new enrollments ended April 30, 2026, so banks are sending notices that the two-way feed will stop. Web Connect, the file-based method, is unaffected. Your history and reconciliations stay exactly as they are.
My bank sent a Direct Connect discontinuation notice. What do I do?
Move that account to Web Connect before the October 30, 2026 cutoff. In QuickBooks Desktop, deactivate Bank Feeds for the account, then download a .qbo file from your bank and import it through Banking, Bank Feeds, Import Web Connect File. If your bank only offers a CSV, convert that CSV to a .qbo first and import the result the same way.
What if my bank never offered a QBO or Web Connect download?
Plenty of smaller banks, credit unions, and fintech accounts only give you a CSV or Excel export, never a .qbo. Download the CSV, then convert it to a .qbo file in your browser and import that into QuickBooks. The converter reads any column order, fixes mixed date formats, and writes a valid Web Connect file QuickBooks accepts natively.
Can I just upload the bank CSV to QuickBooks instead?
Only in QuickBooks Online, and only if the file fits its strict rules: a 3-column or 4-column layout, English, 350 KB or smaller, and 1,000 rows or fewer per upload. QuickBooks Desktop cannot import a CSV at all in any edition, so on Desktop you must convert to .qbo. Even on QBO, a .qbo avoids the column-mapping and reformatting work.
My bank only gives me a PDF statement. Can I still import it?
Yes, but you convert it in two hops: turn the statement into a spreadsheet, then convert that to a .qbo. If your only record is a PDF, you can turn the statement into a clean spreadsheet first, then bring that CSV here to build the .qbo. From there the import into QuickBooks is the usual Web Connect step.
Will importing a converted file create duplicates?
No, when the file is a proper .qbo. Each transaction in the converted .qbo carries a unique ID, so if you accidentally import the same file twice QuickBooks recognizes the duplicates and does not add them again. That safety net is one reason a .qbo is more reliable than pasting a CSV, where QuickBooks has no ID to match against.
Does this change affect QuickBooks Online users?
No. QuickBooks Online uses aggregation-based feeds, not Direct Connect, so QBO connections are not affected by the October 2026 retirement. If a QBO feed breaks for other reasons, you can still upload a bank file manually, and its manual upload accepts a .qbo along with CSV, QFX, and OFX. The Direct Connect change is a Desktop and Quicken issue.
How do I keep this from being a monthly chore?
Standardize on one export and one converter. Each period, download the same CSV from your bank, convert it to a .qbo, and import through Bank Feeds. If you handle several accounts, each export converts in seconds, so working through the stack keeps a lost Direct Connect feed from turning into hours of manual entry.
| What your bank actually gives you | What that means | Route into QuickBooks |
|---|---|---|
| QuickBooks Web Connect (.qbo) | The native file. Nothing to convert | Import directly through Bank Feeds on Desktop, or the bank upload on Online |
| OFX or QFX (.ofx, .qfx) | The same family of file under a different name | QuickBooks Online accepts .ofx directly. Desktop generally wants it as .qbo |
| CSV or Excel | The most common fallback once a download is retired | Convert to .qbo. QuickBooks Online can also take a CSV directly if it fits the strict layout |
| PDF statement | No machine readable transactions | QuickBooks Online can read a PDF or image statement with side by side review. Otherwise convert the PDF to a spreadsheet first, then to .qbo |
| Online banking screen only | No export at all, which is rare but happens at small institutions | Ask for a CSV export by name. Almost every core banking platform has one, it is just buried |
Which banks are discontinuing Direct Connect in 2026?
The largest publicly announced round is Zions Bancorporation, which retires Direct Connect on October 30, 2026 and closed new enrollments on April 30, 2026. That covers all six brands: Zions Bank, Amegy Bank, California Bank and Trust, National Bank of Arizona, Nevada State Bank and Vectra Bank Colorado. Bank of America moved earlier, on September 30, 2025. Your own bank's notice always outranks any industry date.
Can I still use Express Web Connect if Direct Connect is going away?
Sometimes, and it depends on your bank. Intuit's own Desktop bank feeds setup article lists exactly two choices, Direct Connect or Web Connect, but Express Web Connect does exist in Desktop for some institutions and Intuit publishes refresh instructions for both Windows and Mac. So a bank notice telling a Desktop user to simply switch to Express Web Connect is not a guaranteed path. Check whether your specific bank offers it before you rely on it.
What does bank feed error 102 mean in QuickBooks?
It means the bank's own site or server is not responding, not that anything is wrong with your file or your company file. The common codes are worth knowing because they change what you do next.
| Code | What it means | What to do |
|---|---|---|
| 102 and 105 | The bank's site or server is down or in maintenance | Wait it out. Nothing on your side fixes this |
| 185 | The bank wants more than a user ID and password, typically a one time code | Complete the extra verification when prompted |
| 324 | QuickBooks cannot find the account, often after the bank renumbered or migrated it | Disconnect and reconnect the account, or import a file instead |
How far back can I download transactions from my bank?
Usually about 90 days through the bank feed, which surprises people mid migration. A freshly connected QuickBooks bank feed commonly pulls only that window, and Capital One caps its export at roughly 90 days too. If you need more history, download it in chunks from the bank's own export screen. At Chase that is the Account Activity download rather than the Statements page.
What file types can QuickBooks import from my bank?
QuickBooks Online accepts .csv, .txt, .qbo and .ofx, plus a PDF or image statement (JPG, PNG, HEIC) that it reads with a side by side review step. QuickBooks Desktop is stricter: transactions come in as .qbo through Bank Feeds, or as IIF, and nothing else. Desktop cannot import a bank CSV in any version, Enterprise included.
Does QuickBooks Desktop still work after my bank drops Direct Connect?
Yes. Losing Direct Connect removes the automatic pull, not the ability to import. You download the file yourself and bring it in through Bank Feeds, which is exactly how Web Connect has always worked. The review and match queue behaves identically, so your reconciliation routine does not change. The only difference is that you fetch the file instead of QuickBooks fetching it.
How do I avoid duplicates when I switch from Direct Connect to a file import?
Note the date of the last transaction that came through Direct Connect, then start your first imported file the day after. Every transaction in a .qbo file carries a FITID that is unique within the account, and QuickBooks skips IDs it has already seen, so a genuine overlap is usually caught. Non overlapping date ranges are still the cleaner habit, especially where rows were posted by an API integration and carry no FITID at all.
Losing a bank download sounds worse than it is. The import step in QuickBooks does not change; only where the .qbo comes from does. Convert your bank's CSV export with the tool at the top of this page, then import it exactly as you always have. If you want to weigh the alternatives first, the comparison of CSV to QBO converters puts the desktop licenses and the browser tools side by side. For the full switch, read the Direct Connect alternative for QuickBooks and, if you are unsure of the file rules, the QuickBooks CSV import template.