Malaysia MyInvois E-Invoicing: LHDN Guide (2026)

MyInvois in one sentence

MyInvois is Malaysia's national e-invoicing system, run by the Inland Revenue Board (LHDN/IRBM), where every invoice is cleared by the tax authority in near real time before it reaches the buyer. It is a continuous transaction control (CTC) model, and since 1 January 2026 it has applied to every taxpayer with annual turnover of RM1 million or more — the four turnover phases are complete, and taxpayers below RM1 million are exempt. It runs alongside Malaysia's adoption of the Peppol network.

If CTC clearance is a new concept, the Oman Fawtara 5-corner model and ZATCA in Saudi Arabia are useful comparators — different countries, same underlying idea of the tax authority sitting inside the transaction.

Who runs it

E-invoicing in Malaysia is administered by the Inland Revenue Board of Malaysia — LHDN (Lembaga Hasil Dalam Negeri), also known as IRBM — through the MyInvois platform. Unlike a pure exchange network, MyInvois is a clearance system: the authority validates each invoice as it is issued.

The phased rollout by turnover

LHDN set four dated phases by annual turnover, and the last of them started on 1 January 2026. There is no 2027 phase.

Two things about that table matter more than the dates themselves.

Your phase is fixed by one historic figure. LHDN determines it from your financial-year 2022 turnover — the statement of comprehensive income in your audited accounts if you have them, the annual revenue in your year-of-assessment 2022 tax return if you do not, pro-rated to twelve months if you changed your year end. Once your date is set, growing past a threshold in a later year does not move it.

Below RM1 million there is no obligation at all. Taxpayers with an annual turnover or revenue of less than RM1,000,000 are exempted from issuing e-invoices, including self-billed e-invoices. Two related cases sit next to that exemption: businesses that started trading between 2023 and 2025 with turnover of at least RM1,000,000 begin on 1 July 2026, and a business that later crosses RM1,000,000 begins on 1 January of the second year following the year it crossed. Anyone below the threshold may still adopt MyInvois voluntarily, and a supplier below it still receives validated e-invoices from larger customers.

Sources: LHDN's own e-Invoice implementation timeline and the IRBM e-Invoice Guideline (version 4.7, published 7 July 2026), sections 1.5 and 1.6.1(e).

Where Malaysia sits among the wider 2026 wave is mapped in the e-invoicing mandates 2026 tracker, and the country page — Malaysia e-invoicing — carries the same table with our delivery detail.

How the clearance model works

MyInvois inserts the tax authority into the invoicing flow:

1. The supplier creates an invoice and submits it to MyInvois (via API for volume, or the portal for low volumes).
2. MyInvois validates it against LHDN's rules.
3. On success, MyInvois assigns a Unique Identifier Number (UIN) and returns a validated invoice with a QR code.
4. Only then does the supplier share the validated invoice with the buyer.

The UIN is the proof of clearance — used for traceability, the cancellation window, and audit. Submitting invalid documents is the common failure mode; the general classes of error are covered in invoice validation errors you can prevent.

The format

MyInvois accepts structured invoices in XML or JSON, built to LHDN's specification, which is based on UBL 2.1. The document carries the mandatory tax fields; after clearance it comes back with the UIN and QR code. Because it's UBL underneath, the mapping discipline is similar to other UBL regimes — see Peppol vs PINT for how the same base standard supports many national profiles.

MyInvois and Peppol together

Here is the nuance that trips up planners: Malaysia is both a clearance country and a Peppol country. MDEC (the Malaysia Digital Economy Corporation) acts as the national Peppol Authority, so businesses can exchange documents over the Peppol four-corner network in addition to clearing them through MyInvois. A capable provider treats these as one integrated flow — clear through MyInvois, exchange over Peppol — rather than two disconnected projects. For the single-integration principle, see the multi-country e-invoicing API.

A readiness checklist

• [ ] Confirm your phase from your financial-year 2022 turnover — and check first whether you are under the RM1 million exemption.
• [ ] Produce UBL-based XML or JSON to the MyInvois specification.
• [ ] Integrate with the MyInvois API (portal only for low volumes).
• [ ] Validate every invoice before submission; block on errors.
• [ ] Handle the returned UIN and QR code on the cleared document.
• [ ] Plan Peppol exchange and cross-border flows alongside clearance.
• [ ] Store validated invoices with their UINs for audit.

How GoRoute helps

GoRoute (POP000991) is a certified Peppol Access Point and SMP whose value in Malaysia is a single integration that handles both sides — MyInvois clearance and Peppol exchange — with validation before submission, behind one REST API that also covers your other markets. If Malaysia is one country in a wider regional rollout, that's the architecture to build toward rather than a MyInvois-only connector. See the Malaysia country page for what we deliver there, book a demo, or read how to choose a Peppol Access Point.

Sources: IRBM e-Invoice implementation timeline; IRBM e-Invoice Guideline version 4.7, published 7 July 2026, sections 1.5 and 1.6.1(e); MyInvois Portal; OpenPeppol.