QuickBooks Bank Feed Not Working? Fix It Fast + Import Manually

Quick Answer

A QuickBooks bank feed usually stops working for one of four reasons: you changed your bank password or added two-factor authentication, the bank's servers are down, there's a pending message or agreement on your bank's website, or Intuit's connection to the bank is broken. Try the force update in section 2 first. If the feed stays dead, stop troubleshooting and import manually, month-end close doesn't wait for your bank.

Table of Contents

1. Why bank feeds break
2. Try these 5 steps first (QuickBooks Online)
3. Error code quick reference
4. QuickBooks Desktop: what's different
5. When to stop troubleshooting and import manually
6. Bank only gives you a PDF statement?
7. Clean up duplicate transactions
8. The 90-day limit trap
9. How to make feeds break less
10. FAQ

1. Why Bank Feeds Break

Match your symptom to the cause:

2. Try These 5 Steps First (QuickBooks Online)

Work through these in order. Most feeds come back after step 1 or 2.

Step 1: Force an update

In QBO, go to Bank transactions (left menu) and click Update in the top right. This makes QuickBooks try to sync right away instead of waiting for its automatic overnight pull (most banks update around 10 PM).

Step 2: Check your bank's website

More often than not, the problem is on the bank's side, not QuickBooks':

• Is there a pending agreement, security prompt, or alert on the bank site? (Banks pause data sharing until you act on these.)
• Did you recently change your password, phone number, or add two-factor auth?
• Is there a maintenance notice on the bank's site?

Step 3: Update your sign-in info in QBO

Bank transactions → click the edit icon on the account → Edit account sign in → enter the current credentials → Save and connect.

Step 4: Clear your browser cache

Sign out of QBO, clear browser cache and cookies, and sign back in. It sounds basic, but it fixes plenty of "stuck on the spinner" cases.

Step 5: Disconnect and reconnect the account

If nothing else works, disconnect the account and reconnect it. Don't worry: disconnecting does not delete transactions already in QuickBooks. One thing to know from Intuit's guidance: when you reconnect, choose the correct start date (the day the connection was lost) so QuickBooks can pull in the transactions it missed. If the gap is still missing afterward, download the missing period from your bank and upload it as a file.

3. Error Code Quick Reference

When QBO shows an error, it usually includes a number in brackets. Match yours:

• 101: Account inactive for 12+ months (zero balance, no transactions). Reactivate it on the bank site, then refresh the connection.
• 102 / 105: Problem on the bank's servers. Wait 24-48 hours; import manually in the meantime.
• 103: Wrong login details, or you connected to the wrong bank URL. Update credentials / retry with the correct URL.
• 106: Account is closed. Confirm, disconnect it in QBO, and add the new account.
• 108: Pending popup or agreement on the bank's website. Complete it, then refresh.
• 109: Bank requires an online password update. Update it and sync to QBO.
• 155: Bank no longer supports automatic connection (some banks dropped OFX direct connect). Use manual import, this is the officially recognized alternative.

Note: Error codes change over time. This is the most common set; always defer to Intuit's official documentation for the latest.

4. QuickBooks Desktop: What's Different

Desktop errors usually start with OL / OLSU (e.g., OL-202, OLSU-1011). The approach is similar to Online, with two extra steps:

1. Update QuickBooks Desktop first: Many OL/OLSU errors come from an outdated financial institutions directory (FiDir). Updating the software refreshes the bank directory.
2. Test in a new company file: Create a test company, set up Bank Feeds for the problem account, and try to download. If the test file downloads but your company file doesn't, the company file's account data is damaged, fix it with "create and merge accounts." If the test file fails too, the problem is on the bank's end; contact the bank.
3. QBD only opens .qbo files: QuickBooks Desktop only accepts downloaded transactions with the .qbo extension. If your bank exports a different format, QBD can't open it, download a .qbo file from the bank's website and import that.

5. When to Stop Troubleshooting and Import Manually

If you've gone through the steps and the feed is still dead, stop fighting it, especially during month-end close. Manual import is the officially recognized fallback, it's unaffected by the bank connection, and a single month of data takes a few minutes. (For a deeper look at the formats themselves, see our guide on QBO vs CSV vs OFX.)

Method A: Download a CSV from your bank (simplest)

1. Log in to your bank's website → download the transactions → choose CSV (most banks offer it)
2. In QBO: Bank transactions → Upload from file
3. Pick the account → map the columns (Date, Description, Amount) → import → review in the For review tab

Method B: Download QBO/OFX from your bank

QBO recognizes .qbo and .ofx files better (OFX keeps signed amounts, so categorization is more accurate). Same flow as Method A, just pick that format.

Method C: Backfill older transactions

The feed only reaches back 90 days (see section 8). Anything older must be imported manually.

6. Bank Only Gives You a PDF Statement? The Ignored Path

This is the scenario most guides miss: many banks, especially smaller banks, credit unions, and older accounts, don't offer CSV or QBO downloads at all. They only give you a PDF statement.

Feed down + PDF-only bank looks like a dead end. It isn't:

• A PDF statement can go into QBO, you just have to convert it to QBO/CSV first (note: QBO Online does accept a PDF upload directly, but it sends the statement to Intuit's cloud for AI extraction, which is the privacy tradeoff to weigh)
• After conversion, it follows the exact same import flow as Method A/B, with identical results
• Watch out for the converter you use: it must process locally, not upload to a server. Bank statements are the most sensitive data you handle. Nobody wants to send their transaction history to an unknown server just to reconcile.

As a company that builds a bank statement conversion tool, we work with these files every day. Testing taught us one thing quickly: statement formats vary wildly between banks, and even within the same bank. Chase personal and business accounts have completely different table structures. Wells Fargo is even more unpredictable; accounts from different states produce differently formatted PDFs. "The bank only gives PDF" is not an edge case, it's the norm, just rarely talked about.

Our workflow: get the PDF → convert to QBO locally → import to QBO → reconcile normally. We verify amounts and dates after conversion before importing. (If you deal with PDF-only banks often, see our step-by-step guide on how to convert PDF bank statements to QBO for QuickBooks.)

7. After the Feed Recovers: Clean Up Duplicates

The most common post-recovery trap: your manually imported transactions + the feed's newly downloaded ones = duplicates.

1. Go to Bank transactions → everything lands in the For review tab
2. Tick the duplicate transactions one by one → Exclude
3. Excluded items won't enter your books and won't download again

If you already imported them by mistake: find the transaction in the Excluded tab → Undo, then exclude the correct one.

8. The 90-Day Limit Trap

QBO's bank feed only reaches back 90 days. That's by design, not a bug:

• Transactions older than 90 days are never back-filled by the feed, you must import them manually
• So when you connect a new account, if the business had activity before the 90-day window, find the old statements and backfill them
• We've seen more than one user hit this trap: the account connects, the feed works, but the first few months of books are empty, because those months fall outside the 90-day window. The only fix is converting the historical PDF statements to QBO and importing them
• One real case we observed on r/QuickBooks: a user's account was off by $17k and they couldn't find why for a long time, it turned out the opening balance was never entered, because the historical data was never brought in. A lot of "numbers don't add up" problems trace back to data missing outside the 90-day window

9. How to Make Feeds Break Less (Prevention Checklist)

• Every time you change your password or phone number at the bank, update it in QBO the same day
• Clear any popup agreement on the bank's website the day it appears, don't let it pile up
• Force an update once a month instead of relying only on the overnight pull
• Reconcile on a fixed schedule (e.g., month-end) so feed problems surface early
• Keep PDF statement backups for important accounts, when a feed dies, that PDF is your fastest lifeline

10. FAQ

Why did my QuickBooks bank feed suddenly stop working?

The most common causes: credentials changed at the bank, a new two-factor step, a bank server outage, a pending agreement on the bank's site, or an Intuit-to-bank connection failure. Force an update first, then check the bank's website.

Will I lose transaction data if the feed breaks?

No. Disconnecting doesn't delete data already in QuickBooks, and after reconnecting the feed back-fills the gap. Exception: anything older than 90 days, which you must import manually.

Is manual import different from the bank feed?

The reconciliation result is the same, only the method differs. Manual import isn't affected by the bank connection and is the officially recognized fallback when a feed fails.

Does QuickBooks Online only pull 90 days of transactions?

Yes, the feed only auto-downloads the most recent 90 days. Anything older must be imported manually.

My bank only provides PDF statements, no CSV download. Can I still import to QuickBooks?

Yes. Convert the PDF to QBO/CSV format and import it. Prefer a converter that processes locally to avoid uploading your bank statements to a third-party server.

After reconnecting a disconnected account, will my manually imported transactions duplicate?

They can. Exclude the duplicates in the For review tab, this doesn't affect data already posted.

The Bottom Line

A broken feed is annoying, but it's never a dead end. Fix the connection when you can; when you can't, manual import gets the same transactions into QuickBooks without touching the feed at all. And if your bank only hands you a PDF, the case most guides skip, convert it locally and import it the same way. For a full comparison of tools that handle all of this, see our 7 Best Bank Statement Converters for 2026 review.