Loading…
Keep your Oracle ERP 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.
LHDN Clearance UUID
Documents exported from your Oracle system are checked against LHDN's structural and tax-total rules before they're ever submitted.
Follow every Oracle-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 your Oracle environment already produces.
UrusHQ does not import Oracle — 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 Oracle.
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 Oracle client first.
An LHDN rejection surfaces with its error code and a 72-hour remediation clock, so it can be routed back into Oracle rather than found at month end.
How the integration works
Pull invoice data out of Oracle 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 — Oracle 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%
Whichever one you run — E-Business Suite, Fusion Cloud, NetSuite or another Oracle system. The mechanism is the same either way: export the data, feed it to UrusHQ, and UrusHQ handles LHDN MyInvois clearance.
No. Your Oracle system stays your ERP of record. UrusHQ sits outside it purely as the LHDN MyInvois clearance layer — validating, signing, submitting and tracking documents to their clearance UUID.
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.
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.