What Malaysia Requires: E-Invoicing Explained
Watch this as a presentation — 1 on this page, slides with narration.
Before you configure anything, it helps to know what LHDN is actually asking for and why. This page is the background: who has to comply and from when, what an e-invoice contains, what happens after you send one, and which parts of it BigLedger does for you. Ten minutes, and no screens to open.
What e-invoicing is
Malaysian e-invoicing is an Inland Revenue Board (LHDN) programme that replaces the paper or PDF invoice as the tax record with a structured digital document, submitted to LHDN and validated by them before it counts. Your customer may still receive a PDF that looks much as it always did — but the version LHDN holds is the one that matters, and it only exists once LHDN has validated it.
Three consequences follow, and they shape everything else in these guides:
- An invoice is not finished when you print it. It is finished when LHDN says Valid.
- The data has to be right before it is sent, because the correction path after validation is narrow and time-limited.
- Someone has to check, every month, that everything got there — which is why the month-end cycle exists.
Who has to comply, and from when
The rollout is phased by annual turnover, so businesses came into scope in waves:
| Phase | In force from | Annual turnover |
|---|---|---|
| 1 | 1 August 2024 | Above RM 100 million |
| 2 | 1 January 2025 | RM 25 million to RM 100 million |
| 3 | 1 July 2025 | RM 5 million to RM 25 million |
| 4 | 1 January 2026 | RM 1 million to RM 5 million |
Businesses with annual turnover below RM 1,000,000 are exempt (e-Invoice Guideline 4.6, §1.6.1(e)). Businesses that started between 2023 and 2025 with turnover of at least RM 1,000,000, and businesses started from 2026 onwards, come in on 1 July 2026 (§1.5).
What goes on an e-invoice
LHDN’s own list runs to 55 data fields (e-Invoice Guideline 4.6, Appendix Table 1). Twenty of the 55 carry the marker [Optional] against the field name — e-mail addresses for both parties, billing frequency and period, quantity, unit of measure, discounts, fees, rounding, and the whole payment block. The other 35 are required. In practice they group into five blocks:
- Who is selling — your company’s name, tax number, registration number, industry classification, address and contact number. BigLedger takes these from your company record, so one bad field here fails every document at once.
- Who is buying — name, tax number, identity document type and value, address and contact number. This block causes most rejections; see Validation Rules & Troubleshooting.
- The document — type, version, issue date and time, currency.
- The lines — item classification code, description, quantity, unit of measure, unit price, tax type and tax amount.
- The money — subtotal, total excluding tax, total including tax, and any discounts or charges.
Four document types cover almost everything you will send: the invoice, the credit note, the debit note and the refund note. A self-billed e-invoice reverses the roles — you issue it as the buyer, typically when your supplier cannot.
How a document gets to LHDN
There are two routes, and which one you are on changes what you have to do:
The MyInvois portal. You type each invoice into LHDN’s own web portal. Workable at low volume; unworkable for a retailer ringing up thousands of receipts a month. Note that an invoice created this way exists at LHDN but not in BigLedger, so it will not appear in any BigLedger report.
API integration — what BigLedger does. Your documents are submitted straight from BigLedger. You authorise BigLedger as your e-invoice intermediary on the MyInvois portal once, and from then on BigLedger submits on your behalf.
What happens after you submit
- Submission. BigLedger sends the e-invoice to LHDN. Your document status becomes Submitted.
- Validation. LHDN checks it and returns Valid or Invalid, along with a unique identifier for the validated document.
- Sharing. The validated e-invoice — with its QR code — is what you give the buyer. BigLedger can e-mail it automatically.
- The 72-hour window. From validation, the supplier has 72 hours to cancel the e-invoice, and the buyer has 72 hours to reject it. After that neither is possible, and the only correction is a credit, debit or refund note — LHDN’s rule, e-Invoice Guideline 4.6 §2.3.6 (which version we cite). See Cancelling and Correcting a Validated E-Invoice.
Consolidated e-invoices, and why retailers care
You do not issue an individual e-invoice for every walk-in sale. Receipts where the buyer did not give their details are reported together in a consolidated e-invoice — one document, the buyer recorded as General Public, due at LHDN by the 7th of the following month.
For a 22-branch electronics retailer like GadgetSphere Sdn Bhd that is the difference between a small set of documents somebody can actually check before the 7th and roughly 38,000 that nobody can.
The one line to plan around is the large sale. LHDN bars consolidation for any single transaction with a value exceeding RM 10,000, in every industry, from 1 January 2026 — e-Invoice Specific Guideline 4.9, §3.7.2, Table 3.6 row 7. Such a sale needs an individual e-invoice with the buyer’s real identity, which in practice means asking for it at the counter, because chasing it a week later rarely works.
BigLedger applies its own line one sen lower. A sales invoice or cash bill marked Consolidated is diverted to the Individual Pool at RM 10,000 and above, not above RM 10,000 — so a sale of exactly RM 10,000.00 is diverted here although the guideline would still allow it in a consolidation. That is deliberate: erring on the safe side of a tax rule costs you one extra individual e-invoice and never a compliance failure. Pools & Submission Routing explains how the sorting works and which document types it covers.