Duplicates across a client roster

One file, or all of them

Clearing duplicates out of a single QuickBooks Online file is a known task with a known method. Fixing duplicate transactions in a bank feed covers the mechanics, including the awkward case where a duplicate has already been reconciled and cannot simply be deleted without moving a balance somebody signed off.

This is the other half. If you find duplicates in one client file you will find them in most of them, because banks are not having a bad day. Four configuration choices produce them, each made once per file, usually at onboarding, usually by whoever set that file up and moved on. Fix them file by file and the work never ends.

The four causes, and where each is actually decided

Cause	Where the decision really got made
An account is deleted and re-added, pulling roughly 90 days again	The moment a card was replaced, and whether staff disconnected the feed or deleted the account
A processor posts a batch, then the bank posts the same settlement	At onboarding, when both connections were made without agreeing which one is the transaction
An auto-add rule fires on something that also arrives via a second feed	In the rule itself
Two people enter the same transaction	In how the firm divides work, not in the software

Three of those four are decisions about your own process. Even the first one is: the bank is only responding to how the reconnection was done.

The Square and Stripe case is worth spelling out, because it is the one that generates the most volume. The processor posts individual sales as they happen. Two days later the bank posts one settlement deposit, net of fees. Both are legitimate. Only one of them is the revenue, and the other should match against it as a deposit. Files where nobody decided which is which end up with revenue counted twice and merchant fees missing entirely, which is a P&L that is wrong in two directions at once.

Five rules worth writing into onboarding

Never delete and re-add a bank account to fix a feed problem. Disconnect the feed, leave the account and its history in place, reconnect. Deleting triggers the backfill and it is the single biggest source of a sudden duplicate wave. Intuit’s own troubleshooting steps sometimes end at “disconnect and reconnect”, which people read as “remove the account”, and the two are different operations with very different consequences.

Auto-add is for single-source transactions only. A fixed loan payment. One subscription on one card. Anything that could also arrive through a processor feed gets a categorise-only rule that still needs a human to click Add.

Decide the processor convention at onboarding and write it in the client’s notes. The person doing the close eight months from now is not the person deciding this today, and they will not guess the same way.

One person owns the For Review tab per file. Not one person per client relationship. One person who touches the feed.

Sort For Review by amount, not date. True duplicates cluster by amount even when settlement dates differ by a day or two. Sorted by date they sit apart and read as unrelated charges.

The check that catches what slips through

Prevention shortens the check, it does not remove it. Three steps, per file, and genuinely under five minutes on a file set up properly:

Reconcile to the statement. A file full of duplicates can show a completely clear For Review tab and still be out. That gives you a diagnostic worth memorising: a reconciliation off by exactly one line item is a duplicate until proven otherwise. Off by a round number is usually a transposition. Off by twice a transaction amount is normally a transfer booked in both directions.

Sort by amount and scan for adjacent identical values.

Exclude, do not delete. Excluding leaves a record that a transaction existed and was reviewed. Deleting leaves nothing, and eventually somebody asks why a charge on the bank statement is absent from the books. If the duplicate is already reconciled, undo that month’s reconciliation first, remove it, then re-reconcile. QuickBooks will let you delete a reconciled transaction with no warning at all, and the balance moves silently.

Why it matters beyond tidiness

Duplicates inflate revenue. Clients feel that one. A business paying estimated tax against a revenue figure carrying duplicated deposits is paying tax on money it never made, and nobody notices, because the number looks plausible and larger is the direction people expect.

The quieter failure is yours. A file that carried duplicates for eight months has eight months of reconciliations that were signed off while the file did not tie. Whether or not anyone noticed, the review step was not doing its job for most of a year. That is a process finding instead of a bookkeeping one, and it is why this belongs in the onboarding standard instead of a monthly cleanup habit.

When it has already piled up

A roster of files with duplicates spread across reconciled periods is cleanup work. The fix has to walk back through each affected period, not patch the current one, which is what a cleanup is scoped and priced for:

$199 per month of backlog

For firms sending several files at once, the fee schedule publishes a bulk rate for ten or more client files. If the real question is whether to send files out at all, should your firm subcontract bookkeeping sits upstream of it.

If this is your own business rather than a client’s, the same problem gets fixed the same way: bookkeeping for business owners, with fees published in full.