MyInvois e-Invoicing
Invoicemonk submits Malaysian invoices to the LHDN MyInvois portal as validated XML/JSON, receives the MyInvois UUID and validation link, and embeds the QR on the PDF for the buyer. Live since August 2024.
Built for Malaysia from day one
What MyInvois requires
LHDN requires every in-scope taxpayer to transmit invoices, credit notes, debit notes, and refund notes to the MyInvois portal in UBL XML or JSON, receive a validated UUID, and pass that UUID plus QR to the buyer. Rollout is phased by turnover: >MYR 100m from 1 August 2024, >MYR 25m from 1 January 2025, all taxpayers from 1 July 2025.
How Invoicemonk meets MyInvois
On send, Invoicemonk builds the MyInvois-compliant XML/JSON, signs with your LHDN-onboarded digital certificate, submits to the MyInvois API, captures the UUID and validation link, and binds the QR to the buyer-facing PDF. Self-billed e-invoices and consolidated B2C e-invoices are both supported. Cancellation within the 72-hour MyInvois window is exposed as a one-click action.
Who this applies to
Malaysian taxpayers in the active rollout wave for their turnover band. Foreign suppliers issuing to Malaysian buyers are in scope where the buyer requires self-billed e-invoicing.
Cryptographic artefacts, in every jurisdiction we cover
Invoicemonk issues cryptographically signed structured invoices in every one of the 18 jurisdictions we cover, using the local artefact the tax authority requires:
- CSID — ZATCA (Saudi Arabia)
- IRN — GST India (NIC IRP), FIRS Nigeria, GRA Ghana
- UUID — MyInvois Malaysia
- QR + Control Unit Number — KRA eTIMS (Kenya)
- Chave de Acesso — NF-e / NFS-e (Brazil)
- Fiscal signature — ZIMRA FDMS (Zimbabwe)
- XAdES digital signatures — Peppol (EU), MTD (UK)
- ICP-Brasil A1 — Brazilian NF-e / NFS-e signing
Each mandate page documents the local artefact, signing algorithm, certificate authority, and the spec section that requires it.
Malaysia e-invoicing, answered
Implementation playbooks for Malaysia
Step-by-step guides, explainers, and error catalogues for the MyInvois UUID workflow.
How to Comply with MyInvois in Malaysia: Onboard with LHDN and Issue Your First UUID-Stamped Invoice (2026)
Step-by-step playbook for issuing LHDN MyInvois e-invoices in Malaysia — onboarding, UBL 2.1 / JSON payload, UUID issuance, 72-hour rejection window, and the Phase 4 / Phase 5 small-taxpayer rollout deferred to 2026.
Read guide
MyInvois Malaysia Explained: Scope, Rollout Waves, SST Handling, and the 2026 Phase 4 Deferral
A plain-English explainer for LHDN MyInvois — what it is, who must comply, the five-phase rollout schedule, how 8% SST is handled, the 72-hour rejection window, and what changes through 2026.
Read guide
Common MyInvois Malaysia Errors and How to Fix Them: Validation, TIN Mismatches, Cancellation Windows, and QR Failures (2026)
The recurring failure modes in MyInvois — payload validation rejections, TIN mismatches, missed 72-hour cancellation windows, QR errors, self-billed scenarios, consolidated B2C cut-offs, and foreign-currency rejects — and the exact fix for each.
Read guideMalaysia: compliant from day one
XML/JSON validated by LHDN MyInvois with a UUID + QR returned to the buyer.