Release 2026.09.24-R1

Correcting and resubmitting invoices

• When an invoice is in Error or Invalid status, the fields that caused the problem are now marked on the invoice itself, and hovering over a marked field shows the error. You no longer need to read the Activity Trail to find what to correct, though it still keeps the full history.
• Fixed: when you edited an invoice received through the API, Approve & Submit could stay disabled with "Please fill up required fields" even though every required field was filled, until you typed something into the optional Terms field.
• Fixed: resubmitting an invoice could change or remove its Tax Exempted Amount and Tax Exemption Reason even when you had not edited them.
• Fixed: a discount amount captured on an invoice was missing from the invoice edit page, or shown there as 0.

General Public identity

• A document that uses the General Public identity (the general TIN with registration number NA) as its Customer, Supplier or shipping recipient can now be submitted only as a consolidated e-invoice. LHDN rejects this identity on any other document, so JomeInvoice now stops such a document before it is sent, instead of letting it fail at LHDN.
• You can still save these documents as drafts. In a Direct Upload or SFTP file, a row that breaks this rule shows as Conversion Failed.

MSIC Codes

• A workspace can now hold more than one MSIC Code. For invoices you upload as a CSV file, through Direct Upload or SFTP, the MSIC Code on each row is the one submitted to LHDN for that invoice.
• A valid MSIC Code in your file that is not yet saved on the workspace is added to it automatically. A code that is not a valid MSIC Code is rejected with "Validation failed - MSIC Code not found".
• A workspace with a single MSIC Code works exactly as before.

Search and filters

• Search boxes across the app now say which fields they search, so an empty result is easier to interpret.
• Import Log search now finds files by name across all your imports, not only the rows already loaded on screen, and still respects the date range and other filters you have set.
• The Issuers/Branches and Customers filters now have a search box and let you select more than one value. Selected values are listed first, and the filter shows how many you have selected.

Settings, teams and roles

• The Activity Trail now records changes made on the Organisation, Email Notifications, General, Mappings and Direct Upload Mapping settings tabs, showing who made each change and the value before and after. Sensitive values such as credentials are never recorded.
• In Team Settings, admins can now choose which API sources each team's members can see and filter invoices by. This no longer depends on the API Credentials permission in User Roles. A member of several teams sees the sources of all their teams combined, and every existing team keeps access to all API sources until you narrow it.
• A new default role, Editor, is available under Settings → User Role, with the same permissions as the Member role in JomeInvoice V1. Users moved from V1 with the Member role are now given the Editor role.

Emails and notifications

• Emails about an e-invoice request (submitted, completed and rejected) now appear in the Email Log. Choose Requests under Sales in the invoice-type filter to see them. You can search them by receipt number, which is shown in the Invoice column.
• The confirmation email your customers receive after requesting an e-invoice now makes clear that the details shown are the ones they entered.
• Fixed: the confirmation email sent after an e-invoice request showed the receipt date one day early. The same fault could also show the previous day's date in request completed, request rejected, invoice cancellation and new-invoice emails, and is fixed there too.
• Fixed: Bulk Notify Customer emailed at most 200 invoices even when more were selected, and listed invoices by validation date rather than issue date. It now covers every matching invoice, and its invoice and customer counts are accurate.

Request e-invoice form

• Fixed: the public e-invoice request form could fail with a "not authenticated" error, and the request was not saved. Your customers can again submit it without an account.