Skip to content

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.

    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

    PartChecks
    DocumentInvoice 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 buyerTIN 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 lineUnit 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.
    TotalsLine amounts add up to the document totals, tax totals match, and the RM10,000 single-sale rule on consolidated and general-TIN e-invoices.

    Common questions

    Is my e-invoice JSON uploaded anywhere?
    No. The checker runs in your browser. The document you paste or open is read on your own computer and never sent to us or anyone else.
    Does passing this check mean LHDN will accept the e-invoice?
    No. It catches the mistakes that most often get e-invoices refused or marked Invalid: missing or wrong codes, general TIN pairings, phone and email formats, and totals that don't add up. LHDN also checks the TIN against its records, the digital signature on version 1.1 and its full schema, which only a submission to its sandbox can confirm.
    Which format does it read?
    MyInvois UBL 2.1 JSON, the document you send to LHDN's submission API, with values written as arrays of objects carrying an underscore key. XML documents are not checked here.
    Why does the issue time need a Z?
    LHDN takes the issue date and time in UTC, and the time must end with Z, for example 01:30:00Z. Without it the document is refused with an invalid issuance date time format. Malaysian time is 8 hours ahead of UTC, so a sale at 9:30 in the morning is 01:30:00Z.
    Skip the JSON altogether Our e-Invoice platform builds this document for you from your POS, ERP or Excel export, runs these checks on every invoice and resubmits corrected ones for free. See the e-Invoice platform → Try the live demo, no sign-up → Looking for a code? MyInvois code lookup →