11/6/2026

What’s New

#1 Enhanced the release note command fetching logic to improve accuracy and reliability

Overview
We are improving the release notes fetching process to ensure existing content can be updated properly in line with Doc Scalar requirements.

1. What Has Changed
Improved Content Fetching Logic:
The system will now support updating both new and existing content instead of only fetching new entries.

Previously:
Only new content was fetched and processed
Existing content was ignored and not updated
This caused outdated information in the system

Now:
Both new and existing content will be fetched and updated
System will ensure all content stays aligned with Doc Scalar
Scheduler will consistently refresh content during each run

2. Where This Is Reflected
Scheduled content fetching process
System-wide content update mechanism
Doc Scalar content synchronization flow

3. Impact
Ensures all content remains up to date, improves data consistency, and prevents outdated records from persisting in the system.

Bug-Fixes

#1 Consolidated directly uploaded invoices into the Processed tab for improved invoice management

Overview
We are addressing an issue where consolidated invoices are immediately moved to the processed state after upload, bypassing the expected consolidation workflow.

1. What Has Changed
Consolidation Workflow Corrected:
Consolidated invoices will now follow the proper processing flow before being marked as processed.

Previously:
Uploaded consolidated invoices were directly moved to the processed tab
Child invoices were immediately assigned a processed state
Users were unable to perform proper bulk consolidation steps

Now:
Uploaded invoices will first remain in an unprocessed state
Invoices will only move to processed after completing the full consolidation process
Parent invoice numbers will only be generated after successful consolidation

2. Where This Is Reflected
Invoice upload and consolidation workflow
Unprocessed and processed consolidation tabs
Bulk consolidation process

3. Impact
Ensures correct consolidation flow, prevents premature processing of invoices, and allows users to properly manage and consolidate invoices in bulk without workflow disruption.

#2 Fixed an issue where invoices could not be created via the API when the optional description parameter was omitted

Overview
We are fixing an issue in the API invoice creation flow where invoices fail to be created when an optional field is not provided, resulting in unclear system behavior.

1. What Has Changed
Improved Error Invoice Creation Flow:
The system will now ensure an error invoice is still created even when certain optional fields are missing, so users can clearly identify and correct the issue.

Previously:
Invoice creation would fail when optional parameters were not provided
No error invoice was generated
Users were not informed what needed to be fixed

Now:
Error invoices will still be created even if optional fields are missing
Users will receive a clear record indicating what needs attention
System behavior is more consistent and traceable

2. Where This Is Reflected
API invoice creation flow (UAT environment)
Error handling and invoice generation process

3. Impact
Improves transparency in invoice creation errors, ensures users can identify and fix issues more easily, and prevents silent failures during API submissions.

#3 Resolved a "Buyer Not Found" error that occurred during Purchase Invoice synchronization

Overview
We are fixing an issue in the Purchase Invoice sync process where invoices fail due to a “Buyer Not Found” error, even though buyer information is not required for purchase invoices.

1. What Has Changed
Improved Invoice Type Handling During Sync:
The system will now correctly differentiate between purchase invoices and customer invoices during the sync process.

Previously:
The system attempted to process buyer/customer information for all invoices
Purchase invoices triggered a “Buyer Not Found” error
Sync process failed unnecessarily

Now:
Purchase invoices will bypass buyer/customer processing
Only invoices that contain buyer information will go through customer validation
Purchase invoice sync will proceed without errors

2. Where This Is Reflected
Purchase invoice sync process
Invoice type validation during LHDN submission flow

3. Impact
Prevents unnecessary sync failures, ensures purchase invoices are processed correctly, and improves overall stability of the invoice sync workflow.

#4 Fixed an issue where the Request eInvoice module displayed duplicate validated invoice records

Overview
We are fixing an issue where multiple validated invoice records are being shown for a single eInvoice request, leading to duplicate entries and incorrect status display.

1. What Has Changed
Duplicate Validation Records Fixed:
The system will now ensure only one validated record is shown per eInvoice request.

Previously:
Multiple validated records could appear for the same request
Exported reports showed duplicate entries
Status updates were inconsistent

Now:
Only the latest validated record will be displayed per request
Duplicate entries will no longer appear in reports
Status will reflect the correct final submission outcome

2. Where This Is Reflected
Request eInvoice module
Workspace eInvoice report export

3. Impact
Improves data accuracy, removes duplicate records, and ensures each eInvoice request reflects only one correct validated result.