How to Fix QBO Bank Feed Sync Errors and Duplicate Transactions (Without Breaking Reconciliation)
Your bank feed drops, reconnects, and suddenly the same $412.18 charge is sitting in your For Review tab twice. Before you start deleting things, read this. The wrong cleanup is what breaks a reconciliation, and the right one takes about ten minutes.
Receipts first: who to trust on this topic
Search this problem and most of the first page is “support number” bait: free-hosted pages and blog posts stuffed with phone numbers. Don’t call a number you found on one of those pages. Go through Intuit’s own support pages or a real QBO Payments advisor.
Intuit’s own explanation is plain: QBO relies on the bank to decide which transactions get pulled in, and updates to the bank’s connection can occasionally produce duplicates. QuickBooks is the receiving party, so most “duplicates” are the bank re-sending data after a connection reset, not QBO making things up. Other common causes:
- Two connections to the same account
- A manual CSV upload that overlaps with the automatic feed
- Rematching after a reconnect
Step 1: Fix the connection before you touch transactions
Cleaning up duplicates while the feed is still unstable just invites a second wave. Work through these in order and stop when the feed behaves.
- Check the bank itself. Log in at your bank’s site. If the bank is down, locked your login, or is pushing a security prompt, QBO can’t fix that from its side.
- Run a manual refresh. Go to Banking, select the account, and click Update. Let it finish completely before clicking anything else.
- Rule out your browser. Open QBO in an incognito window or a different browser. If it works there, clear the cache and cookies in your main browser and restart it.
- Re-authorize the connection. If the account shows a warning or error, update the credentials or complete the bank’s MFA prompt. Don’t disconnect and reconnect unless you have to.
- If you must reconnect, do it once. Confirm no duplicate connection to the same account is hiding in your Banking setup. Two live connections to one account guarantees repeat downloads.
Menu names shift between QBO versions and layouts, so if a label doesn’t match, look for the closest equivalent in Banking.
Step 2: Clean up duplicates in the right order
Where the duplicate sits decides what you do with it.
Duplicate is still in For Review (not added yet): Select it and click Exclude. Don’t add it. Excluding keeps the transaction out of your books without deleting anything, and it’s the cleanest fix.
Duplicate was already added or matched, and that period isn’t reconciled: Go to the Reviewed/Categorized view, select the transaction, and click Undo to send it back to For Review. Then exclude it. If it’s a true double entry in the register, you can delete the extra one there.
Duplicate sits inside an already-reconciled period: Stop. Don’t delete or void a cleared transaction. That is how reconciliations break. Run the Reconciliation Discrepancy report first to see what changed, and have your accountant weigh in before undoing anything in a closed period.
The rule to remember: exclude from the feed instead of deleting matched transactions from the register.
Step 3: Where bank rules fit
Bank rules don’t fix sync errors. They categorize and sort what comes in, and they have no way of knowing a transaction is a duplicate.
The risk is rules set to auto-add. If a duplicate wave hits, an auto-add rule will happily book every copy. During a cleanup, switch affected rules to categorize only, review everything, then turn auto-add back on once the feed is stable. After that, rules are what keep your feed clean month to month.
Step 4: The QBO Payments double-count trap
This one is specific to payment processing and gets missed constantly. Deposits from QuickBooks Payments land in your bank feed as lump sums, while the individual customer payments already exist in QBO. If you add the feed line as a new deposit instead of matching it to the existing Payments deposit, your income gets counted twice. The books look like a feed duplicate even though the feed is fine.
Always match a Payments deposit to the existing record. Only add a new transaction when nothing exists to match.
Want to see what your processing is really costing you while you clean up? Run your numbers through the free QuickBooks Payment Fees Calculator, then read Is QuickBooks Payments Worth It in 2026? and the hidden invoice settings that can cost you thousands a year.
Step 5: Stop it from coming back
- Keep one connection per bank account.
- Don’t upload a CSV for dates the feed already covers.
- Choose a sensible start date when you reconnect, so old history doesn’t re-download.
- Reconcile every month so any problem gets caught within 30 days.
- Review For Review weekly instead of letting it pile up.
The bottom line
Fix the connection first, exclude duplicates instead of deleting them, never touch cleared transactions without checking the discrepancy report, and always match QBO Payments deposits instead of adding them.
Stuck on a payments or bank feed problem you can’t untangle?
Get a real person on it. Request a quote on the QuickBooks Payments consulting page and your case gets reviewed before any quote goes out. Or start with the free fee calculator and QBO problem solver.
Published by TEG Digital LLC. General information, not accounting advice. Confirm steps against your own QBO screens.



Really enjoying the current promotions. The gameplay is fluid and the wins feel rewarding. Jump into pkq98 and see for yourself.