Malaysia e-Invoice Exemption Threshold Raised to RM3 Million

Malaysia e-Invoice Exemption Threshold Increased to RM3 Million from 1 September 2026

Malaysia has increased the Malaysia e-Invoice exemption threshold from RM1 million to RM3 million, with the policy taking effect from 1 September 2026. This means many smaller businesses below the revised threshold may no longer be required to implement e-Invoicing, but turnover alone does not determine eligibility.

Businesses must also examine ownership, holding-company, related-company and joint-venture relationships before assuming that the exemption applies. For companies already using MyInvois, the change should trigger a compliance review rather than an immediate shutdown of existing processes.

The practical question is therefore not simply, “Are we below RM3 million?” Finance teams need to determine whether the business meets the exemption conditions, whether it has already entered mandatory implementation, and whether continuing e-Invoicing voluntarily still makes operational sense.

Malaysia Raises the e-Invoice Exemption Threshold to RM3 Million

The Malaysia e-Invoice exemption threshold has been raised from RM1 million to RM3 million as part of measures announced on 30 August 2026, effective from 1 September 2026. The change substantially expands the population of smaller businesses that may qualify for exemption from mandatory e-Invoice implementation.

For an SME with annual revenue of RM1.8 million, for example, the previous threshold could have placed e-Invoice implementation directly on its compliance roadmap. Under the revised RM3 million threshold, that business may now fall within the exemption, provided the additional eligibility conditions are satisfied.

That qualification is important. The new threshold should not be treated as a blanket cancellation of e-Invoicing obligations for every company below RM3 million.

For finance teams, the correct response is to reassess three things:

• the taxpayer’s relevant annual turnover or revenue;
• its ownership and wider group relationships;
• whether an e-Invoice implementation obligation has already arisen.

This makes the change both a compliance relief measure and a governance exercise. A standalone owner-managed SME may reach a different conclusion from a RM2 million subsidiary operating inside a much larger corporate group.

What Has Changed in Malaysia’s e-Invoice Requirement?

The main change is that eligible taxpayers below the revised RM3 million level can fall outside mandatory e-Invoice implementation, replacing the previous RM1 million exemption threshold. The revised rules also introduce important conditions that prevent businesses from assessing eligibility solely from their own turnover.

The HASiL e-Invoice Guideline Version 4.8, published on 30 August 2026, should be reviewed as the primary regulatory reference because it updates the exemption threshold and introduces the relevant ownership and group-related conditions.

In practical terms, the exemption may not apply where the taxpayer has specified relationships with a non-individual shareholder, holding company, related company or joint venture whose annual turnover or revenue reaches the relevant RM3 million level.

This distinction matters particularly for:

• subsidiaries within larger groups;
• joint ventures;
• businesses owned by corporate shareholders;
• related entities managed under a common finance function.

Consider a subsidiary generating RM2.2 million annually while its holding company generates RM20 million. Looking only at the subsidiary’s own sales could lead its finance team to the wrong compliance conclusion.

That is why the Malaysia e-Invoice RM3 million threshold is better understood as an eligibility test, not simply a revenue cut-off.

Who Is Eligible for the RM3 Million e-Invoice Exemption?

Businesses with annual turnover or revenue below the applicable RM3 million threshold may qualify for the exemption, provided they do not fall within the specified ownership or group-related exclusions. Eligibility therefore needs to be assessed at both taxpayer and corporate-structure level.

A practical eligibility assessment should ask:

1. Is the taxpayer’s relevant annual turnover or revenue below RM3 million?
2. Does it have a non-individual shareholder or equivalent?
3. Is it a subsidiary of a holding company?
4. Does it have a related company or joint venture?
5. Do any relationships identified above trigger the conditions set out in the revised guideline?

For a small independent professional services firm with RM1.5 million turnover and no relevant corporate ownership relationships, the exemption assessment may be relatively straightforward.

A multi-entity business is different. A finance team managing several legal entities cannot simply classify every subsidiary below RM3 million as exempt. Each entity’s position needs to be tested against its ownership and related-company structure.

There is also an important boundary issue. The regulatory guideline describes the exemption using turnover or revenue below RM3 million, while public announcements have also used language such as sales “not exceeding RM3 million.” Businesses exactly at the RM3 million boundary should therefore check the latest HASiL clarification rather than relying on a simplified headline.

When Does the New RM3 Million Threshold Take Effect?

The government’s revised RM3 million e-Invoice threshold takes effect from 1 September 2026. The change was announced on 30 August 2026 as part of measures intended to reduce the compliance burden on smaller Malaysian businesses.

That date does not mean every business below RM3 million should immediately disable MyInvois processes on 1 September.

This is particularly important for taxpayers with annual sales between RM1 million and RM3 million that had already implemented e-Invoicing under the previous requirements. Industry groups have sought further clarification on whether such businesses can opt out or should continue participating voluntarily.

For those businesses, maintaining the existing process while confirming their position is more controlled than disconnecting an ERP integration, changing invoice procedures and later discovering that e-Invoicing still needs to continue.

What Businesses Need to Know About the e-Invoice Exemption

An e-Invoice exemption reduces the immediate compliance requirement for eligible businesses, but it does not make invoice data quality, accounting controls or digital readiness irrelevant. Companies approaching RM3 million or expecting rapid growth should consider whether delaying all preparation simply shifts the same project into a more compressed future window.

Malaysia e-Invoicing is also more than creating an electronic PDF. MyInvois processes structured transaction data and applies validations to submitted documents, including structural, taxpayer, reference, code, duplicate and currency checks.

For businesses that will eventually enter scope, typical readiness risks include:

• incomplete buyer TIN records;
• incorrect or outdated Business Registration Numbers;
• inconsistent customer master data;
• incorrect invoice or adjustment-document mapping;
• tax fields maintained differently across systems;
• products and services mapped inconsistently;
• ERP invoice statuses not reconciled with MyInvois responses.

From 1 August 2026, MyInvois technical changes also strengthened TIN and BRN validation considerations, making accurate buyer registration data increasingly important to integrated finance processes.

The strategic point is simple: exemption and readiness are separate decisions. A qualifying RM2.7 million business may decide not to implement now but still clean its customer data and confirm its accounting software capabilities so crossing the threshold later does not become an emergency integration project.

MyInvois and Peppol Malaysia Serve Different Purposes

MyInvois is the tax authority platform used for e-Invoice submission, validation and related document processes. Peppol Malaysia focuses on interoperable business-to-business invoice exchange between accounting and ERP environments.

A company can therefore have MyInvois compliance requirements without treating Peppol as mandatory for every transaction. Peppol becomes particularly relevant where businesses want structured system-to-system invoice exchange with customers or suppliers and where PINT-MY interoperability supports that operating model. Malaysia’s national Peppol initiative is designed around interoperable invoice exchange between business systems.

Does the RM3 Million Threshold Apply Automatically?

No. A company’s turnover falling below RM3 million does not, by itself, prove that the Malaysia e-Invoice exemption applies.

One of the most important changes in the revised framework is the need to examine corporate relationships. Businesses with qualifying non-individual shareholders, holding-company relationships, related companies or joint ventures may fall outside the exemption even where the taxpayer’s own turnover is below RM3 million.

This creates a common risk for decentralised groups.

Imagine three subsidiaries each producing RM1 million to RM2 million in annual revenue. Local finance teams might independently conclude that all three are exempt. If the entities are connected to a holding or related company meeting the relevant threshold, that conclusion may be incorrect.

The eligibility decision should therefore be documented centrally, particularly where legal entities share:

• common ownership;
• finance teams;
• ERP instances;
• customer or supplier masters;
• tax governance;
• invoicing infrastructure.

The exemption is a regulatory classification decision, not something accounting software should infer simply from the sales ledger.

How Businesses Can Assess Their e-Invoice Eligibility

Businesses should assess eligibility through a structured compliance review covering revenue, entity structure, implementation history and future growth. This is more reliable than asking the finance team to look at the latest annual sales number in isolation.

A useful decision framework is:

• Step 1: Confirm the taxpayer being assessed: Do not mix group revenue and legal-entity revenue without first identifying the taxpayer whose obligation is being reviewed.
• Step 2: Determine the relevant turnover or revenue position: Check the basis prescribed under the applicable e-Invoice rules rather than using an informal management estimate.
• Step 3: Review corporate relationships: Identify non-individual shareholders, holding companies, related companies and joint ventures that may affect exemption eligibility.
• Step 4: Confirm implementation history: Determine whether the taxpayer has already implemented MyInvois under a previous phase.
• Step 5: Consider expected growth: A business sitting at RM2.8 million with strong recurring growth has a different technology decision from one consistently operating at RM500,000.
• Step 6: Document the conclusion: Record the revenue basis, ownership assessment and decision date so finance and tax teams can explain why the business treated itself as exempt or in scope.

This process is especially important for multi-branch and multi-entity groups where accounting responsibility is centralised but tax obligations remain entity-specific.

What Should Businesses Do Before e-Invoice Implementation?

Businesses that remain in scope, expect to enter scope or choose voluntary adoption should prepare the finance architecture before connecting transactions to MyInvois. The biggest implementation failures typically occur when companies focus on API connectivity before fixing the underlying invoice and master data.

The MyInvois SDK should be treated as a technical implementation baseline because it defines API behavior, document structures, taxpayer validation, submission responses and integration practices that ERP-connected finance teams need to design around.

Start with these controls:

• Clean TIN and BRN data: MyInvois provides taxpayer validation capabilities using TIN together with identifiers such as BRN. For API-connected systems, validating buyer information when master records are created or updated is more scalable than repeatedly checking the same buyer before every invoice.
• Map invoice document types correctly: ERP workflows must distinguish invoices, credit notes, debit notes, refund notes and other applicable transactions instead of forcing every document through a standard sales-invoice process.
• Design response reconciliation: A successful API request is not the end of the process. MyInvois can initially accept documents for further processing, after which the ERP or middleware needs to retrieve and reconcile validation results.
• Prevent duplicate submissions: Retry logic should understand prior responses rather than blindly resubmitting invoices. MyInvois includes duplicate-submission controls, so uncontrolled retry mechanisms can create avoidable exceptions.

MyInvois Portal or API Integration?

An existing accounting or ERP system does not necessarily need to be replaced. The real question is whether it can supply accurate required data, support document mapping and exchange information reliably with MyInvois directly or through an integration layer.

Advintek Malaysia becomes relevant where businesses require MyInvois API integration, ERP-connected invoice automation, multi-entity workflows, submission monitoring, error management, TIN and BRN controls, self-billed or consolidated e-Invoice processes, or Peppol connectivity without replacing their core ERP.

Treat the RM3 Million Exemption as a Compliance Decision, Not a Delay Strategy

The revised Malaysia e-Invoice exemption threshold gives many smaller businesses meaningful relief from mandatory implementation, but the decision cannot be made from turnover alone. Ownership relationships, group structure, implementation history and the latest HASiL position all need to be considered.

Businesses that qualify for exemption may reasonably postpone full implementation. They should not, however, ignore master-data quality, accounting-system capability or future growth.

Companies remaining in scope need a different priority: reliable MyInvois integration, accurate TIN and BRN information, controlled invoice mapping, status reconciliation, duplicate prevention and clear exception ownership.

For organisations operating ERP, accounting, POS or multi-entity environments, Advintek Malaysia can help assess the appropriate e-Invoice architecture and determine whether portal-based processing, API integration, automation or interoperable invoice exchange best fits the business.

Frequently Asked Questions About Malaysia e-Invoice Exemption

What is the new Malaysia e-Invoice exemption threshold in 2026?

Malaysia increased the e-Invoice exemption threshold from RM1 million to RM3 million with effect from 1 September 2026. Eligible businesses below the revised threshold may be exempt from mandatory e-Invoice implementation. However, businesses should also review the ownership and group-related conditions introduced in the revised guideline before assuming that turnover alone establishes eligibility.

Is every business with revenue below RM3 million automatically exempt from e-Invoicing?

No. Businesses below RM3 million should also assess whether they have relevant non-individual shareholders, holding companies, related companies or joint ventures that affect their exemption status. A small subsidiary inside a larger corporate structure may therefore have a different e-Invoice requirement from an independent SME generating the same amount of revenue.

Can a business between RM1 million and RM3 million stop issuing e-Invoices immediately?

Businesses already implementing e-Invoicing should be cautious about stopping immediately. Current commentary around the revised guideline has identified a need for further clarification for taxpayers that previously entered implementation under the RM1 million threshold. Finance teams should confirm their individual position before disabling existing MyInvois or ERP processes.

Should an exempt SME still prepare for Malaysia e-Invoicing?

Yes, particularly if turnover is approaching RM3 million or the business is growing quickly. An exempt company can prepare without implementing a full integration immediately by cleaning TIN and BRN data, standardising customer records, checking accounting-system capabilities and mapping invoice processes. This reduces the implementation effort if the company later enters the mandatory scope.

Can businesses use their existing accounting software for MyInvois?

Potentially. Businesses do not automatically need to replace an existing ERP or accounting system. The key issue is whether the system can maintain the necessary e-Invoice data and support submission through an appropriate integration, connector or intermediary. Higher-volume businesses also need reliable response handling, retries, exception management and reconciliation between MyInvois and accounting records.

What is the difference between MyInvois and Peppol Malaysia?

MyInvois supports Malaysia’s tax-related e-Invoice submission and validation process. Peppol Malaysia supports interoperable structured invoice exchange between businesses and their accounting or ERP systems. They solve related but different problems. Businesses should not assume that Peppol is mandatory for every MyInvois submission. Peppol is more relevant where structured B2B interoperability forms part of the company’s digital invoicing model.

How should businesses choose between the MyInvois Portal and API integration?

The MyInvois Portal may be practical for businesses with relatively low invoice volumes and simple processes. API integration becomes more valuable when invoices originate from ERP, POS, e-commerce or multiple billing systems, or when manual entry creates excessive workload. The decision should consider invoice volume, system complexity, error handling, reconciliation requirements, security and expected future scale.

Source by:

Image by Gemini