To undo a bank upload in QuickBooks Online, treat the file as a set of separate lines. Exclude every line from that file still waiting for review. For lines someone already added or matched, select Undo so each one returns to review, then exclude it too. Leave lines from other files and the bank feed alone.
Is there an undo button for a bank upload in QuickBooks Online?
No single button reverses a whole uploaded file. QuickBooks Online forgets which file a line came from once the upload finishes. Each line then sits in the account's bank transactions list like a line from the bank feed. You undo the upload one line at a time, or in batches you tick by hand.
That design catches people out. They look for an import history screen, the way some programs keep a log of every file, and find nothing. The upload screen only goes forward: pick a file, map the columns if it is a CSV, choose the account, finish. Afterwards, the only record of the file is the lines it created.
The upside is that the undo is precise. You decide what happens to each line, so a file that was half right does not have to come out completely. A file uploaded to the wrong account, or uploaded twice, usually has to come out in full. A file with one bad week can stay, minus that week.
Before touching anything, write down three facts about the bad file: its first date, its last date and its number of lines. Those three numbers let you find its lines later and prove they are all gone.
Sorting an uploaded batch by bank transactions tab
An uploaded line can be in one of three places on the Bank transactions page, and each place needs a different action. Lines nobody has touched are on the review tab. Lines someone accepted are on the accepted tab. Excluded lines are on the Excluded tab. Count how many of the file's lines sit in each before you start.
Intuit has renamed these tabs over time, and both sets of names are still in use. Intuit's article on fixing duplicate bank feed transactions calls them For review, Categorized and Excluded, and notes the Categorized tab may be labelled Posted instead. Newer screens call the review tab Pending. The guide to pending transactions in the QuickBooks Online bank feed explains why the same word means something different at your bank.
Worked example: a 40-line file sorted by tab
The numbers below are an example. Say a CSV covering 1 to 31 May was uploaded to the savings account by mistake, and it held 40 lines. A week passed before anyone noticed, and a colleague had already worked through part of it.
| Where the lines are (example) | Lines | Action |
|---|---|---|
| For review (or Pending) | 22 | Exclude them in one batch |
| Categorized (or Posted), added as new records | 13 | Undo each, then exclude |
| Categorized (or Posted), matched to existing entries | 4 | Undo each, then exclude |
| Excluded already | 1 | Leave as it is |
| Total | 40 | Matches the file's line count |
The total row is the point of the table. If your three tabs add up to fewer lines than the file held, some lines are hiding behind a date filter or sit in another account. Do not move on until the count agrees.
Excluding upload lines still waiting for review
Lines from the bad file that nobody has accepted are the easiest part of the undo. On the review tab, tick each one and select Exclude. They move to the Excluded tab, and none of them ever reached your registers or reports, so nothing else changes.
Sorting helps you find them fast. Sort the review tab by date, then tick from the file's first date to its last. If the bank feed brought in lines for the same dates, compare the descriptions before you tick. Uploaded CSV lines often carry the description exactly as your spreadsheet had it, which may differ from the feed's wording for the same payment.
The batch exclude works on as many lines as you tick at once. Intuit's own help article on excluding a downloaded transaction shows ticking several checkboxes before one Exclude. It also says excluded lines appear in no account history and no financial report, which is the outcome you want for a file that should never have gone in.
Undoing uploaded lines that were already added or matched
Lines from the file that someone already accepted need one more step. On the accepted tab, select the link in the Added or Matched column for the line, then select Undo. The line returns to the review tab, and from there you exclude it like the rest.
What Undo does depends on how the line was accepted. Intuit's article on unmatching and moving downloaded transactions separates the two cases:
- Added. QuickBooks created a new record when the line was accepted, such as an expense or a deposit. Undo resets that record, so the expense or deposit is gone from the register.
- Matched. The line was linked to a record that already existed, perhaps an invoice payment or a check you wrote. Undo disconnects the two. The existing record stays in your books, which is correct: it was there before the upload.
Work through the accepted lines in date order and tick each one off against your count. A line that cannot be excluded straight away is usually still tied to another record, and the duplicates article says to undo that match first. The full walk-through for one line is in the post on undoing an added bank transaction in QuickBooks Online.
Numbered steps for the whole undo
- Note the bad file's first date, last date and line count.
- Open Bank transactions and select the tile for the account the file went into.
- On the review tab, tick the file's lines and select Exclude.
- On the accepted tab, open each of the file's lines from the Added or Matched column and select Undo.
- Return to the review tab and exclude the lines that just came back.
- Count the file's lines on the Excluded tab and compare the total with step 1.
Should the excluded upload lines be deleted afterwards?
Excluding is usually enough. An excluded line has no effect on your books, and keeping it leaves a visible trail of what happened. Delete excluded lines only if they clutter the tab so much that you might restore one by mistake, or if a colleague reviews that tab regularly.
There is a reason Intuit prefers exclude over delete for feed lines. The duplicates article says that once a downloaded line is added or excluded, QuickBooks stops the bank from sending it again. Deleting a feed transaction instead makes QuickBooks download it again. For a line that came from your own file, no bank will resend it, but the habit of excluding first is still the safer one.
Deleting the records an upload created is a separate job. If someone edited an added expense after accepting it, or the line was pasted into a journal entry, Undo may not reach it. Those records come out from the register. The post on deleting imported transactions in QuickBooks Online covers that register work and what it can and cannot reverse.
Reconciled upload lines: when not to undo them yourself
Stop and ask your accountant if any of the file's accepted lines are already part of a reconciliation. Undoing a reconciled line changes a period you have already agreed against a bank statement. The reconciliation's opening balance for the next month then shifts, and the gap is hard to trace later.
Intuit's unmatching article gives the same advice: if you already reconciled the transaction, reach out to your accountant before you change it. In the register, reconciled lines carry an R in the check mark column, so you can spot them before you start.
A wrong-account upload reconciled into the wrong account is the hardest version. The reconciliation itself is wrong, not only the lines. Your accountant may prefer to undo the reconciliation, fix the lines and reconcile again, rather than unpick the lines one by one. Either way, leave the reconciled lines alone until you have decided together.
Uploading the corrected bank file without fresh duplicates
Once the bad lines are excluded, check the correct file before you upload it. Its dates must not overlap lines that should stay in the account. Then upload it to the right account, review its lines and compare the account's balance with the bank statement for the same date.
Intuit's guide to manually uploading transactions says to find the date of the last transaction already in the account and start the file on the next day. That rule matters more after an undo, because the account now has a gap where the bad file was. Your new file should fill that gap exactly, from the first missing date to the last.
Count again after the upload. The number of new lines on the review tab should equal the line count of the corrected file. If it is higher, part of the new file overlaps lines that were already there. If it is lower, the file is missing rows or some went somewhere unexpected.
If the bad upload started life as a PDF statement typed into a spreadsheet, rebuilding the file is often slower than the undo. SimpleBankConvert is being built to produce the QuickBooks file from the PDF with dates in one format and money out shown as minus amounts. It is not open yet, and the get started page lets you ask for an invitation.