16/7/2026

Bug-Fixes

#1 Enhanced buyer validation for Request e-Invoices to prevent incomplete addresses from triggering incorrect General Public submissions to LHDN.

1. Overview
Improved Request e-Invoice processing to ensure invoice submissions use the latest buyer information instead of falling back to outdated or General Public data.

2. What Has Changed

Previous:
If the buyer profile contained incomplete address information, the invoice could be rejected by LHDN.
After rejection, the system reverted the invoice to General Public.
Subsequent validation could proceed using General Public information instead of the intended buyer.

Now:
The system updates the invoice with the latest buyer information provided through the Request e-Invoice process.
Buyer information is refreshed before submission.
Additional validation prevents submission when mandatory buyer address information is incomplete, reducing unintended fallback scenarios.

3. Impact
Ensures invoices are submitted using the correct buyer information.
Reduces the risk of invoices being validated under General Public unintentionally.
Improves data accuracy and user confidence during Request e-Invoice processing.
Reduces LHDN submission failures caused by incomplete buyer information.

#2 Fixed a timezone issue with the "Use Submission Date as Invoice Date" setting to prevent unintended alterations to the Original Receipt Date.

1. Overview
Fixed a timezone issue affecting the Use Submission Date as Invoice Date setting to ensure the Original Receipt Date remains unchanged.

2. What Has Changed

Previous:
When Use Submission Date as Invoice Date was enabled, both the Invoice Date and Original Receipt Date were affected.
The Original Receipt Date was unnecessarily converted to GMT+8 instead of preserving the value from the source file.

Now:
Enabling Use Submission Date as Invoice Date now updates only the Invoice Date.
The Original Receipt Date always remains exactly as provided in the source file.
No timezone conversion is applied to the Original Receipt Date.

3. Impact
Preserves the integrity of the original receipt information.
Prevents incorrect receipt dates caused by timezone conversion.
Ensures Invoice Date and Original Receipt Date serve their intended purposes independently.
Improves consistency for audit and reporting purposes.

What’s New

#1 Optimized the CSV invoice export process using data streaming to drastically reduce memory consumption and prevent system timeouts during large-volume exports.

1. Overview

Optimized the CSV invoice export process by implementing data streaming to drastically reduce memory usage and prevent system crashes during large-volume exports.

2. What Has Changed

Previous:

The system loaded all invoices and their related data into memory simultaneously before writing the CSV file.
This approach caused massive memory spikes.
Large exports were highly susceptible to Out-Of-Memory (OOM) errors and system timeouts.

Now:

The export process utilizes a streaming implementation. It fetches invoice IDs first and processes the data in ordered chunks.
Each chunk is written directly to the CSV file, and the memory is released immediately.
Memory usage remains constant and stable, regardless of how many invoices are being exported.

3. Impact

Drastically reduces memory consumption during exports.
Improves overall export processing speed by approximately 25%.
Eliminates the risk of system timeouts and failed export jobs for users with high daily volumes.
Maintains 100% data integrity; the final CSV rows, columns, and values remain perfectly intact and identical to the previous method.