Malaysia E-Invoicing
FAQ

E-invoicing in Malaysia refers to the mandatory submission of all commercial invoices to LHDN's MyInvois platform for real-time government validation before they are considered legally issued.

Unlike a PDF invoice sent by email, a Malaysia e-invoice must be submitted to MyInvois, validated by IRBM (the Inland Revenue Board of Malaysia), and stamped with a Unique Identification Number (UIN) and QR code. Only validated invoices are legally recognised for tax and audit purposes.

The system uses structured data formats (UBL XML or JSON) with up to 55 required fields — far more structured than a traditional free-form PDF invoice.

Read our full explainer: What is E-Invoicing in Malaysia? →

All businesses operating in Malaysia and meeting the annual revenue thresholds are required to issue e-invoices through MyInvois. The rollout is phased by revenue:

• Phase 1 — 1 August 2024: Businesses with annual revenue over RM100 million
• Phase 2 — 1 January 2025: RM25 million to RM100 million
• Phase 3 — 1 July 2025: RM5 million to RM25 million
• Phase 4 — 1 January 2026: RM1 million to RM5 million (active now)
• Exempted (for now): Businesses with revenue below RM1 million

This applies to companies, sole proprietorships, partnerships, and other business entities operating in Malaysia. Always verify your specific obligation directly with LHDN or a qualified tax professional.

View the full rollout timeline with phase details →

Not necessarily — but for most businesses, API integration is strongly recommended. LHDN allows two submission methods:

• API Integration: Your accounting software sends invoices directly to MyInvois automatically as you generate them. Validation happens in real time — typically within seconds. Recommended for any business issuing more than a few invoices per month.
• MyInvois Web Portal: You log in to the MyInvois portal and enter or upload invoice data manually. This works for very low-volume businesses but becomes extremely time-consuming as invoice counts grow.

Popular Malaysian accounting software — including AutoCount, SQL Accounting, QuickBooks, and Xero — now offer MyInvois integration either natively or via add-on. Some require software upgrades or paid modules.

There are also authorised middleware platforms that sit between your software and MyInvois, but these incur additional ongoing costs and should be evaluated carefully against direct API integration.

If LHDN's MyInvois system rejects your e-invoice submission, you will receive a detailed error response — typically within seconds — identifying the specific field(s) that caused the failure.

Common rejection reasons include:

• Seller name or TIN does not match LHDN records
• Missing or invalid MSIC code
• Tax type code not matching the actual tax treatment
• Tax calculation mismatch between line items and total
• Duplicate invoice number
• Invalid buyer TIN or registration number
• Missing mandatory fields (e.g. currency code, exchange rate for foreign currency)

You must correct the identified issues in your accounting system and resubmit. You cannot resend the same invoice data unchanged — you must create a corrected submission. Once you have correctly resolved the errors, the corrected invoice should pass validation on resubmission.

Note: This is different from a buyer-initiated rejection. Buyers have 72 hours to reject a validated invoice for commercial reasons — that is a separate process handled through MyInvois.

Sales and Service Tax (SST) must be applied and calculated per line item in a MyInvois e-invoice. Each line must specify:

• A tax type code (e.g. 01 = SST taxable, E = Exempt, Z = Zero-rated, 02 = Service Tax)
• The applicable tax rate (as a percentage)
• The calculated tax amount for that line (unit price × quantity × tax rate)

The invoice-level total tax amount must exactly equal the sum of all per-line tax amounts. LHDN's validation performs this arithmetic check — any rounding discrepancy between per-line calculations and the invoice total will cause rejection.

If multiple tax types apply across different products in the same invoice (e.g. some items are SST-taxable, others are exempt), each must be correctly classified on its own line. You cannot mix different tax treatments into a single line item.

Under Malaysian tax law, all e-invoice records must be retained for a minimum of 7 years and must be retrievable for LHDN audit at any time during that period.

While all validated e-invoices are automatically recorded on the MyInvois platform (LHDN's server), businesses should also maintain their own copies in their accounting system as a backup. Cloud accounting software typically handles archiving automatically.

Buyers are also responsible for retaining copies of all e-invoices they receive — both parties in a transaction carry the retention obligation. Records that cannot be produced during an LHDN audit may result in penalties.

Implementation costs vary significantly depending on several factors:

• Current software: If your accounting software already supports MyInvois API (or offers an affordable add-on), costs are lower. If you need to upgrade or switch software, this is a larger investment.
• Transaction volume: Higher invoice volumes typically justify API integration, which may require professional setup services.
• Data complexity: Businesses with many product categories, multiple tax treatments, or complex legacy data require more extensive field mapping work.
• Training needs: Larger teams or businesses with multiple billing staff require more training time.

Typical cost components include: accounting software MyInvois module fees, implementation professional services, and staff training. Middleware platforms have ongoing subscription fees that should be evaluated carefully.

A free gap assessment can give you a clear picture of exactly what you need — and a fixed-price quote for implementation. Request a free assessment here →

Yes. The MyInvois platform uses government-grade encryption and secure API authentication (OAuth 2.0) for all submissions. LHDN applies digital signatures to all validated invoices, making them tamper-proof after validation.

For your own security, ensure that:

• Your MyInvois API credentials are stored securely in your accounting software — never in plain text or shared documents
• API keys and credentials are rotated periodically or immediately if you suspect compromise
• Only authorised staff have access to your MyInvois account
• Your accounting software provider follows security best practices (data encryption at rest and in transit, regular security patching)

The invoice data submitted to LHDN is used for tax administration purposes under Malaysia's tax laws. Review LHDN's official data privacy documentation for full details on how your data is processed.

The UIN (Unique Identification Number) is a unique alphanumeric code generated and stamped onto every validated e-invoice by LHDN's MyInvois system after successful submission and validation.

Think of it as an official government seal. It confirms that:

• The invoice has been submitted to LHDN
• All required fields passed IRBM validation
• The invoice is on official government record

The UIN appears on the validated invoice alongside a QR code. When a buyer scans the QR code with their phone, it links directly to the official LHDN record for that specific invoice — allowing instant verification of authenticity.

An invoice without a valid UIN is not a legally-recognised e-invoice under Malaysian tax law. It cannot be used to support input tax claims, SST deductions, or audit documentation. You do not generate the UIN yourself — it is issued by LHDN automatically after successful validation.

For B2C (business-to-consumer) transactions — sales to individual end consumers — LHDN allows a simplified approach:

• Consolidated e-invoices: Rather than validating each individual retail sale through MyInvois, businesses may issue a single consolidated e-invoice covering all B2C transactions within a daily or defined period. This significantly reduces the submission volume for high-transaction retail businesses.
• Relaxed buyer details: B2C consolidated invoices do not require the full buyer TIN and registration details needed for B2B invoices.
• Individual B2C invoices on request: If a consumer specifically requests an individual e-invoice for a transaction, the business must issue and validate one through MyInvois.

LHDN's specific rules for B2C — including consolidated invoice thresholds, timing requirements, and what must appear on the consolidated invoice — are available in the official LHDN e-invoicing guidelines. These rules are subject to update, so always check the latest official guidance.

If your business serves a mix of B2B and B2C customers, your e-invoicing system will need to handle both types correctly.

After a seller submits and receives LHDN validation for an e-invoice, the buyer has 72 hours to formally reject it through the MyInvois system for legitimate commercial reasons, such as:

• Incorrect seller or buyer details on the invoice
• Wrong goods or services described
• Incorrect quantities or amounts
• Duplicate invoice for the same transaction
• Invoice issued for a cancelled transaction

If the buyer does not reject within 72 hours, the invoice is permanently accepted and on official LHDN record. Rejections by email or phone do not count — the formal rejection must be submitted through MyInvois.

After the 72-hour window has passed, the only way to correct an error on a validated e-invoice is to issue a Credit Note or Debit Note — which must itself be submitted to and validated through MyInvois, referencing the original invoice's UIN.

Yes. Under the Income Tax Act 1967, businesses that fail to comply with Malaysia's e-invoicing requirements may be subject to penalties, including fines and other enforcement actions by LHDN.

The specific penalty amounts and enforcement approach are governed by LHDN and may evolve as the e-invoicing rollout progresses. LHDN has indicated that initial enforcement will focus on education and supporting compliance, particularly for Phase 4 businesses — but penalties are legally available and will be enforced.

Beyond legal penalties, non-compliant invoices may not be recognised for tax deduction purposes, potentially resulting in disputes and additional tax liabilities. Importantly, buyers who receive non-validated invoices may also be exposed to risk when claiming input tax credits.

The safest approach: implement e-invoicing correctly now. Contact us for a free compliance review →