Understanding LHDN E-Invoicing Requirements
Malaysian businesses navigating the transition to digital invoicing must first understand the precise LHDN E-Invoicing Requirements they are expected to meet. The Inland Revenue Board has published comprehensive technical and operational guidelines governing how invoices must be generated, formatted, submitted, validated, and retained. These requirements are not optional enhancements — they are legally binding obligations with financial penalties attached to non-compliance.
This article provides a structured breakdown of the mandatory LHDN E-Invoicing Requirements, helping businesses understand exactly what changes they need to make to their invoicing processes and systems. Whether you are in the early stages of planning or approaching your compliance deadline, this guide gives you the factual foundation to act with confidence.
Mandatory Invoice Fields Under LHDN E-Invoicing Requirements
The most fundamental aspect of LHDN E-Invoicing Requirements concerns the data that must appear on every valid invoice. LHDN has defined a set of mandatory fields that every electronic invoice must contain, regardless of the nature of the transaction. Any invoice that omits or incorrectly populates these fields will be rejected by the MyInvois platform.
Core mandatory fields include the seller’s and buyer’s Tax Identification Number (TIN), the seller’s and buyer’s legal name and address, the invoice number, the invoice issue date, a line-by-line description of goods or services supplied, quantities, unit prices, the applicable tax classification and rate, the tax amount per line item, and the total invoice value including tax. Businesses reviewing their current invoice templates against LHDN E-Invoicing Requirements will frequently discover gaps that must be addressed before submission.
Approved Invoice Formats
LHDN E-Invoicing Requirements specify that invoices must be submitted in XML or JSON format, structured according to the schema published on the official MyInvois developer portal. These are machine-readable structured formats designed to enable automated validation. PDF files, Word documents, Excel spreadsheets, and scanned paper invoices are not accepted by the MyInvois platform and cannot fulfil the electronic invoicing obligation.
Businesses that currently issue invoices in PDF or other unstructured formats must either implement software that generates XML or JSON directly, or use a middleware solution that converts their existing invoice data into compliant formats before submission. A Malaysia E-Invoice compliance platform like Advintek handles this conversion automatically, eliminating the need for manual format management.
MyInvois Submission and Validation Requirements
Under LHDN E-Invoicing Requirements, every in-scope invoice must be submitted to the MyInvois platform for validation before it is legally recognised. Submission can be made via the MyInvois API for businesses with integrated systems, or through the MyInvois web portal for lower-volume businesses. In both cases, the platform validates the invoice in real time against the LHDN schema and business rules, returning either a validation confirmation or a rejection with error codes.
A validated invoice receives a Unique Identifier Number (UIN) that must be displayed on the invoice document provided to the buyer. This UIN serves as proof that the invoice has passed Malaysia Tax E-Invoicing validation and is legally recognised by LHDN. Invoices without a UIN cannot be used as the basis for tax deduction or legal accounting recognition.
Buyer Notification Requirements
Once an invoice has been validated through the LHDN E-Invoicing Requirements process, the seller is responsible for ensuring the buyer receives a copy of the validated invoice. This can be done through the MyInvois platform itself, which allows buyers to access validated invoices directly, or through supplementary channels such as email delivery of the validated document. Whichever method is used, the invoice provided to the buyer must include the LHDN-assigned UIN.
The MyInvois Malaysia platform maintains a record of all validated invoices accessible to both parties, ensuring that buyers can verify the authenticity and LHDN-validated status of any invoice they receive.
Credit Note and Debit Note Requirements
LHDN E-Invoicing Requirements extend beyond standard sales invoices to cover credit notes and debit notes as well. When a business needs to adjust a previously validated invoice — for example, due to a pricing error, a return of goods, or a discount applied after invoicing — the adjustment must be made through a validated credit note or debit note submitted via MyInvois.
Credit notes and debit notes must reference the original validated invoice by its UIN, enabling LHDN to maintain a complete and auditable record of all adjustments. Businesses that apply credits or adjustments outside the MyInvois framework risk creating discrepancies between their accounting records and the data visible to LHDN through LHDN Invoice Reporting channels.
Self-Billed Invoice Requirements
A specific category of LHDN E-Invoicing Requirements concerns self-billed invoices. In situations where a supplier is not registered for Malaysian e-invoicing — for example, foreign vendors, individual contractors, or exempt entities — the buyer assumes responsibility for generating and submitting a self-billed invoice on the supplier’s behalf. This ensures that all taxable transactions are captured within the MyInvois system regardless of the supplier’s registration status.
Self-billed invoices must meet all the same mandatory field and format requirements as standard invoices under LHDN E-Invoicing Requirements, and must be submitted and validated through MyInvois in the same way. Businesses with significant numbers of self-billing scenarios should ensure their e-invoicing software supports this invoice type.
Retention and Archiving Requirements
LHDN E-Invoicing Requirements mandate that validated invoices be retained for a minimum of seven years. This retention obligation applies to both the original invoice document and the LHDN validation response, including the UIN assignment confirmation. Businesses must ensure that retained documents are stored securely, remain retrievable on demand, and are protected against tampering or deletion.
Cloud-based archiving solutions that form part of a comprehensive Electronic Invoice Malaysia compliance platform are the most effective approach, providing geographically redundant storage with role-based access controls and search functionality designed for efficient audit response.
Penalties for Failing to Meet LHDN E-Invoicing Requirements
Businesses that fail to meet LHDN E-Invoicing Requirements face a range of regulatory consequences. Financial penalties may be imposed for each non-compliant invoice issued, and businesses with systemic compliance failures face increased audit scrutiny. In severe cases, LHDN may disallow tax deductions claimed on the basis of non-validated invoices, creating significant financial exposure beyond the penalty itself.
Proactive compliance, supported by certified e-invoicing software with full MyInvois integration, is the most effective way to avoid these consequences and maintain a clean compliance record.
Conclusion
The mandatory LHDN E-Invoicing Requirements are comprehensive, technically specific, and legally enforceable. Businesses that understand exactly what is required — from mandatory invoice fields and approved formats through to MyInvois validation, buyer notification, credit note handling, and seven-year archiving — are well-positioned to implement a compliant solution that meets LHDN expectations.
Frequently Asked Questions
What mandatory fields are required under LHDN E-Invoicing Requirements?
Mandatory fields include TINs of both parties, invoice date and number, line item descriptions, tax rates, tax amounts, and invoice totals.
What invoice formats are accepted under LHDN E-Invoicing Requirements?
LHDN accepts XML and JSON formats structured according to the official MyInvois schema; PDF and paper invoices are not accepted.
Are credit notes subject to LHDN E-Invoicing Requirements?
Yes. Credit notes and debit notes must be submitted and validated through MyInvois, referencing the original invoice by its UIN.
What is a self-billed invoice under LHDN E-Invoicing Requirements?
A self-billed invoice is generated by the buyer on behalf of an unregistered supplier and submitted to MyInvois by the buyer.
How long must businesses retain invoices under LHDN E-Invoicing Requirements?
Validated invoices and LHDN validation responses must be retained for a minimum of seven years and remain retrievable on demand.
