Loading…
Keep SQL Accounting exactly as it is. UrusHQ sits in front of it as a regulatory gateway — validating, signing and transmitting your invoices to LHDN MyInvois, and tracking clearance all the way to the UUID. No migration, no re-entering your books.
LHDN Error Code
Recomputed Tax Total
Documents pulled out of SQL Accounting are checked against LHDN's structural and tax-total rules before they're ever submitted.
Follow every SQL Accounting-sourced invoice through to its LHDN-issued clearance UUID. Rejections surface with the LHDN error code and a 72-hour clock.
REST API for single or bulk documents with dry-run validation — it takes the export SQL Accounting already produces.
Clearance is the urgent part, but a workspace with no history is a second set of books. SQL Accounting is a supported migration source, so the records behind your invoices come too — staged and previewed before a single row is written, so you see exactly what lands.
Migrations run in booked slots rather than on demand, so someone is actually watching yours go through. Book a migration slot.
How the integration works
Pull invoice data out of SQL Accounting the same way your finance team does today — no new module, no reconfiguration of the ERP itself.
Push it in over the REST API — single documents or bulk, with dry-run validation before anything is submitted, so a bad document fails on your side rather than at LHDN.
Documents are checked against LHDN's rules before they ever leave, then signed and transmitted to MyInvois for clearance.
Follow each document to its LHDN-issued UUID. A rejection surfaces with the LHDN error code and a 72-hour remediation clock — SQL Accounting stays your books of record throughout.
Every document that clears LHDN writes to a double-entry ledger. Every action writes an append-only audit record.
Data is hosted in the asia-southeast1 region.
A free read-only accountant seat, and cleared documents, journals and payslips remain exportable even if you stop paying.
No card required. Cancel any time — cleared documents, journals and payslips stay exportable even if you stop paying.
Starter
RM59/mo
excl. SST 8%
Growth
RM149/mo
excl. SST 8%
Scale
RM399/mo
excl. SST 8%
No. SQL Accounting stays your accounting system of record. UrusHQ sits alongside it purely as the LHDN MyInvois clearance layer — validating, signing and submitting documents, then tracking each one to its clearance UUID.
Export it the way your team already does, then feed it to UrusHQ over the REST API — single documents or bulk, with dry-run validation before anything is actually submitted.
The rejection surfaces in UrusHQ with the LHDN error code and a 72-hour remediation clock, so you know exactly what to fix and how long you have before it lapses.
No. Your bookkeeper keeps working in SQL Accounting as normal. UrusHQ keeps its own double-entry ledger with an append-only audit record for every clearance action, separate from your SQL Accounting books.
In the asia-southeast1 (Singapore) region.
Cleared documents, journals and payslips stay exportable even after you cancel, and your accountant keeps a free read-only seat.
No migration, no re-entering your books. Connect your export, and UrusHQ validates, signs and tracks every document to clearance.