LHDN e-Invoice (MyInvois): what your business system needs

The LHDN e-invoice requirement changes how Malaysian businesses issue invoices. Instead of simply printing or emailing a PDF, each e-invoice is sent to LHDN's MyInvois system, checked, and given a unique reference before it is shared with the buyer. For many SMEs, the real question is not what MyInvois is, but what their business system needs to do to comply without adding hours of manual work. This guide explains the key concepts and helps you choose the right approach.

Implementation phases, turnover thresholds, exemptions and deadlines are set by LHDN and have been revised several times. This guide does not state specific dates or thresholds. Please check the official LHDN website at www.hasil.gov.my and the MyInvois guidelines to confirm which phase applies to your business.

What is an LHDN e-invoice?

An e-invoice is a digital record of a transaction between a supplier and a buyer, in a structured format that LHDN's systems can read. It replaces the traditional paper or PDF invoice as the official record for tax purposes. The same concept covers credit notes, debit notes and refund notes, which adjust an earlier invoice.

The key difference from a normal PDF invoice is validation. An e-invoice is not final until LHDN has checked and accepted it.

How the e-invoice flow works

1. Create. You prepare the invoice with all required fields, either in your own system or on the MyInvois Portal.
2. Submit. The invoice is sent to MyInvois, through the Portal or through an API connection from your system.
3. Validate. MyInvois checks the structure and the data, such as whether tax identification numbers are valid. If something is wrong, the submission is rejected with an error you must fix.
4. Receive the UIN. A validated e-invoice receives a Unique Identifier Number (UIN) from LHDN.
5. Share with the buyer. You share the validated e-invoice with your buyer, including a QR code that links to the record on MyInvois so anyone can verify it.
6. Cancel or reject within the window. LHDN allows a short window after validation in which the supplier can cancel or the buyer can request rejection. After that, changes are made with a credit or debit note.

MyInvois Portal vs API integration

LHDN offers two main ways to submit e-invoices. Both are valid; the right choice depends on your volume and how your business already works.

The MyInvois Portal

The Portal is a free web interface from LHDN. You log in and key in, or upload, invoice details. It suits businesses that issue a small number of invoices a month, such as a consultant who bills a handful of clients.

The drawback is double entry. If you already create invoices in an accounting system or POS, you would need to type each one again into the Portal. That is slow and invites mistakes once volumes rise.

API integration from your business system

With API integration, your ERP, accounting system, POS or online store submits e-invoices to MyInvois automatically when you issue them. The validated UIN and QR code flow back into your system and onto the printed or emailed invoice. API submissions use a digital certificate and the technical formats LHDN specifies.

This suits any business issuing more than a few invoices a day, for example a trading company in Shah Alam sending dozens of delivery orders and invoices daily, or a retail chain with several outlets.

Consolidated e-invoices for retail and F&B

A kopitiam or mini market serving walk-in customers cannot realistically collect a tax number from every buyer of a teh tarik. For transactions where the buyer does not ask for an e-invoice, LHDN's guidelines allow suppliers to issue a consolidated e-invoice summarising those sales over a period, submitted within the time LHDN specifies.

However, if a customer does ask for an individual e-invoice, you must be able to issue one. A practical POS handles both: it groups normal receipts into a consolidated submission and lets customers request their own e-invoice, often by scanning a QR code on the receipt and filling in their details. Note that LHDN restricts consolidation for certain types of transactions and industries, so confirm the current rules for your sector. Our POS buying guide covers this in more detail.

Credit notes, debit notes, refunds and self-billing

Real business is messy. Goods come back, prices are corrected, deposits are refunded. Your system needs to issue:

• Credit notes to reduce the value of a validated invoice, for returns or discounts given after invoicing.
• Debit notes to increase the value, for example additional charges.
• Refund notes where money is returned to the buyer.
• Self-billed e-invoices in certain situations where the buyer issues the e-invoice instead of the supplier, such as some purchases from individuals or foreign suppliers, as defined in LHDN's guidelines.

Each adjustment document must reference the original e-invoice's UIN, so your system has to store that link reliably.

What data your system must hold

Most e-invoice rejections come from missing or wrong master data, not from software bugs. Before you go live, make sure your system can store and send:

• Your own details: Tax Identification Number (TIN), business registration number, SST registration number where applicable, MSIC code and business activity description, address and contact details.
• Buyer details: buyer TIN and registration or identification number, address and contact. LHDN provides general TINs for some cases, such as sales to the general public or foreign buyers.
• Line item details: description, quantity, unit price, classification code, tax type and rate, tax amount, discounts and totals.
• Invoice details: invoice number, date and time, currency and exchange rate if not ringgit, and payment information where relevant.
• Validation results: the UIN, validation date and time, QR code link and status for each document.

Cleaning your customer list now, especially collecting TINs from business customers, will save a great deal of trouble later.

How to choose: Portal, add-on or integrated system

Ask yourself three questions:

1. How many invoices do we issue each month? If it is a handful, the Portal may be enough for now.
2. Where are our invoices created today? If they already live in an accounting system, POS or online store, connecting that system avoids double entry.
3. Are our systems connected to each other? If sales, stock and accounts sit in separate tools, e-invoicing is a good moment to bring them together.

If you are choosing a new system, check that it supports MyInvois API submission, consolidated e-invoices, credit and debit notes, self-billing where relevant, error handling and the ability to update when LHDN revises its specifications. Ask to see a test submission in LHDN's sandbox environment before you sign.

At Syncolink, our ERP system, POS system and online stores can submit e-invoices to MyInvois directly, alongside SST handling. If you already have a system you like, we can often connect it instead of replacing it.

Common mistakes to avoid

Businesses often leave e-invoicing until the last few weeks, then discover their customer records have no TINs and their item list has no classification codes. Others pick the Portal to save money, only to find staff spending hours each week retyping invoices. Start with your data, be realistic about volume, and give yourself time to test.

Getting ready: a short checklist

• Confirm your implementation phase on the official LHDN site.
• Register for MyInvois and decide who in your company manages access.
• Collect and verify TINs for your regular business customers and suppliers.
• Confirm your MSIC code and the classification codes for your products or services.
• Decide on Portal or API, and test in the sandbox before going live.
• Train staff on what to do when a submission is rejected.
• Agree how consolidated and self-billed e-invoices will be handled.

E-invoicing is a compliance requirement, but done well it is also an opportunity: cleaner data, faster invoicing and fewer disputes. The key is a system that does the submission for you, so your team keeps selling instead of retyping invoices.

Frequently asked questions