9/4/2026

What’s New

#1 Enhanced Invoice Edit Handling

Overview
We have enhanced the invoice edit handling to improve tracking and visibility of uploaded invoice versions. The system now preserves and displays both the original and edited files in the edit history.

1. What Has Changed
Invoice Edit History Improved

The system now stores and displays both:

• The original uploaded invoice file

• The edited invoice version

Users can now:

• View and download multiple uploaded versions under Edit History

• Verify that each uploaded file reflects the correct submitted values

Previously:
Edited invoice history and uploaded file versions were not consistently reflected

This behavior has now been improved.

2. Where This Is Reflected in the Portal
This enhancement applies to:
Invoice Edit History

When users:
Upload an invoice
Edit and resubmit invoice details

The system will now:
Retain and display both invoice versions in the history tab

3. Impact
Improves visibility, enhances invoice tracking accuracy, and provides better transparency for invoice edit activities.

Bugs-Fixes

#1 CSV Import TIN Validation Enhancement

Overview
We have resolved an issue where invalid TIN values (e.g. “NA”) could be successfully imported and approved via CSV import, bypassing validation checks. The system has now been enhanced to enforce stricter validation rules to ensure only valid tax information is accepted.

1. What Has Changed

• CSV import process now enforces strict TIN format validation

• Invalid or placeholder values (e.g. “NA”) are rejected

• System behavior for invalid TIN:

  • Record is rejected with error:

    • “Invalid TIN number detected. Please provide a valid TIN.”

  • OR moved to Awaiting/Review (based on validation outcome)

• Previously:

  • Invalid TIN values could be approved and stored

2. Where This Is Reflected in the Portal

• Customer CSV Import module

• Supplier CSV Import module

• Validation is applied before approval or creation

3. Impact

• Prevents invalid tax data from being stored

• Improves compliance and data accuracy

• Reduces manual data cleanup effort

#2 Supplier Branch CSV Validation & Error Message Correction

Overview
We have resolved an issue where incorrect error messages were shown during supplier branch CSV uploads when HQ data was missing.

1. What Has Changed

• Improved HQ–Branch validation logic

• Branch upload now requires valid HQ reference

• Missing HQ will return correct error message

• Removed incorrect “duplicate registration” error behavior

• Improved MSIC Code validation for supplier branches

2. Where This Is Reflected in the Portal

• Supplier > Upload Supplier Template module

• Applies to UAT and Production

3. Impact

• More accurate validation messages

• Improved data integrity for supplier records

• Prevents incorrect branch processing

#3 Billing To & Shipping To Data Consistency Fix

Overview
We have resolved an issue where Billing To and Shipping To details were changing unexpectedly after invoice submission.

1. What Has Changed

• Billing To & Shipping To now remain fixed based on user selection

• Values will no longer be overwritten during submission

• Previously values could change automatically after submission

2. Where This Is Reflected in the Portal

• Invoice creation and submission flow

• Staging 2 and UAT environments

3. Impact

• Ensures consistency of invoice address data

• Prevents unexpected data changes after submission

#4 Bulk Cancel Sales Invoice Count Display Fix

Overview
We have resolved an issue where incorrect invoice counts were displayed during bulk cancel operations due to incorrect status detection.

1. What Has Changed

• Improved invoice status detection logic

• Total selected count now reflects actual selected invoices

• Fixed mismatch between UI count and actual data

2. Where This Is Reflected in the Portal

• Bulk Cancel Sales Invoice → Perform Cancel section

3. Impact

• Accurate invoice count display

• Improved reliability during bulk cancellation

#5 Currency Filter Fix in Consolidation (Sales Invoices)

Overview
We have fixed an issue where the Currency Filter in Consolidation was not working correctly, leading to incorrect or inconsistent invoice results.

1. What Has Changed

• Currency filtering logic corrected

• Only invoices matching selected currency will be returned

• Prevents empty or incorrect results when filtering

• Blocks cross-currency selection in consolidation

2. Where This Is Reflected in the Portal

• Consolidation → Sales Invoices module

3. Impact

• Accurate filtering by currency

• Prevents incorrect consolidation results

• Improves workflow reliability

#6 Missing “Total Excluded” Indicator in SME Bulk Consolidation

Overview
We have resolved an issue where the “Total Excluded” indicator was missing in SME bulk consolidation flow.

1. What Has Changed

• “Total Excluded” indicator restored

• Invoices > MYR 10,000 now:

  • Excluded from Total Selected

  • Shown under Total Excluded

• Fixed incorrect inclusion of high-value invoices

2. Where This Is Reflected in the Portal

• SME → Bulk Action → Consolidate Sales Invoice

3. Impact

• Accurate invoice categorization

• Prevents invalid consolidation attempts

• Improves UI clarity

#7 Incorrect Invoice Count Display (Issued Date Filter Issue)

Overview
We have resolved an issue where invoice counts were inconsistent when filters were applied in the Sales dashboard and bulk actions.

1. What Has Changed

• Issued Date filter logic corrected

• Dashboard count now matches filtered results

• Bulk actions now reflect correct Total Selected count

• Fixed mismatch between UI and actual dataset

2. Where This Is Reflected in the Portal

• Sales → Invoice Dashboard

• Bulk actions: Export / Consolidation

3. Impact

• Accurate invoice counts

• Consistent filtering results

• Improved user confidence in data accuracy

#8 Tax Exemption Logic Validation Enhancement

Overview
We have enhanced the Tax Exemption logic to ensure that only valid exemption reasons are considered during invoice submission. This change prevents placeholder values from being incorrectly interpreted as valid tax exemption inputs, improving accuracy in tax calculations and ensuring compliance with LHDN guidelines.

1. What Has Changed

• Improved validation for “Details of Tax Exemption” field before applying exemption logic

• System now only applies tax exemption when a valid exemption reason is provided

• The following values will no longer trigger tax exemption logic:

  • “NA”

  • “N/A”

  • “0”

• If these values are provided:

  • Invoice will still be successfully created

  • Line items will not be treated as tax exempt

• Previously:

  • Any input (including placeholders) could trigger tax exemption logic

  • This caused incorrect tax calculations and missing tax amounts

• Behavior updated to align with LHDN guidelines

2. Where This Is Reflected in the Portal

• Applies across all invoice submission channels:

  • Sales invoices

  • Self-billed invoices

  • SFTP / Direct Upload

  • API submissions

• System validates tax exemption field before applying exemption logic

3. Impact

• Ensures compliance with LHDN requirements

• Improves accuracy of tax calculations

• Prevents invalid placeholder values from triggering tax exemption

• Enhances overall data integrity across invoice submissions

#9 Invoice Submission Field Mapping Standardization (All Channels)

Overview
We have standardized invoice submission templates across all channels to ensure consistency and compliance with LHDN requirements. Field mappings for SFTP, Direct Upload, and API are now fully aligned to ensure a uniform structure regardless of submission method.

1. What Has Changed

• Invoice field mappings have been standardized across all submission channels

• SFTP, Direct Upload, and API now use a consistent field structure

• All required fields are aligned based on LHDN requirements

• Ensures uniform data format regardless of submission method

• Previously:

  • Field mappings differed across SFTP, Direct Upload, and API

  • This caused inconsistencies and potential compliance risks

• These inconsistencies have now been resolved

2. Where This Is Reflected in the Portal

• Applies across all invoice submission channels:

  • SFTP uploads

  • Direct Upload (portal)

  • API submissions

• System now enforces consistent field structure during invoice processing

3. Impact

• Ensures full alignment with LHDN requirements

• Reduces submission errors caused by inconsistent field mappings

• Improves reliability and predictability across all invoice submission channels

• Enhances overall data consistency and compliance