All 5 IRBM document types. Phase 2 (1 Jul 2025) and Phase 3 (1 Jan 2026) deadlines. LHDN API integration, X.509 digital signature, UBL 2.1 XML mapping — end-to-end.
IRBM has structured the rollout in three phases by annual turnover. Non-compliance carries financial penalties and, for repeated offences, criminal liability.
Large corporations were the first wave. Mandatory API or MyInvois Portal submission required. LHDN validation and UUID assignment live for this group since August 2024.
Mid-size businesses — including manufacturers, distributors, and service firms above RM25M — must be fully compliant by 1 July 2025. This is the most time-sensitive deadline right now.
All Malaysian businesses regardless of turnover must comply by 1 January 2026. No exemptions remain after this date. Now is the time to begin implementation planning.
Under the Income Tax Act 1967 (as amended), failure to issue a valid e-invoice carries a penalty of RM200 to RM1,000 per invoice. Repeated or wilful non-compliance can result in fines of up to RM20,000, a term of imprisonment, or both. X.509 digital signature and UUID are required on every validated document.
Where does your business fall?
IRBM mandates five distinct e-invoice document types. Each has a specific use case, set of mandatory fields, and the party responsible for issuance. Implementation must cover all five.
Standard commercial invoice for any taxable supply of goods or services between a supplier and a buyer — B2B and B2C.
Issued to reduce the value of a previously validated invoice. Used for returns, discounts granted after invoice validation, or pricing corrections downward.
Issued to increase the value of a previously validated invoice. Used for additional charges, under-billed amounts, or price adjustments upward.
Issued when a validated invoice has been settled and the supplier subsequently refunds part or all of the amount. Distinct from a Credit Note in that payment has already occurred.
Buyer issues the invoice on behalf of the supplier. Applies to specific qualifying transactions: agents and sub-agents, dealers, distributors, payments to foreign suppliers, and other IRBM-defined categories.
Implementation note: Your middleware or ERP integration must be capable of generating, signing, and submitting all five document types. A common implementation gap is handling Credit Notes and Self-Billed Invoices correctly — particularly the UUID cross-reference requirement and buyer-initiated submission flow.
Every validated e-invoice passes through this five-stage flow. Understanding it is the first step to implementing it correctly — and building the rejection and archival handling that most implementations miss.
The invoice (or other document type) is generated with all mandatory IRBM fields populated: Supplier TIN, Buyer TIN, MSIC code (Malaysia Standard Industrial Classification), SST registration number (where applicable), and line-item tax category codes. UBL 2.1 XML schema must be correctly mapped from internal ERP data structures.
The document is signed with an X.509 digital certificate before transmission. There are two submission paths: the LHDN API (programmatic, used by middleware and ERP integrations — recommended for volume) and the MyInvois Portal (manual, web-based — suitable for very small volumes or testing). Most Phase 2 businesses will require API integration.
LHDN validates the document in real time — checking schema compliance, TIN references, tax calculations, and MSIC codes. On successful validation, LHDN assigns a Unique Document Identifier (UUID) and generates a QR code. The LHDN validation timestamp is returned and starts both 72-hour windows simultaneously.
From the LHDN validation timestamp, a 72-hour window opens simultaneously for two actions: (1) the Buyer may formally reject the invoice via LHDN (e.g., wrong amounts, wrong party details); (2) the Supplier may cancel the invoice. After 72 hours, neither action is possible — the invoice is confirmed. Your ERP must monitor rejection status and surface alerts to the relevant team.
If not rejected or cancelled within 72 hours, the invoice is confirmed. Both parties must retain the validated document — including the UUID and QR code — for the IRBM-stipulated archival period. The QR code links to the LHDN verification portal where anyone can verify the invoice's authenticity. Archival must be integrated into your document management workflow.
Every item below reflects work I have personally built, tested, and deployed in production environments — not knowledge drawn from documentation alone.
Certificate embedded into the submission payload prior to LHDN API call. Covers certificate provisioning, signing algorithm configuration, and signature validation handling.
Submit document, get document status, cancel document, and reject document endpoints — all implemented and tested against LHDN's sandbox and production environments.
Internal ERP invoice line items mapped to the IRBM UBL 2.1 schema. Covers namespace handling, extension schema compliance, and all mandatory/conditional field population.
MSIC code lookup table integrated with product/service catalogue in the ERP. Automated assignment at line-item level based on product classification rules.
Buyer-initiated rejection via LHDN portal reflected back into the ERP in near real-time. Supplier cancellation flow with 72-hour enforcement and ERP status synchronisation.
UUID and QR code stored against each invoice record in the ERP. QR verification link embedded in customer-facing invoice PDF. Archival retention policy implemented.
Direct middleware connection to MyInvois. Handles document submission, real-time validation response, UUID/QR retrieval, status polling, rejection detection, and cancellation flows.
Connect SAP, Oracle, Xero, SQL Accounting, or custom internal systems to the e-invoice pipeline. No disruption to existing finance workflows. Covers all 5 document types.
Know exactly where you stand before your compliance deadline. A structured review of your current invoicing stack, data quality, and team readiness — delivered as a ranked action list.
Finance and IT team handoff. Standard operating procedures covering daily submission, error handling, rejection response, and LHDN portal navigation. Includes ongoing advisory support.
Coverage of all five IRBM document types — including the commonly missed Self-Billed Invoice (buyer-issued) flows for agents, dealers, distributors, and foreign suppliers.
Phase 2 deadline is 1 July 2025. First consultation is complimentary — let's identify your gaps and map out your implementation plan.
hello@peppwise.com