9/6/2026

What’s New

#1 Added PDF customization support for both consolidated and non-consolidated invoices

Overview
We are introducing support for custom PDF wording to ensure compliance with KPDN requirements for a specific client industry.

1. What Has Changed
Custom PDF Wording Support:
The system will now allow custom wording to be included in the invoice PDF instead of using a fixed default format.

Previously:
All invoices used a standard default PDF format
No option to include client-specific compliance wording

Now:
PDF format can include custom wording when required
Wording will be provided dynamically from the client’s invoice submission
Only applicable to the specific invoice type that requires KPDN compliance

2. Where This Is Reflected
Invoice PDF generation (Consolidated & Non-consolidated invoices)
API invoice submission flow (for clients using API integration)

When invoices are generated:
System will include the provided custom wording in the PDF
Default PDF format remains unchanged for other cases

3. Impact
Ensures compliance with KPDN requirements, allows flexibility for client-specific wording, and avoids hardcoded PDF changes while supporting future customization needs.

#2 Updated copywriting across the portal for improved consistency and clarity

Overview
We are improving and standardizing all portal copywriting to ensure consistent language, tone, and grammar across the system.

1. What Has Changed
Standardized Portal Copywriting:
All user-facing text across the portal has been reviewed and updated for consistency.

Previously:
Inconsistent wording and tone across different modules
Some grammar and phrasing issues in labels, buttons, and messages
Error messages and prompts varied in clarity and style

Now:
All copy has been aligned to a single standard reference style
Grammar, tone, and formatting have been standardized
Labels, buttons, placeholders, and system messages are now consistent across the portal

2. Where This Is Reflected
All modules across the portal
UI labels, buttons, and placeholders
System prompts, notifications, and error messages

3. Impact
Improves overall user experience by providing clearer, more consistent communication, reducing confusion, and enhancing the professionalism of the platform.

Bug-Fixes

#1 Resolved an issue preventing members from being added and introduced edit functionality for Branch and HQ contact details in Workspace Settings

Overview
We have resolved issues related to contact management in Workspace Settings, Customer, and Supplier modules.

1. What Has Changed
Contact Management Improvements:
Users can now successfully add new contacts in Workspace Settings.
Edit functionality has been added for HQ and branch contact details where applicable.
Contact information can now be updated more easily across the portal.

Previously:
Adding new contacts could fail in Workspace Settings.
Certain HQ and branch contact details could not be edited.

These issues have now been resolved.

2. Where This Is Reflected
This enhancement applies to:
Workspace Settings
Customer Module
Supplier Module

3. Impact
Improves contact information management, provides greater flexibility when maintaining records, and enhances the overall user experience.

#2 Fixed an issue where the TIN number could not be updated for existing customers and suppliers

Overview
We have resolved an issue that prevented users from updating TIN information for existing customers and suppliers.

1. What Has Changed
TIN Update Functionality Improved:
Users can now update and save TIN information for existing customer and supplier records.
TIN updates are supported regardless of the current customer or supplier status.

Previously:
Updating TIN information could fail and return validation errors for existing records.

This issue has now been fixed.

2. Where This Is Reflected
This fix applies to:
Customer Module
Supplier Module

3. Impact
Improves data maintenance flexibility, allows correction of customer and supplier information, and reduces unnecessary administrative effort.

#3 Resolved an issue where foreign buyers were incorrectly treated as local companies during invoice submission

Overview
We have resolved an issue where foreign buyer information was not being consistently recognized during invoice submission.

1. What Has Changed
Foreign Buyer Classification Corrected:
The system now consistently recognizes and applies the correct buyer classification during invoice processing and submission.
Foreign and local buyers will now be handled according to their respective requirements.

Previously:
Some foreign buyers could be incorrectly treated as local entities during invoice submission.

This issue has now been fixed.

2. Where This Is Reflected
This fix applies to:
Customer Module
Supplier Module
Invoice Submission Processing

3. Impact
Improves submission accuracy, reduces validation issues, and ensures buyer information is processed correctly based on the appropriate buyer classification.

#4 Fixed calculation discrepancies when exporting multiple-currency invoices using Bulk Actions

Overview
We have resolved an issue affecting invoice exports when multiple currencies exist within the selected date range.

1. What Has Changed
Multi-Currency Export Filtering Corrected:
Export generation now correctly applies the selected currency filter throughout the export process.
The exported invoice count will now match the filtered invoice count shown to users.

Previously:
Exports could include invoices from other currencies, resulting in incorrect invoice counts and longer processing times.

This issue has now been fixed.

2. Where This Is Reflected
This fix applies to:
Sales → Bulk Action → Export
Self-Billed → Bulk Action → Export

When users export invoices using a currency filter:
Only invoices matching the selected currency will be included in the export.

3. Impact
Improves export accuracy, ensures invoice counts remain consistent, and provides a more reliable export experience for multi-currency invoice data.

#5 Resolved state code validation errors caused by incomplete client information during invoice creation

Overview
We have enhanced state information validation during invoice submission to improve data accuracy and reduce submission issues.

1. What Has Changed
State Validation Enhanced:
State information is now required before an invoice can be submitted.
The system will validate the provided state information and display a clear error message if it cannot be verified.
Existing state correction mechanisms will continue to assist where possible.

Previously:
Invoices could proceed with missing or incorrect state information, which could lead to submission issues later in the process.

This behavior has now been improved.

2. Where This Is Reflected
This enhancement applies to:
Sales Invoice Submission
Self-Billed Invoice Submission
Create / Upload / Integration Submission Flows

3. Impact
Improves data quality, reduces submission errors, supports compliance requirements, and encourages more accurate information during invoice creation and submission.

#6 Fixed an issue where invoice consolidation could fail with the message "Zero invoices found in the selected date range or invoice source" despite eligible invoices being available

Overview
We are addressing an issue in the Sales Invoice consolidation flow where users are unable to retrieve invoices even when valid records exist within the selected filters.

1. What Has Changed
Invoice Filtering Issue Under Review:
The system is currently not returning eligible invoices during consolidation, even when valid invoices exist within the selected date range and filters.

Previously:
Users selected a valid date range with existing invoices but the system returned:
“Zero invoices in the selected range”

This prevented invoice consolidation from proceeding.

2. Where This Is Reflected
Sales Invoice → Consolidation flow
Date range and filter selection (branch/source)

3. Impact
Ensures invoices are correctly retrieved based on selected filters, enabling successful consolidation and preventing missing or empty invoice results when valid data exists.

#7 Fixed an issue where editing an invoice from the API module incorrectly redirected users to the Create Invoice page instead of the Edit Invoice page

Overview
We are fixing an issue where invoices submitted via API are incorrectly redirected to the “Create Invoice” flow instead of the proper “Edit Invoice” page.

1. What Has Changed
Correct Edit Flow for API Invoices:
Invoices submitted through API will now open in the correct edit view without triggering recalculations or data changes.

Previously:
Clicking “Edit Invoice” on API-submitted invoices redirected users to the Create Invoice page
Line item values could be recalculated and slightly changed during this process
This led to inconsistencies in invoice values

Now:
API-submitted invoices will open in the correct Edit Invoice page
Line item data will remain unchanged (“frozen”) as originally submitted
No recalculation will be triggered for API invoices

2. Where This Is Reflected
Sales Invoice → Edit Invoice flow
API-submitted invoice handling
Invoice line item display and edit view

3. Impact
Prevents unintended data changes during editing, ensures invoice values remain consistent with API submissions, and aligns the behavior with other integration flows (e.g. SFTP invoices).

#8 Resolved inconsistent purchase counter calculations caused by incorrect start date handling

Overview
We are fixing an inconsistency in the Purchase Counter module where internal and external counts were using different start time calculations, leading to mismatched results.

1. What Has Changed
Unified Start Date Calculation:
Both internal and external counters will now use the same start-of-day 기준 for calculations.

Previously:
Internal count used the current date and time
External count used start of day (00:00:00)
This caused inconsistent and inaccurate count results

Now:
Both internal and external counts will use start of day (00:00:00)
System will follow Malaysia timezone consistently for all calculations

2. Where This Is Reflected
Purchase Counter module (internal and external counters)
All related counting and reporting processes

3. Impact
Ensures consistent and accurate counting across the system, aligns internal and external logic, and prevents mismatched results caused by different date calculation methods.