In mid-2023, Malaysia's Inland Revenue Board (LHDN) began rolling out MyInvois—a mandatory e-Invoice system designed to tighten tax compliance and reduce fraud. If you run a business in Malaysia with annual turnover above a certain threshold, you are no longer optional. Your invoices must flow through the system, and the compliance window has narrowed considerably. The challenge is not the concept—it's the execution. Many SMBs still invoice on spreadsheets or fragmented tools. Retrofitting those workflows to meet LHDN standards, generate compliant e-Invoices, and submit them on time requires clarity on three things: who must comply and by when , what a valid submission looks like , and what actually changes in your day-to-day invoicing . This guide walks you through all three. A note on currency: LHDN rules can shift. This guide reflects the framework as of early 2025. Before you lock in your workflow or tool choice, verify current deadlines and specs with LHDN's official portal or a local tax advisor. Who is in scope and by when? The MyInvois mandate applies in phases, not all at once. The first cohort—large businesses with annual turnover over RM50 million—had to go live in June 2024. That deadline has passed. The second wave is where most SMBs sit: businesses turning over RM25 million to RM50 million annually. If you are in that band, your compliance date is 31 December 2024 (verify this; LHDN has revised dates before). The final phase captures businesses with turnover of RM5 million to RM25 million, with a deadline (as currently communicated) of 30 June 2025 . If you are below RM5 million annual revenue, you are in the voluntary category—no hard deadline, but LHDN is encouraging adoption. If you do adopt, the same rules apply. Action point: Look at your last audited or filed returns. If your annual revenue falls into the RM25–50 million or RM5–25 million bands, mark the deadline on your calendar now. If you are already past the first deadline and haven't complied, reach out to LHDN immediately—penalties for late adoption exist. What exactly is a MyInvois compliant invoice? A MyInvois e-Invoice is not just a PDF sent over email. It is a structured, digitally signed document—generated in XML format, validated against LHDN specs, and either submitted directly or through an intermediary platform. Here's what LHDN requires on every invoice: Unique Invoice Reference Number (IRN): A 24-digit identifier generated by the MyInvois portal or your integration. It's non-negotiable and non-reusable. Digital Signature: Your invoice must be cryptographically signed using a certificate linked to your business. LHDN uses this to verify the invoice hasn't been tampered with. Standard metadata: Supplier details (name, tax ID, address), buyer details (same), invoice date, due date, line items (description, quantity, unit price, amount), GST or SST breakdown, and payment terms. Compliance with XML schema: Your invoicing system must generate output that validates against LHDN's published schema. Rough formatting or missing fields will cause submission rejection. Cancellation or amendment workflow: If you need to void or correct an invoice, MyInvois has a formal process. You cannot just reissue over the top of an old one. The practical implication: you cannot hand-craft these or generate them from a template. You need a system—either LHDN's official MyInvois portal (which is manual and slow for any real volume) or a certified invoicing platform that integrates with MyInvois and handles the signing and submission automatically. The integration path: portal, intermediary, or platform LHDN offers three ways to submit invoices: 1. Direct portal submission You log into the MyInvois website, manually enter or upload invoice data, and LHDN signs and validates it. This works if you issue 5–10 invoices a month. Beyond that, it becomes a bottleneck. Many SMBs start here out of familiarity, then abandon it once volume grows. 2. Intermediary platform (API relay) You use a third-party invoicing or ERP tool (many Malaysian vendors now offer this). That tool handles the XML generation, signing, and submission to MyInvois on your behalf. You see your invoices in your familiar interface, and compliance happens behind the scenes. This is the most common path for SMBs with 50+ invoices per month. The intermediary is responsible for maintaining the API connection to LHDN. 3. Direct API integration Your business integrates directly with LHDN's API. Your invoicing system generates compliant XML, signs it using your digital certificate, and pushes it to LHDN's servers. This requires technical setup and an in-house developer or a vendor partnership. It's rarely worth it for SMBs unless you are issuing hundreds of invoices monthly. For most Malaysian SMBs, path 2 is the pragmatic choice. You need a tool that already holds your invoicing workflow—something that tracks your customers, line items, tax, and payment status—and that tool should have MyInvoi