This is one of the most common questions Malaysian SMEs ask before switching systems, so let's answer it plainly. SQL Account generates, validates and submits e-invoices directly to LHDN's MyInvois portal, and is one of the most widely used LHDN-compliant accounting systems in the country. Its developer, E Stream MSC Sdn Bhd, is a registered MyInvois intermediary. If your real question is “will SQL Account keep me compliant with the e-invoicing mandate?” — the answer is yes.
SQL Account e-invoice capability at a glance
| MyInvois submission | Yes — direct integration with LHDN's MyInvois portal |
|---|---|
| Peppol e-invoicing | Yes — supported for cross-border / B2B exchange |
| Intermediary | E Stream MSC Sdn Bhd is a registered MyInvois intermediary |
| Validation & QR | e-invoices are validated by LHDN and return a QR / unique identifier |
| Consolidated e-invoices | Supported for B2C where individual e-invoices aren't required |
What “LHDN approved” actually means
There's a common misconception that LHDN hands out a single “approved software” badge and you just look for the sticker. In practice, e-invoice compliance is about whether your software can connect to MyInvois and produce valid, accepted e-invoices — not a one-off certification. SQL Account does exactly this through direct API integration with MyInvois, plus Peppol support. So when people ask if it's “approved,” the honest and useful answer is: it is fully integrated and compliant, and used by hundreds of thousands of Malaysian businesses to meet the mandate.
How e-invoicing works in SQL Account
Inside SQL Account, an e-invoice is created from your normal sales document, validated against LHDN's rules, and submitted to MyInvois — which returns a validation and QR code you can share with your customer. It handles customer TIN capture, consolidated e-invoices for B2C, and Peppol for cross-border exchange. The point is that it fits into the invoicing you already do, rather than being a separate portal you have to key everything into twice.
The intermediary detail worth knowing
For SQL Account users, the software's developer acts as the registered intermediary: E Stream MSC Sdn Bhd (intermediary TIN C24050894070, BRN 200801024110). That means you don't need to bolt on a separate third-party middleware to talk to MyInvois — the pipeline is built in.
Who has to comply, and when
Malaysia's e-invoicing mandate rolls out in stages by annual turnover. Businesses in the RM1–5 million band became mandatory from 1 July 2026, with the smallest businesses phasing in afterwards. For the full deadline timeline and a readiness checklist, see our Klang Valley e-invoice guide.
Get SQL Account e-invoice ready
We'll configure MyInvois in your SQL Account, handle TINs and consolidated e-invoices, and train your team — so your first real e-invoice goes out clean.
Related guides
Frequently asked questions
Is SQL Account LHDN e-invoice compliant?
Yes. SQL Account generates, validates and submits e-invoices directly to LHDN's MyInvois portal, and is one of the most widely used compliant accounting systems in Malaysia.
Does SQL Account connect to MyInvois directly?
Yes — it integrates directly with MyInvois via API, so e-invoices are submitted and validated from within SQL Account rather than through a separate portal.
Does SQL Account support Peppol?
Yes. Alongside MyInvois, SQL Account supports Peppol e-invoicing for cross-border and B2B document exchange.
Do I need separate middleware or an intermediary?
No. SQL Account's developer, E Stream MSC Sdn Bhd, is a registered MyInvois intermediary, so the connection to LHDN is built in — you don't need a separate third-party bridge.
How do I get SQL Account set up for e-invoicing?
As a Klang Valley SQL dealer, we configure MyInvois in your SQL Account, set up TIN handling and consolidated e-invoices, and train your team. Book a free readiness check and we'll get you submission-ready.