12/3/2026

Bug-Fixes

#1 72-Hour Issued Date Validation Now Respects Bypass Setting

Overview
We have resolved an issue where the 72-hour Issued Date validation was still being enforced even when the 72-hour bypass setting was enabled. The system now correctly respects the configuration and allows invoice submission beyond the 72-hour limit when the bypass is turned on.

What Has Changed
72-Hour Validation Logic Corrected:

• The validation logic has been updated to properly reference the 72-hour bypass toggle.

• When the 72-hour bypass setting is enabled, the system will no longer enforce the 72-hour Issued Date restriction during invoice creation or submission.

• This correction ensures that users can successfully submit invoices with an Issued Date exceeding 72 hours when the bypass configuration is active.

  Where This Is Reflected in the Portal
  This fix applies across all invoice submission methods:

• Manual invoice creation

• File upload

• SFTP submissions

• API submissions

When the 72-hour bypass setting is enabled, the system will allow invoices to be created or submitted regardless of the Issued Date exceeding 72 hours.

Impact
Ensures the system configuration works as intended, prevents unnecessary submission blocks for users with the bypass enabled, and improves reliability across all invoice submission channels.

#2 Duplicate BRN Validation Blocking New Workspace Onboarding

Overview
We have resolved an issue where new onboarding clients were unable to create a workspace due to their Business Registration Number (BRN) already existing in the system under another workspace. The system logic has been updated to prevent unnecessary blocking during workspace creation.

What Has Changed
Duplicate BRN Validation Logic Updated:
- The workspace creation validation has been improved to prevent legitimate onboarding clients from being blocked when a BRN already exists in another workspace.

Previously, the system could prevent new clients from completing the onboarding process if the same BRN was already associated with an existing account. This behavior has now been corrected.

Where This Is Reflected in the Portal
This fix applies during the new workspace onboarding and account creation process.

When a new client creates a workspace:
- The system will no longer incorrectly block the process due to an existing BRN in another workspace.
- Users will be able to proceed with onboarding successfully.

Impact
Ensures a smoother onboarding experience for new clients, prevents unnecessary account creation failures, and reduces support cases related to duplicate BRN validation during workspace setup.

#3 Improved Buyer Validation and Duplicate Detection for API Invoice Submissions

Overview
We have resolved an issue where multiple buyers sharing the same Profile ID could cause incorrect buyer information to be sent to LHDN and reflected in the generated PDF invoice.
The system logic has been enhanced to improve buyer validation during invoice submission. It now detects duplicate buyer records and ensures the correct buyer information from the invoice payload is used during processing.

What Has Changed
We have enhanced the buyer identification process to improve accuracy when matching buyer records during invoice processing. The system now performs a strict sequential check using the following data fields:
i. Buyer Email
ii. Company Name
iii. Business Registration Number (BRN)
iv. Tax Identification Number (TIN)

User Steps

If a unique buyer cannot be identified after these checks, the invoice will automatically be moved to Error status.
Error Message
“A duplicate buyer information found in our system. Please verify the data and contact JomeInvoice Support for further action.”

When this occurs, user will contact Jomeinvoice Support to obtain the correct buyer information.

Where This Is Reflected in the Portal
This update applies to the Sales > API Invoice submission flow.
When an invoice is submitted via API:
The system will validate buyer records associated with the same Profile ID.
Duplicate buyer records will trigger an error message requiring verification.
Valid buyer records will proceed with submission and use the buyer information provided in the payload for both LHDN submission and PDF invoice generation.

Impact
Prevents invoice submission when duplicate buyer records are detected.
Ensures correct buyer information is sent to LHDN.
Ensures the PDF invoice reflects the buyer information provided in the payload.
Improves buyer data validation and overall data integrity.