E-Invoicing Under IRBM: What E-Commerce Brands Need to Get Right

If your business sells online in Malaysia, e-invoicing is not a future compliance project. The Inland Revenue Board of Malaysia's (IRBM) phased rollout has been running since August 2024, working down from the largest taxpayers, and the final phase began on 1 January 2026. For most businesses the mandate is already live.

What is less widely understood is what the relaxation period actually permits, and that is where most of the confusion — and a good deal of published advice — currently sits. This article is written against the two current primary documents: the e-Invoice Guideline version 4.7 and the e-Invoice Specific Guideline version 4.8, both published on 7 July 2026. Anything citing version 4.5 or 4.6 predates material changes.

Where the rollout actually stands

The phases are set out in Guideline v4.7, §1.5.

Two details get missed. First, Phase 4 has a second implementation date of 1 July 2026, covering businesses that commenced operations between 2023 and 2025 with turnover of RM1 million or more, and any business commencing from 2026 onward. Second, there is no Phase 5 — the fifth phase that was originally floated was cancelled in December 2025 when the exemption threshold was raised.

Businesses with annual turnover or revenue of less than RM1 million are not mandated at all (Guideline v4.7, §1.6.1(e)). Note "less than", not "up to". One caveat worth knowing: under §1.6.5 the exemption attaches to the person, so entities owned by an exempt person must still comply on the normal timeline.

For a typical business, e-invoicing means connecting accounting software to IRBM's MyInvois system. For an e-commerce business it is a different scale of problem, and it is one we have worked through directly on Adobe Commerce (Magento) implementations.

Why e-commerce makes this harder

A single retail POS terminal issues invoices one at a time, in a predictable format. An e-commerce store generates transactions through checkout, but also through credit memos, cancellations, staff purchases, vouchers, and month-end consolidation — each of which IRBM's validation rules treat differently. A few of the specific complications:

• Not every order should trigger an e-invoice immediately. IRBM requires the invoice to reflect a completed, invoiced transaction, not an order that has merely been placed. Submitting too early creates invoices that do not match what actually shipped.
• Refunds and cancellations need their own e-invoice events. A credit memo against an already-submitted e-invoice is not just a backend adjustment. It has to be reflected back to IRBM correctly, and only for items that were actually invoiced.
• Discounts, vouchers, and staff purchases all need to be shown correctly, with consistent decimal precision and correct sign display, so the figures IRBM validates reconcile with the order total. This is easy to get subtly wrong when a store has several discount mechanisms layered together.
• Not every customer wants an e-invoice for every purchase. Malaysian e-commerce businesses generally still need to support consolidated month-end e-invoices for B2C transactions that were not individually requested, alongside real-time, on-request e-invoices for customers who do want one.
• Rejections happen, and the system needs to handle them gracefully. IRBM can reject a submission, and the store needs to correct and resubmit without manual intervention every time.

The RM10,000 rule, and what the relaxation period really allows

This is the part most commonly got wrong, and it is worth being precise about.

The rule is real. Specific Guideline v4.8, §3.7.2, requires an individual e-invoice for any single transaction exceeding RM10,000, across all industries, effective 1 January 2026. Consolidation is not permitted for those transactions. Note "exceeding" — sources describing this as "RM10,000 or more" are overstating it.

What is frequently reported incorrectly is that this applies regardless of phase or relaxation status. It does not. §16.2(a) states that during the interim relaxation period a taxpayer may issue a consolidated e-invoice for all activities and transactions, expressly including the industries and activities listed under §3.7 — which is where the RM10,000 rule lives. §16.2(d) goes further: during relaxation, a taxpayer may decline a buyer's request for an individual e-invoice altogether.

Phase 4's relaxation period runs until 31 December 2027 (Specific Guideline v4.8, §16.1, Table 16.1), covering both the 1 January and 1 July 2026 implementation dates. It was originally six months, ending 30 June 2026, and was extended in April 2026 — advice still quoting the June 2026 date is out of date. §16.3 confirms that no prosecution under section 120 of the Income Tax Act 1967 will be pursued during relaxation, provided the conditions in §16.2 are met.

So a Phase 4 business — which is most Malaysian e-commerce SMEs — can currently consolidate transactions above RM10,000 and can decline individual requests, until 31 December 2027. Full enforcement begins 1 January 2028.

None of which is an argument for waiting, and we will come back to that.

The new Special Voluntary Disclosure Programme

The single most significant change in the current documents is §17 of Specific Guideline v4.8, which is the only substantive addition from version 4.7. It introduces an e-Invoice Special Voluntary Disclosure Programme (SVDP), announced in Parliament on 7 July 2026 and running from that date until 31 December 2027.

It covers taxpayers who missed submitting e-invoices, submitted non-compliant or erroneous ones, or are already under IRBM compliance review. Under §17.3, e-invoices disclosed through the programme attract no compliance review, penalty, or prosecution. The exceptions in §17.4 matter: relief does not apply where submissions still fail to meet requirements, or where there is fraud, wilful default, or negligence.

Two mechanical details are easy to trip over. Submissions must use e-Invoice version SVDP 1.2 (without digital signature) or SVDP 1.3 (with), which exist only for disclosures under this programme. And under §17.6, unsubmitted consolidated e-invoices must be filed against the relevant month of transaction rather than lumped together across months.

If a store has been live through any part of the mandate and its submissions have been patchy, this is the window to fix that cleanly.

How we have approached it

Across the Adobe Commerce e-invoice implementations we have delivered, the approach has consistently covered the same core pieces:

• A customer-facing request flow, letting customers request an e-invoice at checkout or from their order history, rather than only generating one automatically.
• Backend automation tied to order state, so e-invoices trigger only once an order is genuinely invoiced, with automatic resubmission if IRBM rejects the first attempt, and separate handling for credit memos and cancellations.
• Correct line-item treatment for discounts, vouchers, and staff purchases, standardising decimal precision and sign display so promotional pricing reconciles cleanly against IRBM's validation rules rather than triggering rejections or mismatches.
• Consolidated e-invoicing for month-end, automatically batching B2C transactions that were not individually requested into a compliant consolidated file, while excluding anything already issued individually during the month. Under §3.6.2 that submission is due within seven calendar days after month end.
• Customer notification with the validation QR code, so that once IRBM validates an e-invoice the customer receives it by email with the QR code and a clear path to request cancellation if needed.
• Exportable compliance reporting, on demand and monthly, for finance and audit purposes, with e-invoice status visible directly against each order.
• Encryption at rest and in transit for all data passed to and from IRBM's systems.

None of this is exotic engineering. But getting the order-state logic, the discount and voucher edge cases, and the retry handling right is what separates an e-invoice integration that quietly works from one that produces a steady trickle of rejected submissions and manual finance cleanup.

What to do if you have not started

The relaxation period is genuine breathing room, and it is longer than most businesses realise. It is also not free.

E-invoice integration touches checkout, order management, refunds, and finance reporting all at once. Those are four areas that rarely change together, and a rushed integration close to a deadline is where most implementation problems come from. There is a difference between having until 31 December 2027 and having a fortnight in December 2027.

Two practical points. If you are relying on consolidation during relaxation, make sure that is a decision someone has actually made rather than a default nobody checked — because the day it lapses, every transaction above RM10,000 needs an individual e-invoice and the mechanism has to already exist. And if past submissions have been incomplete or wrong, the SVDP window closes on the same date the relaxation does.

If you are working out what this looks like for your own store, our Adobe Commerce (Magento) Development page covers the broader platform integration work, and ERP and back-office integration deals with the order and finance data flow an e-invoice implementation depends on.

---

Sources: Inland Revenue Board of Malaysia, e-Invoice Guideline version 4.7 and e-Invoice Specific Guideline version 4.8, both published 7 July 2026. Section references throughout are to those two documents. Rules in this area have changed at short notice more than once — check the current version before acting on any date quoted here.