Duplicate Bank Feed After Reconnecting in QuickBooks Online: How to Fix It Without Losing Your History
I Reconnected My Bank in QuickBooks and Now I Have 15 Months of Duplicate Transactions
Hi, I'm Elena. And before we do anything, I want you to take a breath.
Here's the scenario I see at least twice a month:
"I updated my bank credentials in QuickBooks because the feed disconnected. Now I have what looks like every transaction from the last year and a half in my bank feed again. My bank balance is off by thousands. Did I just destroy my books?"
You didn't destroy your books. But you do have a mess, and left unaddressed, it will make your Profit & Loss unreadable and your next reconciliation feel like a crime scene.
This is a different problem from the "I clicked Add on everything" scenario (that article is here if you landed in the wrong place). What we're dealing with today is a bank reconnect that re-downloaded months of transaction history that QuickBooks Online had already processed.
We're going to cover:
Why this happens — so you understand what you're actually dealing with
How to confirm the scale of the damage before you do anything drastic
How to disconnect the problem connection safely
How to bulk-exclude the duplicated feed lines
How to repair any reconciliation damage
When "start over" actually makes sense — and how to do it safely
Why Does Reconnecting a Bank Cause This?
When QuickBooks Online reconnects to your bank, it pulls a fresh batch of transaction history. The problem is it doesn't always know where to draw the line between "new data I haven't seen" and "data I already imported 11 months ago."
Common triggers for this exact problem:
Your bank changed its connection method — for example, switching from Direct Connect to Open Banking — and QuickBooks treated the reconnection as a brand-new account.
You accidentally linked the same account twice — creating two separate "cards" in your Banking screen for the same physical bank account.
You updated your banking credentials and QuickBooks re-imported the full allowable history window (sometimes 90 days, sometimes 12–18 months depending on the bank's API).
Your bank sends pending transactions and cleared transactions as separate items, which can look like duplicates even without any reconnect issue.
The Reddit thread that put this problem on my radar had a user with 8 months of duplicates burning through hours with support every time they called. Another Intuit community post showed a bookkeeper whose client woke up to 15 months of re-imported transactions after a routine bank update — with no warning, overnight.
If that sounds familiar, you're in exactly the right place.
Step 1 – Confirm What You're Actually Dealing With
Before you start deleting or excluding anything, spend 10 minutes understanding the scope of the problem. Rushing this step causes more damage than the original error.
Check Whether You Have One or Two Bank Connections
Go to Banking / Transactions → Bank transactions.
At the top of the screen, you'll see "cards" for each connected account.
Ask yourself:
Do you see two cards for the same bank account (same bank name, same last four digits)?
If yes, you have a duplicate bank connection — the most common cause of this flood.
If you only see one card, the issue is more likely a re-import from the reconnect, not a doubled connection.
Make a note of which card was there first (often the one with correctly reconciled history) and which one appeared after the reconnect.
Count How Far Back the Damage Goes
In the For Review (Pending) tab of the affected account:
Use the date filter to see the earliest transaction in the queue.
Compare that date to the last date you successfully reconciled.
If the pending queue contains transactions going back further than your last reconciliation, those are almost certainly re-imported duplicates of data already in your books.
Write down: "Duplicates appear to start from [date] through [date]." This becomes your cleanup boundary.
Verify Against Your Bank Register
Open your Chart of Accounts → View register for the affected account in a second tab.
Scroll to the date range that matches your pending queue. Ask:
Are those transactions already recorded in the register?
Do they show up as "Matched" or "Added" with dates matching the pending items?
If the register already has them, you are looking at confirmed duplicates in the feed — not new transactions you need to process.
Step 2 – Disconnect the Extra Bank Connection (If You Have Two)
If Step 1 confirmed you have two bank connection cards for the same account, do this first. If you only have one connection and the problem was a re-import, skip to Step 3.
Identify Which Connection to Disconnect
The rule is straightforward: keep the connection that has your already-reconciled, correct history. Disconnect the one that appeared after the reconnect and brought in the flood.
If you're not sure which is which:
Click into each card's Categorized (Posted) tab.
The one with your real, reconciled historical transactions is the one to keep.
Disconnect the Extra Connection
In the extra bank account's card, click the small pencil/edit icon or three-dot menu next to the account name.
Choose Disconnect this account on save (or "Edit account info" → "Disconnect").
Confirm.
What this does:
It removes the live feed from that connection going forward.
It does not delete transactions already in your books or your bank register.
The pending items from that connection will remain in your For Review tab until you deal with them.
What If the Disconnected Account Created a Duplicate in Your Chart of Accounts?
Sometimes when a second bank connection is created, QuickBooks also creates a second bank account in your Chart of Accounts, separate from your real one.
Check:
Go to Accounting → Chart of Accounts.
Look for two accounts that seem to be the same bank (same name or very similar names).
If you find a duplicate account in your CoA with no real transaction history:
Make sure it's disconnected from the bank feed first.
Then you can merge it into the original account by renaming it to exactly match the original account name. QuickBooks will prompt you to merge.
If the duplicate account already has some categorized transactions in it, don't merge yet — flag those transactions first and get them matched or re-assigned to the correct account before merging.
Step 3 – Bulk-Exclude the Duplicated Feed Lines
Now that the extra connection is gone (or if you confirmed you only had one connection and it just re-imported too much history), it's time to clear the For Review queue of the duplicate transactions.
This is the most tedious part. Here's how to do it systematically.
Filter by the Duplicate Date Range
Go to Banking → Bank transactions → For Review (Pending) tab.
Use the Date filter to narrow down to the earliest duplicate start date you identified in Step 1.
You can also filter by transaction type if it helps isolate the flood.
Select and Exclude in Batches
Tick the checkboxes for the first batch of duplicate transactions (QuickBooks lets you select multiple).
Click Exclude.
What Exclude does:
Moves those lines to the Excluded tab — they're out of your books but still accessible if you need to review them later.
Does not create any new income or expense entries.
Does not affect anything already in your register or reconciliation history.
Work through the queue in batches — date range by date range — until the For Review tab is empty of everything that pre-dates your last reconciliation.
Verify After Excluding
Once you've cleared the queue:
Check your register for the same period to confirm balances haven't changed.
Run a quick Profit & Loss for the affected months to make sure income hasn't jumped or dropped unexpectedly.
If everything looks stable, the feed damage has been contained.
Step 4 – Check and Repair Your Reconciliations
Here's the thing about duplicate transactions and reconciliations: they can interact in unexpected ways.
If Your Previous Reconciliations Were Already Completed
Good news: if you reconciled those months before this problem started, and you correctly excluded the re-imported transactions without adding or matching any of them, your prior reconciliations should be intact.
Run a quick check:
Go to Settings → Reconcile for the affected account.
Look at your reconciliation history.
If the beginning balance for your next un-reconciled month matches your last reconciliation's ending balance, you're clean.
If Some Duplicates Were Already Added Before You Caught the Problem
If you (or someone else) accidentally added or matched some of the duplicate transactions before realizing what was happening, those will now show up as extra transactions inside your reconciled or un-reconciled history.
For unreconciled duplicate entries:
Find them in the register.
Open each one and use More → Delete.
Re-check your register balance matches your bank statement.
For already-reconciled duplicate entries, this is more delicate:
Deleting a reconciled transaction will throw off your reconciliation balance.
The community consensus — and my own practice — is to not undo past reconciliations for small errors, but instead create an offsetting entry or let your accountant handle it at year-end.
"Reconcile the bank account so that all duplicate transactions are the only transactions left unreconciled. Be careful which transactions you keep." — r/QuickBooks
If the duplicates that slipped through are large in value or distort your tax year, get a bookkeeper involved before trying to manually undo past reconciliations.
Step 5 – Permanently Remove the Excluded Transactions (Optional But Clean)
Excluded transactions live in the Excluded tab indefinitely unless you delete them. They don't affect your books, but they're dead weight.
When you're confident the exclusions were correct:
Go to Banking → Bank transactions → Excluded tab.
Tick the checkboxes for the transactions you want to permanently remove.
Click Delete.
A word of caution: don't delete from the Excluded tab immediately. Give yourself a few days or until your next reconciliation confirms your books balance correctly. If something went wrong with an exclusion, you can still undo it from the Excluded tab before deleting.
When "Start Over" Actually Makes Sense
This is the conversation nobody wants to have, but it comes up regularly in both Intuit Community threads and bookkeeper Facebook groups.
There is a QuickBooks Online feature called purge company data. It wipes your QBO file back to a blank slate.
The only realistic use case for purge is this:
Your QBO company was created less than 60 days ago.
You are in the early setup phase, no real historical books exist.
The reconnect/duplication happened before you had any correctly processed data worth preserving.
To access it, you would change your QBO URL to include /purgecompany — but I am not going to walk you through the full steps here because I want you to call QuickBooks support or a bookkeeper before doing this. The purge is permanent and cannot be undone.
For anyone whose company file is older than 60 days, purge is not available through that URL method. If you genuinely need to start from scratch and you're past 60 days, the path is:
Cancel your current subscription.
Start a new QBO account.
Migrate any open balances and CoA structure manually or with a clean import.
In most cases I see — where the books were working fine before the reconnect disaster — a systematic cleanup (the process we walked through above) is the right answer. Starting over is almost always overkill.
How to Reconnect Your Bank Safely If It Disconnects Again
Bank feeds disconnect. It's a quirk of the OAuth-based connection system and sometimes your bank's own maintenance windows.
Here's what to do the next time it happens, so it doesn't turn into another flood:
Before reconnecting, note your last reconciliation date and the date of the last transaction in your register.
When reconnecting, set the start date for the import to the day after your last reconciliation or the day after the last transaction already in your books.
After reconnecting, go straight to For Review and check the earliest transaction date before processing anything.
If you see dates that pre-date what's already in your register, filter and exclude immediately before clicking Add or Match on a single item.
Do not connect the same bank account twice. If your reconnect created a new card in your Banking screen, check whether the old connection still exists and disconnect the duplicate before proceeding.
"Don't connect the same account twice — check your connected accounts list if you suspect duplicates." — Peak Advisers
The One-Sentence Summary
If your bank feed re-flooded your QuickBooks with duplicate transactions after a reconnect: disconnect the extra connection, exclude the re-imported transactions in batches, verify your reconciliation balances are intact, and delete from Excluded only after you've confirmed your books are stable.
You can do this without nuking your file, losing your history, or paying for emergency support.
What to Read Next in This Series
This article covered duplicates caused by reconnecting or mis-linking a bank account.
If your duplicates came from a different cause — specifically from clicking Add on every bank feed line when QuickBooks expected you to click Match — that scenario has its own dedicated guide:
Previously in this series: "I Clicked 'Add' on Everything: How to Fix Duplicate Income from Bank Feeds Without Nuking Your Books."
And if the reconnect drama revealed a deeper problem — transactions you genuinely can't identify, mystery deposits, or an "Ask My Accountant" pile that's been growing for two years — I've got you covered in the next article coming up in this series:
Up Next: "My Chart of Accounts Has 200 Lines: How to Prune It Without Wrecking Your Reports."
The chart of accounts is often where the real chaos lives after months of messy bank feeds. Once your feed is clean, the CoA is usually the next thing that needs a forensic review.
Comments
Post a Comment