QuickBooks Bank Feeds Stopped Working: What the October 30, 2026 Direct Connect Retirement Means

Short answer: If your QuickBooks Desktop bank feed suddenly stops downloading transactions in late 2026, the cause is almost certainly Direct Connect being retired. Intuit shuts Direct Connect down on October 30, 2026, and new enrollments already ended April 30, 2026. Web Connect is not affected and keeps working, so the fix is to switch that account from Direct Connect to Web Connect, or to import a .qbo file yourself. Your data is safe; only the automatic download method is going away.

Plenty of people will meet this the hard way, opening the Bank Feeds Center in November and finding nothing comes down. If that is you, this walks through what actually changed, what did not, and the two ways to keep bank transactions landing in QuickBooks after the cutoff.

What is being retired, exactly?

QuickBooks Desktop connects to banks two ways. Direct Connect logs into your bank on a paid channel and pulls transactions straight into the software, and on some banks it also let you pay bills from inside QuickBooks. Web Connect is the manual method: you download a .qbo file from your bank's website and import it. Intuit is retiring Direct Connect on October 30, 2026. Web Connect stays. So the automatic pull is what breaks, not the ability to import bank activity.

The same retirement hits Quicken, which shares the Direct Connect plumbing. If you run both, expect both to stop the automated download at the same time. QuickBooks Online is a separate story: it uses aggregated bank feeds rather than Direct Connect, so QBO company files are not affected by this deadline.

How do I know Direct Connect is why my feed stopped?

Three signs point to it. Your bank sent a notice about QuickBooks or Quicken Direct Connect ending. The Bank Feeds Center shows the account as connected but downloads nothing, or throws a sign-in or OL-type error that was not there before. And it started right around the end of October 2026. If instead a single account broke earlier and the rest are fine, that is usually a password or a bank-side change, not this retirement.

What happens to bill pay?

This is the part that catches people. Direct Connect bill pay, paying vendors from inside QuickBooks Desktop through the bank connection, goes away with Direct Connect. Web Connect only carries transactions one direction, from the bank into QuickBooks, so it cannot replace bill pay. If you paid bills that way, move that workflow to your bank's own bill pay site or a dedicated payables tool before the cutoff so nothing gets missed at month-end.

Option 1: switch the account to Web Connect

For most Desktop users this is the direct replacement. Log in to your bank's website, find the option to download activity for QuickBooks, and choose the Web Connect or .qbo format for your date range. Back in QuickBooks Desktop, go to Banking, then Bank Feeds, then Import Web Connect Files, and select the file. The transactions land in the same Bank Feeds review area you already use. It is a few clicks instead of an automatic sync, but it keeps working indefinitely and imports a full statement in one pass.

Option 2: convert a CSV export to .qbo

Some banks, and a lot of credit unions, do not offer a QuickBooks-format download at all. They give you a CSV or Excel file and nothing else. QuickBooks Desktop cannot import a CSV of transactions in any version, so a raw CSV is a dead end on its own. The way through is to convert the CSV to a .qbo Web Connect file first, then import it exactly like Option 1. You can do that in seconds with the CSV to QBO converter built for the Direct Connect switch, which reads the file your bank gives you and writes the .qbo Desktop accepts. Upload one statement in the converter at the top of this page to see the output before you commit to it.

This route has an upside over the old feed: a single .qbo can hold a full year of history, so cleaning up a backlog after a broken feed is one import per account rather than a month-by-month slog. If your only copy of an old statement is a PDF, you can turn the PDF statement into a spreadsheet first, then convert that to a .qbo.

Will QuickBooks Online users be affected?

No. QuickBooks Online never used Direct Connect. Its bank feeds run through an aggregation service, so QBO company files keep downloading transactions the same way after October 30, 2026. If you have been weighing a move from Desktop to Online, this deadline is a reasonable trigger to evaluate it, but it is not forced. Plenty of firms are staying on Desktop and simply moving those accounts to Web Connect and .qbo imports.

What should I do before the deadline?

Do three things now rather than in November. First, list which accounts currently use Direct Connect, so you know exactly what will go dark. Second, confirm for each one whether the bank offers a Web Connect (.qbo) download or only a CSV, because the CSV accounts need the conversion step. Third, move any Direct Connect bill pay to another method. Handle those before the last week of October and the retirement becomes a non-event instead of a month-end fire.

Frequently asked questions

Will I lose my existing transactions when Direct Connect ends?

No. Everything already downloaded stays in your company file. Only the automatic download stops. You keep every past transaction, reconciliation, and report.

Is Web Connect being retired too?

No. Intuit is retiring Direct Connect only. Web Connect, the .qbo import method, continues to work and is the recommended replacement for downloading transactions into QuickBooks Desktop.

My bank only gives me a CSV. Can I still use bank feeds?

Yes, indirectly. Convert the CSV to a .qbo file and import it through Bank Feeds, Import Web Connect Files. QuickBooks Desktop cannot read a transaction CSV directly, but a converted .qbo imports normally and matches in the same review screen.

For the full timeline and what changes for Quicken, see our explainer on whether QuickBooks Direct Connect is being discontinued.