When a document will not go at all — 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 and you have a document that has defeated everything in this course. Some documents genuinely cannot be submitted as they stand, and recognising one quickly is worth more than another hour of trying. In about eleven minutes you will learn the five of them, what each one actually needs, and what to put in front of support when the answer is someone else’s.

Step 1 — The foreign buyer with no tax number

After this step you will recognise the one genuine dead end in ordinary retail. A tourist buys a laptop at a Penang branch and pays on a passport. That sale cannot be consolidated, because a consolidated e-invoice cannot carry a foreign buyer. It cannot fall back on the general public tax number either, because that number is only ever substituted for a Malaysian identity type, and LHDN rejects it alongside a passport anyway. So with no tax number the document is not submitted at all and simply waits in the Individual Pool. There is a general number for foreign buyers, but nothing fills it in for you — it has to be keyed onto the document by hand. The real fix happens at the counter, while the customer is still standing there.

Reference: E-Invoice Validation Rules & Troubleshooting — General TINs — when you don’t have the buyer’s TIN

Step 2 — The large sale that cannot hide in the batch

After this step you will stop trying a move that the system will always refuse. A sales invoice or cash bill of ten thousand ringgit or more marked for consolidation is diverted into the Individual Pool automatically, with the amount given as the reason, and the threshold includes exactly ten thousand. If you then try to move it into the Batch Pool so it goes out with everything else, BigLedger refuses and tells you a transaction of that size or more cannot be moved. That is not a bug to work around. Below the threshold you may move a receipt whose buyer has walked away; above it, the buyer’s real tax number is the only way that sale ever reaches LHDN.

Reference: E-Invoice Pools & Submission Routing — The RM 10,000 rule

Step 3 — Get the details from the buyer instead of chasing them

After this step you have a route that does not depend on a phone call. Your customers can supply their own e-invoice details through the customer portal: they find their own receipt, key their tax number, identity and address, and those details land on your customer record. The pooled receipt is then ready for you to complete and resubmit. For a twenty-two branch retailer that is the difference between chasing details and having them arrive. Two things worth remembering. It does not help for a receipt already inside a validated consolidated e-invoice, because that sale has been reported and the correction routes there are different. And a request made from your web store rather than the portal does not wait for you at all: the receipt leaves the batch, goes as an individual e-invoice in the buyer’s name, and nothing tells you it happened.

Reference: E-Invoice Pools & Submission Routing — Frequently asked questions

Step 4 — The stranded pool row and the document that was never there

After this step you can deal with two documents that are invisible to ordinary filters. A Batch Pool row marked processed and failed is not waiting for the consolidation any more, so no run will ever collect it: read its Validation Error, fix the underlying record and resubmit it, or move it back so it is swept, but decide something. The second case is worse — a document finalised while the company’s e-invoice setting was switched off was dropped with no pool row, no queue row and no error. There is no screen for those. A standing sweep e-mails a digest when it finds one, and support has to push the document into the pipeline by hand.

Reference: My E-Invoice Admin Applet — Troubleshooting

Step 5 — The one that is already Valid and wrong

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: Validation and clearance — How it behaves in BigLedger

Step 6 — Hand it over with the right evidence

After this step a support request will come back with an answer rather than a question. When the document is genuinely not yours to fix, what support and LHDN both need is what was actually sent and what actually came back. For a document LHDN accepted, that is the Submission History row: it holds the exact payload and LHDN’s exact response, and quoting it saves a round of guessing. For a transmission that failed, there is no history row at all, so quote the submission queue row and its request error instead. Add the document number, the company and the date range. Then say plainly what you have already corrected, so nobody sends you back to the customer record.

Reference: E-Invoice Submission Mechanics — Procedure: trace one document from FINAL to LHDN

How the steps fit together

    flowchart TD
  s1["Step 1 — The foreign buyer with no tax number"]
  s2["Step 2 — The large sale that cannot hide in the batch"]
  s3["Step 3 — Get the details from the buyer instead of chasing them"]
  s4["Step 4 — The stranded pool row and the document that was never there"]
  s5["Step 5 — The one that is already Valid and wrong"]
  s6["Step 6 — Hand it over with the right evidence"]
  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.

Back to the series · Play this as a presentation