What is MyInvois? Malaysia's Official E-Invoicing Platform Explained (2026)

MyInvois is the official e-invoicing platform developed and operated by the Inland Revenue Board of Malaysia (Lembaga Hasil Dalam Negeri, or LHDN). It serves as the national system through which Malaysian taxpayers issue, validate, and store electronic invoices for business-to-business (B2B), business-to-consumer (B2C), and business-to-government (B2G) transactions.

Launched as part of Malaysia's broader digital economy transformation, MyInvois replaces the traditional paper-based and PDF invoicing workflow with a structured, machine-readable digital format. Every invoice submitted through the platform is validated in real time by LHDN, ensuring tax compliance at the point of transaction rather than during retrospective audits.

The platform is accessible at sdk.myinvois.hasil.gov.my for developers seeking API integration, and through the MyInvois web portal for manual submissions. By mandating electronic invoicing, LHDN aims to reduce the tax gap, improve revenue collection efficiency, and align Malaysia with global e-invoicing standards recognised by countries such as Australia, Singapore, and members of the European Union.

As of 2026, the rollout has reached Phase 4, meaning businesses with annual turnover of RM1 million and above must now comply. If you are unsure whether your organisation falls within the current mandate, use our compliance calculator at /calculator to check your deadline instantly.

MyInvois accepts invoices in two structured data formats, both conforming to the UBL 2.1 (Universal Business Language) standard — an internationally recognised specification for electronic business documents.

XML Format: The XML submission follows the OASIS UBL 2.1 schema with Malaysia-specific extensions defined by LHDN. It is the more established format and is widely supported by enterprise ERP systems such as SAP, Oracle, and Microsoft Dynamics.

JSON Format: The JSON submission is functionally equivalent to XML and is often preferred by developers building modern API integrations because of its lighter syntax and native compatibility with web frameworks. Both formats produce identical validation outcomes.

Mandatory fields across both formats include: supplier TIN and registration number, buyer TIN (for B2B transactions), invoice date and currency, line-item descriptions with MSIC classification codes, individual and total tax amounts, and payment terms. Self-billed invoices, credit notes, debit notes, and refund notes each have additional required fields documented in the LHDN e-invoice SDK.

Businesses should work closely with their software vendors — you can browse compliant providers in our vendor directory at /vendors — to ensure that whichever format they adopt includes every mandatory field specified in the latest SDK release.

When an invoice is submitted to MyInvois, it passes through a multi-step validation pipeline:

1. Schema Validation — The system checks that the document conforms to the UBL 2.1 schema and that all required fields are present and correctly formatted.

2. TIN Verification — The supplier's and buyer's tax identification numbers are validated against LHDN's taxpayer database to confirm they are active and correctly matched.

3. Tax Calculation Check — Line-item amounts, tax subtotals, and the overall invoice total are recalculated to ensure mathematical accuracy.

4. Business Rule Validation — Additional rules are applied, such as verifying that MSIC codes are valid, that the invoice date is within acceptable ranges, and that duplicate submissions are flagged.

If the document passes every check, MyInvois assigns a Unique Identifier (UUID) and returns a success response. The UUID serves as the canonical reference for the invoice across all LHDN systems.

If validation fails, the system returns structured error codes indicating precisely which fields failed and why. Common rejection reasons include invalid or inactive TIN numbers, missing mandatory fields, incorrect tax calculations, and MSIC code mismatches. Organisations should implement programmatic error handling in their integration layer to parse these responses and trigger corrective workflows automatically.

Every validated e-invoice must carry a QR code that links directly to its verification page on the MyInvois portal. This QR code functions as a tamper-proof digital seal, enabling any party — buyers, auditors, bank officers, or tax authorities — to scan and confirm that the invoice was legitimately issued and validated by LHDN.

The QR code is generated server-side by the MyInvois system upon successful validation and is included in the API response payload. Businesses must embed this QR code on any printed or PDF version of the invoice shared with counterparties.

For B2C transactions, the QR code is especially important. Consumers can scan the code on a receipt or simplified invoice to verify that the transaction has been reported to LHDN. This transparency helps prevent tax evasion at the point of sale and gives consumers confidence that the business is operating compliantly.

Note that the QR code is not optional — invoices distributed without it are considered incomplete under the LHDN e-invoicing framework.

MyInvois provides a 72-hour cancellation window after an e-invoice has been validated. During this period, the supplier may cancel the invoice — for example, if it was issued to the wrong buyer or contains incorrect line items. The buyer may also reject the invoice within the same window if they believe it is inaccurate.

Once the 72-hour period elapses without cancellation or rejection, the invoice is locked and becomes part of the permanent tax record for both parties. After this point, corrections can only be made by issuing a credit note (to reduce the amount) or a debit note (to increase it). Both credit and debit notes must themselves be submitted through MyInvois and validated in the same manner as a standard invoice.

This rule means businesses need robust internal review processes. Invoices should be checked promptly after submission, and staff must understand that the cancellation window is strict — there are no extensions. Organisations that issue high volumes of invoices should consider building automated alerts that flag newly submitted invoices for review within the first 24 hours.

All businesses and self-employed individuals registered with LHDN are being brought into the MyInvois mandate through a phased rollout based on annual turnover:

- Phase 1 (1 August 2024): Taxpayers with annual turnover exceeding RM100 million. - Phase 2 (1 January 2025): Taxpayers with annual turnover between RM25 million and RM100 million. - Phase 3 (1 July 2025): Taxpayers with annual turnover between RM5 million and RM25 million. - Phase 4 (1 January 2026): Taxpayers with annual turnover between RM1 million and RM5 million.

Importantly, the originally planned Phase 5 for taxpayers below RM500,000 has been cancelled. Instead, the government doubled the exemption threshold from RM500,000 to RM1 million, meaning businesses with annual turnover below RM1 million are not required to issue e-invoices at this time.

Prime Minister Anwar Ibrahim also extended the relaxation period for Phase 4 taxpayers to a full 12 months — until 31 December 2026. During this relaxation window, Phase 4 businesses can familiarise themselves with the system without facing penalties for errors. Full enforcement, with penalties ranging from RM200 to RM20,000 per non-compliant invoice, begins on 1 January 2027.

Individuals are required to issue e-invoices for any single transaction exceeding RM10,000, regardless of total annual turnover.

Foreign entities with operations or income sourced from Malaysia may also be subject to compliance requirements. For a detailed breakdown of all deadlines, see our dedicated guide at /guides/e-invoicing-deadline-malaysia.

Adopting MyInvois delivers tangible advantages that extend well beyond regulatory compliance:

- Faster tax refunds: With real-time visibility into validated invoices, LHDN can process tax refund claims significantly faster than under the traditional audit-based approach.

- Reduced paperwork and costs: Electronic invoicing eliminates the need to print, post, and physically archive paper invoices. Organisations save on storage, stationery, and administrative labour.

- Improved cash flow visibility: When all invoices are digitised and centrally accessible, businesses gain clearer insight into receivables and payables, enabling more accurate cash flow forecasting.

- Lower audit risk: Because invoices are pre-validated at the point of submission, the likelihood of discrepancies during tax audits drops considerably — meaning fewer disputes and lower penalty exposure.

- International interoperability: MyInvois is aligned with UBL 2.1 and the Peppol framework, making it easier for Malaysian businesses to exchange compliant invoices with trading partners in Peppol-enabled countries across Asia-Pacific and Europe.

- Fraud prevention: Real-time validation and QR code verification make it extremely difficult to circulate fake invoices or engage in fraudulent tax-claim schemes.

Getting ready now — before the enforcement deadline of 1 January 2027 — gives your organisation time to test, train staff, and resolve integration issues without the pressure of penalties.