Malaysia e-Invoice

The Malaysian Inland Revenue Board (LHDN) is transitioning businesses across the country toward a mandatory, real-time digital tax structure. This operational framework breaks down execution requirements, validation systems, transition rules, and special transaction rules.

Executive Summary & Regulatory Purpose

Malaysia’s e-Invoicing system forms a central component of the country’s national digitalization strategy. It is designed to modernize tax administration by validating and archiving commercial transactions in real time or near-real time across B2B, B2C, and B2G channels.

Primary framework guidelines, technical documentation, and official updates can be accessed directly on the LHDN Official e-Invoice Portal.

Phased Implementation Strategy

Mandatory adoption follows a phased schedule structured around audited annual turnover.

Mandatory Rollout Timeline

Phase	Audited Annual Revenue Threshold	Mandatory Start Date
Phase 1	Exceeding RM100 million	1 August 2024
Phase 2	Exceeding RM25 million – RM100 million	1 January 2025
Phase 3	Exceeding RM5 million – RM25 million	1 July 2025
Phase 4	Exceeding RM1 million – RM5 million	1 January 2026

Threshold Assessment Baseline:
Start dates are determined strictly by Audited Financial Statements (AFS) from Financial Year Ended (FYE) 2022. If 2022 statements are unavailable, reference FYE 2023, moving forward chronologically.
Evaluation depends on your fiscal year end—not the calendar year. For instance, a firm recording RM6 million in audited revenue for FYE 2022 falls under Phase 3 (1 July 2025).

Threshold Rules, Exemptions & Group Aggregations

General Exemption Standard

Entities recording audited annual revenues below RM1,000,000 are exempt from mandatory e-Invoice generation and may continue standard invoicing practices.

Annual Re-evaluation & Entry Rules

Exempt entities must reassess revenue figures at the close of every financial year. Crossing the threshold triggers mandatory compliance on January 1st of the second year following the breach.

Example: Exceeding the RM1,000,000 benchmark in FYE 2026 requires full e-Invoicing adoption by 1 January 2028.

Group Revenue Aggregation Rules

Individual entities operating below the RM1,000,000 mark lose exemption status and must comply if any of the following apply:

Controlled by a corporate shareholder exceeding the threshold.
Operating as a subsidiary of a parent company exceeding the threshold.
Affiliated with a joint venture or related entity exceeding the threshold.
Operating as a sole proprietorship or partnership whose aggregated revenue under a single owner crosses the threshold.

Transition Protections & High-Value Limits

To smooth the technical transition, LHDN provides a 6-month grace period from each entity’s phase start date.

Consolidated E-Invoicing Allowance: Businesses unable to issue individual B2C or self-billed e-Invoices immediately may submit a single, aggregated monthly e-Invoice covering all applicable transactions.
Exempted Distribution: Consolidated e-Invoices do not need to be issued directly to buyers or suppliers during this period.
RM10,000 Transaction Threshold (Effective 1 January 2026): Transactions exceeding RM10,000 cannot be included in consolidated monthly e-Invoices. Individual e-Invoices must be issued for every single transaction above this amount.

Technical Transmission Systems

LHDN provides two transmission models to accommodate different operational scales:

Model	Primary Features	Optimal Deployment
MyInvois Portal	Web-based interface supporting manual single entry and batch CSV/spreadsheet uploads.	Micro, Small & Medium Enterprises (MSMEs) Entities without automated system integrations Lower overall transaction volumes
API Integration	Direct system-to-system transmission using standardised XML or JSON data formats.	Large enterprises High-volume transaction environments Integrated ERP ecosystem operations

Standard Transaction Workflow

Scenario A: Buyer Requires an E-Invoice

The buyer provides necessary tax identification details to the supplier.
The supplier populates the required data fields specified by LHDN guidelines and submits the document for validation.
Once validated by LHDN, the e-Invoice serves as official tax proof for the buyer’s expense claim.

Scenario B: Buyer Does Not Require an E-Invoice

The supplier issues a standard paper or digital receipt/invoice at the point of sale.
Within 7 calendar days after the end of the month, the supplier aggregates all unissued individual receipts into a single consolidated e-Invoice.
Once validated, the consolidated e-Invoice serves strictly as internal proof of income for the supplier and is not distributed to end buyers.

Consolidation Structural Options
Suppliers issuing consolidated monthly e-Invoices may structure data using one of four methods:

Itemised Lines: Listing each transaction receipt as a separate line item.
Summary Line: Combining total monthly sales into a single line item with reference numbers included.
Branch-Level Submissions: Submitting separate consolidated e-Invoices for each operating branch or location.
Location-Specific Lines: Submitting a single consolidated e-Invoice with distinct line-item summaries for each branch.

Specialised Accounting Treatments

Periodic Statements & Recurring Bills
Sectors that issue recurring batch bills (such as telecommunications, banking, insurance, healthcare, and utilities) can transmit data directly to LHDN in XML or JSON formats for validation. Validated data can then be formatted into standard visual statements for customers.
 
Disbursements vs. ReimbursementsDisbursements (Out-of-pocket expenses incurred on behalf of the buyer): The primary vendor issues an e-Invoice directly to the buyer. The intermediary settling the bill does not include the payment in their own invoice but provides payment proof to recover funds.
Reimbursements (Expenses incurred by a service provider while delivering work): The service provider receives an e-Invoice from the vendor, pays the cost, and re-bills the buyer by including the expense as an itemised line item on their own e-Invoice.
 
Employee Claims & BenefitsEmployees claiming company expenses (e.g., parking, tolls, travel) should request e-Invoices issued in their employer’s name where possible.
LHDN permits e-Invoices issued in an employee’s name to be accepted as valid proof of expense for tax deduction purposes.
Overseas expenses paid by employees do not require self-billed e-Invoices; standard foreign receipts remain acceptable.

Self-Billed E-Invoice Mandates

For certain transactions, the buyer assumes responsibility for generating and submitting the e-Invoice to LHDN:

Foreign transactions (goods and services acquired from overseas suppliers).
Commissions, fees, or payouts to agents, dealers, and distributors.
Corporate dividend distributions (excluding listed companies on Bursa Malaysia and entities exempt under Section 108 of the Income Tax Act 1967).
E-commerce platform transactions.
Purchases made from individual sellers who do not run a registered business.
Prize payouts for gaming and betting (excluding casino and gaming machine payouts until further notice).

Cross-Border & Foreign Income Frameworks

Import & Export RulesImports: Foreign sellers are not bound by Malaysian tax laws. The local buyer must generate a Self-Billed e-Invoice to document and claim the expense.
Exports: Malaysian businesses exporting goods or services overseas must issue a standard e-Invoice to record their export revenue.

Foreign Income RemittancesForeign Dividends: Malaysian taxpayers receiving overseas profit distributions must issue an e-Invoice listing themselves as the supplier and the foreign entity as the buyer to document taxable income.
Foreign-Sourced Income: Any foreign income remitted into Malaysia requires an e-Invoice for tax validation. The document must be generated by the end of the month following the month of receipt.

Operational Readiness Checklist

To ensure full technical and legal compliance prior to your assigned phase deadline, evaluate your readiness across three key areas:

Personnel Allocation & Training: Assign dedicated team members to oversee system implementation, data compliance, and LHDN reporting workflows.
Systems & Data Architecture Audit: Review internal IT capabilities, database compatibility, and standard data fields to ensure seamless integration with the MyInvois Portal or API endpoints.
Process Mapping: Audit current issuing workflows for invoices, credit notes, debit notes, and refund notes to ensure alignment with LHDN specifications.