Country
Malaysia
Article type
Regulatory update
Last checked
2026-08-30
HASiL published General e-Invoice Guideline v4.8 on 30 August 2026, superseding v4.7. Together with Specific Guideline v4.8 and current MyInvois release notes, it changes the evidence enterprises need for exemption decisions, new-business timing, document-version controls and production validation readiness.
Regulatory update · Malaysia
Principal regulatory and technical changes
The exemption test now starts below RM3 million
General Guideline v4.8 provides an exemption for taxpayers below RM3 million, but the exemption is unavailable in defined group, subsidiary, related-company and joint-venture circumstances. A turnover figure alone is therefore not a complete scope decision.
General and Specific Guideline v4.8 form the current baseline
The general guideline published on 30 August 2026 supersedes v4.7; the Specific Guideline remains v4.8. Project teams should date and version the source used for every exemption, consolidated-invoice, self-billing and transition decision.
SVDP introduced dedicated document versions
MyInvois added SVDP 1.2 without signature validation and SVDP 1.3 with signature validation for the voluntary disclosure programme through 31 December 2027. These versions are programme-specific, not a new default for every invoice.
Production validations continue to evolve
The SDK release notes announced enhanced field validations for production from 15 August 2026. Integration governance must therefore cover document versions, validation rules and regression testing.
Section references: HASiL implementation timeline · HASiL e-Invoice guidelines · MyInvois SDK release notes
How to determine whether the rules apply
Test each legal entity
Determine annual turnover or revenue using the basis and accounting period specified in Guideline v4.8. Retain the calculation, source accounts and approval rather than recording only the conclusion.
Apply the exemption exclusions
A taxpayer below RM3 million is not automatically exempt. Defined shareholder, parent, subsidiary, related-company and joint-venture relationships can remove the exemption when the connected entity meets the threshold.
Treat new businesses separately
Businesses commencing in 2023–2025 and those commencing from 2026 follow different start rules. The threshold year and commencement date should be stored as compliance attributes.
Inventory document scenarios
The scope assessment should cover individual and consolidated invoices, self-billed invoices, credit notes, debit notes and refund notes, not only standard sales invoices.
Section references: HASiL implementation timeline · HASiL e-Invoice guidelines · MyInvois SDK release notes
Current implementation timeline
| 1 Aug 2024 | Turnover or revenue above RM100 million | First mandatory group. |
|---|---|---|
| 1 Jan 2025 | Above RM25 million and up to RM100 million | Second group. |
| 1 Jul 2025 | Above RM5 million and up to RM25 million | Third group. |
| 1 Jan 2026 | Up to RM5 million | Phase 4. Guideline v4.8 separately provides a below-RM3-million exemption subject to stated exclusions. |
| 1 Jul 2026 onward | New businesses and threshold crossings | Different commencement rules apply to businesses starting in 2023–2025 and from 2026 onward; the first year in which RM3 million is reached must be retained as evidence. |
| 30 Aug–23 Oct 2026 | Guideline and SDK controls | General Guideline v4.8 is the current baseline; enhanced validations are in production, with new length controls announced for production from 23 October 2026. |
Section references: HASiL implementation timeline · HASiL e-Invoice guidelines · MyInvois SDK release notes
Enterprise implications
- Scope decisions should be recorded by legal entity, not inferred from a group turnover headline. New businesses, changed accounting periods and exemptions require the detailed guideline rules.
- Document version selection must be explicit. Standard invoice processing and SVDP submissions should not be mixed by a silent fallback in the integration layer.
- Validation changes should enter regression testing with named owners. A field that passed last year may be rejected after a platform rule update even when the source invoice has not changed.
- Transition relief changes how compliance is operated; it does not remove the need to reconcile source invoices, submitted documents and customer-facing records.
From regulatory decision to operating control
Entity scope register
Maintain a versioned register of entity, turnover basis, related-party test, mandatory date, exemption rationale and approving tax owner.
SAP/ERP fact ownership
Assign one authoritative source for supplier, buyer, tax, monetary, reference and original-document facts; block incomplete records before transformation.
Version and validation governance
Map each business scenario to an approved MyInvois document version and regression-test announced platform validation changes before their production date.
Operational reconciliation
Reconcile ERP invoices, submission identifiers, final MyInvois statuses, customer documents and corrections as one lifecycle with named exception owners.
Evidence retention
Retain the guideline version, scope approval, outbound payload, platform response, status history, customer representation and correction relationship.
Recommended implementation actions
- Replace General Guideline v4.7 in the compliance evidence pack and record General Guideline v4.8 dated 30 August 2026 together with Specific Guideline v4.8.
- Reconfirm entity thresholds, exemptions, consolidated and self-billed scenarios with Malaysian tax owners.
- Verify supported MyInvois document versions and run regression tests against current production validation rules.
- Review invalid-document routing, duplicate prevention and finance reconciliation before the next period close.
Frequently asked questions
Is every taxpayer below RM3 million exempt?
No. Guideline v4.8 contains exclusions connected with ownership, parent, subsidiary, related-company and joint-venture relationships. The full entity context must be tested.
Did Guideline v4.8 replace all rollout dates?
No. The principal phased dates remain, while v4.8 changes and clarifies exemption and new-business rules. Both the phase table and the detailed rules are needed.
Should SVDP 1.2 or 1.3 become the default invoice version?
No. The SDK identifies them as versions for the voluntary disclosure programme. Standard processing should retain its approved version unless an authoritative change applies.
Does an accepted API request prove the invoice is valid?
No. Submission acceptance and final validation are different events. The final status must be retrieved and reconciled before downstream completion is recorded.
Conclusion
A sustainable Malaysia e-Invoicing solution requires controlled regulatory change management. Each guideline or SDK change must be traceable to scope decisions, ERP data, validation tests, operating procedures and retained evidence while preserving the invoice's business identity.
Official sources
Last checked: 2026-08-30