Skip to content
The consolidated e-invoice after a cancellation: where the receipts went · presentation 2 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.

The consolidated e-invoice after a cancellation: where the receipts went · presentation 2 of 4

Four buttons, one missing column: why three cancellation choices do nothing here

You can explain why void, regenerate and new reversal document all fail on a consolidated e-invoice for the same single reason…

One cause, four symptoms

Step 1 — Recognise that all four buttons ask the same question

You will predict every failure in this presentation before you see it.

  • Save and Resubmit, the second half of the fourth option…
Screen capture pending the demo tenant

Cancellation → Rejection Requests, the Processing Logic drop-down open with all four options

Step 2 — Void original document: refused before anything happens

You will treat this failure as the harmless one.

  • Change the logic on the request and process the queue row again

Valid

Your e-invoice is still Valid

Step 3 — Regenerate new e-invoice: the order of operations is the damage

You will never choose this one on a consolidated e-invoice.

Where this step sits
    flowchart TD
  s1["1. Recognise that all four buttons ask…"]
  s2["2. Void original document: refused before anything…"]
  s3["3. Regenerate new e-invoice: the order of…"]
  s4["4. New reversal document: fails without saying…"]
  s5["5. Cancel for edit and resubmit…"]
  s6["6. Change a logic without starting again"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

The two quiet ones

Step 4 — New reversal document: fails without saying so

You will know why one request can look untouched and be finished.

Where this step sits
    flowchart TD
  s1["1. Recognise that all four buttons ask…"]
  s2["2. Void original document: refused before anything…"]
  s3["3. Regenerate new e-invoice: the order of…"]
  s4["4. New reversal document: fails without saying…"]
  s5["5. Cancel for edit and resubmit…"]
  s6["6. Change a logic without starting again"]
  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 — Cancel for edit and resubmit: the one that works, and its own dead end

You will know what to choose and what to expect afterwards.

  • Cancel for edit and resubmit cancels at LHDN and stops
Screen capture pending the demo tenant

Internal Submission → To IRB E-Invoice, the Cancelled consolidated record with Save and Resubmit still offered

Step 6 — Change a logic without starting again

You will recover from a wrong choice in under a minute.

What you do
  1. Open the request, change the Processing Logic to cancel for edit and resubmit…

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.