Cancel inside the window — transcript

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

This lesson is for you if you run the books at GadgetSphere, you have read the validation date-time on a wrong e-invoice, and the 72 hours are still running. In about twelve minutes you will raise the cancellation request, approve it with the right decision about the sales document behind it, send it to the Inland Revenue Board, LHDN, and confirm that the record now reads Cancelled. The whole thing takes about ten minutes when the approver is available today, which is the one thing to check before you start.

Step 1 — Check that the e-invoice is actually wrong

After this step you will not destroy a valid e-invoice on the strength of a report that looked odd. One false alarm to know is two rows on the submission listing with the same document number. That is very often not a duplicate: sales invoices and self-billed purchase invoices draw their numbers from two independent sequences that start at the same value, and the listing does not show which direction a document went. Cancel on the strength of repeated numbers alone and you can destroy perfectly valid e-invoices that are still inside their 72 hours. Check the document type on both rows before you conclude anything. A real duplicate is one sale inside two Valid e-invoices, typically a receipt submitted individually while a copy still sat in the Batch Pool, and you find it by reconciling, not by reading a listing. GadgetSphere’s laptop invoice is simpler: the customer is right, and the amount is wrong.

Reference: E-Invoice Validation: Five Common Errors and Their Fixes — 4. The same sale looks like it is at LHDN twice

Step 2 — Line up the approver before you raise anything

After this step the request you are about to raise will not stall for want of a person. Three things must be true. The e-invoice status is Valid; nothing here applies to a document still in a pool or still In Queue, which you simply fix and resubmit. You have read its validation date-time, from the Submission Date column of the Submission Detail Report under Monthly Report; for GadgetSphere’s laptop invoice that was 21:40 last night, so the deadline is 21:40 two nights on. And somebody who can set a request to Approved is available today. A cancellation request does not travel on its own. If the person who normally approves is on leave and nobody else has been shown the screen, you will raise the request, watch it sit, and run the clock out. Find your approver now, tell them what is coming, and only then go to the next step.

Reference: I submitted a wrong invoice and LHDN has already validated it. Can I cancel? Cancelling and correcting a validated e-invoice — Before you start

Step 3 — Raise the request

After this step a cancellation request exists against the e-invoice, waiting for approval. On the To IRB E-Invoice row, use Request for Rejection. The button lights only on a Valid e-invoice still under seventy-two hours old by your computer’s clock, so if it is greyed out, either the status is not Valid or the window has closed; a lit button is a good sign, not a guarantee, because the server counts again later. Give the reason; it is sent to LHDN as the cancellation reason, so write something a tax officer can read, such as invoiced quantity ten, delivered eight. The request lands in Cancellation, then Rejection Requests, as requested and in progress, with no approval status yet. A buyer can raise the same rejection from the customer portal; it arrives in the same list and needs the same approval from you. Either way, what you have now is a request and nothing more.

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

Step 4 — Approve it and decide what happens to the sales document

After this step the request is approved with a recorded decision about the invoice behind it. This is the step that is easy to miss, because nothing advances a cancellation request automatically. A request you raised and walked away from sits at requested and in progress until the 72 hours expire and the option is gone. Go to Cancellation, then Rejection Requests, open the request, set the approval status to Approved, and choose a processing logic. Void the original document if the sale itself is wrong, and raise a fresh one. Regenerate a new e-invoice if the invoice is right and only the e-invoice was built wrong. A new reversal document cancels nothing at LHDN: the e-invoice stays Valid beside a reversing document. Cancel for edit and resubmit fixes only the buyer’s identity or a reference, and sends the same record back. GadgetSphere’s laptop invoice has the wrong amount, so void original document is right.

Reference: Approve and send a cancellation of a validated e-invoice to LHDN — Step 3: Approve the request and choose what happens to the source document

Step 5 — Send the cancellation to LHDN

After this step LHDN has cancelled the e-invoice, or you know exactly why not. With the request approved and a logic chosen, use Process Request. BigLedger builds a Cancellation Queue row and calls LHDN there and then. Go to Cancellation, then Cancellation Queue, and read the row. If the call failed, Request Error carries the reason. Before calling LHDN, BigLedger checks three things and refuses on any of them: the e-invoice must be Valid, it must actually carry an LHDN document reference, and fewer than 72 hours must have passed since validation. The refusal you least want to see reads Passed 72 hours from validation date time. It means the window closed while the request sat waiting for approval, and the route is now a credit note, the next lesson. Do not wait for an e-mail: the one BigLedger sends goes to the buyer, and on a consolidated e-invoice nowhere. The queue row is your notification.

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

Step 6 — Handle a consolidated e-invoice

After this step you will not destroy a month’s reporting with one wrong choice. A consolidated e-invoice covers hundreds of receipts and has no single sales document behind it, so only cancel for edit and resubmit works. The other three fail, and not equally. Void original document is refused with Can not void the generic document before LHDN is called. Regenerate new e-invoice cancels the e-invoice at LHDN first and only then fails to rebuild it, so the month is cancelled and nothing replaces it. New reversal document fails silently, with nothing on the screen. If cancel for edit and resubmit is not offered, raise a support request and say the e-invoice is consolidated. Do not try the others. The receipts inside still need reporting and do not come back on their own: support pushes them back to the Batch Pool as a named list, so ask in the same request. The Discrepancies Report still reads clean meanwhile.

Reference: Cancel a consolidated e-invoice, and get its receipts reported again — Step 5: If it is a consolidated e-invoice, act immediately

Step 7 — Confirm it went through

After this step you can prove the cancellation, in thirty seconds. Open the e-invoice on Internal Submission, then To IRB E-Invoice. Its status now reads Cancelled. Go to Cancellation, then Rejection Requests; your request shows as completed and approved, not still in progress. Then look at the sales document behind it, which should be in the state you chose: voided, re-issued, or still Final after cancel for edit. For GadgetSphere that means the RM 12,400 invoice reads Void, and the branch raises a fresh invoice for eight machines and RM 9,920, which gets its own e-invoice when it is finalised. Watch that one on To IRB E-Invoice to Valid, not Submitted, as you would any other. When the corrected e-invoice reads Valid and the old one reads Cancelled, LHDN holds the right figure. Whether the customer has the document is the Email Dashboard’s question, not this screen’s. Keep both rows in mind for month-end; the last lesson explains why.

Reference: I submitted a wrong invoice and LHDN has already validated it. Can I cancel? Cancelling and correcting a validated e-invoice — What success looks like

How the steps fit together

    flowchart TD
  s1["Step 1 — Check that the e-invoice is actually wrong"]
  s2["Step 2 — Line up the approver before you raise anything"]
  s3["Step 3 — Raise the request"]
  s4["Step 4 — Approve it and decide what happens to the sales document"]
  s5["Step 5 — Send the cancellation to LHDN"]
  s6["Step 6 — Handle a consolidated e-invoice"]
  s7["Step 7 — Confirm it went through"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  

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: Correct with a credit note · Back to the series · Play this as a presentation