Duplicate Web Connect transactions in QuickBooks Desktop appear when two files cover the same dates and their transaction IDs differ, or when a downloaded line is added instead of matched to an entry you typed. Leave extras unaccepted in the Bank Feeds Center, and delete copies already in the register only after checking which one is reconciled.
How QuickBooks Desktop decides a Web Connect transaction is new
A Web Connect file is a .qbo file from your bank, and each transaction in it carries an identifier. QuickBooks Desktop remembers the identifiers it has already taken into a company file. When a later file repeats one, Desktop treats that line as already downloaded rather than as new activity.
Intuit's page on downloading bank feed transactions in QuickBooks Desktop states the rule from the user's side: you can't download transactions into the same company file more than once. That is why two bank downloads with overlapping dates usually import cleanly. The overlap is recognised and skipped.
The same page adds a consequence that matters for cleanup. Once you delete downloaded transactions, you can't download them again. Your bank may be able to reopen them for you, but that is a request to the bank, not a button in QuickBooks.
Why do duplicate Web Connect transactions get through?
Duplicates get through when the identifiers do not line up, or when the same payment enters by two routes. The skip only works if a repeated line carries the same identifier as before. A file whose identifiers change, or a payment you typed by hand and then added from the bank, defeats it.
Common causes:
- Identifiers that change between files. Some files built from spreadsheets or PDFs give each line a new identifier every time they are made. Two overlapping files then look like different activity.
- Adding instead of matching. You wrote a check in the register, then the bank line arrived and was added as a new payment. Intuit's page suggests matching downloaded lines to entries you made yourself to avoid recording a payment twice.
- A file opened into a different account. Lines that went into the wrong Desktop account once and the right one later now sit in both.
- A mix of feed and file. Direct Connect downloads and a Web Connect file for the same dates can each bring in the activity.
Removing duplicate Web Connect lines still in the Bank Feeds Center
A duplicate still waiting in the Bank Feeds Center has not reached your books, so the safe fix is to not accept it. Find each extra line in the account's transaction list and remove it there instead of adding or matching it. In Advanced mode the action is Ignore, which deletes the line from the list.
Before removing anything, sort the waiting lines by amount and compare them with the register. A waiting line whose twin is already in the register is the extra. A waiting line with no twin is new activity and should be added. Remember that a deleted downloaded line cannot be downloaded again, so remove only what you have checked.
Removing duplicate Web Connect transactions already in the register
When both copies were accepted, delete one from the account register. Open the register, find the pair, check which copy is reconciled or linked to a bill or invoice payment, and delete the other one. Then compare the register balance with your bank statement for the last date of the file.
Checklist before you delete a register copy
Work through these points for each suspect pair:
- Same amount, same direction. A deposit and a payment of the same figure are not duplicates.
- Dates within a few days. Bank dates and the date you wrote a check often differ slightly.
- Reconciled status. A copy marked as reconciled stays. Delete the other.
- Links to other records. A copy that pays a bill or receives an invoice payment stays.
- The statement itself. Count how many times the payment appears on the bank statement. If it appears twice, keep both.
- Balance after deleting. The register should agree with the statement once the extras are gone.
Xero users meet the same problem under different names. If you also keep a Xero organisation, duplicate statement lines in Xero covers line-by-line cleanup, and deleting an imported bank statement in Xero covers removing a whole file uploaded twice.
When are duplicate Web Connect pairs not duplicates?
Some pairs look doubled but are two real payments. Two identical subscription charges in one month, two deliveries from one supplier, or a bank fee charged and charged again all produce matching lines. The bank statement settles it: if the statement lists the payment twice, both lines are correct.
Scanned statements make this harder, because the source file has no identifiers at all and reading errors can repeat a line. If your statements are scans, the guide to importing a scanned bank statement into Xero explains what to check on a scan before trusting any file made from it.
Files with stable lines prevent most of this. SimpleBankConvert is being built to turn a PDF statement into a QBO file one statement at a time, so you can bring in each period once and keep the dates from overlapping.