Void vs. Delete in QuickBooks: Which Button Keeps Your Audit Trail Intact?

A duplicate bill for $4,200 is sitting in your QuickBooks, and your finger is hovering over Delete. One click and it will be like the mistake never happened — which is exactly the problem. Auditors, lenders, and future-you all prefer your mistakes to come with paperwork. In QuickBooks Online, the difference between Void and Delete is the difference between a corrected record and a missing one, and picking the wrong button can break a reconciliation, open a gap in your invoice numbering, or erase the only proof of what you changed and why.

This guide walks through what each button actually does, when deleting is genuinely the right call, how to recover when you delete something you shouldn't have, and the handful of transactions you should never touch at all.

What Voiding Actually Does​

When you void a transaction in QuickBooks Online, the software zeroes out every dollar amount but keeps the transaction itself on the books. The entry stays in your registers and reports with a zero balance, the word "VOID" is stamped into the memo, and the original transaction date is preserved. Your account balances and financial reports show no trace of the amounts — but the record that something was there, and that someone deliberately zeroed it, survives.

That surviving record is the whole point. Intuit's own guidance says that for recordkeeping purposes, voiding is recommended over deleting, precisely because it keeps the transaction in your books without affecting your totals. A voided invoice keeps its invoice number, a voided check keeps its check number, and anyone reviewing the books later can see the full story: created on this date, voided on that date, amounts zeroed, balances untouched.

Voiding is also reversible in a practical sense. If you void a check and later learn the vendor cashed it after all, the voided shell is still sitting there with its number and date, so you know exactly what to fix. A deleted transaction gives you no such starting point.

What Deleting Actually Does​

Deleting removes the transaction from QuickBooks almost entirely. It disappears from registers, reports, and customer or vendor histories — everywhere except the Audit Log, which keeps a private note that something was deleted. QuickBooks does not renumber anything to fill the hole: if you delete invoice 1042, invoices 1041 and 1043 keep their numbers, and 1042 simply stops existing. That gap in the sequence is permanent, and it is the first thing an auditor or a tax examiner will ask you about.

The second thing to know is that there is no undo. QuickBooks Online has no recycle bin and no one-click restore for deleted transactions. Once you confirm the delete, the only way the entry comes back is by hand: you look up its details in the Audit Log and re-enter it from scratch. That is doable for one invoice on a quiet afternoon. It is miserable for twenty bills discovered missing during month-end close.

Why the Difference Matters More Than You Think​

For day-to-day bookkeeping the two buttons can look interchangeable — either way the wrong amount leaves your reports. The difference shows up in the three places where your books get judged by someone else.

Audits and reviews. An audit trail is a complete, chronological record of what entered your books and what changed afterward. Voided transactions are part of that trail; deleted transactions are holes in it. A reviewer who finds invoice numbers skipping from 1041 to 1043 with nothing in between cannot tell whether you deleted a duplicate, hid income, or fat-fingered a number. A voided $0 invoice 1042 answers the question before it is asked.

Reconciliations. Deleting a transaction that was already reconciled changes the history your bank reconciliation was built on, which produces the dreaded beginning-balance discrepancy the next time you reconcile. Voiding a reconciled transaction changes amounts too — neither button is safe on reconciled entries, as we'll cover below — but at least the voided shell tells you what moved.

Internal control. In a business where more than one person touches the books, deletions are invisible to everyone except whoever digs through the Audit Log. Voids are visible to anyone who runs a report. If you care about knowing who changed what — and you should — the button that leaves a marker wins.

How to Recover a Deleted Transaction From the Audit Log​

Sooner or later, someone deletes something they shouldn't have. Maybe a reconciled deposit vanishes and the next reconciliation won't balance, or a bill disappears and the vendor's statement suddenly disagrees with yours. The Audit Log is your recovery path. Here is the exact workflow:

1. Click the gear icon and select Audit Log.
2. Narrow the search with the filters: set User to whoever deleted the entry, Date Changed to when it happened, and Events to Deleted/Voided transactions.
3. Find the deleted transaction in the list and click View to expand it. The log shows the transaction's full details — type, date, amounts, accounts, customer or vendor — as they were when it was deleted.
4. Click + New and re-enter the transaction manually, using the original transaction date from the log, not today's date. Backdating to the original date keeps your period reporting correct.
5. If the deleted transaction had been reconciled, open the reconcile screen for that account, enter the same ending date and ending balance as your last completed reconciliation, and re-tick the re-entered transaction. When the difference hits zero, the reconciliation is whole again.

Two honest caveats. First, the Audit Log gives you the details, not the transaction — re-entry is manual, line by line, and on a long invoice that takes real time. Second, linked items may need re-linking: if you void or delete an invoice that had a payment attached, QuickBooks keeps the payment but leaves it unapplied, so you must apply it to the correct invoice yourself. Prevention (voiding instead of deleting) is dramatically cheaper than this cure.

When Deleting Is Actually the Right Call​

Deleting has a bad reputation in this article so far, but there are narrow cases where it is the correct tool. The common thread: the transaction should never have existed at all, so there is nothing worth preserving a record of.

True duplicates. The classic case. You entered a bill by hand on Monday, the bank feed imported it on Tuesday, and now the same expense appears twice. One of them is fiction — delete it. (For bank-feed duplicates specifically, excluding the downloaded transaction is often better than deleting, since a deleted feed item can simply download again.)

Entries that never happened. Test transactions from when you were learning the software, an invoice created in the wrong company file, a bill entered for a purchase you canceled before anything changed hands. If no money moved, no document went to a customer or vendor, and no period has closed over it, deleting keeps the books clean without hiding anything real.

Freeing billable items stuck on a voided invoice. This is the gotcha that surprises even experienced users: billable time and expenses stay linked to a voided invoice, so you cannot reuse them on a corrected invoice until you delete the voided shell completely. Void first to preserve the record while you sort things out, then delete the void when you need the billable items back.

Notice what all three have in common: nothing was reconciled, nothing was reported to a tax agency, and nobody outside your company ever saw the transaction. The moment any of those becomes true, stop reaching for Delete.

When to Void Instead​

Voiding is the default for real transactions recorded incorrectly. Reach for it when:

• You sent an invoice with errors and it hasn't been paid. Void it, then issue a corrected invoice with a new number. The customer can't pay a voided invoice, and your numbering stays sequential.
• A bill was entered wrong — wrong vendor, wrong amount, wrong date. Void the bad bill and enter the correct one. The audit trail shows the correction instead of a silent swap.
• A check was recorded but never reached the payee. If you recorded a bill as paid by check and the vendor never received it, void the payment to restore the bill to unpaid status while keeping the full history of what happened.
• You're fixing a prior period your accountant hasn't closed. If the books for the period are still open and you're correcting your own recent error, a void keeps the correction visible.

The pattern: the transaction represents something that really happened (or that someone really believed happened), and the honest record is "we recorded this, then we reversed it" rather than "this never existed."

When Neither Button Is Right​

Some situations call for neither voiding nor deleting:

• The invoice is already paid. Don't void or delete history your customer also holds. Issue a credit memo against the invoice and, if money is owed back, a refund receipt. That preserves both sides of the story.
• The transaction sits in a closed period. If you've closed the books with a closing date, or your accountant has filed a return covering that period, don't quietly rewrite history. Post the correction in the current period or talk to your accountant first.
• Sales tax was already reported. If the transaction fed into a filed sales tax return, corrections belong on an amended return or a current-period adjustment — not in a backdated deletion that silently changes what you reported.
• You're tempted to delete because the truth is embarrassing. Miscategorized personal spending, a duplicate that reveals sloppy processes, a bill you forgot for months — these are exactly the entries the audit trail exists to preserve. Fix them with visible corrections, not disappearances.

Five Transactions to Never Delete​

Keep this list taped next to whoever does your bookkeeping:

1. Reconciled transactions. Deleting one guarantees a beginning-balance discrepancy on your next reconciliation. If a reconciled entry is wrong, unreconcile it properly or recreate-and-reconcile — never just delete it.
2. Transactions with payments applied. Delete the invoice and the payment survives as an unapplied orphan; delete a bill payment and the bill silently returns to unpaid. Unapply the links first, then decide.
3. Automatically collected tax payments. Payroll tax payments QuickBooks already collected can't be deleted at all — the software will refuse. If a duplicate appears here, fix it with help, not force.
4. Anything in a closed or filed period. Changing filed history without a paper trail is how small cleanups become big problems.
5. Anything you're deleting to hide a mistake. If the motive is concealment rather than correction, that's the signal to void instead — or to fix it openly with a journal entry your accountant can see.

Lock Down the Buttons​

The best void-vs-delete policy is one your software enforces, not one people remember. Three controls do most of the work:

• Limit who can delete. Most staff who enter bills and invoices never need delete rights. In QuickBooks Online, review user roles so that only you or your bookkeeper can delete, while everyone else can create and edit within their lane.
• Close your books. Set a closing date with a password after each month-end or year-end. Anyone attempting to change a closed-period transaction gets warned — or blocked — instead of silently rewriting history.
• Review the Audit Log regularly. Make the Audit Log part of your month-end routine, not just your disaster-recovery plan. Filter for Deleted/Voided transactions and skim what changed. Five minutes of review catches both honest mistakes and the kind of deletions that deserve a conversation.

Keep Your Books Clean From Day One​

Getting the void habit right is one small piece of a bigger discipline: every change to your books should leave a trace you can follow later. That instinct matters whether you track finances in QuickBooks, a spreadsheet, or a plain-text ledger — and it's the reason Beancount.io is built on version-controlled, plain-text accounting, where your full edit history is the audit trail and nothing ever silently disappears. If you're curious how that workflow looks, the documentation walks through the core concepts, and Fava shows what dashboards and reports look like on top of a plain-text ledger. Get started for free and keep every correction visible from day one.