QuickBooks Bank Feed Not Working: Fix QuickBooks Desktop and Online Bank Feeds

In most cases the connection between your bank and QuickBooks broke on the bank's side, not in your company file. The common causes are a bank core system migration, a new multi factor security prompt the feed cannot answer, a bank that stopped publishing the download format QuickBooks reads, an aggregated connection that silently returns nothing, or a fintech account that never had a real feed to begin with. None of these are fixed by rebuilding your QuickBooks file.

Because the balance and the transaction list come from different parts of the connection. QuickBooks can still read the account balance while the transaction request returns an empty set, which is exactly what happened to Barclays US cardholders in 2026 when the issuer stopped serving the download format the feed expects. The account looks connected, so nothing warns you, and the register just quietly stops filling.

They differ by edition, and the code tells you where the break is. Use this table to place your error before you start troubleshooting, because several of them cannot be fixed from inside QuickBooks at all.

Fix the register first, then the connection. Sign in to your bank, export the missing date range as a CSV, upload it in the converter above, and import the resulting .qbo into the matching QuickBooks account. That closes the gap immediately, with no waiting. Then, separately, try reconnecting the feed: disconnect the account in QuickBooks, sign in on the bank's own website to clear any pending security prompt, and link it again.

Because the connection points at infrastructure that no longer exists. When a bank moves customers onto a new digital banking platform, as BMO did after retiring the BMO Harris brand, the old connection details stop resolving and QuickBooks starts returning errors like 350 or stalling on a security prompt. The bank eventually publishes a new connection, but that can take weeks, and the transactions you missed in the meantime still have to be imported from a file.

Yes. Intuit is retiring Direct Connect for QuickBooks on October 30, 2026, and stopped accepting new Direct Connect enrollments on April 30, 2026. Direct Connect is the automatic, two-way connection many QuickBooks Desktop users rely on, and when it goes away the remaining options are Express Web Connect and manual Web Connect files. If your Desktop feed is already failing, moving to a .qbo import workflow now means the sunset costs you nothing.

Direct Connect is an automatic two-way link that your bank enables, and it retires on October 30, 2026. Express Web Connect has Intuit aggregate transactions from your bank login on a schedule, which is where most dropped and duplicated transactions come from. Web Connect is a file you download or build yourself, a .qbo, and import into QuickBooks. Web Connect is the only one of the three that does not depend on a live connection, which is why it keeps working when the others fail.

Because fintechs are not chartered banks and almost never publish an OFX Direct Connect service, which is the protocol QuickBooks Desktop uses to download transactions. Mercury, Brex, Ramp, Relay, Novo, and Bluevine all fall into this group: their native integrations reach QuickBooks Online only. On QuickBooks Desktop there is no feed to fix, so a converted .qbo is not a workaround, it is the supported path.

In QuickBooks Online yes, with manual column mapping and a file size limit that long exports exceed. In QuickBooks Desktop no, not for bank transactions: Desktop's bank feed reads only Web Connect files, meaning .qbo, .qfx, and .ofx. That is why converting the CSV to a .qbo is the step that matters. The converted file imports the same way on both editions and skips the mapping screen entirely.

Go to File, then Utilities, then Import, then Web Connect Files, and select the .qbo you downloaded from the converter. QuickBooks asks which account the transactions belong to, so pick the register that matches the bank account you exported. The transactions appear in the Bank Feeds Center for review, and you accept them into the register. Nothing is typed by hand.

Open Transactions, then Bank transactions, select the account, and use the upload option to add the .qbo file. QuickBooks reads it, lists the transactions for review, and posts them when you accept. Because a Web Connect file is already in the structure QuickBooks expects, there is no column mapping and no size ceiling to work around.

Not if you set the date range correctly. QuickBooks matches incoming Web Connect transactions against what is already posted and flags likely duplicates for review rather than adding them blindly. Before you export from the bank, check the last date that actually landed in the QuickBooks register, then start the export the day after it. Import only the gap, and the register stays clean.

As far back as your bank lets you export. Bank feeds only look forward, so history from before the connection was made never arrives on its own. Most banks let you download a year or more of activity as a CSV, and each export becomes one .qbo. If you are catching up several accounts at once, convert them together and reconcile each one against its statement as you go.