QuickBooks bank feed issues
QuickBooks bank feed issues
Feed not importing right? Here's the fix.
QuickBooks bank feed issues are downloaded transactions that stop importing, arrive twice, or land in the wrong category. Reconnecting the feed and cleaning up a few recent items is usually a do-it-yourself fix; months of duplicated or miscategorized transactions need a cleanup so your reports and reconciliation can be trusted again.
Last reviewed October 2026 by a Certified QuickBooks ProAdvisor
- Free, view-only review first
- Every fix re-reconciled
- One specialist — never a rotating pool
Which do you need?
Start with what the feed is doing
Start here
What is your bank feed doing?
STOPPED IMPORTING
Reconnect it yourself
A dropped connection usually just needs the feed disconnected and re-authorized at your bank — no specialist required.
IMPORTING DUPLICATES
Dedupe, then decide
A few recent duplicates you can delete yourself; months of them across accounts is a cleanup.
See duplicate transactionsMISCATEGORIZED FOR MONTHS
Cleanup
When bank rules mislabeled transactions for months, every wrong entry has to be recategorized and re-reconciled.
See QuickBooks cleanup
Read this as text
- STOPPED IMPORTING: Reconnect it yourself — A dropped connection usually just needs the feed disconnected and re-authorized at your bank — no specialist required.
- IMPORTING DUPLICATES: Dedupe, then decide — A few recent duplicates you can delete yourself; months of them across accounts is a cleanup.
- MISCATEGORIZED FOR MONTHS: Cleanup — When bank rules mislabeled transactions for months, every wrong entry has to be recategorized and re-reconciled.
Honest answer
Who this affects
A bank feed problem is not the same as a bookkeeping problem, and most feed hiccups don't need a specialist at all. Feeds drop their connection when a bank changes its login, adds a security step, or times out — an inconvenience, not damage to your file. If your books were reconciled through last month and the feed simply stopped last week, you're looking at a reconnection, not a cleanup.
Where it turns into real work is when a broken or misconfigured feed ran unnoticed for months. Duplicates accumulate when the same transactions are imported twice, or entered manually and then imported again. Miscategorization compounds when a bank rule quietly files dozens of transactions under the wrong account. In both cases the feed is only the source — the fix lives in the transactions it created, which is why this crosses over into cleanup.
Intuit's own order of fixes — gentlest first
- Update manually. In QuickBooks Online: All apps → Accounting → Bank transactions → Update (Intuit, updated August 2026, checked October 2026). Most banks send transactions to QuickBooks about once a day.
- Try a private or incognito window and update again, which rules out the browser.
- Sign in to the bank's own website and look for alerts, new security requirements or maintenance notices; QuickBooks also shows a notice on the banking screen when Intuit knows of a bank issue, and Intuit says outages usually clear within 24–48 hours.
- Update the sign-in details if anything changed at the bank: the account card → Edit → Edit sign in info → Save and connect. Error 103 is usually this (Intuit).
- Only then disconnect and reconnect — carefully. First add or match everything in the Pending tab: Intuit says disconnecting removes pending transactions, that anything older than 90 days can't be downloaded again, and that a reconnect can create a new account with its own opening balance (Intuit).
Do-it-yourself
When you can fix it yourself
The For Review decision
Read this as text
A downloaded item sits in the For Review tab. If it's already entered in your books, Match ties it to that entry — one register line. If it's genuinely new, Add posts it once. If the real transaction is already recorded and the download isn't needed, Exclude drops the copy. Clicking Add on top of an existing entry is how duplicates start.
For a feed that just stopped, reconnecting is a do-it-yourself fix. In QuickBooks Online, edit the account on the banking screen, disconnect it, and reconnect through your bank so the feed re-authorizes; in Desktop, deactivate bank feeds for the account and set them up again. If Desktop refuses with a specific code along the way, error OL-301 is the connection failing and error OLSU-1013 is the online-banking setup failing — each has its own walkthrough. Transactions that downloaded while the feed was down can be imported with a .QBO or .CSV file from your bank if needed.
For a handful of recent duplicates, you can clean them yourself too: match or exclude the copies in the For Review tab before you accept them, and delete any that already posted. Do this before you reconcile, and check the register against the statement as you go. The moment the duplicates or miscategorized entries stretch back months — or you've already reconciled around them — stop, because unwinding that safely is what a cleanup is for. Deleting reconciled transactions to start fresh usually makes the next reconciliation worse.
How the bank-feed cleanup is documented
Who’s responsible for your file
A Certified QuickBooks ProAdvisor handles your file from the review through the corrections to the hand-back — the same person throughout, never a rotating pool.
About QBSpecialist
Illustrative example — not a client file.Sample before-and-after
The corrected register and reconciliation report you receive once duplicate and miscategorized feed entries are cleared.
How we work
Every corrected transaction re-reconciled to the statement. Read the method.
Read the reconciliation referenceResponse commitment
A written reply within one business day.
Remote-first, nationwide
Mon–Sat · 8am–6pm CT
We work entirely remote — view-only access for the free review, QuickBooks' accountant access if you hire us to clean up what the feed created, every change visible to you in the audit log, and every corrected month documented in writing.
- All 50 states
- Remote-first
- View-only review
Questions about bank feed issues
Why did my bank feed stop importing?
Almost always a connection issue on the bank's side — a changed password, a new security prompt, or a maintenance window. Updating the sign-in or answering the new security prompt usually restores it; disconnecting is the last resort, and only once the Pending tab is cleared, because Intuit says disconnecting removes any transactions still in Pending.
Why is my bank feed importing duplicates?
Duplicates happen when the same transactions are downloaded twice, or entered by hand and then imported. QuickBooks tries to match them, but overlapping date ranges or a re-added account defeat that. A few you can delete; months of them is a cleanup.
Why is my bank feed missing transactions?
Feeds skip items when the connection drops mid-download, and a newly connected account only pulls a limited window of history — often around 90 days. Fill the gap by importing a .QBO or .CSV file from your bank, then reconcile against the statement: that's the check that catches anything the feed missed.
Can I just delete everything and re-import the feed?
Not safely once you've reconciled. Deleting reconciled transactions breaks the reconciliation behind them and usually creates more work than it saves. Corrections should be made transaction by transaction, then re-reconciled to the statement.
Why does the feed keep miscategorizing transactions?
A bank rule is matching too broadly. Rules auto-assign a category from the payee or description, so one loose rule can mislabel dozens of transactions. Tightening the rule fixes it going forward; the already-miscategorized history still has to be corrected.
Is a bank feed the same as reconciling?
No. The feed imports transactions; reconciliation proves your books match the statement line by line. A feed can import cleanly and still leave you unreconciled, and a broken feed doesn't excuse skipping the reconciliation — that's the check that catches what the feed missed.
Should I disconnect and reconnect the bank account?
Only after the gentler steps fail, and only once the Pending tab is cleared. Intuit's help says disconnecting removes any transactions still in Pending, that transactions older than 90 days can't be downloaded again, and that a reconnect can arrive as a brand-new account with its own opening balance. If the account shows a connection error, fix the error first, or the reconnect may download duplicates.
What do bank error codes like 103 or 179 mean?
They come from the connection, not your books. Intuit's banking help ties 103 to a wrong user ID or password at the bank, 179 to being signed in to the bank elsewhere, 187 and 192 to security questions or one-time passcodes, 102 and 105 to a problem on the bank's side, and 323 to an account added twice. The fixes are Intuit's — our part is the books afterwards.
Where to go next
- QuickBooks reconciliation services— Tie every account to its statement, difference to zero.
- File repair— when the feed problem is really a damaged company file
- Second opinion— an independent read of what the feed has already posted
- QuickBooks errors— if the feed stops with an error code, the code points to the fix
Not sure how bad it is?
Talk to a QuickBooks specialist.
Describe the file and a specialist will tell you which of these you are dealing with — including when the answer is that you don't need us.