The clock, on both sides of 72 hours — transcript

Presentation 3 of 4 in The cancellation queue: what each button tells LHDN, and what it does to your books · about 11 minutes · for the whole-system operator — you run the books.

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 at GadgetSphere is racing the seventy-two hours and wants to know exactly what they are racing. In about eleven minutes you will learn where the clock starts, how it is counted, why approval does not pause it, what the last minute looks like on each record, what the screen does the moment the window shuts, and why support cannot open it again.

Step 1 — Know where the clock starts, and how it counts

After this step you will count from the right moment. The clock starts at the validation time LHDN returned, which BigLedger writes onto the e-invoice record in universal time. It does not start when the sale was made, when the document was finalised, when it was submitted, or when you noticed the mistake; a document that sat in a pool for a week and was validated on Tuesday night has a window that ends on Friday night. The backend counts in whole hours: seventy-one hours and fifty-nine minutes passes, seventy-two hours exactly does not. And the clock stops for nothing on your side. Raising a request does not pause it, approving it does not pause it, and a request waiting for an approver who is on leave is a request running out of time in silence.

Reference: Cancelling and Correcting a Validated E-Invoice — The one rule that decides everything

Step 2 — Trust the record, not the countdown

After this step you will read the hours off the right place. The Rejection Request screen, and the customer portal, both show hours remaining for cancellation, and both compute it in the browser from the validation time and the clock on your machine. It is a convenience, and it can be optimistic: a laptop set to the wrong time, or a validation time read in the wrong zone, shows hours you do not have. The backend’s whole-hour check is the rule, and it is the one that decides when you press Process. So when the figure on the screen is small, do not plan around it; open the record on To IRB E-Invoice, read the validation date-time, add seventy-two hours, and treat that as the deadline. The same seventy-two hours is your buyer’s window to reject; a buyer’s rejection through the portal lands with you and needs your approval like any other.

Reference: MY E-Invoice Portal Applet — Lifecycle and effects

Step 3 — Read the last minute: what a late request leaves on each record

After this step you will recognise a request that arrived too late, on any of the three records. If the window has closed by the time Process Request runs, BigLedger refuses before calling LHDN. The Cancellation Queue row stays, at submission failed, with the Request Error passed seventy-two hours from validation date time. The request itself is marked completed with a cancellation status of FAILED. The buyer’s address gets an e-mail saying the request is not submissible, and you get nothing. And the e-invoice record keeps reading Valid, because nothing reached LHDN. If instead BigLedger’s check passed and LHDN’s own did not, because the two clocks disagreed by a minute, the shape is the same except that the Request Error carries LHDN’s response text word for word. Either way, the retry button in the previous presentation cannot help; a closed window stays closed.

Screen: Cancellation → Cancellation Queue with a failed row and the Request Error reading Passed 72 hours from validation date time

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

Step 4 — Watch the screen change the moment the window shuts

After this step you will know what the single remaining option is doing. Open a request whose validation time is more than seventy-two hours old and the processing logic list has changed: the three cancelling choices are gone and only new reversal document remains. That is the screen being honest with you. Nothing can now cancel the e-invoice, so the only thing worth offering is the one logic that never tried to: it clones the sales document into its reversing type, a sales return for GadgetSphere’s laptop invoice, finalises it so it posts like any other document, and gives it an e-invoice of its own. The original stays Valid, and LHDN’s records net out. If you would rather raise the credit note by hand, or no request was ever raised, the credit note applet does the same job; either way, check the reference to the original before it goes.

Screen: Cancellation → Rejection Requests, the request opened on Update, Remained Hours For Cancellation at zero and the Processing Logic list holding one entry

Reference: Cancelling and Correcting a Validated E-Invoice — Step 6: Past 72 hours — issue a credit note instead

Step 5 — Know that support has no back door

After this step you will not ask for one. BigLedger does carry two direct cancellation routes that skip the request and approval screens, a bulk cancellation and a direct cancellation by document, and they exist for support to clear duplicates. Both run the same three checks as Process Request before they call LHDN: Valid, an LHDN identifier, fewer than seventy-two hours. So a request to support after the window is a request they cannot fulfil, however quickly they answer; the check is BigLedger’s, and LHDN applies its own on top. What support can do late is help with the correction, the reversing document or the credit note, and for a consolidated e-invoice the re-reporting of the receipts inside it. Ask for that, and say the e-invoice is consolidated if it is, rather than asking for a cancellation that no path on the platform will perform.

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

Step 6 — Cancel early, because the estate shows how late people leave it

After this step you will treat day one as the deadline. Across the estate, cancellation is a minority activity and a real one: about a third of tenants hold at least one Cancelled e-invoice, most of them consolidated. The commonest state a rejection request is found in is raised and never approved, on more than a dozen tenants. And of the cancellations whose validation and cancellation times can be compared, about half fall in the last twenty-four hours of the window, none beyond it, because the check holds. Put together, that is a picture of people noticing late, raising a request, and waiting for an approver. So the rule at GadgetSphere is the one the guide gives: before you raise anything, line up the person who can approve it today, then raise, approve and process in one sitting, and read the queue row before you leave the screen.

Reference: Cancelling and Correcting a Validated E-Invoice — Before you start

How the steps fit together

    flowchart TD
  s1["Step 1 — Know where the clock starts, and how it counts"]
  s2["Step 2 — Trust the record, not the countdown"]
  s3["Step 3 — Read the last minute: what a late request leaves on each record"]
  s4["Step 4 — Watch the screen change the moment the window shuts"]
  s5["Step 5 — Know that support has no back door"]
  s6["Step 6 — Cancel early, because the estate shows how late people leave it"]
  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.

1. Where do the 72 hours start? When the sales document was finalised
At the validation time LHDN returned, recorded on the e-invoice in universal time
When the rejection request was approved

2. Does approving a request stop the clock? Yes, an approved request can be processed at any time
No; nothing on your side pauses it, and the request waits in silence
Only if the buyer raised it

3. Process Request runs after the window has closed. What does LHDN receive? Nothing; BigLedger refuses first and leaves a failed queue row reading Passed 72 hours
The cancellation, which LHDN rejects
A credit note

4. The processing-logic list on a request shows only New reversal document. Why? Your role lacks the other permissions
The e-invoice is consolidated
More than 72 hours have passed; the screen keeps only the logic that never cancels

Answer key

At the validation time LHDN returned, recorded on the e-invoice in universal time — Cancelling and Correcting a Validated E-Invoice — The one rule that decides everything
No; nothing on your side pauses it, and the request waits in silence — Cancelling and Correcting a Validated E-Invoice — The one rule that decides everything
Nothing; BigLedger refuses first and leaves a failed queue row reading Passed 72 hours — My E-Invoice Admin Applet — 6. Cancellation (Rejection Requests → Cancellation Queue)
More than 72 hours have passed; the screen keeps only the logic that never cancels — Cancelling and Correcting a Validated E-Invoice — Step 6: Past 72 hours — issue a credit note instead

This is a self-check. Your answers are marked in your browser and stay there — nothing is sent anywhere, nothing is recorded, and the marking is readable in the page source, so it is not a credential. Open the answer key at any time.

Next: How you will know: three records, and the check before you void a cash bill · Back to the series · Play this as a presentation

Last updated on September 18, 2026

The clock, on both sides of 72 hours How you will know: three records, and the check before you void a cash bill