Free tool · for developers and integrators
MyInvois JSON checker
Paste the UBL JSON your system sends to LHDN, or open the file, and see what would get it refused or marked Invalid, with the field and the fix for each. It runs in your browser: the document never leaves your computer.
Result
Paste a document and press Check.
These checks catch the mistakes that most often get e-invoices refused. LHDN also checks the TIN against its records, the signature on version 1.1 and its full schema: only its sandbox can confirm those. What LHDN's error codes mean →
Checks follow LHDN's code lists in the MyInvois SDK, the invoice field rules and the e-Invoice Specific Guideline v4.9. The general TIN, phone, email and UTC time rules also come from our own submissions to LHDN's test environment in October 2026. Format checks, not tax advice. Checked on 19 November 2026.
What it checks
| Part | Checks |
|---|---|
| Document | Invoice number, issue date, issue time in UTC ending with Z, document type code, currency code, and on credit, debit and refund notes the original e-invoice's LHDN UUID. |
| Seller and buyer | TIN present, the general TIN pairings behind ERR222, ERR228, ERR236 and ERR237, contact number of at least 8 characters, email format, state and country codes, name, and the seller's MSIC code. |
| Each line | Unit of measure, classification and tax type codes against LHDN's lists, an exemption reason on tax type E, and tax worked out from the rate. |
| Totals | Line amounts add up to the document totals, tax totals match, and the RM10,000 single-sale rule on consolidated and general-TIN e-invoices. |