Bank feed duplicates after reconnecting a connection: why it happens
One of the most persistent community complaints: reconnect a bank feed and a stretch of already-categorized transactions comes back twice. The mechanics, and the cleanup that doesn't wreck your history.
If there is one evergreen complaint in QuickBooks community forums, it’s this one: a bank connection breaks, you reconnect it, and a week or a month of transactions you already categorized reappears in the review queue — sometimes as exact duplicates of entries already in the register.
Why reconnecting causes duplicates
Bank feeds work by matching incoming transactions against what’s already downloaded. That matching depends on identifiers the bank supplies with each transaction. When a connection is rebuilt — because the bank changed its login flow, the aggregator switched endpoints, or the user disconnected and reconnected — those identifiers can change. To the feed, a transaction with a new identifier is a new transaction, even if the date, amount, and description are identical to one it delivered last month.
The overlap window varies. Some reconnections pull only a few days of history; others pull ninety. The wider the pull, the more of your already-processed transactions come back for a second pass.
The cleanup that preserves your history
The order of operations matters:
- Exclude, don’t delete-and-redo. Duplicates sitting in the For Review queue haven’t touched your books yet. Excluding them leaves your existing categorized entries — and your reconciliations — untouched.
- Resist “undo” on matched transactions. Unmatching entries that were already reconciled creates discrepancies that surface months later as a reconciliation that no longer ties out.
- Check the register before assuming. A transaction can look duplicated in the review queue while the register still holds exactly one copy. The queue is a staging area, not the ledger.
When it’s not this
A steady trickle of duplicates without a reconnection event is a different animal — often two active connections to the same account (for example, one at the bank level and one through a card program). That one is worth an audit of the connections list rather than queue triage.
Seeing a variant of this the desk should document? Tell us via the contact desk.