The phase timeline, as it stands in 2026
| Phase | Effective date | Annual turnover (FY2022 basis) |
|---|---|---|
| Phase 1 | 1 August 2024 | Above RM100 million |
| Phase 2 | 1 January 2025 | RM25 million โ RM100 million |
| Phase 3 | 1 July 2025 | RM5 million โ RM25 million |
| Phase 4 | 1 January 2026 | RM1 million โ RM5 million (relaxation period to 31 Dec 2027) |
The exemption threshold was raised from RM500,000 to RM1 million effective 1 January 2026, and the previously planned Phase 5 was cancelled as a result โ the four-phase rollout is now complete, and businesses below RM1 million turnover remain exempt (though exemption isn't automatic; LHDN's MSME criteria apply). Phase 4 businesses have a relaxation period on penalties running to 31 December 2027, but the submission requirement itself is already live. Confirm your specific obligations directly against LHDN's published MyInvois guidance โ this is factual context, not tax advice, and dates and thresholds are set by LHDN, not by us.
Why "replatform your billing system" is usually the wrong answer
The instinct many businesses have on hearing "mandatory e-invoicing" is to assume they need new accounting or billing software entirely. In most cases they don't. MyInvois is a submission destination โ what actually needs to change is the connection between the system that already generates a quote, order or invoice and LHDN's platform, so that connection happens automatically instead of a staff member re-keying the same figures into a separate portal by hand. Replatforming an entire billing system to solve a submission-integration problem is expensive, slow, and usually unnecessary.
What the integration actually looks like
An invoice already gets created somewhere in your existing process โ a POS system, an accounting package, a custom order system. The integration adds a step: when that invoice is finalised, its data (the required fields โ buyer details, line items, tax treatment) gets formatted and submitted to MyInvois automatically, and the validated response (or any rejection requiring correction) flows back into the same system your staff already use. The invoice-creation step for staff doesn't change; what changes is what happens immediately after it, invisibly.
Where this connects to broader automation
For businesses already running custom booking or CRM systems โ a clinic's appointment-and-billing flow, for instance โ the e-invoicing integration is one more connection point in a system that's likely already handling WhatsApp reminders and CRM updates. It's rarely a standalone project once the underlying system is already custom-built; it's an additional module. For businesses still running fully manual billing, this is often the trigger that justifies building a proper system rather than continuing to patch a spreadsheet-based process.
What we do differently
We treat this as a factual, integration-level engineering task โ connecting your existing quote, order or billing flow to MyInvois โ and we don't provide tax advice as part of it; LHDN's own published guidelines govern the compliance side, and businesses should confirm their specific phase obligations with LHDN or their tax agent directly. See our custom software service for how the integration gets scoped and built, and our custom software vs SaaS guide if you're still deciding whether this needs a custom integration at all versus an off-the-shelf accounting tool's built-in e-invoice feature.
What to do about it
- Confirm your business's turnover band and current phase obligation directly against LHDN's published guidance.
- Identify where invoices are currently generated in your existing process โ that's the integration point, not a reason to replace the system.
- Scope the integration as a connection to MyInvois, not a full billing-system replatform, unless your existing process is genuinely inadequate for other reasons.
- If you're already running (or considering) a custom booking, CRM or billing system, treat e-invoicing as one module within it rather than a separate project.