Loading…
A MyInvois rejection is rarely dramatic. It is usually one field — a buyer TIN that does not match, a tax total that is off by a sen — and you find out after the document has gone, with a clock running on the correction. UrusHQ checks what it can check locally first.
Production submission remains unavailable until the approved LHDN credential and signing workflow are configured. We state that plainly rather than implying live clearance you do not have.
Affected Field
Contact Record
Illustrative interface — not live customer data
Under Malaysia’s e-invoicing regime a rejected document has to be corrected within a limited window, and the clock does not care that the person who raised the invoice is on leave. The practical problem for a finance team is not the correction itself — it is finding out in time, and knowing which field to fix without reading a raw API error.
UrusHQ surfaces the LHDN error code, the specific field it applies to, and the time left to remediate, in that order. Where your own contact record already holds a different value for the failing field, that value is shown next to the rejected one so the correction is a decision rather than an investigation.
Document structure and tax totals are checked locally before anything is submitted, so the errors that are cheapest to catch are caught first and for free. External TIN and BRN verification is a different class of check: it is shown only when an approved live integration actually returns evidence, never asserted on our own authority.
Draft through validated, plus rejected, retry pending, cancelled and externally cleared. Sandbox is tracked as its own state and never counts toward your clearance rate — a test document inflating a compliance metric is how a team convinces itself it is ready when it is not.
Self-billed and consolidated workflows carry their own statutory scope, thresholds and deadlines. They remain gated until those are approved, because getting a self-billed obligation wrong is a compliance exposure rather than an inconvenience.
When production clearance is enabled, the provider UUID, each status change and any resulting accounting reversal are stored as durable evidence against the document. That evidence is what you produce if a filing is ever questioned, so it has to survive independently of whichever provider you were using at the time.
The corollary is a rule we hold to strictly: UrusHQ will not invent a clearance result. If LHDN has not cleared a document, nothing in the interface, the PDF or the API will suggest otherwise — including the validation QR area on the invoice itself, which states plainly that a document has not been cleared rather than displaying a placeholder that looks like one.
Cleared documents post into the same accounts your trial balance reads, so compliance and bookkeeping are one workflow rather than two systems reconciled by hand.