e-Invoice field validator for Malaysian SMEs

Every rule this tool checks comes from one place: the LHDN SDK page's Data Structure tables for Invoice v1.0, read on 2026-11-08 — the Mandatory column, the Number of Chars column and the Cardinality column for each element. The tool does not invent rules and it does not add rules of its own. Where the table says “Required” or “Mandatory where applicable”, the wording here follows the table: a required field is absent and the line says so; a conditional field whose trigger is not visible in the file is reported as not evaluated, never as a pass.

What is checked	How the table says it
e-Invoice Type Code, Invoice number, Issue date and Issue time, Invoice currency	Each is 1-1 and mandatory; the type code is 2 characters and must be one of the published e-invoice types (01, 02, …).
Supplier name (300 characters), supplier TIN (14), MSIC code (5), address, phone	Each mandatory, with the table's own length limits; the phone number is 20 characters at most.
Tax subtotals: Tax Amount, Taxable Amount, Tax Category ID	Tax Amount and Tax Category ID are mandatory in every subtotal; Taxable Amount is conditional on a tax exemption (type E).
Each line: description (300 characters), classification, unit price, tax amount, subtotal, quantity	All mandatory per line except quantity; a description longer than 300 characters shows the limit and the actual length.
Buyer: name, TIN, registration number, address, phone	Each mandatory, with the table's own length limits (buyer TIN 14, address line 150).
Supplier SST registration number, Currency Exchange Rate, exemption details	Conditional on the trigger the table names: a type 02 subtotal, a non-MYR currency, an exemption subtotal. No visible trigger, no evaluation.

• Never a verdict. A finding says “the table marks this Mandatory and it is absent from this file”. It never says “LHDN will reject this” and it never computes an acceptance outcome.
• What this does not check is listed on the page and kept there after every run: signature validity, arithmetic between the amounts, whether the issue date is today in UTC, MSIC/classification codes against the full LHDN code lists (only the two code lists shipped here are checked), and the buyer's tax residency.
• Money, dates and numbers are never parsed or recomputed. The validator reads presence, length and code values only, so no amount in the file is ever added, compared or rounded here.
• Elements are matched by local name. A document that uses Cbc:, cbc: or any other prefix for the same namespace reads the same way.
• Party identifiers are told apart by schemeID. The table lists three rules that all point at PartyIdentification/ID; the written TIN, BRN and SST each carry their own schemeID, and each rule reads only its own.
• Every rule is read from the table itself, and the read is recorded on this page with its date, exactly like a rate table. When the table changes, the rules are re-read; nothing on this page asserts a compliance outcome about a file.

Nothing you paste leaves your browser: the page is static JavaScript with no network calls.