LHDN MyInvois · API integration
This is a live demonstration of a direct integration with LHDN's MyInvois system — the same flow your ERP, POS or accounting software would run: build a compliant UBL 2.1 document, pass validation, submit, and track the e-Invoice through its lifecycle.
Runs against a simulated MyInvois sandbox — no real taxpayer data.
e-Invoice is being made mandatory in phases by annual turnover. Phase 4 (RM1M–RM5M businesses) went live on 1 January 2026.
| Phase | Annual turnover | Mandatory from | Status |
|---|---|---|---|
| Phase 1 | > RM100 million | 1 Aug 2024 | Live |
| Phase 2 | RM25M – RM100M | 1 Jan 2025 | Live |
| Phase 3 | RM5M – RM25M | 1 Jul 2025 | Live |
| Phase 4 | RM1M – RM5M | 1 Jan 2026 | Grace until 31 Dec 2027 |
| Phase 5 | < RM1M | — | Exempt |
From 1 Jan 2026, consolidated e-Invoices are no longer permitted for transactions exceeding RM10,000 — every qualifying sale needs its own validated document.
Invoices are generated in the exact UBL 2.1 JSON structure the MyInvois API expects — the same payload a production system sends.
Every document runs the same validator pipeline LHDN applies: structure, core fields, taxpayer, codes, duplicates, currency and more.
Tax types, payment modes, state codes and classifications are data-driven — the console tracks LHDN revisions without code changes.
Accepted submissions return an LHDN UUID and long ID, rendered as the official validation link and QR code.
Create an invoice, watch it pass the same validators LHDN runs, and get a UUID + QR validation link back — all in the console.
Open the console