You reconnect a payment processor or your bank feed catches up after an outage, and suddenly your books are wrong. The same sale is sitting there twice, your revenue looks bigger than it is, and the account will not reconcile against the statement. It is one of the most common headaches in small-business bookkeeping, and the resync is usually the cause: it re-imported items your software had already recorded. The fix is not to start deleting rows in a panic, because some of what looks like a duplicate is a real, separate record. Here is how to tell them apart, clear the true duplicates the safe way, and set things up so a future resync does not do this again.
Menu names differ across QuickBooks, Xero, and other tools, so the steps below describe the moves in plain terms rather than exact clicks. The logic is the same everywhere: identify what genuinely doubled, remove the extra copy without breaking anything already reconciled, and remove the reason it happened.
Why the duplicates appear after a resync
The usual trigger is an overlap between two feeds. When you disconnect and reconnect a bank feed, or a processor connector re-syncs after a hiccup, it can re-import transactions your software already had, so each one lands a second time. It gets worse when a payment processor and your bank both feed the same sale into your books: the processor posts the income, and then the bank feed posts the deposit when the money arrives, which can look like two of the same thing. A resync on top of that can add yet another copy. Knowing which feed produced which entry is the first step to cleaning it up without deleting a record you truly need.
Back up before you touch anything
Do not start deleting first. Export the affected transactions, or take a backup or a dated report, so you have a record of the state your books are in before you change it. Bulk-deleting rows is the fastest way to turn one problem into two, especially if some of those entries are tied to a past reconciliation. A quick export to a spreadsheet also makes it far easier to sort by date and amount and see the duplicates side by side. Five minutes of backup now can save you an afternoon of rebuilding later.
Tell a true duplicate from a two-sided record
This is the step people skip, and it causes the most damage. A payment processor records the gross sale and its fee, while your bank records the net amount that landed, so an income entry and a matching deposit are two sides of the same sale, not a duplicate to delete. A real duplicate is the exact same transaction, same date and same amount, imported twice by the same feed. Before you remove anything, confirm you are looking at a true copy and not the processor income paired with its bank deposit. If you delete the fee or the gross sale by mistake, your double-entry records will no longer add up.
Exclude the extra copies first
Once you have confirmed a true duplicate that is still waiting in your bank feed to be reviewed, most tools let you exclude it rather than delete it outright. Excluding takes the extra copy out of the review queue without destroying the record, and you can remove it for good afterward once you are sure. This matters because a downloaded item you delete can sometimes get re-pulled by the next feed refresh, whereas an excluded one stays out of the way. Work through the duplicates one at a time, exclude the extra copy, and keep the original that is already matched or recorded correctly.
Match instead of add, so a sale counts once
Prevention starts inside the review screen. When your bank feed shows a deposit that you already recorded as income from the processor, choose the option to match it to that existing entry rather than adding it as a new one. Adding creates a second transaction, which is exactly how the double count starts, while matching links the deposit to the income you already have so the sale is counted a single time. Getting into the habit of matching, not adding, is the single biggest thing that keeps processor and bank feeds from doubling your revenue.
Handle items that were already reconciled
Some resync duplicates are copies of transactions you had already reconciled in a past period, and these need care. Do not un-reconcile or delete the original to get rid of the copy, because that breaks a reconciliation you already completed and throws off your historical balances. Instead, exclude or remove the newly imported copy and leave the reconciled original untouched. If a resync has re-opened or uncleared items that were settled, resist fixing it by editing the old entries, and deal only with the fresh copies the sync brought in. When a past reconciliation is involved, this is the moment to ask your bookkeeper before you change anything.
Prevent the next resync from doing it again
Fixing the mess is half the job; the other half is making sure one feed owns each type of transaction. Decide on a single source of truth for your sales, so either the processor connector or the bank feed records the income, not both, and use matching to tie the two together rather than importing the same sale twice. Many businesses route processor payouts through a dedicated clearing account so the gross sales, fees, and net deposit line up cleanly. Check that your bank feed runs once a day rather than pulling repeatedly, and review your connector’s settings after any reconnection, since that is when re-imports tend to happen. A little structure here stops the whole problem at the source.
Reconcile to confirm you are clean
Finish by reconciling the account against the statement. A bank reconciliation is the check that proves your books match reality: when the cleared balance in your software equals the balance on the bank statement, you know the duplicates are gone and nothing real was removed by accident. If it does not tie out, the difference often points straight to the transaction still doubled or the one deleted in error. Reconciling is both the proof that you fixed it and the routine that catches the next duplicate early, before it buries itself in your numbers.
This is general information, not accounting or tax advice. Bookkeeping tools, feeds, and the right treatment for a given transaction vary by business and by software, and mistakes here can affect your tax filings. Back up your data before making changes, and check with a qualified accountant or bookkeeper before adjusting reconciled periods or anything you are unsure about.
What To Know
- Resync duplicates usually come from a reconnected bank feed re-importing items, or a processor and bank both recording the same sale.
- Back up or export the affected transactions before you change or delete anything.
- An income entry and its matching bank deposit are two sides of one sale, not a duplicate, so confirm a true copy first.
- Exclude extra copies rather than deleting them, and match a deposit to an existing entry instead of adding it again.
- Do not un-reconcile or edit already-reconciled originals; remove only the fresh copies, then reconcile to confirm.
Frequently Asked Questions
Why did a resync create duplicate transactions in my books?
Because the resync re-imported transactions your software already had. Reconnecting a bank feed, or a processor connector catching up after an outage, can pull in items a second time, and if both your processor and your bank feed record the same sale, that adds to the overlap. The result is the same transaction appearing more than once, inflating your income. The fix is to confirm which entries are true copies, exclude the extras, and match rather than add going forward.
How do I know if a transaction is a real duplicate or not?
A true duplicate is the identical transaction, same date and same amount, brought in twice by the same feed. What often looks like a duplicate is two sides of one sale: the gross income the payment processor records, and the net deposit your bank records when the money arrives. Those belong together and should be matched, not deleted. Before removing anything, compare the entries carefully and make sure you are looking at an exact copy rather than the income and its related deposit.
Should I delete duplicate bank feed transactions?
Prefer excluding them to deleting them, at least at first. Most accounting tools let you exclude a downloaded transaction, which takes the extra copy out of your review queue without destroying it, and a deleted feed item can sometimes get re-pulled on the next refresh. Exclude the confirmed duplicate, keep the correctly recorded original, and only delete for good once you are certain. Never delete or un-reconcile a transaction that is part of a completed reconciliation just to clear a copy.
How do I stop payment processor syncs from duplicating sales?
Give each transaction a single source of truth. Decide whether the processor connector or the bank feed records your sales income, and use the match function to link the two rather than letting both add it. Routing processor payouts through a dedicated clearing account keeps the gross sale, fee, and net deposit lined up. Also make sure your bank feed runs once daily, and review your connector settings after any reconnection, since re-imports usually happen right after you reconnect a feed.
What should I do if the duplicates were already reconciled?
Tread carefully, because reconciled transactions affect your historical balances. Do not delete or un-reconcile the original to remove a copy, as that breaks the reconciliation you already completed. Instead, exclude or remove only the newly imported duplicate and leave the reconciled entry alone. If a resync re-opened previously settled items, avoid editing the old records and handle only the fresh copies. When a closed or reconciled period is involved, check with your accountant before making any change.
What To Do Next
Back up first, then separate true duplicates from two-sided records, exclude the extra copies, and match deposits to income you already recorded. Leave reconciled originals alone, set a single source of truth for each feed, and reconcile to confirm. For related help, see our comparison of QuickBooks and Xero bank rules and our guide to a Stripe or Square payment that did not record. The business section has more on keeping your books clean.
