Guides · Troubleshooting
QuickBooks Online bank feed not updating or missing transactions: a checklist
When the QuickBooks Online bank feed stops updating or skips transactions, the cause is almost always one of a dozen known things. Work through this list in order; most feeds are fixed by step 3. Nothing here deletes data.
First, confirm what "missing" means
Before touching the connection, rule out the three cases that only look like a broken feed:
- Check the Categorized and Excluded tabs. Go to All apps › Accounting › Bank transactions, select the account tile, and look at Categorized (sometimes Posted) and Excluded. An auto-post rule moves rows straight to Categorized with an AUTO badge; a past batch exclude puts them in Excluded. Neither is a download problem.
- Check the date filter. The All dates dropdown remembers your last choice. Set to a past month, this week's rows are downloaded but hidden.
- Check the account tile. Two tiles for the same card (common after a reconnect) means the rows may be on the other one. Each tile shows its last update date under the balance.
Step 1: run a manual update
QuickBooks downloads new transactions every night, starting around 10 PM Pacific for most banks, with up to five retries over the following hours. American Express and a few others send data less often, sometimes two or three times a week. If the tile's last update is older than that, select Update on the Bank transactions page. If the bank asks for multi-factor authentication, enter it and choose Continue update. It can take a few minutes.
Step 2: understand what the bank sends
QuickBooks can only download what the bank's data connection publishes. Two consequences:
- Pending transactions at the bank do not download. A card swipe still pending on the bank's site appears in QuickBooks after it posts, typically one to three business days later. Compare against the bank's posted list.
- History is limited. Download windows run from 90 days to 24 months depending on the institution. Older transactions never arrive through the feed and need a file upload (step 8).
Step 3: check the bank's side
Sign in to the bank's website directly. If you cannot, the feed cannot either. Look for banners about maintenance, a forced password change, new terms to accept, or a security alert; each blocks the connection until a human clears it on the bank site. Then run Update again. Intuit's guidance is that bank-side issues usually resolve within 24 hours; past that, ask the bank whether third-party aggregator access is enabled on the account.
Step 4: read the error code on the tile
A failing connection shows a message or numbered error on the tile. The common codes in practice:
| Code | Meaning | What to do |
|---|---|---|
| 102 / 105 | The bank's site is down, under maintenance, or its layout changed and Intuit's connection has not caught up | Wait, retry Update after a few hours, confirm you can sign in at the bank |
| 103 | The sign-in details QuickBooks has stored are rejected | Update the credentials on the tile (step 5) |
| 106 | The account was closed or is no longer visible under that login at the bank | Confirm at the bank; disconnect the tile if the account is closed |
| 108 | The bank is showing a message that must be acknowledged on its own site (new terms, a notice) | Sign in at the bank, dismiss the message, then Update |
| 185 / 187 / 324 | Multi-factor authentication is required or the account could not be found after sign-in | Run Update and complete the MFA prompt; check the account is still listed at the bank |
| Any error for over 48 hours | Likely a connection the bank has changed (merger, new online banking platform) | Reconnect (step 6) |
Codes and wording change; treat the message on the tile as authoritative.
Step 5: fix stored sign-in details
If the bank password changed, QuickBooks keeps trying the old one until you update it. On the tile, open the edit (pencil) menu, choose the option to edit sign-in information, enter the new credentials and complete any MFA step. History stays intact; this is not a disconnect.
Step 6: disconnect and reconnect, the right way
Reconnecting cures most stubborn connections, including after a bank merger or platform change. Done wrongly it creates duplicates, so follow this sequence:
- Finish or note any rows still in For review for that account; disconnecting removes them. Transactions already in your books are untouched.
- On the tile, open the edit (pencil) menu, choose Edit account info, tick Disconnect this account on save, and save.
- Select Link account, search for the bank (after a platform change the listing may have a new name), sign in and complete MFA.
- When asked which Chart of accounts entry to connect to, choose the existing account. Choosing "create new" is how duplicate tiles happen.
- Set the date range start to the day after the last transaction already in that register. Starting earlier re-downloads rows you already have, and each will need excluding.
Step 7: look for a duplicate account
Open Chart of accounts and search for the bank's name. Two accounts with the same name, one showing a bank balance and one not, means a past reconnect created a second account. Decide which holds the history, disconnect the other, and merge by editing the empty one to the exact name of the other.
Step 8: upload what the feed cannot provide
For history beyond the bank's window, or the gap while a connection was down, export a file from the bank and upload it: open the Link account dropdown and choose Upload from file. QuickBooks accepts CSV, QBO, QFX, OFX and TXT files up to 350 KB and 1,000 lines per upload; a CSV needs three or four columns (date, description, one amount column or separate debit and credit columns). Pick the right QuickBooks account on the mapping screen and trim the file to exactly the missing dates so the feed and the upload never overlap. Uploading a PDF or image of a statement is also supported.
If it is still not working
At this point the problem is on Intuit's side or the bank's, not in your file. Intuit publishes a bank feed status page for known outages; if your bank is listed, no action is needed. Otherwise contact Intuit support from inside QuickBooks with the error code, bank name and date of the last successful download. Bridge the gap with a file upload and reconcile against the statement as normal.
A note on what comes next
Once the feed flows again there is usually a backlog. Clearing the For review tab faster covers filters and batch actions in native QuickBooks; the bank rules guide stops the same vendors returning unrecognised. For heavy backlogs, Rowpost, a free Chrome extension, adds keyboard review and bulk add with confirmation to the same table.
Frequently asked questions
How often does QuickBooks Online update the bank feed?
Automatically once a night for most banks, starting around 10 PM Pacific time, with up to five retries over the following hours. Some institutions, notably American Express, send data only two or three times a week. You can trigger a manual update at any time with the Update button on the Bank transactions page.
Why are pending transactions at my bank not in QuickBooks?
Banks only publish posted transactions to the feed. A charge that still shows as pending on the bank's site arrives in QuickBooks after it posts, usually within one to three business days.
How far back does the bank feed download when I connect an account?
It depends on the bank. Download windows range from 90 days up to 24 months, and you pick the start date from the date range dropdown when connecting. Anything older has to be uploaded from a CSV, QBO, QFX, OFX or TXT file.
Will disconnecting and reconnecting a bank account delete my transactions?
No. Transactions already added to your books stay. Rows still waiting in For review for that account are removed, so finish or note them first, and when reconnecting choose the existing account and a start date after your last recorded transaction to avoid duplicates.