28/5/2026

What’s New

#1 Resolved an issue that caused invoices to remain in the "Submitted" status due to intermediate LHDN response handling.

Overview
We fixed an issue where some invoices were getting stuck in “Submitted” status after being sent to LHDN, preventing them from reaching their final state.

1. What Has Changed
Improved LHDN Status Handling:
The system will now properly handle intermediate responses from LHDN to ensure invoices continue processing correctly.

Previously:
Invoices could remain stuck in “Submitted” status indefinitely
Intermediate responses were sometimes treated as final
PDF generation and final processing were not triggered

Now:
“Submitted” (intermediate) status from LHDN will be ignored
Only final statuses (Valid, Invalid, Cancelled, Rejected) will be stored
System will continue retrying until a final status is received

2. Where This Is Reflected in the Portal
Invoice submission and status tracking flow
LHDN response handling process
PDF generation trigger after final status

3. Impact
Prevents invoices from getting stuck in “Submitted”
Ensures only final, accurate statuses are recorded
Improves reliability of invoice processing and PDF generation
Reduces issues during LHDN processing delays

#2 Added additional Company Type options during workspace creation.

Overview
We are enhancing the “Add Workspace” feature to support more company registration types in line with LHDN requirements.

1. What Has Changed
Expanded Company Type Options:
The workspace creation process will now support additional business entity types to better align with LHDN registration categories.

Previously:
Only a limited set of company/identity types were available
Some LHDN business categories could not be selected during workspace setup

Now:
System will support a wider range of business types, including:
Company (C) / BRN
Limited Liability Partnership (PT)
Co-operative Society (CS)
Trust Body (TA)
Partnership (D)
Association (F)
Hindu Joint Family (J)
Labuan Entity (LE)
Public Entertainer (FA)
Deceased Person’s Estate (TP)
Unit Trust / Property Trust (TC)
REIT / Property Trust Fund (TR)
Business Trust (TN)
Each type will follow its respective registration and TIN format rules

2. Where This Is Reflected in the Portal
Add Workspace flow
Company/identity type selection step during workspace setup

When creating a workspace:
Users can select the appropriate LHDN-aligned business type
System will validate based on the selected registration category

3. Impact
Ensures full alignment with LHDN business classification standards
Supports more accurate workspace setup for different entity types
Reduces limitations for non-standard company registrations

#3 Enhanced the Purchase Resync process with improved rate limit handling and retry mechanism after the rate limit is exceeded.

Overview
We are improving the purchase invoice syncing process to better handle LHDN rate limits and prevent repeated “429 Rate Limit Exceeded” errors.

1. What Has Changed
Improved Sync Stability:
The system will now handle API limits more intelligently to avoid failed syncs when LHDN is temporarily overloaded.

Previously:
Sync runs in a fixed cycle without controlling request load
Too many requests at once can trigger rate limit errors
Failed syncs may build up over time

Now:
System will slow down and retry automatically when limits are reached
Sync requests are better spread out to avoid spikes
Failed invoices will be retried safely without duplication
Overall sync process is more stable and controlled

2. Where This Is Reflected in the Portal
Purchase invoice syncing process with LHDN
Background retry of failed syncs
Invoice sync status updates

When syncing invoices:
The system will automatically adjust and retry when needed
Temporary LHDN limits will no longer break the sync flow

3. Impact
Fewer sync failures due to rate limits
More reliable and consistent invoice syncing
Prevents backlog of unsynced invoices
Improves overall stability during high traffic periods

Bug-Fixes

#1 Improved API basic validation to ensure validation guards are applied correctly.

Overview
We have improved API validation handling to ensure invalid data is rejected before entering the submission process.

1. What Has Changed
API Validation Guard Improved:
The system now stops processing when validation errors are detected.
Invalid data will be rejected immediately instead of proceeding further.

Previously:
Some invoices could continue to process despite failing validation checks.

This issue has now been fixed.

2. Where This Is Reflected
This fix applies to:
API Invoice Submission

3. Impact
Improves data accuracy, prevents invalid submissions from being processed, and provides more reliable validation results.

#2 Resolved an issue where validated eInvoice requests were not reflected in the report

Overview
We have resolved an issue where invoices validated through the Request e-Invoice process were not appearing in the Request module and reports.

1. What Has Changed
Request e-Invoice Visibility Improved:
Validated request e-Invoices will now be correctly displayed in the Request module.
These invoices will also be included in Request e-Invoice reports.

Previously:
Some validated request e-Invoices were not visible in the module or report listings.

This issue has now been fixed.

2. Where This Is Reflected
This fix applies to:
Request e-Invoice Module

3. Impact
Improves reporting accuracy, enhances invoice traceability, and ensures validated request e-Invoices are consistently visible within the portal.

#3 Fixed an issue where the customer name was not displayed when the same business was registered across multiple workspaces.

Overview
We have fixed an issue in the Customer Module where customer information was not consistently displayed when the same business is added across multiple workspaces.

1. What Has Changed
Customer Details Now Properly Copied Across Workspaces:
When a business is added as a customer in another workspace, all customer information—including the customer name—will now be fully copied and displayed correctly.

Previously:
Customer name was missing or not displayed in some workspaces
Only partial customer information appeared after adding an existing business

Now:
Full customer details are copied across workspaces
Customer name is displayed correctly immediately in the customer list
Consistent data is maintained across all workspaces

2. Where This Is Reflected in the Portal
Customer Module → Customer list across multiple workspaces
Adding an existing business as a customer in a new workspace

When a customer is added:
All details will be automatically populated
Customer name will be visible immediately

3. Impact
Ensures consistent and complete customer data across workspaces
Improves visibility and user confidence when reusing existing customers
Removes confusion caused by missing customer names