Malaysia MyInvois (LHDN) E-Invoicing for Magento 2

核心功能

Real-time MyInvois (LHDN) clearance under the Continuous Transaction Control (CTC) model, submitted on invoice creation via a sales_order_invoice_save_after observer

Full 55-field LHDN schema assembly in both XML and JSON formats through Magento service contracts

LHDN UUID and validation QR code persisted on the cleared invoice and embedded in the invoice PDF and customer email

TIN (Tax Identification Number) validation for both supplier and buyer, with idType/idValue (BRN, NRIC, passport) handling

SST and tax-type classification mapping, plus MSIC and item classification-code assignment per product or category

Credit note and debit note submission referencing the original cleared invoice UUID for refunds and adjustments

OAuth2 client-credentials authentication to the MyInvois API with sandbox/preprod and production endpoint switching

Admin ACL-protected configuration and a submission status grid (Submitted, Valid, Invalid, Cancelled) with raw response inspection

Cron-based retry and status polling for pending or failed submissions, with exponential backoff and audit logging

REST and GraphQL endpoints exposing clearance status, UUID and QR so headless storefronts and ERP systems can read results

Built entirely with di.xml dependency injection and plugins/interceptors — no core class rewrites, upgrade-safe

Multi-store / multi-store-view aware so different legal entities and TINs can submit under separate MyInvois credentials

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Magento 2 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

Malaysia's phased e-invoicing mandate brings RM1m+ turnover merchants into scope from 2026, and every B2B, B2C and self-billed transaction must be cleared through LHDN's MyInvois platform before it is legally valid. Magento Open Source and Adobe Commerce have no native MyInvois support — there is no field for the 55-element LHDN schema, no TIN validation, and nothing that calls the Continuous Transaction Control (CTC) API.

This is a build-to-order Magento 2 extension — not an instant Adobe Commerce Marketplace download. ECOSIRE designs, builds, installs and supports a dedicated module under app/code/Ecosire/MyInvois on your Magento install (Open Source or Adobe Commerce), tuned to your tax setup, store views and order workflow.

The module hooks Magento's invoice lifecycle with an observer on sales_order_invoice_save_after (and optional async queue consumer), assembles the 55-field LHDN document (XML or JSON) via service contracts, and submits it to the MyInvois API for real-time validation under the CTC model. On a cleared response it persists the LHDN UUID and validation QR code, attaches them to the invoice PDF and customer email, and writes the long-id and submission status back to the order. TIN validation for both supplier and buyer, SST / tax-type classification, MSIC code and classification-code mapping, and credit/debit-note handling are all wired in.

Everything follows Magento engineering standards: dependency injection via di.xml, plugins/interceptors over core rewrites, service contracts for the MyInvois client, admin ACL for credentials and a status grid, cron for retry/polling of pending submissions, and full REST/GraphQL coverage so headless and ERP integrations can read clearance status. You get the source, install help, and an honest delivery lead time — no fabricated marketplace listing, no instant download.

你得到什么

A dedicated Magento 2 module delivered under app/code/Ecosire/MyInvois (composer-installable), with full source code

Installation and configuration on your Magento Open Source or Adobe Commerce environment (staging first, then production)

MyInvois sandbox/preprod onboarding and end-to-end clearance testing against your real tax and order setup

Admin configuration of credentials, supplier TIN/MSIC, SST classification and per-product classification-code mapping

REST/GraphQL clearance-status endpoints documented for your headless or ERP integration team

Technical handover documentation plus a defined warranty/support window and update path

这是给谁的

Malaysian Magento merchant in mandate scope

A RM1m+ turnover online retailer brought into the MyInvois mandate from 2026 who needs every Magento invoice cleared by LHDN automatically, without re-keying into the MyInvois portal.

Finance / tax compliance lead

The controller or accountant responsible for SST and LHDN compliance who needs auditable proof of clearance — UUID, validation QR and submission status — tied to each Magento order and invoice.

Magento developer or systems integrator

An in-house or agency engineer who wants an upgrade-safe module using di.xml, plugins and service contracts (no core rewrites) and clean REST/GraphQL hooks to wire MyInvois status into their ERP or headless stack.

Malaysia MyInvois (LHDN) E-Invoicing for Magento 2 如何比较

标准	伊科西尔	定制建造	竞争对手	Magento 2 原生
Real-time MyInvois (LHDN) CTC clearance from Magento invoices	包含	部分支持	部分支持	不包括在内
Full 55-field LHDN schema mapping (XML & JSON)	包含	部分支持	部分支持	不包括在内
UUID + validation QR persisted on invoice, PDF and email	包含	部分支持	部分支持	不包括在内
TIN validation + SST / classification-code mapping	包含	部分支持	部分支持	不包括在内
Tailored to your tax setup, store views and order workflow	包含	包含	不包括在内	不包括在内
Upgrade-safe (di.xml, plugins, service contracts — no core rewrites)	包含	部分支持	部分支持	包含
Installed and supported by the vendor on your environment	包含	不包括在内	不包括在内	不包括在内
Ongoing schema/version updates as LHDN changes the SDK	包含	不包括在内	部分支持	不包括在内
Instant self-service download	不包括在内	不包括在内	包含	包含

关于Malaysia MyInvois (LHDN) E-Invoicing for Magento 2的常见问题

Is this an instant download from the Adobe Commerce Marketplace?

No. This is a build-to-order extension. ECOSIRE builds, installs and supports the module directly on your Magento install. There is no instant Marketplace download — you receive the source code, a managed installation on staging then production, and a defined support window. This lets us tune the 55-field mapping, SST classification and TIN handling to your specific tax setup rather than shipping a generic one-size listing.

How long does delivery take after I order?

Typical lead time is 2 to 4 weeks from kickoff, depending on your Magento version, theme/customizations and whether your MyInvois sandbox credentials are ready. The flow is: requirements and tax-setup review, build and unit testing, installation on your staging environment, end-to-end clearance testing against the MyInvois preprod sandbox, then a supervised production go-live. We confirm a firm date in writing once we've reviewed your environment.

Does it work on both Magento Open Source and Adobe Commerce?

Yes. The module targets the standard Magento 2 framework (Open Source and Adobe Commerce / Cloud) and uses only supported extension points — di.xml dependency injection, plugins/interceptors, observers, service contracts and ACL. It does not rewrite core classes, so it is upgrade-safe. On Adobe Commerce Cloud we follow the read-only filesystem deployment model and submit changes via the standard composer/Git deployment pipeline.

What ongoing support and updates do I get if LHDN changes the schema?

Every build includes a warranty window for defect fixes, plus an optional ongoing support and maintenance plan. Because LHDN iterates the MyInvois SDK and validation rules, the support plan covers schema/version updates (for example new classification codes or field changes), MyInvois API endpoint changes, and Magento security-patch compatibility. You are never left on a frozen version of a regulated integration.

How is invoice clearance actually triggered and stored in Magento?

When a Magento invoice is created, an observer on sales_order_invoice_save_after assembles the LHDN document and submits it to the MyInvois API (synchronously or via an async queue/cron consumer for high volume). On a valid response the module persists the LHDN UUID, long-id and validation QR against the invoice, embeds the QR in the invoice PDF and email, and exposes the status via REST/GraphQL. Failed or pending submissions are retried and polled by cron, with full audit logging visible in the ACL-protected admin grid.

Can it handle refunds, credit notes and self-billed invoices?

Yes. Credit memos in Magento map to LHDN credit notes and reference the original cleared invoice UUID, so adjustments and refunds stay compliant. Debit notes and, where your business model requires it, self-billed and consolidated e-invoices can be configured during the build. The exact document types enabled are scoped to your transaction flows during requirements review.