Malaysia is rolling out mandatory e-invoicing under the Inland Revenue Board of Malaysia (IRBM) via the MyInvois platform. For in-scope businesses, invoices must be submitted for validation before they are legally issued, making e-invoicing both a process and systems change.
This guide explains what’s changing, who is affected, the phased rollout dates, and how to get compliant without turning e-invoicing into a recurring internal project
TL;DR summary
- Malaysia’s e-invoicing mandate is governed by the Inland Revenue Board of Malaysia (IRBM) and enforced through the MyInvois platform, using a clearance-style validation model
- Implementation is phased by annual revenue, starting 1 August 2024 for businesses above RM100 million, and extending to lower revenue bands over time
- In-scope taxpayers must generate structured invoice data and submit it to MyInvois via API or portal for validation, after which the document is returned with a UUID, with a QR code displayed in the portal or generated via the API from the validation link
- Key compliance topics include format readiness (UBL 2.1 / JSON), integration and monitoring, the 72-hour rejection window, and 10-year retention
- A managed provider approach can reduce ongoing effort by centralising format transformation, validation submission, status handling, monitoring, and change management across countries
Malaysia e-invoicing at a glance
E-invoicing in Malaysia involves the mandatory electronic issuance and validation of invoice data through the MyInvois platform, which is governed by the Inland Revenue Board of Malaysia (IRBM).
For in-scope transactions, two steps are required:
- You must provide a readable invoice to your customer through your normal channels
- You must submit the required invoice data to MyInvois for validation in the prescribed structured format
An invoice is only treated as legally valid once it has been validated and assigned identifiers (such as a UUID) by IRBM.
Malaysia’s e-invoicing journey: a timeline
Malaysia’s rollout followed a phased timeline based on annual turnover or revenue.
Key milestones
- 1 August 2024: Mandatory for businesses with annual revenue above RM100 million
- 1 January 2025: Mandatory for businesses with annual revenue above RM25 million and up to RM100 million
- 1 July 2025: Mandatory for businesses with annual revenue above RM5 million and up to RM25 million
- 1 January 2026: Mandatory for businesses with annual revenue above RM1 million and up to RM5 million
It’s worth noting here that, as of December 2025, businesses with an annual revenue below RM1 million are exempt from complying with the mandate.
How regulations may affect you
How much changes for your organisation depends on your current invoicing setup. However, most businesses see impact in three areas:
1) Process changes
- Moving from paper or PDF-first invoicing to structured, system-generated invoice data
- Aligning invoice issuance, internal controls, and customer delivery with MyInvois validation and status feedback
- Handling exceptions such as rejections, cancellations, and corrections
2) Systems and integration
- Ensuring your ERP, billing, POS, or invoicing tools can produce the required data fields consistently
- Integrating via MyInvois API (or using the portal for manual submission)
- Managing retries and error handling so issues are resolved quickly
3) Compliance operations
- Setting up monitoring so failures are visible early, not discovered at month-end
- Meeting retention and audit-readiness needs (Malaysia guidance commonly references 10-year retention)
Who is in scope for Malaysia e-invoicing?
Malaysia’s mandate is being rolled out in phases. In general, e-invoicing applies to B2B, B2G, and B2C transactions for businesses that meet the revenue thresholds for the relevant phase.
If you’re in scope, you must be able to:
- Submit invoice data to MyInvois for validation
- Receive validation status, including the identifiers needed to make the invoice legally recognised
- Store validated invoices and related artefacts for audit purposes
If you’re unsure whether a specific entity is in scope, confirm using your finance and tax team’s turnover figures and the latest official IRBM guidance.
What documents are covered?
Malaysia’s e-invoicing requirements cover a set of sales and accounting documents, including:
- Invoices
- Credit notes
- Debit notes
- Refund invoices
- Self-billed invoices (important for certain cross-border scenarios)
How does Malaysia’s e-invoicing system work?
Malaysia operates a centralised clearance-style model, where invoice data is validated before the invoice is considered legally issued.
A typical flow looks like this:
1) Supplier generates invoice data in the required structured format (commonly UBL 2.1 or JSON)
2) Invoice is submitted to MyInvois via API (or manually via the portal)
3) IRBM validates the invoice and assigns:
- A UUID
- A validation timestamp
- Data used to generate a QR code for verification
4) Supplier delivers the validated invoice to the buyer
5) The invoice is stored to support retention and audit-readiness
What about cross-border transactions and self-billing?
Cross-border scenarios often require special handling:
- If a foreign supplier does not issue a MyInvois e-invoice, the Malaysian buyer may need to issue a self-billed e-invoice and submit it to MyInvois for validation
- Import and export scenarios may have additional timing and data requirements, depending on the transaction type
Because cross-border requirements can be detailed, treat this as a key early scoping step for your implementation.
What are the penalties for non-compliance?
Non-compliance can create risk beyond direct penalties, including operational disruption and audit exposure.
Commonly referenced enforcement consequences include:
- Financial penalties for failing to issue compliant e-invoices
- Potential legal exposure in cases of incorrect or fraudulent invoicing
- Audit and assessment risk if invoices are not retained or cannot be retrieved
Penalty rules can change and vary by violation type, so confirm the current penalty mechanics in the relevant IRBM regulation and supporting guidance.
MyInvois compliance plan: what to do first
Because Malaysia uses a validation-before-issuance approach, the most important thing is to design your invoicing process so it can handle clearance timing, rejections and enrichment (UUID and QR) without disrupting billing operations.
1) Confirm when each entity goes live
- Map each legal entity to the correct rollout phase based on annual revenue
- Identify which invoice channels need MyInvois coverage (ERP billing, POS, e-commerce, manual invoicing)
2) Decide your submission approach: API, portal, or hybrid
- Use the portal only if volumes and process allow it, as it introduces manual steps
- For higher volumes, design for API submission, including retries and automated error handling
3) Validate MyInvois data readiness
- Check that required fields are consistently populated across systems and scenarios
- Confirm how you will handle document types such as credit notes, debit notes, refunds, and self-billed invoices (including cross-border scenarios)
4) Build the operational flow around validation outcomes
- Define what happens if MyInvois validation is rejected and how you correct and re-submit within the required time window
- Ensure downstream steps (customer delivery, posting, collections) align with the fact that invoices are only “final” once validated
5) Implement monitoring and audit readiness as day-to-day operations
- Monitor submission status and failures continuously, not only at month-end
- Store validated invoice artefacts, including identifiers such as UUID and QR-related data, and align retention processes with the expected 10-year requirement
Your two implementation options compared
| Your options | Connection | What you manage | Pros | Cons |
|---|---|---|---|---|
| In-house integration | Build and operate direct connectivity to IRBM MyInvois | MyInvois field mapping, API submission orchestration, rejection handling, monitoring, change management | Maximum control over process and timing | Higher engineering and operational burden, ongoing maintenance as requirements evolve |
| Managed provider | Connect once to a provider that supports MyInvois | Provider handles transformation, submission, status handling, monitoring, and regulatory updates | Faster rollout, lower operational risk, scalable across countries | Recurring service fees, dependency on provider SLAs and roadmap |
How ecosio can help
With ecosio’s Global E-invoicing Compliance (GEC) approach, the goal is to help businesses meet Malaysia’s MyInvois requirements without building a one-off local solution.
Typical support areas include:
- Connecting your ERP or invoicing landscape to MyInvois with a single integration
- Transforming supported document types into the required structured format (for example UBL 2.1 or JSON)
- Submitting invoices for validation and tracking identifiers such as UUID and QR verification artefacts
- Monitoring status and handling exceptions so issues are resolved quickly
To discuss how to approach Malaysia e-invoicing readiness as part of a broader global strategy, feel free to get in touch. Our experts are always happy to help!
Frequently asked questions (FAQ)
Is e-invoicing mandatory in Malaysia?
Yes, Malaysia has been rolling out mandatory e-invoicing in phases based on annual revenue, starting from 1 August 2024 for the largest taxpayers.
Who governs e-invoicing in Malaysia?
The e-invoicing mandate is governed and enforced by the Inland Revenue Board of Malaysia (IRBM) through the MyInvois platform.
What is MyInvois?
MyInvois is the central platform used to submit invoice data for validation. A validated invoice is returned with identifiers such as a UUID and information used for verification (for example QR code generation).
Which formats are used for Malaysia e-invoicing?
Commonly referenced structured formats include UBL 2.1 and JSON. Always confirm the latest technical specification for your implementation phase.
What should we do if we purchase from a foreign supplier?
In certain scenarios, Malaysian buyers may need to issue a self-billed e-invoice if the foreign supplier does not issue a MyInvois e-invoice. In such cases, you should confirm the required approach based on transaction type and latest IRBM guidance.
