To delete imported transactions in QuickBooks Online, tick them on the For review tab of Bank transactions and choose Exclude, then open the Excluded tab, tick the same lines and choose Delete. Lines you already added are a different case: undo them first, or delete them one by one from the account register.
Why imported transactions must be excluded before QuickBooks Online deletes them
QuickBooks Online treats a line on the For review tab as a suggestion from the bank, not as a transaction in your books. It has no delete button there because nothing has been recorded yet. Excluding the line is how you tell QuickBooks to set it aside, and the Excluded tab is where the delete lives.
The two-step path makes more sense once you know what each tab holds. The For review tab (called Pending in some versions of the screen) holds lines that came from a bank feed or a file upload and have not been added or matched. The Excluded tab holds lines you have decided to keep out of your books. The Categorized tab, sometimes called Posted, holds lines that became real transactions.
Intuit's page on fixing duplicate transactions in QuickBooks Online bank feeds describes the first step plainly: tick the box for each extra line on the For review tab, then click Exclude. You can tick many lines at once, so a whole bad upload can be excluded in a single action.
Excluding is often enough on its own. An excluded line has no effect on your reports, your register balance or your reconciliation. Many people stop there and never delete, which is fine. Deleting only tidies the Excluded tab so it stays useful for lines you excluded on purpose, such as a personal purchase on a business card.
If you exclude something by mistake, the step is reversible. Restoring excluded transactions in QuickBooks Online covers the Undo button on the Excluded tab and what happens to the line when it returns to For review.
Batch deleting imported transactions from the Excluded tab
The Excluded tab is the only place QuickBooks Online lets you delete bank lines in bulk. Open Bank transactions, switch to the Excluded tab, tick each line you want gone and choose Delete. The lines leave the bank transaction list for good, which is why it pays to check the selection before you click.
Intuit's article on voiding and deleting transactions in QuickBooks Online is direct about the limit: you can only bulk delete excluded transactions. Anything added to the books has to be handled another way.
Step list for a batch delete
- Go to Bank transactions and pick the bank or card account the upload went into.
- On For review, filter or sort by date so the bad batch sits together.
- Tick every line from that batch. Use the select-all box if the filter shows only that batch.
- Choose Exclude. The lines move to the Excluded tab.
- Open the Excluded tab and sort by date again.
- Tick only the lines from the bad batch, leaving older exclusions alone.
- Choose Delete and confirm.
A worked example
Here is an example with made-up figures. A bakery owner uploads a CSV for March into the checking account. The file has 48 lines. Twelve of them are from the last days of February, which the bank feed had already brought in, so those twelve are duplicates.
| Group | Lines | Action |
|---|---|---|
| February 24 to 28 rows from the file | 12 | Exclude, then delete from Excluded |
| March 1 to 31 rows from the file | 36 | Review and add as normal |
| February rows from the bank feed | 12 | Leave alone, already added |
Sorting For review by date puts the twelve February rows from the file at the top. The owner ticks them, excludes them, then deletes them from the Excluded tab. The 36 March rows stay on For review and are added in the usual way. Nothing in the books changed during the cleanup, because the twelve rows were never added.
Can you delete imported transactions that were already added?
Imported transactions that were already added cannot be deleted from the bank transactions screens in a batch. Once a line leaves For review, it is a real expense, deposit or transfer. You either undo it from the Categorized tab, which sends it back to For review, or delete the transaction itself from the register or its own form.
Undo is usually the better first move. On the Categorized tab, the Added or Matched column shows a link for each line. Clicking it and choosing Undo returns the line to For review, where you can exclude it and then delete it from the Excluded tab. Intuit's duplicate-transactions page also notes a catch: if the line was matched into another transaction, you have to undo that match first.
Undo works one line at a time, so a long batch takes patience. The post on undoing an added bank transaction in QuickBooks Online walks through what undo keeps, what it throws away and how it differs from editing the line.
Added versus matched
The difference between added and matched matters here. An added line created a new transaction. Undoing it removes that transaction. A matched line linked the bank line to a record that already existed, such as an invoice payment. Undoing a match breaks the link but leaves the original record in place. If you undo a matched line and then delete it, the invoice payment you entered by hand survives.
Deleting an imported transaction from the account register
The account register is the right place to delete an imported transaction when undo is not available, or when the line was entered some other way. Open Chart of accounts, choose View register for the account, find the line, and use More, then Delete. Each deletion is one transaction, so this suits a handful of lines, not a whole file.
Intuit's duplicate-transactions page lays out this path and offers Void as the alternative. The two do different jobs:
- Delete removes the transaction from every view except the audit log. Intuit says the audit log can be used to re-enter a deleted transaction, but it does not bring the transaction back for you.
- Void keeps the transaction in your books with a zero amount. It shows that something existed and was cancelled. Intuit's void and delete article warns that a voided transaction cannot be unvoided.
For a duplicate created by an upload, delete is normally the cleaner choice. A voided duplicate leaves a zero-value line in the register that someone will have to explain later. Void suits a real payment that was cancelled, such as a check that was never cashed.
The register shows more than the bank feed
A register shows every transaction that touches the account, including ones you typed in by hand and ones created by invoices or bills. That makes it easy to delete the wrong line. Before you delete, open the transaction and check where it came from. A line created from a bank feed or upload shows its bank detail. A line created by receiving an invoice payment does not, and deleting it would leave the invoice open again.
The same job in QuickBooks Desktop
QuickBooks Desktop handles imports through Web Connect files and the Bank Feeds Center, so its cleanup works differently. If the cause was a file opened into the wrong Desktop account, changing the Web Connect account in QuickBooks Desktop covers how to point future files at the right one.
Will deleted bank feed transactions download again?
A deleted bank feed transaction can download again, which is the main reason to exclude rather than delete. Intuit's duplicate-transactions page says that once a downloaded line is added or excluded, QuickBooks stops the bank from downloading it again. If you delete a downloaded transaction instead of excluding it, QuickBooks will download it again from the bank.
That behaviour applies to lines from a connected bank feed. Lines from a file upload behave like the file: if you upload the same file again, the same rows come back. The bank never sent them, so there is nothing for the bank to resend.
Intuit's page also covers the odd case where the bank resends a line you excluded. If that happens, delete the extra copy from the Excluded tab.
Which route to use
| Where the line is | It came from | Best route |
|---|---|---|
| For review | Bank feed or upload | Exclude, then delete from Excluded |
| Categorized | Bank feed | Undo, then exclude |
| Categorized | File upload | Undo, then exclude and delete |
| Register only | Typed in or created by another form | Delete or void from the form |
Reconciled and matched imports you should not delete
A reconciled imported transaction is the clearest case where deleting is a mistake, even if it looks like an extra copy. Reconciled lines carry an R in the register, and cleared lines a C. Removing one changes the balance your last reconciliation agreed with, so your next reconciliation will start from the wrong figure.
Intuit's article on undoing or removing transactions from a reconciliation in QuickBooks Online warns that removing a cleared transaction changes the beginning balance for the next reconciliation. It also advises checking that the transaction really causes a discrepancy before you remove it.
When you face two copies of the same payment and one is reconciled, keep the reconciled one and remove the other. Intuit's duplicate-transactions page gives the same rule, and adds a second test for when neither copy is reconciled: keep the one matched to other records or carrying attachments, such as a receipt photo.
Other lines to leave alone
- Lines matched to invoices or bills. Deleting the bank side can reopen the invoice or bill and confuse your receivables.
- Transfers between your own accounts. Deleting one side of a transfer removes it from both accounts. Check the other account before you act.
- Lines in a closed period. If your books have a closing date, a deletion there changes figures you may have already filed or sent to your accountant.
The cheapest cleanup is the one you never need. A tidy, correctly dated file is much less likely to land in the wrong place. SimpleBankConvert is being built to turn a PDF statement into a CSV or QBO file with consistent dates and one signed amount column, so an upload is less likely to need deleting afterwards.