Two buttons that look the same and aren't

Sooner or later you'll need to undo something in your books — an invoice sent in error, a duplicate bill, a payment recorded against the wrong customer. Most accounting software offers two ways to do it: void the transaction or delete it. They sound interchangeable, and the result on screen can look identical — the amount stops affecting your totals either way. But what happens to the record behind them is completely different, and choosing the wrong one quietly weakens your books. (General education, not accounting advice.)

What deleting does

Deleting a transaction removes it as if it never existed. The record is gone, and so is any trace that it was ever there. That feels clean, but it's exactly the problem: if an invoice was numbered, deleting it leaves a gap in the sequence with no explanation. If anyone — you, an accountant, an auditor — later asks "what happened to invoice 1042?", there's no answer in the books. Deletion erases the history along with the mistake.

What voiding does

Voiding keeps the transaction on file but sets its financial effect to zero and marks it, visibly, as void. Invoice 1042 still exists; it just shows as voided and no longer counts toward revenue or accounts receivable. The number stays in sequence, the date stays put, and anyone reviewing the books can see that a transaction was created and then deliberately cancelled — and ideally why.

That preserved trail is the whole point. A core part of audit readiness is being able to show not just what your books say now, but how they got that way. A void tells that story. A deletion hides it.

When to void (almost always)

Reach for void whenever the transaction touched anything that matters:

  • A numbered invoice — voiding keeps the sequence intact, so there's no unexplained gap.
  • Anything in a closed period — once you've run a month-end close and reported the numbers, deleting a transaction from that period changes history you've already stood behind. Void it and, if needed, record a correction in the current period instead.
  • A recorded payment or a posted bill — these have already moved real balances; voiding reverses the effect while leaving the evidence that it happened.

In a regulated or audit-minded business, voiding is close to a default. The few extra zeroed records cost you nothing and protect the integrity of the trail.

When deleting is genuinely fine

Deletion isn't always wrong — it's fine for things that never really entered your financial record:

  • A draft that was never sent, posted, or numbered. Nothing relied on it, so removing it changes nothing downstream.
  • An obvious duplicate caught immediately, before either copy affected a report or a balance — though even here, voiding is the safer habit.

The test is simple: did anything depend on this transaction, or could anyone reasonably ask about it later? If yes, void it. If it was a scratch entry that touched nothing, deleting it is harmless.

The audit-trail angle

The reason this small choice matters more than it seems is that good books aren't just correct — they're explainable. The difference between a void and a delete is the difference between a record that says "this was cancelled, here's the proof" and a record with a silent hole in it. The first survives scrutiny; the second invites the question you can't answer. This is the same instinct behind keeping business and personal finances cleanly separated: the goal isn't only accurate numbers, it's a history you can defend.

Hosting Books favors voiding for anything that has touched your numbers — keeping the original record, zeroing its effect, and marking it void in a tamper-evident log — so your books stay both accurate and explainable.

This article is general educational information about accounting concepts and is not accounting advice for your specific situation.