17/3/2026

Bug-Fixes

#1 Cancellation Flow for Validated Request e-Invoices

Overview
We have implemented a permanent fix for the cancellation flow of Request e-Invoices after validation. The system now correctly handles canceled invoices by moving them back to the consolidation draft stage, allowing users to resubmit with updated information.

What Has Changed
Cancellation Flow for Validated Request e-Invoices Improved:

• The system now properly handles invoices that are canceled after being validated through the request process.

• When a validated request e-invoice is canceled, it will now be moved back to Consolidation → Unprocessed Draft.

• This allows users to update and resubmit the invoice with correct information.

• Prevents subsequent requests from encountering invalid states or submission errors.

Previously, canceled invoices could lead to inconsistent states, causing errors in future submissions.

Where This Is Reflected in the Portal
This fix applies to the Request e-Invoice module and Consolidation module.

When users:

• Cancel a validated request e-invoice

The system will:

• Automatically move the invoice to Consolidation → Unprocessed Draft

Allow the invoice to be edited and resubmitted

Impact
Improves system consistency after cancellation, reduces submission errors in subsequent requests, and provides users with a clearer and more reliable workflow for correcting and resubmitting invoices.

#2 Block Resubmission of Canceled Invoices Beyond 72 Hour

Overview
We have implemented a validation enhancement to prevent invoices from being submitted to LHDN if they were previously canceled and have exceeded the 72-hour cancellation window. This ensures compliance with LHDN rules and avoids invoices getting stuck in the submission queue.

What Has Changed
Post-Cancellation 72-Hour Validation Added

The system now performs an additional check before submitting invoices to LHDN:

• If an invoice has been canceled, the system will verify whether the cancellation has exceeded 72 hours.

If the cancellation is beyond 72 hours, the system will:

• Block the submission to LHDN

• Update the activity trail with an appropriate message

Previously, the system allowed resubmission of such invoices, which caused them to be stuck in the queue as LHDN would reject them.

Where This Is Reflected in the Portal

This validation applies during invoice submission across all channels.

When attempting to resubmit an invoice:

• If the invoice was canceled and exceeds the 72-hour window, submission will be blocked

• The activity trail will reflect the validation message.

Impact
Prevents invalid submissions to LHDN, reduces stuck invoices in the queue, improves system reliability, and ensures better compliance with cancellation rules.

#3 Buyer Validation & Duplicate Detection for API Invoices

Overview

We have implemented an enhancement to improve buyer validation during API invoice submission. This update ensures that duplicate buyer records sharing the same Profile ID no longer result in incorrect buyer information being sent to LHDN or reflected in the generated PDF invoice.

The system now performs stricter validation and uses the correct buyer information from the invoice payload during processing.

What Has Changed

Buyer Validation & Duplicate Detection Improved:

• The system now performs a strict sequential validation to identify buyers using the following fields:
  i. Buyer Email
  ii. Company Name
  iii. Business Registration Number (BRN)
  iv. Tax Identification Number (TIN)

• If a unique buyer cannot be identified after these checks, the invoice will be automatically moved to Error status.

• The following error message will be triggered:
  “A duplicate buyer information found in our system. Please verify the data and contact JomeInvoice Support for further action.”

• The system ensures that only validated and uniquely identified buyer records proceed with submission, using the buyer information from the payload for both LHDN submission and PDF invoice generation.

Previously, multiple buyers sharing the same Profile ID could result in incorrect buyer information being processed and displayed.

Where This Is Reflected in the Portal

This update applies to the Sales → API Invoice submission flow.

When users:

• Submit an invoice via API

The system will:

• Validate buyer records associated with the same Profile ID

• Trigger an error if duplicate buyer records are detected

• Proceed with submission if a valid and unique buyer is identified

• Use the buyer information from the payload for LHDN submission and PDF generation

Impact

• Prevents invoice submission when duplicate buyer records are detected

• Ensures accurate buyer information is sent to LHDN

• Ensures the PDF invoice reflects the correct buyer details from the payload

• Improves buyer data validation and overall system data integrity