Skip to content
Taking it back: void, undo and discard · presentation 1 of 4 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Taking it back: void, undo and discard · presentation 1 of 4

Four buttons, and only one of them is a void

You can choose between editing, undoing, discarding, voiding and issuing a credit note before you touch anything — and you know in advance which…

Five operations, one screen

Step 1 — Choose the operation before you press anything

You will stop reaching for Void by reflex.

What you do
  1. Pick the one that matches what actually happened, not the one nearest the mouse

Step 2 — Know what the button does while you wait

You will know why nothing has reversed yet when the screen comes back.

Screen capture pending the demo tenant

A finalised sales invoice with the Void dialog open, asking for a reason

Step 3 — Expect a void to be slower than a finalise

You will stop escalating something that is merely queued.

Where this step sits
    flowchart TD
  s1["1. Choose the operation before you press…"]
  s2["2. Know what the button does while…"]
  s3["3. Expect a void to be slower…"]
  s4["4. Read the refusal, because it tells…"]
  s5["5. Understand why e-invoicing takes Void away"]
  s6["6. Accept that a void is permanent…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

When the answer is no

Step 4 — Read the refusal, because it tells you the fix

You will treat a refused void as an instruction rather than an error.

Where this step sits
    flowchart TD
  s1["1. Choose the operation before you press…"]
  s2["2. Know what the button does while…"]
  s3["3. Expect a void to be slower…"]
  s4["4. Read the refusal, because it tells…"]
  s5["5. Understand why e-invoicing takes Void away"]
  s6["6. Accept that a void is permanent…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s4 here;

Step 5 — Understand why e-invoicing takes Void away

You will know why the button worked last quarter and does not now.

What this step names
  1. Once a company's e-invoice status is enabled
  2. Sales invoices
  3. Returns
  4. Credit notes
  5. Debit notes and refund notes cannot be voided at all
  6. A cash bill can be voided only until its e-invoice has actually…

Step 6 — Accept that a void is permanent, and so is the number

You will treat the decision as final, because it is.

Where this step sits
    flowchart TD
  s1["1. Choose the operation before you press…"]
  s2["2. Know what the button does while…"]
  s3["3. Expect a void to be slower…"]
  s4["4. Read the refusal, because it tells…"]
  s5["5. Understand why e-invoicing takes Void away"]
  s6["6. Accept that a void is permanent…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s6 here;

NarrationSlide 1 of 9

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.