Loading…
Keep SAP 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.
Flagged documents are held back from submission — nothing reaches LHDN until it passes.
Bulk documents exported from SAP run through dry-run validation as a batch — flagged documents are held back, not submitted and then rejected.
Every SAP-sourced document is followed 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 whatever format SAP already produces.
UrusHQ does not import SAP — there is no migration path and we won’t pretend otherwise. For an estate this size that is the point: your ledger, your master data and your close stay exactly where they are, and the only thing that changes is that cleared documents come back with an LHDN UUID attached.
Documents are submitted and tracked. UrusHQ never becomes a second set of books competing with SAP.
A dry-run endpoint checks a document against LHDN’s rules and returns the errors without submitting it — safe to wire into a non-production SAP client first.
An LHDN rejection surfaces with its error code and a 72-hour remediation clock, so it can be routed back into SAP rather than found at month end.
How the integration works
Pull invoice data out of SAP 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 — SAP 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. SAP stays your ERP of record and nothing is installed inside it. UrusHQ sits outside SAP as the LHDN MyInvois clearance layer — you export data the way your team already does, and UrusHQ validates, signs, submits and tracks clearance.
Over the REST API — single documents or bulk, with dry-run validation before anything is actually submitted. Built for the volume an SAP estate produces.
Yes. Dry-run validation checks a full batch against LHDN's structural and tax-total rules first, so a flagged document is held back rather than rejected after submission.
It surfaces in UrusHQ with the LHDN error code and a 72-hour remediation clock, so finance knows exactly what to fix and how long they have.
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.