Malaysia: validation rules
Check the requirements that can stop a Malaysian invoice from reaching an accepted state. Start with the document type and actual seller, buyer and line values.
Check the GETS request
Select Malaysia and the document type in the field reference. The Requirement column shows which GETS fields are mandatory, optional or conditional. In List with sample request, choose the document type and inspect the fields for that selection. Use values from the invoice and the company’s registration records.
A 422 response from Unify lists fields that failed validation. Read each getsPath and message, correct the source data, then send the document again. See Unify errors for the response format.
Check the MyInvois result
After submission, check the document status to confirm whether LHDN accepted the invoice. Do not treat the request’s HTTP status alone as the authority’s final result.
LHDN publishes its document validation rules. The checks cover the document structure and core fields, taxpayer identities, references on credit and debit notes, codes, duplicate documents, currency and exchange rates. Check the current MyInvois code tables when a code is rejected.
If LHDN rejects a document, use the returned reason to correct the source invoice. For a credit or debit note, check that its referenced invoice is valid in MyInvois. For a taxpayer error, confirm the identifiers against the company’s registration records. Do not replace a rejected identifier with a guessed value.
Last updated