LHDN's MyInvois system is here. TIN validation, MSIC classification codes, and electronic submission — here's everything you need to comply.
Malaysia's Lembaga Hasil Dalam Negeri (LHDN) has mandated electronic invoicing through the MyInvois system. This isn't optional — all businesses must submit invoices electronically. For agencies, this means your invoicing system needs to support e-invoicing natively, not as an afterthought.
What MyInvois requires
Every invoice submitted to MyInvois must include:
- Tax Identification Number (TIN): Both the supplier and buyer must have valid TINs registered with LHDN.
- MSIC Classification: Your business activity must be classified using the Malaysia Standard Industrial Classification code.
- UNSPSC Codes: Each line item should be classified using the United Nations Standard Products and Services Code.
- Digital Signature: Invoices must be digitally signed using a valid certificate.
- PEPPOL UBL Format: The invoice must be structured as a PEPPOL UBL XML document.
Validation before submission
Submitting an invalid invoice to MyInvois results in rejection. Your system should validate the invoice before submission: is the TIN valid? Are the MSIC codes correct? Is the tax calculation accurate? Does the XML conform to the PEPPOL UBL schema?
Catching errors before submission saves time and avoids the back-and-forth of rejected invoices.
Built-in, not bolted on
Some systems treat e-invoicing as an export format — generate the invoice normally, then export it as XML. This creates a gap where the invoice in your system and the invoice submitted to MyInvois can diverge.
The better approach is to build compliance into the invoice from the start. When you create an invoice, the TINs are validated, the MSIC codes are applied, and the tax scheme is configured. The XML is generated from the same data that produces the PDF. One source of truth, two output formats.