QuickBooks Desktop Bank Feeds Not Working: How to Fix It

Short answer: QuickBooks Desktop bank feeds fail because the connection to the bank breaks, not because your company file is damaged. Whatever the error code, you can get the missing transactions in immediately: download the period as a CSV from your bank, convert it to a Web Connect (.qbo) file, and import it through File, Utilities, Import, Web Connect Files. Desktop reads that file natively, with no feed and no column mapping.

Last updated July 2026.

Desktop feed failures are their own species. QuickBooks Online users get a numbered banking error and a support article. Desktop users get an OL or OLSU code, a suggestion to verify and rebuild the data file, and a lot of time lost to steps that were never going to help, because the break is on the bank's side of the wire.

The three ways a Desktop bank feed dies

The first is a broken session. OL-301, OL-221, and OLSU-1013 all come down to QuickBooks and the bank failing to complete a conversation: an expired enrollment, a changed password, a new security prompt, or a bank that altered its connection details. Verifying the data file does nothing for any of these, because nothing is wrong with the data file.

The second is a connection that works but returns nothing. The balance refreshes, the account looks healthy, and the transaction list stays empty. That is what Barclays US cardholders hit in 2026 when the issuer stopped serving the download format the feed expects. Nothing warns you. The register just stops filling, and you usually notice at month end.

The third is a bank that was never there. If you bank with a fintech (Mercury, Brex, Ramp, Relay, Novo, Bluevine and the rest), there is no QuickBooks Desktop feed to fix. Their native integrations reach QuickBooks Online only, and they do not publish an OFX Direct Connect service, which is the protocol Desktop uses to download transactions. There is no setting, no support ticket, and no workaround at the feed level.

Direct Connect is retiring, so this gets worse before it gets better

Intuit is retiring Direct Connect for QuickBooks on October 30, 2026, and stopped taking new Direct Connect enrollments on April 30, 2026. Direct Connect is the automatic, two-way connection that a lot of Desktop users have relied on for years, often paying their bank a monthly fee for it. After the sunset the remaining paths are Express Web Connect, which aggregates from your bank login on Intuit's schedule and is where most dropped and duplicated transactions come from, and manual Web Connect, which is a file you import yourself.

If your Direct Connect feed is already throwing OL errors, that is worth knowing, because it changes the calculation. Fighting to restore a connection that has a hard end date in October is not a good use of a Saturday. Moving to a file based workflow now costs you nothing later. See the Direct Connect alternative for QuickBooks Desktop for what the switch actually looks like.

Why QuickBooks Desktop will not take your CSV

This is the part that catches people. You have the transactions. Your bank hands you a perfectly good CSV. And QuickBooks Desktop refuses it, because Desktop cannot import CSV bank transactions at all. Its bank feed reads exactly three formats: .qbo (Web Connect), .qfx, and .ofx. QuickBooks Online will take a CSV with manual column mapping, which is why advice written for QBO keeps sending Desktop users down a road that ends in a wall.

So the CSV is not useless, it is just the wrong container. Converting it to a .qbo puts the same transactions in the format Desktop's Web Connect importer expects, and from there it behaves exactly like a file downloaded from the bank.

The fix, step by step

Start by checking the last transaction date that actually made it into the QuickBooks register. That is the boundary you are filling from, and getting it right is what keeps duplicates out.

Sign in to your bank's website and export the transactions from the day after that date through yesterday, as a CSV. Almost every US bank and card issuer offers a CSV or Excel download even when its QuickBooks feed is broken, and many let you go back a year or more, which is enough to catch up an account that has been dark for months. If your bank only hands you a statement as a PDF, turn the PDF into a clean spreadsheet first and work from that.

Upload the CSV to the CSV to QBO converter. It normalizes the dates into the format QuickBooks expects, strips currency symbols and thousands separators, signs debits and credits correctly, and totals every transaction it parsed so you can check the figure against the bank before you import anything.

In QuickBooks Desktop, go to File, then Utilities, then Import, then Web Connect Files, and select the .qbo. QuickBooks asks which account the transactions belong to, so choose the matching register. The transactions land in the Bank Feeds Center for review and you accept them into the register the same way you always have.

Then, if you want, try the feed again

With the register current, there is no urgency, which is the right position to troubleshoot from. Deactivate bank feeds for the account in the chart of accounts, sign in to your bank on its own website to clear any pending security prompt or agreement, and set the account up again. If the bank recently migrated to a new digital banking platform, expect to reconnect from scratch rather than repair the old connection, because the old one points at infrastructure that no longer exists.

If it reconnects, feeds only look forward, so it will pick up from today and leave the historical gap untouched. You have already filled that gap with the import, which is why doing the file first is the right order.

Will the import create duplicates?

QuickBooks compares incoming Web Connect transactions against what is already posted and flags likely duplicates for review rather than adding them blindly. Combined with starting your export the day after the last posted transaction, that is usually enough. If a feed did partially deliver some days, import a file only for the range it missed, and review before you accept.

The takeaway

A dead Desktop bank feed is a connection problem, not a bookkeeping problem, and you do not have to let it hold your books hostage while the bank works through it. Export, convert, import, reconcile. For the full picture across both editions, including QuickBooks Online banking errors 350, 185, and 102, see QuickBooks bank feed not working, and for the file format itself, the QuickBooks Web Connect file converter.