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, rolled out in phases by company size, and 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

Malaysia is bringing businesses into MyInvois in waves defined by annual turnover, largest first:

The largest taxpayers (turnover above RM100 million) went live in 2024.
Successively smaller revenue bands followed through 2025 and into 2026.
The stated goal is to cover all businesses by 2027.

Because thresholds and dates have been refined over time, every business should confirm its specific phase date directly with LHDN. Where Malaysia sits among the wider 2026 wave is mapped in the e-invoicing mandates 2026 tracker.

How the clearance model works

MyInvois inserts the tax authority into the invoicing flow:

The supplier creates an invoice and submits it to MyInvois (via API for volume, or the portal for low volumes).
MyInvois validates it against LHDN's rules.
On success, MyInvois assigns a Unique Identifier Number (UIN) and returns a validated invoice with a QR code.
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 rollout phase and go-live date with LHDN.
[ ] 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. Book a demo or read how to choose a Peppol Access Point.

Sources: LHDN e-Invoice (IRBM); MyInvois Portal; OpenPeppol.

Frequently asked questions

What is MyInvois e-invoicing?

MyInvois is Malaysia's national e-invoicing system, operated by the Inland Revenue Board (LHDN/IRBM). Taxpayers submit each invoice to the MyInvois platform for near-real-time validation; once validated, the invoice receives a Unique Identifier Number and a QR code before it is shared with the buyer. It is a continuous transaction control (CTC) clearance model.

When is MyInvois e-invoicing mandatory in Malaysia?

Malaysia rolls out MyInvois in phases by annual turnover. The largest taxpayers (turnover above RM100 million) went first in 2024, followed by successively smaller revenue bands through 2025 and into 2026, with the aim of covering all businesses by 2027. Each taxpayer should confirm their specific phase date with LHDN.

How does the MyInvois clearance model work?

Before an invoice is issued to the buyer, the supplier submits it to MyInvois (via the portal or API). MyInvois validates it, assigns a Unique Identifier Number, and returns a validated document with a QR code. Only then is the invoice shared with the buyer. This lets the tax authority see each transaction in near real time.

Is Malaysia's e-invoicing based on Peppol?

Malaysia supports both. MyInvois is the tax authority's clearance platform, while Malaysia is also a Peppol jurisdiction — MDEC acts as the national Peppol Authority — so businesses can exchange documents over the Peppol network alongside MyInvois clearance. A good provider handles both together.

What format does MyInvois use?

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, and once validated it is returned with a Unique Identifier Number and QR code.

What is the Unique Identifier Number in MyInvois?

The Unique Identifier Number (UIN) is the reference MyInvois assigns to each validated invoice. It confirms the invoice has been cleared by LHDN and is used for traceability, cancellation windows and audit. The validated invoice, with its QR code, is what the supplier shares with the buyer.

What do businesses need to do to comply with MyInvois?

Confirm your rollout phase, produce UBL-based XML or JSON invoices, integrate with the MyInvois API (or use the portal for low volumes), validate before submission, handle the Unique Identifier Number and QR code on the returned document, and store validated invoices for audit. Cross-border and Peppol flows should be planned alongside.