Malaysia · LHDN MyInvois
Malaysia MyInvois E-Invoicing Integration
Connect your ERP, accounting or POS system directly to LHDN's MyInvois API. We handle UBL 2.1 document generation, digital signatures, submission, validation status, cancellations and consolidated e-invoices, with no double entry in the portal.
Who must comply with Malaysia e-invoicing?
Malaysia's Inland Revenue Board (LHDN, also known as IRBM) introduced e-invoicing in phases based on annual turnover or revenue, starting with the largest taxpayers and extending to smaller businesses, with thresholds and exemptions set in LHDN guidance.
E-invoicing applies to transactions with businesses (B2B), individuals (B2C) and government (B2G), including cross-border transactions and self-billed scenarios. Check the LHDN e-Invoice page for the current phase schedule, any exemption thresholds and the latest guidelines before planning dates.
How does MyInvois validation work?
Malaysia uses a validation model, a form of continuous transaction control:
- Your system creates the e-invoice and submits it to MyInvois via portal or API.
- LHDN validates it in near real time and returns a Unique Identifier Number (UIN) plus validation details.
- The supplier shares the validated e-invoice with the buyer, including a QR code that links to the record on MyInvois.
- Within a limited window after validation, the buyer can request rejection or the supplier can cancel. After that, corrections use credit, debit or refund notes.
- Definition: Consolidated e-invoice
- A single MyInvois e-invoice summarising multiple transactions where buyers did not request individual e-invoices, submitted within the period set by LHDN.
What are the MyInvois technical requirements?
- Document structure: UBL 2.1, submitted as XML or JSON.
- Digital signature using a certificate from an approved certificate authority.
- Authentication: OAuth 2.0 client credentials for the taxpayer system or intermediary.
- Mandatory fields including supplier and buyer TIN, registration numbers, SST registration where applicable, MSIC code, business activity description, classification codes, tax type and amounts.
- Document types: invoice, credit note, debit note, refund note, and self-billed versions of each.
- Retention of validated documents and responses.
How does Co-Mate integrate your ERP with MyInvois?
- Extract posted documents from your ERP or POS.
- Map and validate against MyInvois rules, including TIN checks through the API.
- Sign and submit in batches, with queues and retry logic.
- Poll status and write back the UIN, validation date, QR link and any errors.
- Consolidate eligible B2C transactions on schedule, with review before submission.
- Notify finance users of rejections and cancellations requiring action.
Which ERPs and billing systems do we support for Malaysia?
- SAP Business One
- Microsoft Dynamics 365
- Oracle NetSuite
- Odoo
- ERPNext
- Zoho Books
- Tally
- QuickBooks
- Xero
- Sage
- Custom PHP / .NET / Java
- POS systems
Don't see yours? If it stores invoices in a database or exposes an API, export or webhook, we can connect it. See all ERP e-invoicing integrations.
Implementation steps
A predictable path from first call to live, monitored e-invoicing.
- 1
Phase & scope check
Confirm your implementation phase under LHDN guidance, your taxpayer details and which transactions need individual or consolidated e-invoices.
- 2
Field mapping
Map ERP data to the MyInvois document structure: TIN, BRN, SST registration, MSIC codes, classification codes, tax types and currencies.
- 3
API connector build
Build OAuth authentication, UBL 2.1 XML or JSON generation, digital signature, document submission and status polling against the MyInvois API.
- 4
Sandbox testing
Test invoices, credit notes, debit notes, refund notes, self-billed documents and consolidated B2C submissions in the MyInvois sandbox.
- 5
Production go-live
Register the integration in the MyInvois portal, switch on production credentials and monitor the first cycles closely.
- 6
Run & support
Handle rejections and cancellations within the allowed window, store validated documents and QR links, and apply SDK updates.
Common Malaysia e-invoicing challenges and how we handle them
| Challenge | Why it matters | How we handle it |
|---|---|---|
| Buyer TIN collection | Individual e-invoices need buyer TIN and identification details. | TIN validation via the MyInvois API at customer setup and clear fallbacks for general public buyers. |
| Classification and MSIC codes | Each line and supplier needs the right codes or validation fails. | Mapping tables maintained in the connector, editable by finance. |
| Consolidated B2C submissions | Aggregation rules and timing are easy to get wrong. | Scheduled consolidation jobs with review before submission. |
| 72-hour cancellation window | After the window, corrections need notes, not cancellation. | Connector enforces the window and guides users to the right document type. |
| API rate limits | High-volume batches can be throttled. | Batching, queues and back-off aligned with published limits. |
Malaysia e-invoicing FAQ
What is MyInvois?
Should I use the MyInvois Portal or API integration?
What formats does the MyInvois API accept?
What is a consolidated e-invoice?
Can an e-invoice be cancelled in MyInvois?
Which ERPs can you integrate with MyInvois?
Do I need a digital certificate for MyInvois API integration?
Is Co-Mate an LHDN-approved provider?
Official sources
Last reviewed:
E-invoicing rules, timelines and technical specifications change often. This page summarises the official guidance as we understood it on the review date. Always confirm obligations and dates with the tax authority or your tax adviser before acting. Co-Mate provides integration engineering, not tax or legal advice.
Related e-invoicing guides
- E-invoicing integration hubAll countries, models and our approach in one place.
- ERP e-invoicing integrationsSAP Business One, Dynamics, NetSuite, Odoo, Zoho, Tally and more.
- Philippines BIR e-invoicingBIR Electronic Invoicing System integration.
- Saudi Arabia (ZATCA) e-invoicingAnother UBL 2.1 clearance-style regime.
- Integrate e-invoicing with your existing ERPArchitecture options and pitfalls.