What is MyInvois? A Plain-English Guide for Malaysian Businesses (2026)

If you run a business in Malaysia, you have almost certainly heard about e-invoicing and the MyInvois system. The topic is everywhere — in WhatsApp groups, at accounting seminars, in emails from your bank. But for every person who explains it clearly, there are three more who make it sound more complicated than it needs to be.

This article cuts through the noise. By the time you finish reading, you will know exactly what MyInvois is, how it works under the hood, whether your business is affected, what happens if you ignore it, and what practical steps you should take today. Everything here is based on official documents from LHDN — no speculation, no guesswork.

What Exactly Is MyInvois?

MyInvois is Malaysia's national e-invoicing infrastructure, built and operated by LHDN (Lembaga Hasil Dalam Negeri). It comes in two flavours that serve different types of businesses.

The first is the MyInvois Portal at myinvois.hasil.gov.my. This is a free web interface where you can log in with your MyTax credentials and key in invoices manually, one by one. LHDN built it specifically for micro businesses and sole traders who issue only a handful of invoices per month and do not want to invest in software.

The second is the MyInvois API at api.myinvois.hasil.gov.my. This is a REST API that allows accounting systems, ERP platforms, and middleware solutions to submit invoices programmatically in bulk. If your business issues more than a handful of invoices a day, the API route is the only practical path.

Both channels accept invoice data in either XML or JSON format, following the UBL 2.1 international standard. The good news: you do not need to know what UBL 2.1 means. Your accounting software or a middleware provider handles that translation.

How Does the Validation Process Actually Work?

Understanding the flow end-to-end helps demystify what feels like a bureaucratic black box. Here is what happens every time you submit an invoice:

1. 1
   You create the invoice in your accounting software or billing system, exactly as you do today — line items, amounts, buyer details, SST if applicable.
2. 2
   The invoice is converted into XML or JSON format following the UBL 2.1 schema. Your software or middleware handles this automatically.
3. 3
   It is submitted to LHDN via the MyInvois API (or manually typed into the portal).
4. 4
   LHDN validates it in near real-time — generally less than 2 seconds. LHDN checks the structure, the tax identification numbers, and other mandatory fields.
5. 5
   On success, LHDN stamps the invoice with an IRBM Unique Identifier Number and generates a QR code. This is your proof that the invoice is legally valid.
6. 6
   You share the validated invoice (with the UIN and QR code embedded) with your buyer. Your buyer can scan the QR code to verify authenticity on LHDN's portal.

If validation fails — say, because the buyer's tax identification number is wrong — the API returns an error, and you fix and resubmit. Nothing reaches the buyer until LHDN says it is valid.

The 72-Hour Window and How to Make Corrections

Once an invoice is validated and stamped, it is not completely locked forever. Both parties have a 72-hour window after validation to act:

• The buyer can reject the invoice within 72 hours if there is a genuine dispute — for example, goods not received or incorrect amounts.
• The supplier (you) can cancel the invoice within 72 hours if you made an error and need to start over.

After the 72-hour window closes, the invoice is permanently recorded in LHDN's system. You cannot delete or void it. If a correction is needed after that point, you must issue one of the accepted correction documents:

• Credit Note — to reduce the value of a previously issued invoice (e.g., returns, overcharges).
• Debit Note — to increase the value of a previously issued invoice (e.g., undercharges, additional charges).
• Refund Note — to document a refund paid back to the buyer.

Which Document Types Are Covered?

MyInvois covers eight document types in total. The first four are standard business-to-business or business-to-consumer transactions where you are the supplier:

• Invoice
• Credit Note
• Debit Note
• Refund Note

The remaining four are self-billed variants. Self-billing is used in situations where the buyer issues the invoice on behalf of the supplier — common in platform-based businesses, agent relationships, and certain procurement arrangements:

• Self-Billed Invoice
• Self-Billed Credit Note
• Self-Billed Debit Note
• Self-Billed Refund Note

All eight types go through the same validation pipeline on LHDN's servers and receive a UIN upon successful validation.

All document types must use version 1.1 — version 1.0 has been deprecated by LHDN and no longer validates digital signatures.

Who Needs to Comply and When?

LHDN is rolling out e-invoicing in phases, based on annual turnover. Here is the full schedule:

If your business is in Phase 4 — annual turnover between RM 1 million and RM 5 million — you are technically mandated from January 2026, but LHDN has extended a grace period to 31 December 2027 (announced April 2026), with full enforcement beginning 1 January 2028. This grace period is not a reason to delay indefinitely; it is breathing room to implement properly.

Businesses with annual revenue of RM 1 million and below received a permanent exemption following a Cabinet decision in December 2025. If you fall into this category, you are not required to use MyInvois — though you may still choose to do so voluntarily.

What Are the Penalties for Non-Compliance?

This is the part that tends to get people's attention. The penalties under the Income Tax Act 1967 are not trivial.

Consider a business that issues 200 invoices per month and ignores e-invoicing for six months. That is 1,200 invoices. At the minimum fine of RM 200 per invoice, the exposure is RM 240,000. At the higher end, it is RM 24 million. These are not theoretical risks — LHDN has the audit infrastructure to identify non-compliant taxpayers systematically.

The Three Ways to Connect to MyInvois

When businesses realise they need to comply, the first question is always: how do I actually do this? There are three common approaches.

1. Use the MyInvois Portal Directly

If you issue fewer than 10 invoices a month, logging into myinvois.hasil.gov.my and entering them manually is viable. It is free, it works, and there is nothing extra to set up. The downside is that it is entirely manual — no connection to your accounting records, no bulk submission, no automation.

2. Integrate Your Accounting Software Directly with the API

Large companies with in-house IT teams often build a direct integration between their ERP and the MyInvois API. This is technically the most tightly coupled solution but requires significant development effort — you need to handle OAuth 2.0 authentication, UBL 2.1 schema transformation, error handling, retry logic, digital signing, and ongoing maintenance as LHDN updates the API. LHDN provides a free sandbox at preprod-api.myinvois.hasil.gov.my for testing before going live.

3. Use a Middleware Solution

This is the route most Malaysian SMEs take. A middleware provider sits between your existing accounting system and the MyInvois API. You continue using your current software — SQL Account, QuickBooks, Xero, a custom system — and the middleware handles the transformation, authentication, submission, error handling, and record-keeping. You get compliance without rebuilding your entire finance stack.

This is exactly what EasyInvois does. We connect to the MyInvois API on your behalf, handle all the technical complexity, and give you a clean dashboard to manage your e-invoices — without needing an IT team or developer.

Getting Ready: A Practical Checklist for SMEs

Whether you are in Phase 3 playing catch-up or in Phase 4 preparing ahead of the grace period deadline, here is a practical checklist:

1. 1
   Confirm your obligation. Check your annual revenue figure. If it is above RM 1 million, e-invoicing applies to you.
2. 2
   Collect buyer TINs. Every invoice must include your buyer's Tax Identification Number. Start requesting this from your regular customers now — do not wait until the day you need to submit. Note that individual TINs now use the 'IG' prefix (e.g. IG12345678901), replacing the older 'OG' and 'SG' prefixes.
3. 3
   Audit your current invoicing process. How many invoices do you issue per month? Are they generated from a system or typed manually? This determines which integration approach makes sense.
4. 4
   Choose your integration approach. Portal for very low volume, middleware for most SMEs, direct API integration for businesses with development resources.
5. 5
   Test in the sandbox first. LHDN's preprod environment is free and lets you test end-to-end without affecting live records. Do not go straight to production.
6. 6
   Train your finance team. They need to understand the 72-hour window for rejections and cancellations, and what to do when validation fails.