QuickBooks Online duplicate transactions after an upload almost always mean two sources covered the same dates: a file that overlaps the bank feed, the same file uploaded twice, or a downloaded line added when it should have been matched. Find each pair by date and amount, keep the reconciled or matched copy, and exclude or delete the other.
Where QuickBooks Online duplicate transactions after an upload come from
A duplicate after an upload is a second record of one real payment, created because QuickBooks Online received the same activity twice. Intuit names an overlapping file as one cause, so treat any overlap as a likely double. Most cases trace back to dates that two sources both covered.
Intuit's page on fixing duplicate transactions in QuickBooks Online bank feeds lists the usual causes. The ones tied to uploads are:
- A file that overlaps the bank feed. The feed brought in March 1 to 10, then a CSV for all of March arrives, and ten days appear twice.
- The same file uploaded twice. A second upload of an identical file repeats every row.
- Adding instead of matching. You typed an expense by hand, then the bank line arrived and was added as new rather than matched to it.
- Reconnecting an account. A reconnected feed may pull history that is already in the books.
- The same account connected twice. Two connections to one bank account each deliver the full activity.
Intuit's page also lists causes that have nothing to do with uploads, such as a sale recorded both as an invoice and a sales receipt. Those look the same in a register but need a different fix, so it helps to confirm the double started with a file before you change anything.
When the "duplicate" is really a different problem
Some lines look doubled when they are actually misfiled. If a card statement was uploaded into checking, the checking register shows lines that also appear on the card, and the fix is moving them, not deleting them. Fixing transactions imported to the wrong account in QuickBooks covers that case. A pair where one line is a deposit and the other a withdrawal for the same amount usually means the signs were flipped on upload, which deposits imported as withdrawals in QuickBooks explains.
How do you find each duplicate pair in the bank register?
Sort the account register by amount, then scan for two lines with the same figure a few days apart. Dates can differ by a day or two between a feed and a file, but the amount rarely does. Sorting by date alone hides pairs that sit far apart on a long list.
Open Chart of accounts, choose View register for the bank or card account, and narrow the date filter to the period of the upload. Then use these passes:
- Sort by amount. Identical amounts land next to each other. Mark every pair within about five days of each other.
- Sort by date. Look for a stretch where the number of lines per day roughly doubles. That stretch is usually the overlap window.
- Check the bank side. On the Bank transactions screen, compare the For review count with the number of lines in your file. A review list that is twice as long as the file is a strong hint.
- Compare the balance. If the register balance is higher or lower than the statement by the total of the suspect pairs, you have found the whole double.
An example of five suspect pairs
The table is an example with made-up values. It shows how the decision falls out once each pair has been looked at.
| Date | Payee | Amount | Copy A | Copy B | Keep | Action on the other |
|---|---|---|---|---|---|---|
| Mar 3 | Flour Supply Co | -412.80 | Feed, reconciled | Upload, added | A | Undo B, then exclude |
| Mar 5 | Card deposit | 1,906.00 | Feed, matched to invoice | Upload, in For review | A | Exclude B |
| Mar 7 | Utility Co | -138.25 | Typed by hand | Upload, added as new | A | Undo B, then exclude |
| Mar 9 | Coffee Roasters | -64.00 | Upload, added | Upload, added | Either | Undo the one with no attachment, then exclude |
| Mar 12 | Parking | -12.00 | Feed | Feed | Both | Two real payments, keep both |
Deciding which duplicate copy to keep
Keep the copy that has done the most work in your books. A reconciled copy wins over everything, because removing it changes the balance your last reconciliation agreed with. If neither is reconciled, keep the one matched to an invoice or bill, or the one with a receipt attached. Remove the bare copy.
Intuit's duplicate-transactions page gives the same order. A reconciled line shows an R in the register, and a cleared line a C. Matched lines show in the Added or Matched column on the Categorized tab as a match rather than an add.
The reasoning is simple once you picture what each copy is tied to. A bare added line affects only the account and one category. A matched line also closes an invoice or a bill. A reconciled line is part of a past proof that your books agreed with the bank. Removing the bare line costs nothing. Removing the others undoes work and can reopen invoices or break a reconciliation.
When both copies came from the same source and carry nothing extra, it does not matter which one goes. Pick the later one, so the earlier entry date stays in the audit trail.
Excluding duplicates still waiting in For review
A duplicate that is still on the For review tab has not touched your books yet, so excluding it is all the cleanup it needs. Tick the extra copies on For review, choose Exclude, and they move to the Excluded tab. Intuit's page notes that once a downloaded line is excluded, QuickBooks stops the bank from sending it again.
You can tick many lines at once, so a whole repeated upload can be excluded in one action. Sort For review by date first so the overlap window sits together, then tick only the rows from the file, not the ones from the feed.
An excluded line can be left where it is. It has no effect on balances or reports. If you want the Excluded tab clean, Intuit's article on voiding and deleting transactions in QuickBooks Online explains that excluded lines are the only ones you can delete in bulk.
When QuickBooks suggests a match
On For review, QuickBooks sometimes shows a suggested match for a line, pointing at a transaction already in the register. If that existing transaction is the same payment, accept the match instead of excluding. The result is one transaction that is linked to the bank line, which is better than an orphan record and an excluded line.
Removing duplicates that were already added or matched
A duplicate that was already added is a real transaction and needs undoing or deleting. On the Categorized tab, click the link in the Added or Matched column for the extra copy and choose Undo. The line goes back to For review, where you can exclude it. Lines entered another way are deleted from the register.
Intuit's duplicate-transactions page describes both paths. Undo suits a copy that came from a feed or an upload, because it returns the line to the review stage without losing the bank detail. If the line was matched into another transaction, undo that match first.
For a copy that exists only in the register, open it and choose More, then Delete. Each line is handled on its own, so set aside time if the overlap was long. Void is also offered, but it leaves a zero-value line behind, which is untidy for a pure duplicate.
Check the result against the statement
After removing the extras, compare the register balance on the last day of the upload with the closing balance on the bank statement. They should agree. If they still differ, the gap is often one pair you missed, or a pair where the two copies had slightly different amounts because one included a fee.
When an upload overlaps a live bank feed
An upload that overlaps a live bank feed will double every day both sources cover. The fix is to upload only the dates the feed does not reach. Check the earliest date the feed brought in, then trim the file so it ends the day before. Intuit's manual upload page also advises setting the date range carefully to avoid duplicates.
Intuit's page on manually uploading transactions into QuickBooks Online gives a rule for accounts that already hold transactions: find the date of the last transaction and pick the next day as the start. It also suggests checking the Chart of accounts before you upload, to avoid creating duplicate transactions.
A routine that prevents the overlap
- Before each upload, open the register and note the first and last dates already present.
- Trim the file so its dates fall entirely outside that range.
- Name the file with its date range, for example "checking-2026-02-01-to-2026-02-28", so a repeat is obvious.
- After the upload, compare the count of new lines on For review with the count of rows in the file.
QuickBooks Desktop works differently, because Web Connect files carry an ID for each line that Desktop uses to skip repeats. If you also keep books in Desktop, how to import bank transactions into QuickBooks Desktop covers its import route and why overlapping files can still double there.
Are near-duplicates sometimes two real payments?
A near-duplicate is two lines with the same amount and payee that are both genuine. They are common for subscriptions, parking, tolls, transfers and repeat orders from one supplier. Before you remove any pair, check the bank statement itself. If the statement lists the payment twice, both copies belong in your books.
Signs that a pair is real rather than doubled:
- The statement shows both. This is the only test that settles the question.
- The reference numbers differ. Check numbers, card authorisation codes or transfer references that do not match point to two payments.
- Both came from the same source. Two feed lines for the same amount on the same day are usually two real charges, because a feed does not normally send one line twice.
- The running balance needs both. If removing one breaks the agreement between the register and the statement, it was real.
A careful file avoids most of this work. SimpleBankConvert is being built to read a PDF statement into a CSV or QBO file for one statement period at a time, which makes it easier to upload exactly the dates the feed missed. You can join the list on the get started page to hear when accounts open.