If you’re rolling out Malaysia’s e-Invoicing using Odoo 17 and encountering the following blocking error messages right after clicking “Send to MyInvois,” you’re not alone:
These errors stop your XML invoice payload from reaching the LHDN (Malaysian tax authority) and can be frustrating if you don’t know where to start.
Classification is invalid:
Every product or invoice line must include a valid classification code from the official MyInvois classification list, which ranges from 001 to 045. If the product lacks this code, or the code isn’t correctly included in the XML, MyInvois will reject the invoice with this error.
LineItem_ItemPriceExtension_Amount is invalid:
This value represents the net amount of each invoice line after discounts but before taxes. If the related XML tag <cac:ItemPriceExtension> is missing or contains the wrong subtotal value, validation will fail.
IdValue is invalid:
Every party on the invoice—whether customer or supplier—must have a valid Tax Identification Number (TIN) and a properly formatted secondary identifier (like NRIC, BRN, or Passport number). Missing or malformed identifiers cause this error.
To resolve these errors and ensure seamless MyInvois submissions from Odoo:
With these safeguards in place, Odoo generates valid UBL XML files that pass LHDN’s rigorous validations without manual XML edits.
Dealing with these kinds of validation errors can delay your compliance and frustrate your finance team. Our experts specialize in diagnosing and hardening Odoo e-Invoicing flows tailored to Malaysian regulations. Reach out for a consultation, and let us ensure every XML you send to MyInvois is accepted the first time.