8 QuickBooks Bank Feed Breaks After MFA Updates

Your bank rolls out stronger login security, and the next time you open QuickBooks the bank feed has gone quiet, no new transactions, maybe a “needs attention” flag or a cryptic error code. It is one of the most common accounting headaches of 2026, as banks add multi-factor prompts and device verification that automated connections were not expecting. The reassuring part: almost every one of these breaks is something you can fix yourself in a few minutes. Here are the eight that come up most, and the fix for each.

QuickBooks pulls your transactions by logging into your bank on your behalf, so anything that changes how that login works, a new one-time code, a device check, a moved account, tends to stop the feed until you re-authorize it. That is why a security upgrade you never touched can break the connection. Work down this list in order and you will usually have transactions flowing again without a support call.

Quick Answer

When a bank MFA update breaks a QuickBooks feed, start by running a manual update and completing the one-time code or security question the bank now asks, which is what error 185 means. If that fails, re-enter your current bank credentials, then disconnect and reconnect the account to force a fresh authorization, which also clears expired-connection errors like 350 and 324. Make sure QuickBooks is approved in your bank’s data-sharing settings, approve any new-device verification at the bank directly, and answer any new security questions. If repeated attempts locked your bank login, unlock it at the bank first. Finally, read the specific error code, since each points to its exact fix, and import transactions manually as a stopgap while you sort it out.

Why stronger bank MFA breaks QuickBooks feeds

A bank feed is an automated login. QuickBooks, or the data aggregator behind it, signs into your bank with your credentials and downloads transactions on a schedule. When a bank adds multi-factor authentication, device verification, or new security questions, it inserts a step that a scheduled, unattended login cannot answer on its own, so the connection stalls until you complete that step once, interactively. Many banks have also moved to token-based open-banking connections that expire and must be renewed periodically, which is why a feed that worked for a year suddenly asks you to reconnect. None of it means your data is lost; it means the bank now wants a fresh, verified handshake before it keeps sharing.

This article is general information, not financial, accounting, or security advice. Steps and error codes vary by bank and QuickBooks version and change over time. Verify current instructions with your bank and Intuit, never share your banking credentials with untrusted parties, and consult your accountant about reconciling transactions after a feed interruption.

The 8 fixes

1. Run a manual update and complete the new prompt. In the Banking screen, click Update, and when the bank asks for a one-time passcode or a security question, enter it. A bank that now requires a code each time produces error 185, and entering the code each time it appears is the fix.
2. Re-enter your current bank credentials. The feed uses your online-banking login, so if you changed your username or password during the security update, update them in QuickBooks’ connection settings, or the automated sign-in will keep failing.
3. Disconnect and reconnect the account. Relinking forces a fresh, fully verified authorization and clears most post-MFA breaks, including error 350, which appears when a connection expires. Your already-imported transactions and reconciliations stay intact when you reconnect.
4. Approve QuickBooks in your bank’s data-sharing settings. Many banks now have a connected-apps or data-sharing section where you authorize third-party access. Open it, and make sure QuickBooks or its aggregator is approved and has not been revoked during the security change.
5. Approve the new-device verification at the bank. Log into your bank directly on the web and approve any “new device” or extra verification prompt, so the automated connection is treated as trusted, then return to QuickBooks and run the update again.
6. Answer new or changed security questions. If the bank added security questions, answer them when QuickBooks prompts, or set them at the bank first. An unanswered security question quietly blocks the automated login even when your password is correct.
7. Unlock a bank login locked by failed attempts. Repeated failed sync attempts can lock your online-banking account. Log into the bank directly to confirm and unlock it, wait a little while, then reconnect in QuickBooks rather than hammering Update.
8. Match the error code to its fix. QuickBooks names the problem: 185 means a one-time code or security answer is needed, 108 means there is a message to read on the bank’s own website, 324 means the account moved and must be reconnected, and 350 means the connection expired. Read the code and follow its specific step.

When the feed still won’t connect

Sometimes you run the whole list and the connection still refuses, which usually means the issue is on the bank’s side or the bank is mid-migration to a new connection method. Two moves keep you working in the meantime. First, import transactions manually: most banks let you download a CSV or a QuickBooks-compatible file of recent activity that you upload into the Banking screen, so your books stay current while the automated feed is down. Second, check the timing, since some banks require reconnection every 90 business days or so, and a maintenance window or a just-launched security change can take a day to settle. If it persists beyond that, contact your bank to confirm third-party data sharing is enabled for your account, and then Intuit support, because a genuinely broken connection on their end needs their fix, not yours.

Main Takeaways

• Bank feeds break after MFA updates because an automated login cannot answer a new one-time code, device check, or security question on its own.
• Start with a manual update and enter the one-time code or security answer, which resolves error 185, the classic MFA break.
• Disconnecting and reconnecting forces a fresh authorization and clears expired-connection errors like 350 and 324 without losing your data.
• Approve QuickBooks in your bank’s data-sharing settings and approve any new-device verification at the bank directly.
• Read the specific error code for its exact fix, and import a CSV manually to keep your books current while the feed is down.

For more small-business and accounting tips, browse the DelightfulBlogs Business section, or follow our Finance desk.

Frequently Asked Questions

Why did my QuickBooks bank feed stop after my bank added MFA?

Because the feed is an automated login, and multi-factor authentication adds a step, a one-time code, device check, or security question, that a scheduled connection cannot complete on its own. The feed stalls until you complete that verification once, interactively. Running a manual update and entering the code the bank now asks for usually restores it.

What does QuickBooks error 185 mean?

Error 185 means your bank is asking for additional verification, typically a one-time passcode, after your credentials. When you see it, get the code from your bank via text, call, or app, and enter it in QuickBooks. Because some banks send a new code each time, you may need to repeat this each time the error appears until the connection settles.

Will reconnecting my bank delete my transactions?

No. Disconnecting and reconnecting an account re-authorizes the connection but keeps the transactions you have already imported and any reconciliations. It is one of the safest and most effective fixes for a broken feed, especially after a connection expires, and it is often faster than troubleshooting the old link.

How do I keep my books current while the feed is down?

Import transactions manually. Most banks let you download recent activity as a CSV or a QuickBooks-compatible file, which you upload in the Banking screen. This keeps your bookkeeping up to date while you sort out the automated connection, so a feed outage does not leave a gap in your records.

The feed still won’t connect after everything. What now?

It is likely on the bank’s side. Confirm with your bank that third-party data sharing is enabled for your account and that no security block is in place, since a recent change can take a day to settle. If it persists, contact Intuit support, because a genuinely broken connection on their end requires their fix rather than more attempts from you.

The Bottom Line

A QuickBooks feed that dies after a bank security update looks alarming and is almost always fixable from your side. The bank simply wants a fresh, verified handshake, so the fixes are all variations on completing that verification: run an update and enter the code, re-enter your credentials, or reconnect the account, and check that data sharing is approved at the bank. Read the error code for the exact step, keep your books moving with a manual import if needed, and escalate to your bank and Intuit only when the whole list comes up empty. Most of the time, a few minutes gets your transactions flowing again.