The cancellation queue: what each button tells LHDN, and what it does to your books · 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 cancellation queue: what each button tells LHDN, and what it does to your books · presentation 2 of 4

Four choices, and what each one tells LHDN

You can say, for each of the four processing logics, whether LHDN is told anything at all, what is checked before it is told…

The shape of the four

Step 1 — See that three cancel first, and one never calls LHDN at all

You will not read the list as four flavours of cancel.

What this step names

It never contacts LHDN
Never changes the e-invoice
Instead raises a second document that reverses the first

Void original document

Step 2 — Void original document: the dry run that happens before LHDN hears anything

You will know why one refusal arrives with LHDN never having been called.

Valid

The e-invoice is still Valid and you have lost nothing but time

Step 3 — Void original document: what happens after LHDN says yes

You will check the document and not assume.

Cancelled

BigLedger writes Cancelled onto the e-invoice record and then voids the sales…

The other two that cancel

Step 4 — Cancel for edit and resubmit: no check, no void, and a resubmit that fixes who, not how much

You will know what the word edit covers.

Open the now Cancelled record on To IRB E-Invoice…

Screen capture pending the demo tenant

Internal Submission → To IRB E-Invoice on a Cancelled record, buyer details editable, the lines tab read-only, and the Save and Resubmit button

Step 5 — Regenerate new e-invoice: cancel first, rebuild second, and the two ways that goes wrong

You will use regenerate only when the sale is right and the e-invoice was built wrong.

Where this step sits

    flowchart TD
  s1["1. See that three cancel first…"]
  s2["2. Void original document: the dry run…"]
  s3["3. Void original document: what happens after…"]
  s4["4. Cancel for edit and resubmit…"]
  s5["5. Regenerate new e-invoice: cancel first…"]
  s6["6. New reversal document: LHDN is told…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

The one that does not cancel

Step 6 — New reversal document: LHDN is told nothing, and a second document appears

You will not pick this logic expecting the e-invoice to change.