Malaysia's phased MyInvois mandate under LHDN means every qualifying Sales Invoice now has to be transmitted to a government platform, validated against a strict UBL 2.1 schema, and stamped with a validation link and QR code before it is legally issued. Stock ERPNext v15/v16 produces a perfectly good Sales Invoice DocType and PDF, but it has no concept of MyInvois — no LHDN API client, no UBL mapping for TIN, SST classification codes, MSIC codes or e-invoice type codes, and no way to poll for validation status or handle a rejection. Finance teams end up re-keying every invoice into the MyInvois portal or a spreadsheet, which does not scale past a handful of documents a day and breaks the moment the consolidated B2C deadline arrives.

ECOSIRE builds a dedicated Frappe app that lives inside your ERPNext instance and closes that gap end to end. The app ships a MyInvois Settings single DocType (environment toggle for the LHDN preprod vs production endpoints, client ID/secret, TIN, default classification codes) plus MyInvois Document and MyInvois Log DocTypes that track every submission's UUID, long ID, validation status, and the returned QR/validation-link. A hooks.py doc_events handler on Sales Invoice on_submit builds the UBL 2.1 XML from your invoice, its items, taxes and customer, signs and submits it through the MyInvois API, and stores the response against the invoice — all inside the same transaction boundary so a submission failure surfaces on the document rather than silently.

Technically, the integration is built as a proper Frappe module: whitelisted server-side methods (frappe.whitelist()) handle OAuth2 token acquisition and refresh against the LHDN identity service, UBL generation, submit, cancel and status calls; a scheduler event (scheduler_events in hooks.py) polls MyInvois for documents that are still Submitted and updates them to Valid/Invalid without a human watching. Client scripts add status indicators and a "Submit to MyInvois", "Check Status" and "Cancel e-Invoice" action to the Sales Invoice form. SST tax accounts are mapped to LHDN tax type codes, and a consolidation routine batches non-e-invoice B2C receipts into the monthly consolidated e-invoice that the mandate requires. Everything is permission-gated through a dedicated role profile so only authorized finance users can transmit or cancel.

Because MyInvois behaviour, your chart of accounts, SST setup and item classification are specific to your business, this is a build-to-order engagement, not a marketplace download. After a short scoping call we confirm exact requirements — your entity's TIN/MSIC, tax-code mapping, B2B vs B2C mix, and target LHDN wave — then build against your ERPNext v15 or v16, run UAT on a staging copy connected to the LHDN preprod sandbox, and only cut over to production once your team has validated real documents. Typical delivery is one working week from confirmed scope. You receive the full source code and git repository so you are never locked in.