Skip to content
Courses
Courses C-00000 to C-00999
Cancel, correct and reconcile with MyInvois
The 72-hour window

The 72-hour window

Lesson 1 of 6 in Cancel, correct and reconcile with MyInvois · about 8 minutes · for the whole-system operator — you run the books.

Play this lesson as slides — one slide per step, with the same narration. The full text of every step is on this page.

This lesson is for you if you run the books at GadgetSphere and someone has just told you that an e-invoice the Inland Revenue Board, LHDN, validated yesterday is wrong. In about eight minutes you will be able to say what changed the moment LHDN said Valid, read the one date on the record that decides everything, say what a cancellation actually is, and name which of the two correction routes you are on. Nothing is cancelled in this lesson; that is the next one. This one stops you from wasting the hours you may not have.

Step 1 — Recognise Valid as a one-way door

After this step you know why you cannot simply fix the wrong e-invoice. Yesterday a GadgetSphere branch invoiced a corporate customer RM 12,400 for a laptop refresh. This morning the customer calls: eight machines, not ten, so the invoice should read RM 9,920. The e-invoice went to LHDN last night and came back Valid. From that moment it is a filed tax record, and BigLedger refuses to let you type over it. Press Save and Resubmit on the To IRB E-Invoice row and the message is that the e-invoice is already validated with Valid status and must be cancelled first. You get a similar refusal at Submitted, because LHDN has not finished deciding; wait a few minutes and the status settles. Notice what this rule does not cover. A document still in a pool, or still In Queue, has not been validated by anyone. You fix it and resubmit, as in the previous course.

Reference: Validation and clearance — How it behaves in BigLedger

Step 2 — Name the 72-hour window

Once LHDN has said Valid, an e-invoice is a filed tax record, and there is exactly one way to take it back: cancel it at LHDN within 72 hours. The clock starts at the moment LHDN validated the document, not when you raised the sale and not when you noticed the mistake. BigLedger records that moment on the e-invoice record, in universal time, and it can be earlier than the time the MyInvois portal appears to show you, so read the validation date-time off the record and count 72 hours from that. Inside the window, you cancel and then issue the corrected document. Past it, nothing can cancel the e-invoice at all, and the only correction is a credit note referencing the original. The same 72 hours is your buyer’s window to reject the e-invoice. It is not a submission deadline; no rule says an invoice must reach LHDN within 72 hours of being raised.

Reference: What Malaysia Requires: E-Invoicing Explained — What happens after you submit

Step 3 — Read the deadline off the record

After this step you have a deadline written down that you can trust. Open the My E-Invoice Admin Applet, go to Internal Submission, then To IRB E-Invoice, and search by Doc No, which is your own invoice number. Open the row and read its validation date-time. Add 72 hours. GadgetSphere’s laptop invoice was validated at 21:40 last night, so the deadline is 21:40 two nights from now: comfortable, but not something to leave until the afternoon of the third day. The mistake people make here is counting from the invoice date. On a backdated or queued document the invoice date and the validation time can be days apart, and every one of those days is a day you do not have. Read the field. If the moment you calculated is still ahead of you, you are on the cancellation route. If it has passed, you are on the credit note route, and nothing you press will change that.

Screen: Internal Submission → To IRB E-Invoice with the RM 12,400 invoice opened, status Valid, and its validation date-time visible on the record

Reference: Cancelling and Correcting a Validated E-Invoice — Step 1: Work out whether you are still inside the window

Step 4 — Understand what a cancellation actually does

After this step you can explain a cancellation to the branch that raised the sale. A cancellation asks LHDN to mark the validated e-invoice Cancelled. The record does not disappear; it stays on To IRB E-Invoice with the status Cancelled, and if the sale was real it still needs reporting correctly afterwards. So a cancellation is a request, not a button. Someone raises it, someone approves it and decides what happens to the sales document behind it, and someone sends it to LHDN. Nothing moves it along by itself. The choice at approval is the part people miss. You can void the original document, regenerate a new e-invoice from the same document, create a reversing document, or cancel at LHDN only and fix the document yourself. For GadgetSphere’s laptop order the invoice itself must come down to eight machines, so the last one is right: LHDN cancels, the branch corrects the invoice, and it goes back as a fresh e-invoice.

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

Step 5 — Name the route you are on

After this step you can say, in one sentence, what happens next. Inside the window: cancel the e-invoice at LHDN, then issue the corrected document, which goes to LHDN as a new e-invoice and which you watch to Valid like any other. Past the window: no cancellation is possible, so the correction is a credit note for the difference, or for the whole amount, referencing the e-invoice that was wrong. Once the credit note is validated, LHDN’s records net out correctly even though the original is still there. One thing to settle before you go down the second route: your accountant. In most of these cases GadgetSphere’s own ledger is already right, because the sale was corrected in the books the moment the customer called, and only the tax reporting is overstated. The credit note exists to fix LHDN, not the books. Agreeing that first stops you correcting the same thing twice.

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

How the steps fit together 

    flowchart TD
  s1["Step 1 — Recognise Valid as a one-way door"]
  s2["Step 2 — Name the 72-hour window"]
  s3["Step 3 — Read the deadline off the record"]
  s4["Step 4 — Understand what a cancellation actually does"]
  s5["Step 5 — Name the route you are on"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5

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. From which moment do the 72 hours run?


2. You press Save and Resubmit on an e-invoice whose status is Valid. What happens?


3. More than 72 hours have passed since validation. What corrects LHDN's records?


4. Is the 72-hour window a deadline for getting an invoice to LHDN?


5. Where do you read the validation date-time?


Answer key
  1. From the validation time recorded on the e-invoice record — Validation and clearance — How it behaves in BigLedger
  2. BigLedger refuses; the e-invoice must be cancelled first — My E-Invoice Admin Applet — 5. Fixing an Invalid e-invoice from To IRB E-Invoice
  3. A credit note referencing the original e-invoice — Cancelling and Correcting a Validated E-Invoice — The one rule that decides everything
  4. No; it is the cancellation and rejection window, nothing else — What Malaysia Requires: E-Invoicing Explained — What happens after you submit
  5. On the e-invoice record in Internal Submission, then To IRB E-Invoice — Cancelling and Correcting a Validated E-Invoice — Before you start
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 lesson: Cancel inside the window · Back to the course

Last updated on
The 72-hour window — slides