1.28.55 Release
25/4/2026
What’s New
#1 [Exclude 10K Invoices] Allow Cross-Type Invoice Submission
Overview
We have enhanced the invoice submission logic to support cross-type submissions between Consolidated and Non-Consolidated invoices. Users can now switch submission types without needing to delete and recreate invoices.
1. What Has Changed
Cross-Type Submission Support Added:
- The system now allows invoices to be submitted across different types without triggering duplication errors.
Users can now:
- Submit a previously Consolidated invoice as Non-Consolidated
- Submit a previously Non-Consolidated invoice as Consolidated
The system will:
- Prevent duplication errors during cross-type submission
- Record a clear activity trail indicating the conversion:
Consolidated → Non-Consolidated
Non-Consolidated → Consolidated
Previously:
- Users were required to delete the existing invoice before resubmitting under a different type
- Cross-type submission could trigger duplication errors
This limitation has now been removed.
2. Where This Is Reflected in the Portal
This enhancement applies to:
- Invoice submission flows (Consolidated & Non-Consolidated)
When users:
- Attempt to resubmit an invoice under a different type
The system will now:
- Allow the submission without requiring deletion
- Log the conversion in the activity trail
3. Impact
Improves flexibility in invoice handling, reduces manual effort, prevents duplication errors, and enhances transparency through clear activity tracking.
Bug-Fixes
#1 Resolved timeout 524/504 error during sales invoice export
Overview
We have resolved a timeout issue in the Sales Bulk Action Export that occurred when exporting large volumes of invoices. The export process has been optimized to handle high data loads more efficiently.
1. What Has Changed
Export Performance and Timeout Handling Improved:
The system has been enhanced to support large-volume exports without timing out.
Now:
Optimized query performance (including indexing improvements)
Improved handling for large datasets during export (e.g., 10k+ invoices)
Large exports will be processed and delivered via email without timeout errors
Previously:
Exporting large datasets could result in timeout errors (524/504)
Users were unable to complete export for high-volume invoice data
This issue has now been fixed.
2. Where This Is Reflected in the Portal
This fix applies to:
Sales → Bulk Action → Export Invoices
When users:
Export large volumes of invoices
The system will now:
Process the request without timing out
Deliver the export file via email successfully
3. Impact
Improves system reliability for large data exports, reduces failures due to timeouts, and ensures a smoother experience when handling high-volume invoice data.
#2 Fixed completed status display for invoices not submitted to LHDN
Overview
We have implemented a permanent fix to resolve a discrepancy in the Consolidation Log, where invoices were shown as Completed despite not being successfully submitted to LHDN. The system now accurately reflects the true submission status.
1. What Has Changed
Consolidation Status Handling Corrected:
The system now ensures that consolidation status is consistent with actual submission outcomes.
- If a consolidation is cancelled, it will remain in Cancelled status even if an approval action is triggered afterward
- The system will prevent unintended submission after cancellation
- Consolidations will no longer show Completed unless they are successfully submitted to LHDN
- Source invoices will be correctly restored to their appropriate state after cancellation
Previously:
- A race condition could occur when users performed Cancel and Approve actions in quick succession
- This caused the system to incorrectly mark the consolidation as Completed, even though no submission occurred in LHDN
This issue has now been resolved.
2. Where This Is Reflected in the Portal
This fix applies to:
- Sales → Consolidation Log
When users:
- Cancel and/or approve consolidation records
The system will now:
- Maintain the correct final status (Cancelled or Completed)
- Ensure only valid submissions are reflected as Completed
- Prevent inconsistent states between the portal and LHDN
3. Impact
Improves accuracy of consolidation status, prevents false completion records, ensures consistency with LHDN submissions, and enhances reliability of the consolidation workflow
#3 PDF invoice now reflects the latest updated buyer email
Overview
We have resolved an issue where the PDF invoice did not reflect the latest buyer email address after updates were made and the invoice was resubmitted. The system now ensures that the most recent buyer information is consistently used.
1. What Has Changed
Buyer Email Synchronization Fixed:
The system now ensures that the latest buyer email is applied across all outputs after updates.
Updated buyer email will now be reflected in:
PDF Invoice
Additional Information (Billing To)
Submission data to LHDN
Previously:
After cancelling and resubmitting an invoice, the PDF could still display the old buyer email
This caused inconsistencies between updated records and generated documents
This issue has now been fixed.
2. Where This Is Reflected in the Portal
When users:
Update buyer email in the Customer module
Cancel and resubmit invoices
The system will now:
Use the latest buyer email consistently across all outputs
3. Impact
Ensures data consistency across invoices, improves accuracy in generated PDFs and subm

