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

Play this as a presentation — one slide per step, with the same narration. Every word of every step is on this page.

This presentation is for whoever has a cancellation request open on a consolidated e-invoice and four processing logics to choose between. In about eleven minutes you will see that all four reach for the same missing thing, why one of them is merely a wasted afternoon and another loses you the month, and what to press instead.

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

After this step you will predict every failure in this presentation before you see it. Each of the four processing logics was written for an ordinary e-invoice, the kind that reports one sales invoice. Each of them, at some point, asks the e-invoice record for its source document. Void asks so it can turn that document into a void. Regenerate asks so it can build a fresh e-invoice from it. New reversal document asks so it can clone it. And Save and Resubmit, the second half of the fourth option, asks so it can copy your corrections back onto it. A consolidated e-invoice has no answer to that question. Four different screens, four different messages, one cause.

Reference: My E-Invoice Admin Applet — After a consolidated cancellation: where the receipts are, and what puts them back

Step 2 — Void original document: refused before anything happens

After this step you will treat this failure as the harmless one. Void is the only logic that checks before it acts. Before LHDN is called at all, it runs a dry test to see whether the source document could be turned into a void, and on a consolidated e-invoice that test cannot even begin, because there is no document to test. So the request fails with Can not void the generic document, and you have lost nothing but the time. That exact sentence is worth memorising: no other logic produces it, so seeing it tells you immediately both what was chosen and that LHDN was never contacted. Your e-invoice is still Valid. Change the logic on the request and process the queue row again.

Reference: My E-Invoice Admin Applet — 6. Cancellation (Rejection Requests → Cancellation Queue)

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

After this step you will never choose this one on a consolidated e-invoice. Regenerate does the two halves of its job in the worst possible order. It cancels at LHDN first, and only when that has succeeded does it go looking for the source document to rebuild from. On a consolidated e-invoice that lookup fails, and by then March’s e-invoice is already cancelled at LHDN with nothing to replace it. There is no check beforehand, because the check would have to know what void’s check knows and it does not. The result is a month of takings that were reported and are now not, inside a seventy-two hour window you cannot extend. In the estate this has been done, on a few tenants, many times over.

Reference: Cancelling and Correcting a Validated E-Invoice — Step 5: If it is a consolidated e-invoice, act immediately

Step 4 — New reversal document: fails without saying so

After this step you will know why one request can look untouched and be finished. New reversal document never calls LHDN at all — it clones the source document into its opposite and sends that. On a consolidated e-invoice the clone step fails on the missing document, and that failure is caught by a catch-all at the top of the processor and written only to a log. No Request Error appears on the queue row. No e-mail goes anywhere. Nothing on the screen changes. This matters most past seventy-two hours, when the screen collapses the logic list down to this single option: on a consolidated e-invoice, that one remaining choice is one that silently does nothing. A credit note raised by hand is the real remedy there.

Reference: My E-Invoice Admin Applet — 6. Cancellation (Rejection Requests → Cancellation Queue)

Step 5 — Cancel for edit and resubmit: the one that works, and its own dead end

After this step you will know what to choose and what to expect afterwards. Cancel for edit and resubmit cancels at LHDN and stops. It runs no convertibility check, it does not touch the sales documents, and it leaves them final. That is precisely right for a consolidated e-invoice, because there is nothing to void. What it does not give you is the resubmit. That half is the Save and Resubmit button on the now-Cancelled record, and on a consolidated e-invoice pressing it raises Generic Document Not Found — the fourth appearance of the same missing column, this time in a message that names it. So this route cancels correctly and then hands you back a problem. The next two presentations are about that problem.

Reference: My E-Invoice Admin Applet — 5. Fixing an Invalid e-invoice from To IRB E-Invoice

Step 6 — Change a logic without starting again

After this step you will recover from a wrong choice in under a minute. A request that has failed is marked completed, and Process Request only ever takes requests that are still in progress, so pressing it again does nothing for ever. The retry lives on the other screen. Open the request, change the Processing Logic to cancel for edit and resubmit, save it, then go to Cancellation Queue, select the failed row and use Process. That re-runs the row against the logic as it now stands. This is the fastest way out of a void refusal, and it is the only way out, because nothing else will pick that request up again. If regenerate was the choice, the queue row is gone and this will not help — go straight to the fourth presentation.

Reference: My E-Invoice Admin Applet — 6. Cancellation (Rejection Requests → Cancellation Queue)

How the steps fit together

    flowchart TD
  s1["Step 1 — Recognise that all four buttons ask the same question"]
  s2["Step 2 — Void original document: refused before anything happens"]
  s3["Step 3 — Regenerate new e-invoice: the order of operations is the damage"]
  s4["Step 4 — New reversal document: fails without saying so"]
  s5["Step 5 — Cancel for edit and resubmit: the one that works, and its own dead end"]
  s6["Step 6 — Change a logic without starting again"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  

Check yourself

Three to five questions on what you just heard. Every correct answer links to the page that makes it correct, so you can check the source, not just the mark.

Next: Nobody is going to tell you: the e-mail, the queue and the report all read clean · Back to the series · Play this as a presentation