Connect SQL Account to LHDN MyInvois without rebuilding your stack.
SQL Account is everywhere in Malaysian SMEs — and very few SMEs have spare engineering capacity to bolt on LHDN compliance themselves. The bridge accepts the SQL Account export as-is and runs the LHDN side end to end.
Where SQL Account users hit MyInvois compliance.
- 01
The MyInvois module is sold separately
Most SQL Account installs don't include native MyInvois submission out of the box. The bridge gives you the LHDN integration without you needing to upgrade your SQL Account licence or restructure your invoicing module.
- 02
Bulk historical submissions are painful
Phase 3 SMEs often have a backlog of invoices that should already have been submitted. CSV upload through the bridge handles bulk batches — up to 1,000 rows per file, all validated up front so the rejections don't compound.
- 03
Your accountant works in Excel, not REST
Finance teams shouldn't need to call APIs to be compliant. CSV is a first-class path in the bridge — drop a file, the dashboard validates row by row, you fix what's flagged, then submit.
We pick up where the export stops.
The bridge accepts the SQL Account CSV export shape directly. Map the columns once in the Settings page; re-upload monthly (or daily — there's no penalty for frequency). Every submission lands in your audit log with the LHDN UUID for compliance trails.
Last updated · May 2026
Independent reference. MyInvois is operated by LHDN. We are not affiliated with LHDN.