Malaysian e-invoicing uses LHDN’s MyInvois system to validate structured invoice information. A PDF invoice alone is not a MyInvois submission. Before buying an integration, confirm whether your business is in scope and how invoice data moves through your accounting, POS or ordering systems.
Current Implementation Timeline
Checked on 4 October 2026. HASiL’s Bahasa Malaysia timeline, updated 30 August 2026, lists the following phases and states an exemption for annual revenue or sales below RM3 million. Confirm the applicable guidelines, exceptions and your circumstances with HASiL or your tax adviser.
| Annual revenue or sales | Implementation date |
|---|---|
| Above RM100 million | 1 August 2024 |
| Above RM25 million to RM100 million | 1 January 2025 |
| Above RM5 million to RM25 million | 1 July 2025 |
| Up to RM5 million | 1 January 2026 |
| Below RM3 million | Exempted in the cited current timeline |
Source: HASiL implementation timeline. Earlier versions of this article used an older threshold; use the current official guidance before making a tax decision.
Portal, Existing Software or API Integration?
For a low volume of invoices, assess whether the MyInvois portal is sufficient. If your accounting package already supports your required process, test that path before commissioning custom development.
An API integration may be useful when invoices originate in several systems or transaction volume makes repeated entry impractical. Check your software version, API permissions and provider charges rather than assuming every package includes the same capability.
Map the Data Before Building
Have finance and development agree:
- Where seller and buyer information is maintained
- Which invoice, credit note, debit note and refund flows apply
- How product, tax, currency and document fields are mapped
- Which data checks happen before submission
- How validation status and document identifiers return to staff
- Who investigates rejected or uncertain submissions
Use the official MyInvois SDK for document formats, field rules and API behaviour. Requirements vary by document and transaction type; do not treat a short checklist as a complete specification.
Test Beyond the Happy Path
Test a valid invoice, missing data, a correction, duplicate attempts, an unavailable connection and reconciliation back to the source sale. Staff should see the current status and the next action without re-entering the whole transaction.
Store submission references and a history of changes. Keep credentials out of customer-facing code and restrict access to authorised staff. A successful API response alone does not prove that the business has met every tax obligation.
What to Ask an Implementation Partner
Request a written scope, sample data mapping, test plan, responsibility for guideline changes, operating costs and handover instructions. Decide who owns the production accounts and who supports a failed submission after launch.
For a more detailed operational review, use our e-invoice integration checklist.
Frequently Asked Questions
Does every Malaysian SME need e-invoicing?
No. The cited HASiL timeline includes an exemption below RM3 million annual revenue or sales. Check the current guidelines and your specific circumstances before deciding.
Is an emailed PDF an e-invoice?
A PDF alone is not a structured submission to MyInvois. Your process must follow the applicable official submission and validation requirements.
Can ETD connect an existing internal system?
We can assess the source data and supported integration route. The proposal defines what is built, tested and supported; your finance team confirms tax treatment.
