LHDN MyInvois-compliant e-invoicing built into your Business Central, covering the phased Malaysian mandate with UBL 2.1 / Peppol PINT-MY, API clearance, self-billed and consolidated invoices, TIN validation, and QR codes. One-time license from $499.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

LHDN MyInvois-compliant e-invoicing built into your Business Central, covering the phased Malaysian mandate with UBL 2.1 / Peppol PINT-MY, API clearance, self-billed and consolidated invoices, TIN validation, and QR codes.
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
This is a build-to-order AL extension that brings full LHDN MyInvois compliance into your existing Microsoft Dynamics 365 Business Central environment. ECOSIRE designs, builds, installs, and supports it as a per-tenant extension on your BC online (or on-premises) tenant — there is no instant AppSource download. You buy the build; we deliver a working, tested extension wired into your posting and document flows.
MyInvois API submission with document validation and clearance, returning the LHDN Unique Identifier and submission status written back to Business Central
UBL 2.1 document generation mapped to the LHDN MyInvois data model, with Peppol PINT-MY profile support for interoperability
Self-billed e-invoice support for foreign suppliers and applicable transaction types, generated from posted purchase documents
Consolidated e-invoice support for aggregated B2C sales, batched and submitted within the LHDN monthly window
TIN, BRN, MyKad/passport, SST registration, and MSIC code validation on supplier and buyer records before submission
LHDN QR code capture and a human-readable, QR-coded visual invoice (PDF) for sharing with buyers
The extension hooks into Business Central's sales and purchase posting routines through AL event subscribers, so when you post a Posted Sales Invoice, Credit Memo, or self-billed purchase document, it generates a compliant UBL 2.1 document mapped to the LHDN MyInvois data model with Peppol PINT-MY support. Documents are submitted to the MyInvois API for validation and clearance; the returned Unique Identifier, validation status, and the LHDN QR code are written back onto table extensions and surfaced on page extensions of your invoice cards and list pages.
It covers the realities of the phased Malaysian mandate: standard B2B invoices, self-billed e-invoices for foreign suppliers and specific transaction types, and consolidated e-invoices for aggregated B2C sales submitted within the monthly window. Supplier and buyer TIN, BRN/MyKad/passport identifiers, SST registration, and MSIC code fields are validated before submission to reduce rejections.
Submission runs through the BC Job Queue for ret[ries and batch processing, with full status tracking, error capture, and resubmission from a dedicated MyInvois management page. A QR-coded, human-readable visual invoice (PDF) is produced for sharing with buyers. Permission sets, telemetry, and an audit trail of every API call are included. We scope to your CoA, document types, and which mandate phase your turnover places you in.
Faces an LHDN e-invoice phase deadline tied to annual turnover and needs posted invoices cleared through MyInvois without disrupting the existing Business Central posting workflow.
Owns the BC tenant and wants a clean per-tenant extension with proper permission sets, Job Queue automation, telemetry, and an audit trail — not brittle one-off customizations.
Supports Malaysian clients and needs a reliable, supported MyInvois extension covering self-billed and consolidated scenarios so submissions clear LHDN validation the first time.
Achetez la licence sur ecosire.com et téléchargez le module ZIP Malaysia MyInvois (LHDN) E-Invoicing for Business Central depuis le tableau de bord de votre compte.
Extrayez le ZIP dans votre dossier de modules complémentaires personnalisés Odoo sur le serveur (ou téléchargez-le via Applications > Installer à partir du fichier sur Odoo.sh / runbot).
Activez le mode développeur, ouvrez les applications, cliquez sur Mettre à jour la liste des applications, recherchez Malaysia MyInvois (LHDN) E-Invoicing for Business Central et appuyez sur Installer.
Ouvrez le nouveau menu, collez votre clé de licence ECOSIRE, connectez toutes les informations d'identification externes (Shopify, Amazon, Stripe, etc.) et enregistrez.
Exécutez le test de connexion intégré, synchronisez vos 10 premiers enregistrements et planifiez le cron récurrent. Contactez le support si quelque chose échoue.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| LHDN MyInvois API submission, validation and clearance | ||||
| UBL 2.1 / Peppol PINT-MY document generation | ||||
| Self-billed and consolidated e-invoice scenarios | ||||
| Built, installed and supported on your tenant by the vendor | ||||
| Scoped to your Chart of Accounts, document types and mandate phase | ||||
| Job Queue automation, retry, permission sets and audit trail | ||||
| Ongoing maintenance for evolving LHDN / Peppol rules | ||||
| QR-coded visual invoice (PDF) aligned to your branding |
This is build-to-order, not an instant AppSource install. After a short scoping call we typically deliver in about 2 to 4 weeks depending on your document types, mandate phase, and whether self-billed and consolidated scenarios are in scope. ECOSIRE builds the AL extension, installs it as a per-tenant extension on your sandbox, validates it against the LHDN MyInvois pre-production environment, then cuts over to production with you.
The one-time build includes a hypercare period after go-live for fixes and adjustments. LHDN and Peppol PINT-MY rules evolve through the phased mandate, so we offer an optional ongoing support and maintenance arrangement that covers MyInvois API changes, schema updates, and Business Central version upgrades. We discuss the maintenance option during scoping so you are never left non-compliant after a regulatory change.
Yes. The extension is built in AL and installed as a per-tenant extension, which works on Business Central online (SaaS) and on-premises or private-hosted deployments. We confirm your exact BC version during scoping and target the build to it, since AppSource-style runtime constraints and event signatures vary by release.
Self-billed e-invoices are generated from posted purchase documents for applicable cases such as foreign suppliers, and consolidated e-invoices aggregate qualifying B2C sales into a single submission within the LHDN monthly window. Both are configured to your transaction patterns during the build and tested in the MyInvois sandbox before production.
Submission runs asynchronously through the Business Central Job Queue with retry on transient failures. Validation errors and LHDN rejections are captured with their messages on a dedicated MyInvois management page, where your team can correct the source data and resubmit. Every API request and response is logged for audit, and cancellation/rejection actions are supported within LHDN's allowed time limits.
No. The extension uses AL event subscribers on the standard sales and purchase posting routines, so your team posts invoices exactly as they do today. E-invoicing fires automatically in the background, and the resulting UUID, status, and QR code appear directly on your existing invoice cards and list pages.
LHDN MyInvois-compliant e-invoicing built into your Business Central, covering the phased Malaysian mandate with UBL 2.1 / Peppol PINT-MY, API clearance, self-billed and consolidated invoices, TIN validation, and QR codes.