From August 15, 2026, MyInvois enforces strict formatting on several invoice fields: dates must be YYYY-MM-DD (no more "N/A"), and fields like bank account number, invoice code, payment terms, and incoterms get hard character limits. Non-compliant submissions may fail. UPDATE (19 Aug 2026): these checks went live in the MyInvois production environment on 15 August 2026 — they are active now, not upcoming. Two further rules to watch: State Code 17 (Not Applicable) may only be used on consolidated e-invoices issued in Malaysia or on transactions outside Malaysia, and scientific notation is rejected in every amount field (a total exported as 1E3 instead of 1000 will fail). This mostly affects spreadsheet or custom-built invoice generation.
What to do
1
Confirm your invoicing software has been updated for the new field limits
2
Test a sample submission in the MyInvois sandbox before Aug 15 if you self-integrate
3
Review the full field list in the official SDK release notes
Risk if ignored: Failed submissions from Aug 15 for non-conforming field formats.
Sources: LHDN MyInvois SDK release notes (official) · HASiL MyInvois SDK 1.0 Release Notes · Advintek — MyInvois SDK Update: State Code 17 Rules
✓ Verified against sources on 2026-08-19 · updated when the regulation changes