Malaysia e-Invoice Requirements in 2026

Malaysia's e-invoice requirements in 2026 are driven first by annual turnover, then by the exact transaction types your business handles. Malaysia rolled the mandate out in stages: taxpayers with turnover above RM100 million came in on August 1, 2024, RM25 million to RM100 million on January 1, 2025, RM5 million to RM25 million on July 1, 2025, and businesses with turnover up to RM5 million on January 1, 2026. According to Malaysia's official e-Invoice implementation timeline, updated on August 30, 2026, taxpayers with annual turnover or revenue below RM3 million are exempt from e-Invoice implementation, a threshold raised from RM1 million. The exemption does not reach a small business whose non-individual shareholder, holding company or related company has turnover of RM3 million or more, and the smallest phase keeps an interim relaxation period until December 31, 2027.

That headline answer only gets you part of the way. Malaysia's rules also reach cross-border transactions, and businesses can work through either the MyInvois Portal or the MyInvois API depending on how manual or integrated their workflow needs to be. For most readers, the real question is not just "When do the rules start?" but "What does this change inside our invoicing process once we are in scope?"

Use this Malaysia e-invoice guide as a high-level reference for those questions. It covers who must comply, how the rollout and its relaxation periods work, where the exemption line falls, and what the regime changes for finance operations.

The bands are read from turnover in the 2022 audited financial statements, or from revenue in the year of assessment (YA) 2022 tax return where there are no audited accounts. Once a date is set, later changes in turnover do not move it. The RM3 million exemption has its own entry rule for businesses that grow, covered in the next section.

For AP teams, controllers, and advisers, the operational implication is straightforward: invoice handling is no longer only an internal bookkeeping process. Once you are in scope, invoice data has to be prepared, checked, and submitted within a national framework overseen by Lembaga Hasil Dalam Negeri Malaysia, usually referred to as HASiL or LHDN, so the quality of your upstream invoice process starts to matter as much as the filing step itself.

Who Is Exempt Under the RM3 Million Rule

Under section 1.6.1(e) of IRBM's e-Invoice Guideline Version 4.8, published on August 30, 2026, a taxpayer with annual turnover or revenue below RM3,000,000 is exempt from issuing e-Invoices, self-billed e-Invoices included. Its existing receipts continue to serve as proof of expense. The exemption works in one direction only: a supplier selling to an exempt business still has to issue e-Invoices to it.

The exemption covers every category of taxpayer, with three exceptions set out in section 1.6.10. It does not apply to a taxpayer:

• with a non-individual shareholder whose annual turnover or revenue is RM3 million or more;
• that is a subsidiary of a holding company at RM3 million or more; or
• that has a related company or joint venture at RM3 million or more, with "related company" taking its meaning from section 2 of the Promotion of Investments Act 1986.

IRBM's e-Invoice General FAQs, updated September 4, 2026, give the typical case. A subsidiary with RM400,000 of revenue in 2022 does not qualify, because its parent company is within the mandate, so it implements e-Invoicing from July 1, 2026, the concessionary date for small businesses that fall outside the exemption.

Under the old RM1 million threshold, businesses now below RM3 million could already be live from January 1 or July 1, 2026. If such a business meets the exemption criteria, the FAQ allows it to stop issuing e-Invoices immediately, with no application to IRBM and no prior approval. It may keep issuing them voluntarily instead, and it does not have to join the e-Invoice Special Voluntary Disclosure Programme (SVDP) for e-Invoices it failed to issue.

The exemption is tested again as a business grows:

• A business whose annual turnover or revenue reaches RM3 million implements e-Invoicing from January 1 of the second year after that year of assessment. In the FAQ's example, a company that passed RM3 million in 2026 starts on January 1, 2028.
• Once that date is set, the obligation stays even if turnover later falls back below RM3 million.
• A sole proprietor counts every business registered in their name. Three businesses with RM750,000, RM820,000 and RM1.54 million of revenue total RM3.11 million, so their owner is in scope.
• A business that commenced between 2023 and 2025 with turnover of at least RM3 million starts on July 1, 2026.

If you are advising multiple entities, apply the test entity by entity, and check each one's shareholders, parent and related companies before relying on its own turnover.

What the Interim Relaxation Period Allows Until 2027

Each phase received an interim relaxation period after its implementation date, shown in the table above. For the up-to-RM5 million phase, both the January 1, 2026 and July 1, 2026 dates, relaxation runs until December 31, 2027. During relaxation a business may issue consolidated e-Invoices for all its transactions, including the ones that would otherwise need an individual e-Invoice, though it still has to issue them every month rather than once at the end of the period. The relaxation is optional: a business whose system is ready can issue individual e-Invoices for each transaction now.

Once relaxation ends, consolidation narrows. The most visible limit is that any single transaction above RM10,000 needs its own e-Invoice, a rule in force from January 1, 2026 for every business past its relaxation period. For the three larger phases that is already the position today. For the smallest phase it arrives on January 1, 2028.

MyInvois Requirements and the Portal vs API Decision

MyInvois is the environment businesses use to submit and manage e-Invoices under Malaysia's mandate. At a policy level, that sounds straightforward. At a workflow level, the more useful question is how your team will actually interact with it every day.

Malaysia gives businesses two main submission routes:

• MyInvois Portal, which is better suited to lower-volume or more manual processes where staff can work directly in the government interface.
• MyInvois API, which becomes more relevant when your business wants system-to-system submission, tighter controls, or a process that can handle higher volume without relying on repeated manual entry.

That does not mean the portal is only for very small businesses or that the API is automatically the right answer for every larger one. The real decision turns on how your workflow is built.

The portal is usually easier to picture when invoices are created or reviewed in a hands-on process and the volume is manageable. Teams can work directly in the interface, confirm what is being submitted, and avoid an integration project. The trade-off is that manual handling becomes harder to sustain as transaction volume rises, exception cases multiply, or several people need to work from the same source data.

The API matters when the finance process already depends on systems talking to each other. If invoices originate in ERP, billing, or AP tools, or if your team needs consistent validation and status handling at scale, the API starts to look less like a technical extra and more like an operating requirement. If you want the deeper implementation view, the site's MyInvois API integration workflow covers that path in more detail.

For most finance teams, the best decision frame is:

• Choose the portal when the priority is getting a compliant process live without heavy systems work.
• Choose the API when the priority is integrating submission into a broader finance or billing workflow with less manual intervention.

Either way, separate the high-level policy question from the detailed build question. The rule is "you must comply." The operating question is "which route lets your team comply reliably with the volume, controls, and review process you actually have?"

How Cross-Border, Self-Billed, and Consolidated Scenarios Fit the Rule Set

Malaysia's regime is not limited to ordinary domestic supplier invoices. The rules also reach cross-border transactions, which matters for businesses buying from foreign suppliers, selling across borders, or managing mixed domestic and overseas document flows. For finance teams, that usually means the document trail becomes more important, because the tax and invoice treatment may involve counterparties that do not follow the same local issuance process you use in Malaysia.

The mandate is also broader than the rollout table suggests. A business may understand its turnover band but still need to ask whether the invoice is supplier-issued, self-billed, consolidated, domestic, or cross-border. Those are not side notes. They affect how the invoice should be created, supported, and reviewed.

Two scenarios deserve special attention:

• Self-billed e-Invoice cases, where the document is generated from the recipient side under the applicable rule set rather than following the normal supplier-issued pattern. If that is part of your process, the best next step is to review the dedicated guide on Malaysia self-billed e-Invoice scenarios.
• Consolidated e-Invoice treatment, which can be relevant where multiple transactions are grouped under the permitted framework instead of being handled one by one in the standard way. The details matter, which is why the focused article on Malaysia's consolidated e-Invoice rules is the better place for scenario-specific interpretation.

The key point for this pillar article is scope control. You do not need to master every special-case rule before understanding the regime, but you do need to recognize when your transaction type moves you out of the ordinary invoice pattern. Cross-border transactions, self-billed structures, and consolidated treatment all change the supporting records and review steps that finance teams need to manage, even when the underlying goal is still the same: get accurate invoice data into the right compliant format at the right time.

---

What AP and Finance Teams Need to Change in Their Workflow

Many compliance explainers stop at dates and definitions. The harder part starts after that, when your team has to turn the rule into a repeatable process.

In practice, Malaysia's mandate changes four parts of the workflow:

• Invoice data quality. Teams need the right invoice fields in a structured form before submission.
• Supporting-document handling. Source files, attachments, and transaction evidence need to line up with the invoice record.
• Review ownership. Someone has to check exceptions, validation errors, and rejected submissions instead of treating them as ad hoc clean-up.
• System readiness. Portal or API submission only works consistently if the upstream data is reliable.

Finance teams often discover the bottleneck is not the government platform itself. It is the state of the invoice data before anything reaches MyInvois. Mixed supplier layouts, missing fields, inconsistent coding, and unclear handoffs between AP, operations, and finance all become more visible once the process has a formal validation step.

For AP teams, that can mean standardizing how supplier invoices are captured and reviewed before submission. For controllers, it often means clarifying ownership for rejected or corrected invoices and making sure the audit trail still makes sense. For bookkeepers or shared-service teams, it can mean redesigning handoffs so that invoices, supporting documents, and transaction context stay together instead of being pieced back together later.

This is also the point where neutral, upstream process design starts to matter. If your team is still wrestling with mixed PDF invoices, image files, or incomplete supporting records, broader invoice data extraction workflows become relevant because submission quality depends on what happens before the submission step, not only on the channel you choose at the end.

The practical takeaway is that compliance is partly a tax question and partly an information-quality question. Teams that solve only the filing side usually find that exceptions and manual rework pile up upstream.

2026 Planning Priorities and Official Updates to Watch

Once you understand the rule boundaries, the next step is not to over-engineer the answer. It is to confirm a short list of planning points and keep them current.

Start with the items that directly affect scope:

1. Confirm your phase from 2022 turnover, whether the RM3 million exemption applies once shareholders, parent and related companies are counted, and when your relaxation period ends.
2. Identify whether any part of your transaction mix involves cross-border activity, self-billed flows, or consolidated treatment.
3. Decide whether your operating model fits the MyInvois Portal, the MyInvois API, or a staged move from one to the other.
4. Map the data and document controls that need to happen before submission so compliance does not depend on manual rescue work.

Then keep an eye on official updates, because the rules moved twice for small businesses in 2026. The relaxation period for the up-to-RM5 million phase was extended to December 31, 2027, and on August 30, 2026 IRBM updated the timeline and the e-Invoice Guideline to raise the exemption from RM1 million to RM3 million. The e-Invoice SVDP, under which businesses can disclose and correct e-Invoice non-compliance voluntarily, runs from July 7, 2026 to December 31, 2027. A guide like this helps you frame the decision, but the final answer for an edge case should still come from the latest HASiL and MyInvois materials.

If you take one planning principle away, make it this: get the classification right before you optimize the process. Once you know whether the mandate applies, when it applies, and which scenarios change the rule set, you can choose the right workflow with much less wasted effort.