The two buttons sit right next to each other in QuickBooks Online, but they do different things. Picking the wrong one can quietly distort a business's records in a way that's hard to catch later.

If you've ever wondered about the QuickBooks Online void vs. delete choice, here's what you actually need to know.

What's the Difference Between Voiding and Deleting a Transaction?

Deleting a transaction removes it from the active books. It no longer appears in the usual transaction lists or reports, although QuickBooks Online's audit log still retains a record that the transaction was deleted.

Voiding keeps the transaction in QuickBooks Online but changes its financial effect to zero. The record remains visible, so there's still a trail showing that the transaction existed and was later voided.

The basic difference is simple:

Delete = remove the transaction.

Void = keep the transaction, but remove its financial effect.

Why Deleting an Invoice Number Creates an Unexplained Gap

Invoices and cheques can carry sequential numbers, and that sequence matters when you're trying to maintain a clean, explainable audit trail.

Delete an invoice, and that number disappears from the active transaction history. Someone reviewing the books later may see a gap with no obvious explanation unless they go digging through the audit log.

Void it instead, and the record stays: the invoice existed, it was voided, and the sequence remains visible and explainable.

A missing number isn't automatically a bookkeeping problem. There can be perfectly legitimate reasons for gaps in numbering. The issue is that deleting a transaction can make something that was perfectly explainable much harder to understand later.

A sequence of invoices with unexplained gaps invites questions that a voided-but-visible record answers on its own.

When Is It Safe to Delete a Transaction in QBO?

Not every deletion is a problem.

A transaction entered by mistake and caught immediately — before it has been sent, reconciled, reported, or referenced anywhere else — may be perfectly appropriate to delete.

For example, if you accidentally create an invoice for the wrong customer and catch the mistake before sending it, there's usually little reason to preserve an incorrect transaction.

The important question isn't simply, "Was this entered incorrectly?"

It's "Has anything else happened that now depends on this transaction existing?"

Once the answer is yes, think twice before deleting it.

When Should You Void Instead of Delete?

Once a transaction has become part of the business's actual records, voiding may be the better correction because it preserves the history of what happened.

A cheque that was created and then needs to be cancelled, an invoice sent to a client that turns out to be wrong, or a transaction that was recorded in error after the books have already been reviewed are all situations where preserving the original record may be useful.

There isn't one universal rule that says "always void." The right correction depends on the transaction, what actually happened, and whether the original transaction has already affected other parts of the books.

The general bookkeeping principle is simple: don't erase something that another person may reasonably expect to be able to trace.

How Deleting a Reconciled Transaction Can Affect Your Reconciliation

This is where it gets messy.

If you delete or void a transaction that was included in a completed bank or credit-card reconciliation, you've changed the transactions that made up that reconciled balance.

The exact effect can vary depending on the transaction type and timing, but either action can create reconciliation issues once a period has already been reconciled.

So don't just void or delete a reconciled transaction and move on without checking what it touched.

If a reconciled transaction genuinely needs to be corrected, check the reconciliation and the affected period afterward. Depending on what happened, you may need to undo or redo a reconciliation or make another appropriate correction.

Once a transaction has been reconciled, stop and think before changing it.

Why an Explainable Audit Trail Matters for Reviews

A clean, explainable trail matters most exactly when someone else needs to review the books — an accountant at year-end, a lender reviewing financial information, or the CRA during a review.

A sequence of invoices with unexplained gaps can invite questions. A visible voided transaction can provide part of the explanation without someone having to dig through the audit log to figure out what happened.

This same principle — keeping a clean trail instead of erasing mistakes — comes up constantly during a catch-up.

RSB's catch-up bookkeeping guide covers the broader process this fits into.

FAQ

Can a voided transaction simply be un-voided later if it turns out it shouldn't have been voided?

Not directly. QuickBooks Online doesn't provide a simple one-click "un-void" function.

The usual fix is to create a replacement transaction with the correct information and make sure the books accurately reflect what actually occurred. Because that can affect dates, numbering, reconciliations and reporting, it's worth being sure before you void something rather than treating voiding like an easy undo button.

Does voiding affect GST/HST already reported on a voided invoice?

It can.

If the invoice affected a GST/HST reporting period that has already been filed, voiding the invoice in QuickBooks Online doesn't automatically change what was already reported to the CRA.

You may need to determine whether the original GST/HST treatment needs to be corrected separately. This is one of those situations where you should check the specific circumstances rather than assuming the void alone fixes everything.

Is there a difference between voiding and deleting for bank-feed transactions specifically?

The same basic distinction applies: deleting removes the transaction from the active books, while voiding preserves the transaction but removes its financial effect.

But bank-feed transactions have an additional consideration. If the transaction has already been matched, added, or reconciled, simply deleting or voiding it may not be the right correction.

Look at what happened to the transaction after it entered QBO before deciding how to fix it.

What's the safest default if you're unsure?

Before changing anything, determine whether the transaction has been sent, reconciled, reported, or referenced elsewhere in the books.

In many cases, voiding preserves a clearer audit trail than deleting, but the right answer depends on the transaction and the reporting periods involved.

If you're not sure what the change will affect, stop before clicking either button and work out what actually needs to be corrected.

Follow the system. File with confidence.