MyInvois ERP Integration

Informations vérifiées le : 2026-09-23

Échéances et phases

MyInvois portal, API or intermediary — which fits your volume

LHDN's e-Invoice Guideline (Version 4.8, 30 August 2026) gives you two ways to transmit documents: the MyInvois Portal and the MyInvois API. The portal is free, works through MyTax and lets staff key in documents or upload a batch — enough for a firm issuing a few dozen documents a month. The API is a RESTful service that accepts JSON or XML built on UBL 2.1, processes submissions asynchronously and expects your system to poll for the result. Section 2.4 of the guideline lists three API routes: direct integration of your ERP with the MyInvois System, a Peppol service provider, or a non-Peppol technology provider.

An intermediary is a third party you authorise in the portal to act on your behalf. You add it by TIN, business registration number and exact registered name, grant permissions and set a term. It logs in with the "Login as Intermediary System" endpoint using its own client ID and secret, signs with its own digital certificate, and can only see the documents it submitted for you. A group can appoint its own headquarters as intermediary for subsidiaries, which avoids buying a certificate per company.

The practical decision runs on four questions: monthly volume (under fifty documents, use the portal; hundreds, or any POS or subscription volume, use the API), whether you want to hold and renew your own signing certificate, how many legal entities must submit, and whether your ERP already produces clean line-level data — buyer TIN, classification codes, tax type, unit price, tax amount. Direct integration wins when you want the validated UUID and QR link written straight back into your invoice records; an intermediary wins when you would rather not run the signing and retry logic yourself.

The MyInvois API flow step by step

Step one is registration. In the MyInvois Portal (MyTax, then MyInvois, then your taxpayer profile and the Representatives area) you register your ERP by name and receive a client ID and two client secrets with an expiry of up to three years. Sandbox and production are separate systems — preprod.myinvois.hasil.gov.my and preprod-api.myinvois.hasil.gov.my for testing — with their own credentials. An intermediary is added in the same screen and registers its own.

Step two is document mapping. LHDN recognises eight document types: 01 invoice, 02 credit note, 03 debit note, 04 refund note, and 11–14 for their self-billed equivalents. Sales invoices, credit notes and debit notes map cleanly; refund notes and self-billed documents (imports, payments to agents and the other cases in Section 8 of the Specific Guideline) usually need new document types. A consolidated e-invoice is a normal 01 document for the month's receipts and must be submitted within seven calendar days after month end.

Step three is the payload and the digital signature. The SDK defines a JSON convention where every value is wrapped in an underscore key, and an XML variant that needs the usual entity escaping. Documents submitted through the API must be signed in XAdES with SHA-256 and RSA, using an X.509 certificate from a Malaysian certification authority licensed by the MCMC. The certificate profile is specific: the organisation identifier (OID 2.5.4.97) carries your TIN, the serial number carries your BRN, and key usage must include non-repudiation and document signing. A soft certificate (.p12 or .pfx) sits on the ERP server; a roaming certificate lives in the CA's HSM and is called over an API. When a service provider submits for you, the document is signed with the provider's certificate, not yours.

Step four is submission and validation. You call the submit endpoint, receive a submission UID, then poll until each document is reported valid or invalid. A valid document gets a UUID and a long ID; you build the validation link as {envbaseurl}/{uuid}/share/{longid} and render it as the QR code on the PDF. Store the UUID against your own invoice number — every later credit note, debit note or refund note must quote it in the "Original e-Invoice Reference Number" field.

Step five is the 72-hour window. The supplier may cancel a validated e-invoice within 72 hours of validation and reissue it; the buyer may reject it once within the same 72 hours. After that the document is final and every correction is a credit note, debit note or refund note referencing the original UUID, with no time limit on adjustments. Your integration needs a cancel action enabled only inside the window, a listener for buyer rejections, and a rule that a cancelled document is never edited in place.

The RM3 million exemption — a decision table

Test one is turnover. Section 1.6.1(e) of the e-Invoice Guideline exempts taxpayers with annual turnover or revenue of less than RM3 million, measured per year of assessment, and the FAQ says no application or prior approval is needed. Once you reach RM3 million you must implement from 1 January in the second year after that year of assessment — cross the line in 2026 and you start on 1 January 2028.

Test two is ownership. Section 1.6.10 removes the exemption if you have a non-individual shareholder with turnover of at least RM3 million, if you are a subsidiary of a holding company at that level, or if you have a related company or joint venture at that level. LHDN's own example is a RM400,000 subsidiary of a group that already e-invoices: it does not qualify and must implement from 1 July 2026. If any corporate shareholder sits in your cap table, check its turnover before you assume anything.

Test three is whether you are already onboarded. LHDN has answered the question advisers were hedging in early September: the General FAQs updated on 4 September 2026 (questions 17 to 20) say an eligible taxpayer that has already started issuing e-invoices "may discontinue issuing e-Invoices immediately", with no application, or may continue voluntarily. Two things temper that. The exemption is reassessed every year of assessment, so a firm near the line will be back in scope soon, and re-registration, a fresh certificate and re-testing cost more than keeping the flow alive. And large customers may keep asking for validated e-invoices even though the guideline accepts an exempt supplier's ordinary receipt as proof of expense. Our recommendation for a business already onboarded and between RM1 million and RM3 million: keep the credentials and certificate current, decide with your tax agent, and revisit "we are exempt" every year.

What Flowyana does today and what Dictode builds

Flowyana ships the accounting layer this integration needs: the Malaysian sales tax and service tax split in its tax catalogue, invoices, quotations, credit and debit notes, multi-branch operation with per-branch tax registration, a REST API and webhooks. What it does not ship is the e-invoicing layer itself — Flowyana has no MyInvois JSON generation, signing or submission, and it is not on any LHDN list.

Dictode builds the MyInvois integration on top of Flowyana or your existing ERP, typically in 3–6 weeks: document mapping to the eight LHDN types, JSON generation to the SDK schema, XAdES signing with your certificate or through your appointed intermediary, submission with status polling, UUID and QR write-back to the invoice record, 72-hour cancellation and rejection handling, and scheduled consolidated e-invoice runs for the months until 31 December 2027. The same scope applies to systems that are not Flowyana, through a middleware service that reads invoices from SAP Business One, Odoo or a custom application.

Plain words on vendor lists: LHDN does not certify ERPs. Your integration is registered in your own portal as your ERP or your intermediary, under your TIN, and its correctness is proven by validated documents in the sandbox and then production — the evidence we hand over at go-live.

Guides associés

• Cloud ERP Buyer's Guide
• UAE E-Invoicing Mandate

Sources officielles

• LHDN — MyInvois SDK (API, document formats, sandbox, FAQ)
• LHDN — MyInvois SDK: digital signature requirements
• LHDN — e-Invoice General FAQs (updated 4 September 2026)
• LHDN — e-Invoice Guideline Version 4.8 (30 August 2026)
• LHDN — e-Invoice Specific Guideline Version 4.9 (7 September 2026)
• ClearTax Malaysia — e-Invoice implementation phases and relaxation period
• Jomeinvoice — General Guideline v4.8 and the RM3 million exemption

Ce guide est une information générale et non un conseil fiscal ou juridique. Vérifiez les exigences auprès des sources officielles ci-dessous ou de votre conseiller.