What is LHDN MyInvois? A plain guide
Key takeaways
- An e-Invoice is a structured, machine-readable record of a transaction that LHDN validates in near real time — not a PDF or scanned image.
- MyInvois is LHDN's platform and API for submitting, validating, and storing e-Invoices. Malaysia uses the UBL 2.1 format.
- The lifecycle: create the invoice, validate the fields, generate UBL 2.1 XML, submit to MyInvois, receive validation and a unique identifier, then share the validated invoice (with QR) with your buyer.
- You can submit via the free MyInvois portal (manual), through accounting software, or via the API/middleware — the right choice depends on your volume and whether you want automation.
If you've heard you need to “do e-Invoice” for LHDN but aren't sure what that actually means, this is the plain-language version: what an e-Invoice is, what MyInvois is, and what happens between creating an invoice and it being accepted.
What is an e-Invoice?
An e-Invoice is a structured, machine-readable record of a sale or purchase — issued, validated, and stored digitally. The key word is structured: unlike a PDF or a scanned paper invoice, an e-Invoice is data in a defined format that software (and LHDN) can read and check automatically. That's what lets LHDN validate it in near real time and confirm it's legitimate.
What is MyInvois?
MyInvois is LHDN's (HASiL's) e-Invoicing system — the platform and API that receives your e-Invoices, validates them against the rules, assigns each a unique identifier, and stores them. Malaysia's e-Invoices use the UBL 2.1 format (Universal Business Language), an international XML standard for business documents. You don't have to write UBL by hand — software generates it — but it's the format MyInvois expects.
How e-Invoice submission works, step by step
- 1Create the invoice in plain business terms — buyer, line items, amounts, tax, and the required LHDN fields.
- 2Validate the fields against LHDN's rules, so errors are caught before submission rather than after a rejection.
- 3Generate the UBL 2.1 XML — the structured format MyInvois requires (done for you by software).
- 4Submit to the MyInvois API (sandbox for testing, or production for live invoices).
- 5Receive validation: LHDN checks the document and, if it passes, assigns a unique identifier number (UIN) and a validation timestamp.
- 6Share the validated e-Invoice with your buyer — typically as a visual PDF that carries a QR code linking back to the validated record.
Where the effort actually is
The hard parts aren't “making an invoice” — they're the LHDN-specific bits: correct field validation, UBL 2.1 generation, OAuth authentication to the API, and polling for the accepted/rejected result. Software exists precisely to hide those steps so you work in plain business terms.
The MyInvois document types
MyInvois isn't only invoices. The standard covers a family of documents — invoice, credit note, debit note, and refund note — plus self-billed versions of each (used when the buyer issues the document on the supplier's behalf). Each has its own rules; choosing the right type is part of getting a submission accepted.
The ways to submit an e-Invoice
- MyInvois portal — LHDN's free web portal. You key invoices in by hand. Fine for very low volume; slow and error-prone once you have real volume.
- Accounting software — if your accounting system supports LHDN e-Invoice, it can submit from inside your normal invoicing flow.
- API or middleware — a REST API (or a tool that wraps it) submits e-Invoices programmatically from your existing systems, which is how higher-volume businesses and software vendors handle it.
This is general information, not tax advice
This primer explains how the system works in general terms. For your specific obligations — which documents you must issue, deadlines, and field requirements — refer to the current e-Invoice guidelines on hasil.gov.my or consult your tax adviser.
Is an e-Invoice just a PDF invoice?
No. A PDF is an image of an invoice; an e-Invoice is structured data in a defined format (UBL 2.1) that LHDN can validate automatically. A validated e-Invoice is usually shared as a visual PDF with a QR code, but the underlying record is structured data, not the PDF.
What format does MyInvois use?
Malaysia's MyInvois uses UBL 2.1, an international XML standard for business documents. Software generates the UBL for you — you don't need to write XML by hand.
Do I have to use the MyInvois portal?
No. The free portal is one option (manual entry), but you can also submit through supported accounting software or via the MyInvois API / middleware. Higher-volume businesses generally automate rather than key invoices in by hand.
What is a UIN in e-Invoicing?
When LHDN validates your e-Invoice, it assigns a unique identifier (a validation reference) and a timestamp confirming the document is accepted. That's what makes the e-Invoice official and traceable.
Skip the XML and the portal
MyInvois Bridge turns a plain invoice into a validated LHDN e-Invoice — UBL 2.1 generated, submitted, and tracked, with the accepted/rejected reason shown clearly. 14-day free trial.