E-Invoice & PEPPOL Guides
“I finalised the invoice and nothing was submitted to LHDN.” It is the sentence most e-invoice questions start from, and the answer is nearly always behind the screen: finalising only queues the work, and scheduled background runs route the document, send it and collect LHDN’s verdict afterwards. This page sends you to the guide for the situation you are in today — a rejection, a validated mistake, the week between the 1st and the 7th, a supplier’s e-invoice, or a first company going live — and names who owns each part of the job.
Find the guide for the situation you are in
| You are… | Open |
|---|---|
| New to e-invoicing, and want to know what LHDN requires and why | What Malaysia Requires, then what goes on an e-invoice |
| Bringing a company onto MyInvois for the first time | MyInvois Setup |
| Deciding which sales go to LHDN one by one and which wait for the month | Pools & Submission Routing |
| Looking at an e-invoice that has not moved, with no error anywhere | Understanding E-Invoice Statuses |
| Asked “did that invoice reach LHDN?” by a customer or an auditor | Trace One Document to LHDN |
| Asking “LHDN rejected it. Where do I find out why?” | Validation Rules & Troubleshooting |
| Somewhere between the 1st and the 7th | The Month-End Cycle |
| Asking “I submitted a wrong invoice and LHDN has already validated it. Can I cancel?” | Cancelling & Correcting an E-Invoice |
| Holding an e-invoice one of your suppliers issued to you | Incoming Supplier E-Invoices |
| Asked by a trading partner to deliver over PEPPOL | Peppol Configuration, after MyInvois is running |
| Reading “LHDN requires…” on a page and wondering how current it is | The LHDN guideline versions this wiki cites |
| Planning for a business shape: a distributor, a retail chain, self-billing | E-invoicing use cases |
Three ideas recur in every guide above, each with a short page: consolidated e-invoices, pools and queues, and validation and clearance.
PEPPOL runs beside the LHDN path, not after it; set up MyInvois first, because tax compliance requires it.
What happens after you press Finalise
Each stage after Finalise is a separate run on a clock, so a document can sit at any point while nothing on your screen changes. A document finalised while its company’s E-Invoice Status is not ENABLED gets no record, no pool row and no error — so switch each company on before anyone finalises a sale. The stages, the three pools and the RM 10,000 rule are in Pools & Submission Routing; what each status means, and the moment it was copied, in Understanding E-Invoice Statuses and the module page.
Who does what, before anyone opens a screen
Write the names down before go-live; most of what goes wrong is one of them not knowing the job was theirs.
- Whoever owns tax compliance — authorises BigLedger as intermediary for each company on the MyInvois portal, owns the 7th, and decides cancel-or-credit-note for a validated mistake: MyInvois Setup, Cancelling & Correcting.
- Whoever keeps the master data — customer tax numbers, the e-invoice address, item classifications, done after switch-on, before the first live sale: MyInvois Setup, Steps 5 and 6.
- The counter and sales team — ask whether the buyer wants their own e-invoice and take the details then: Get the buyer’s identity right, the shopper who comes back.
- The accounts clerk — the daily, weekly and monthly checks: How you know e-invoicing is actually working.
- Accounts payable — a validated supplier e-invoice behind every purchase, mostly checked by hand: Incoming Supplier E-Invoices.
And who approves a cancellation, and who covers on leave: nothing advances a request on a schedule, and the server refuses it 72 whole hours after LHDN validated the e-invoice.
When it goes wrong
| Symptom | Read |
|---|---|
| “I finalised the invoice and nothing was submitted to LHDN” | Statuses — waiting, parked in a pool, failed, or the company was not ENABLED |
| “LHDN rejected it”: the record reads Invalid | Validation — correct the record itself and Save and Resubmit, and the customer record too |
| Every submission fails at once | MyInvois Setup — the intermediary authorisation, or the tenant’s one token-refresh clock |
| A validated e-invoice is wrong | Cancel & correct — inside 72 hours of LHDN’s validation time, not the invoice date |
| Last month’s Batch Pool rows still unprocessed on the 3rd | Month-end, Step 5 |
| A walk-in comes back for their own e-invoice | The shopper who comes back |
| Your buyer says they rejected an e-invoice and nothing changed | Cancel & correct — a rejection on the MyInvois portal is not a request in BigLedger |
| A PEPPOL document did not arrive, or was turned down | Peppol Configuration — read the outbound queue first |
What must exist first is on the module’s configuration page; why the three status screens disagree is in Understanding E-Invoice Statuses and the My E-Invoice Admin applet.
What success looks like
Per company: the E-Invoice Status reads ENABLED, the e-invoice clocks read ACTIVE in the Scheduler, yesterday’s documents read Valid, the Individual and Single General pools are empty or every row is being chased, and after the 7th last month’s consolidated e-invoices read Valid. The exact clock codes and the morning routine are under How you know e-invoicing is actually working. If the status or the clocks fail, nothing else will work until they are fixed.
Read next
New to e-invoicing: read What Malaysia Requires, then MyInvois Setup. Already live: read The Month-End Cycle before your next 1st. The architecture is on the E-Invoice & PEPPOL module, and the purchase side on the Purchase Invoice applet.