Malaysia E-Invoicing Mandate: A Business Guide

Malaysia's LHDN e-invoicing mandate is now in force. This guide covers who is affected, key deadlines, and how to get compliant fast.

Malaysia’s Inland Revenue Board (LHDN/IRBM) has made e-invoicing mandatory for businesses above defined revenue thresholds. The mandate is not optional, and it is not distant — the phased rollout is already underway. Whether you are a finance director preparing your ERP, a business owner trying to understand your obligations, or an IT lead evaluating integration options, this guide gives you a complete, accurate picture of what compliance requires.

What the Mandate Means

The e-invoicing mandate requires businesses to issue, validate, and store invoices electronically through IRBM’s MyInvois system. Every invoice must pass through IRBM’s validation layer before it is considered legally issued. This means paper invoices and unvalidated PDFs no longer satisfy the legal requirement for businesses in scope.

The mandate applies to invoices, credit notes, debit notes, and refund notes. The underlying goal is to reduce tax leakage, improve audit efficiency, and bring Malaysia in line with regional and global digital trade standards.

Who Is Affected: Revenue Thresholds and Phase Dates

IRBM has structured the rollout in phases tied to annual turnover:

• Phase 1 (August 2024): Businesses with annual turnover exceeding RM 100 million
• Phase 2 (January 2025): Businesses with annual turnover between RM 25 million and RM 100 million
• Phase 3 (July 2025): All remaining businesses, including SMEs, regardless of turnover

If your business has already passed your phase date, compliance is required now. If your phase is upcoming, preparation should be in progress — implementation typically takes between four and twelve weeks depending on your existing systems.

Three Transaction Types: B2B, B2C, and B2G

The mandate covers three categories of commercial transactions:

B2B (Business-to-Business): Invoices exchanged between registered businesses. This is the highest-volume category and the primary focus of IRBM’s enforcement. Both parties must be identifiable in the invoice data, and the buyer’s tax identification number (TIN) must be included.

B2C (Business-to-Consumer): Invoices issued to individual end customers. For B2C transactions, businesses issue an e-invoice validated through MyInvois, but may provide a simplified receipt to the consumer instead of transmitting the full validated document. This reduces operational friction for high-volume retail scenarios.

B2G (Business-to-Government): Invoices issued to government agencies and statutory bodies. These follow the same validation flow as B2B but may be subject to additional procurement compliance requirements depending on the agency.

Understanding which category your transactions fall into determines how you structure your submission workflow, particularly for B2C where the consumer-facing output differs from the IRBM-validated record.

Exemptions

Not every transaction triggers an e-invoicing obligation. Current IRBM guidance identifies the following exemption categories:

• Cash on delivery (COD): Transactions where immediate payment occurs at the point of sale are currently exempt from the full e-invoicing requirement
• Exports: Goods and services exported outside Malaysia are not subject to e-invoicing under the domestic mandate, though PEPPOL-based cross-border invoicing may still apply
• Specific regulated sectors: Certain financial instruments, insurance premiums, and employment income are excluded by virtue of existing reporting mechanisms
• Foreign individuals and entities without a Malaysian TIN: Transactions where the buyer cannot be assigned a Malaysian TIN follow a simplified process

It is important not to assume exemptions apply without verifying against current IRBM guidance, as the list is subject to revision.

MyInvois Portal vs API Integration: When to Use Each

IRBM provides two submission pathways:

MyInvois Portal is a web-based interface where staff manually key in or upload invoice data. It is designed for businesses with lower transaction volumes — typically fewer than a few hundred invoices per month. The portal requires no technical integration but is labour-intensive at scale. It is an appropriate starting point for small businesses entering compliance, or for handling exception transactions alongside an API setup.

API Integration connects your accounting or ERP system directly to IRBM’s endpoint. Invoices are submitted programmatically without manual intervention. This is the correct model for any business processing hundreds or thousands of invoices monthly. API integration requires development effort upfront but delivers a fully automated, auditable, and scalable workflow. Most mid-market and enterprise businesses will require this pathway.

A hybrid approach is also common during transition: API integration for standard invoice flows, with the MyInvois portal as a fallback for edge cases.

Required Mandatory Fields vs Optional Fields

Every e-invoice submitted to IRBM must contain a defined set of mandatory fields. Missing or incorrect mandatory fields will cause the validation to fail, blocking invoice issuance.

Mandatory fields include:

• Supplier name, address, and TIN
• Buyer name, address, and TIN (for B2B)
• Invoice date and unique invoice number
• Description, quantity, and unit price of goods or services
• Tax type, rate, and total tax amount
• Total invoice amount (pre-tax and post-tax)
• Currency and, if applicable, exchange rate

Optional fields allow businesses to provide additional context: purchase order references, project codes, payment terms, discount details, additional line-item descriptions, and contact information. While not required for validation, optional fields are often required by buyers for their own procurement and finance processes.

Your finance and IT teams should map your existing invoice data model to the IRBM field schema early. Gaps in master data — such as missing buyer TINs — are a common source of compliance delays.

Step-by-Step Workflow: Creation to Storage

The e-invoicing lifecycle follows four sequential stages:

1. Invoice Creation: Your system generates the invoice in the IRBM-specified UBL XML format (or JSON equivalent). If using the MyInvois portal, you enter or upload the data manually.

2. Validation: The invoice is submitted to IRBM’s MyInvois system via the portal or API. IRBM’s engine checks the data against mandatory field requirements and tax logic. Validation typically completes within seconds for API submissions.

3. Issuance: On successful validation, IRBM returns a unique validation number and QR code. The invoice is now legally issued. This validated version — not your original internal document — is the legal invoice. It must be shared with the buyer.

4. Storage: Both the seller and buyer are required to retain the validated e-invoice for a minimum of seven years. IRBM may access stored records during audits. Storage must preserve the integrity of the validated document, including the IRBM-issued QR code and validation reference.

Data Security Requirements

IRBM operates MyInvois under Malaysia’s data protection framework and implements encryption standards for all data in transit and at rest. Businesses using the API pathway are required to authenticate using client certificates issued by IRBM, ensuring that only authorised systems can submit on behalf of a registered taxpayer.

For businesses using third-party e-invoicing middleware or service providers, verify that your provider is certified or recognised by IRBM. Data handling agreements should confirm that invoice data is not retained or processed beyond what is necessary for submission.

Practical E-Readiness Checklist

Use this checklist to assess your current state:

Technology

• Accounting or ERP system can generate UBL XML or JSON in IRBM format
• API credentials obtained from MyInvois developer portal
• Staging environment tested against IRBM sandbox
• Error handling and retry logic implemented for failed submissions

Processes

• Buyer TIN collection process defined for all active customers
• Credit note and debit note workflows updated to include e-invoice submission
• Exception handling process defined for failed validations
• Archival process in place for 7-year document retention

Team Knowledge

• Finance team understands the distinction between internal invoice records and validated IRBM documents
• IT team or implementation partner briefed on IRBM API documentation
• Staff trained on MyInvois portal for exception cases

Getting Started

E-invoicing compliance is a systems change, a process change, and a data quality challenge rolled into one. Starting with a gap analysis — comparing your current invoice data against IRBM’s mandatory field requirements — gives you a concrete picture of what needs to be addressed before go-live.

Businesses already in scope that are not yet compliant face potential penalties under the Income Tax Act. The correct response is not to wait but to begin the implementation process immediately.

Related Reading

• MyInvois vs API Integration: Choosing Your E-Invoice Model — A decision guide for which e-invoicing pathway suits your business.
• How Nematix Handles E-Invoicing: From MyInvois to PEPPOL — How Nematix implements end-to-end e-invoicing for Malaysian enterprises.

Ready to simplify your e-invoicing transition? Talk to our team about seamless MyInvois and PEPPOL integration for your business.