QuickBooks Bank Feed Error Codes: 103, 105, 324, 350 Fixed

Most QuickBooks bank feed error codes fall into two buckets: your saved login no longer matches what the bank expects (103, 350, connection lost), or something changed on the bank's side that QuickBooks can't work around on its own (105, 324, 377, 590). A handful of banks and credit unions, including some that block the screen-scraping connections QuickBooks relies on, will never connect cleanly no matter what you try. When a fix doesn't exist, the fallback that always works is downloading the PDF statement and converting it to a .qbo file for a direct import, which sidesteps the live connection entirely.

Last updated July 2026.

What is QuickBooks error 103?

Error 103 means the bank rejected the username or password QuickBooks sent on your behalf, even if you're sure it's correct. It usually happens because the saved credential in QuickBooks is stale, or because the bank now requires you to explicitly turn on third-party access before any outside app, including QuickBooks, can sign in.

How do I fix QuickBooks error 103?

Open a private browser window and log in directly at your bank's website to confirm the password still works on its own. While you're there, look for a security or third-party access setting and turn it on if the bank asks for it. Back in QuickBooks, go to Bank transactions, select the account, open Edit account sign in, and re-enter the credentials, clearing any auto-filled fields first since browsers sometimes insert an old saved password. If it still fails after that, try again from an incognito window before assuming it's a bigger problem.

What does QuickBooks error 105 mean?

Error 105 means the problem is on the bank's side, not yours. The bank's website may be down for maintenance or running into its own server issues, so QuickBooks simply can't get through to request your data. There's no setting inside QuickBooks that resolves this because QuickBooks isn't the one having trouble.

The only real move is patience: try signing in at the bank's own website to confirm it's actually having problems, then wait a few hours and run Update again from Bank transactions. Intuit's own guidance notes these can take 24 hours or longer to clear on the bank's end. If the transactions you need can't wait, you don't have to sit on your hands. Skip ahead to how to get missing transactions in while the feed is down.

What is QuickBooks error 324?

Error 324 means QuickBooks can no longer find the account it used to see at your bank. This almost always follows a change on the bank's end, a new account number after a card reissue, a platform migration, or the bank simply dropping that account out of the feed it shares with third-party software like QuickBooks.

To fix it, find the account showing the error and select Fix now, then sign in with your current bank credentials. When the bank asks which accounts to share, choose All Accounts rather than just the one you need, since QuickBooks needs the full list to map the account correctly. If a new account number shows up that clearly corresponds to your old one, map it to the existing QuickBooks account rather than creating a new register.

Why does QuickBooks keep saying the connection has been lost?

This message means QuickBooks had a working link to your bank and it broke, most often because the login expired, the bank changed its online banking platform, or (in QuickBooks Desktop) a corrupted network component is interfering. It's a step beyond a simple update failure: the account tile itself shows disconnected rather than just stale.

In QuickBooks Online, look for the disconnected tile on the Bank transactions page and select Link account next to it, then sign in again. In QuickBooks Desktop, run the QuickBooks Tools Hub, use the Network Issues tab if the file is on a server, and confirm your firewall isn't blocking QuickBooks. If reconnecting keeps looping back to the same error, that's usually a sign the bank itself is mid-migration and the fix isn't available yet; see the fuller troubleshooting rundown in QuickBooks won't connect to your bank.

What if my bank never connects at all?

Some institutions simply will not connect to QuickBooks, and no amount of troubleshooting changes that. A number of credit unions never signed on to a bank feed provider, and at least one large one, PenFed, has actively blocked the screen-scraping connections QuickBooks depends on, so the app can't sign in even with correct credentials. If your institution falls into that category, the connection isn't broken, it's unsupported, and the fix below is the path forward. See getting a credit union statement into QuickBooks and, for that specific bank, PenFed statements to QuickBooks.

How do I get the missing transactions in while the feed is down?

Download the statement PDF (or a photo of it, if that's all you have) covering the missing dates, then run it through a PDF to QBO converter that turns the statement into a QuickBooks Web Connect file. In QuickBooks Online, go to Transactions, then Bank transactions, select Upload from file, and pick the .qbo. In QuickBooks Desktop, use File, then Utilities, then Import, then Web Connect Files. Either way, the transactions land dated and ready to categorize, just like a live feed would have delivered them, without waiting on the bank.

The converter on this site reads PDF and image statements only, not CSV, QFX, or OFX files you already have, and it outputs both the .qbo for QuickBooks and a matching Excel or CSV file so you can check the totals against the statement balance before you import anything. That check matters: it's the difference between catching a misread transaction on screen and catching it three weeks later during reconciliation. For a full walkthrough, see importing bank statements into QuickBooks, and if the outage left a gap in an account that's otherwise connected, adding missing bank transactions in QuickBooks covers filling just that hole.

If you just need the numbers in a spreadsheet to eyeball what the feed missed before deciding whether to import at all, a PDF to Excel converter does that in one step without touching QuickBooks yet.

Frequently asked questions

Do I need to call QuickBooks support for every bank error?

No. Errors 103, 324, and 350 are almost always something you can fix yourself by re-entering credentials or reconnecting the account. Reserve a support call for errors that persist for several days with no bank-side explanation, or for account-specific problems the standard fix steps don't resolve.

Will reconnecting my bank account create duplicate transactions?

It can, if QuickBooks re-downloads dates it already imported. Before you disconnect and reconnect, note the date of the last transaction that came in successfully, and after reconnecting, check the new batch for overlap before you accept it into the register.

How long should I wait before treating a bank error as unfixable?

Give bank-side errors like 105 and 590 a few hours to a full day, since Intuit's own guidance says these can take up to 24 hours to clear. If the same error is still showing after two or three days and your bank's own website works fine, treat it as a connection that needs manual troubleshooting or a workaround rather than more waiting.

Can I avoid bank feed errors entirely?

Not entirely, since most of these errors originate on the bank's side of the connection. You can reduce how often they disrupt your bookkeeping by having one person manage the connection credentials, choosing All Accounts whenever the bank asks what to share, and keeping a converted .qbo import as a fallback habit rather than a last resort.

Does QuickBooks Desktop get the same error codes as QuickBooks Online?

Some overlap, like 103 and 105, but QuickBooks Desktop also has its own OL and OLSU error series tied to Web Connect files specifically, and the connection has been lost message can point to a local network or file issue rather than the bank. If Desktop bank feeds stop working generally, start with the broader guide to QuickBooks bank feed not working.

What's the fastest way to catch up if a bank error has blocked the feed for weeks?

Pull the PDF statements covering the gap directly from your bank's website, since most banks let you download several months at once even without a live QuickBooks connection. Convert each one to .qbo and import them in order. This is usually faster than waiting on a bank error to resolve itself, and it works whether the account eventually reconnects or not. Start from the homepage if you haven't converted a statement here before.