Release 2026.11.05-R1

Invoices

• Edit Invoice now shows the invoice's stored shipping recipient in Shipping To, with its name, TIN or registration number, address, charges and description. This includes recipients imported by SFTP that are not linked to a saved customer, which previously left Shipping To empty. You can keep the recipient, replace it by picking another customer or branch, or remove it.
• A new edit (pencil) button next to Shipping To, on both Create and Edit Invoice for Sales invoices, lets you change the recipient's details for that document only. On Edit Invoice, when the document is linked to a saved customer, you can also tick Update the saved customer record as well to save the same change to the customer.
• When you save an invoice with a linked shipping recipient, the invoice now keeps its own copy of the recipient's details, so later changes to the saved customer or branch no longer change that invoice. Shipping changes are recorded in the invoice's Activity Trail.

Unit of measurement

• Each workspace now chooses how the unit of measurement on invoice lines is handled. The choice is in Settings → Workspace Settings → Mappings → Unit of Measurement. Users who can manage workspace settings can change it, and other users can see which option is in use.
  • PDF only: the unit is printed on the PDF exactly as you send it, and is not checked or sent to LHDN. Your own abbreviations, such as Ctn, are accepted.
  • Submit to LHDN: the unit is sent to LHDN. It must be an LHDN unit code, an LHDN unit name, or a value you have mapped on the same page. The PDF still prints the unit exactly as you sent it.
• Workspaces that already had unit mappings are set to Submit to LHDN. Every other workspace, and every new workspace, starts on PDF only, so if your workspace had no unit mappings, units on your e-invoices are no longer sent to LHDN. To keep sending them, map any units of your own on the same page, then switch to Submit to LHDN. A change to the setting applies to new documents, and to an existing document when you upload it again or change a unit on it.
• On Submit to LHDN, a line whose unit matches no LHDN unit and no mapping is not submitted. On Direct Upload and SFTP the row appears in Outbound as Validation Failed with the reason, and the API returns an error for that line.
• Fixed: on Direct Upload and SFTP, a row that failed validation could be left out of Outbound, so you could not see what to fix. A failed row with an invoice number now appears as Validation Failed with every reason it failed, including when you upload it again.
• The first column on the Unit of Measurement mapping page is now headed Source UOM.

Customers and suppliers

• Fixed: the Import CSV option on Customers and Suppliers accepted values longer than the template allows, and NRIC numbers shorter than 12 characters. These rows are now rejected with a message naming the field, and the valid rows in the same file are still imported. The limits are:
  • TIN: up to 14 characters
  • Contact number: up to 20 characters
  • Address lines: up to 150 characters each
  • City: up to 50 characters
  • SST registration number: up to 35 characters
  • Tourism tax registration number (Suppliers only): up to 17 characters
  • NRIC: 12 characters
• Fixed: the downloadable Customer and Supplier CSV templates gave guidance that did not match the field rules. The Supplier template now describes the MSIC code as mandatory, the State note in both templates asks for the state code (01–16) or the full state name, the Customer template's SST column is now headed SST, the sample row's typos are corrected and its Address Line 3 is left empty, and the note about adding a branch in column M is removed because the templates have no branch column.

Cancelling e-invoices

• When you cancel more e-invoices at once than LHDN accepts in a minute, JomeInvoice now holds back the extra cancellations and sends them automatically once LHDN accepts more, so every cancellation is still sent. Cancelling a large batch may therefore take longer to complete.