Skip to main content

Solutions

Law firms

Tax, audit & accounting firms

Corporations

Governments

Products

Legal

Trade & supply

Tax, audit & accounting

Corporate tax

Risk & fraud

Books

Recommended products

Questions? We are here to help.
Contact us

Purchase

Buy solutions

Buy books

Contact sales

Questions? We are here to help.

Resources

Insights

Events

Product training

Product communities

Developers

Release notes

R1.6.0.1 and R1.6.0.2 May 14, 2025 release notes

Enhanced mapping for duplicated document numbers in SFTP clearance statuses

Improvements have been made to the handling of clearance statuses when the invoices are transcated using SFTP systems. Previously, documents with the same number and rejected status were not correctly mapped in the UI. The solution now incorporates additional parameters, including Invoice/Document Number, Issue Date, and the latest invoice timestamp, to ensure accurate mapping and reflection of rejected statuses in the user interface.

AR invoice clearance status retrieval

The ONESOURCE E-Invoicing new API experienced issues retrieving clearance status for some invoices due to concurrent submission of AR invoices for the same company. This caused missing Government ID and clearance status for certain documents. The issue has been resolved by processing submissions sequentially, ensuring all invoice clearance statuses are accurately retrieved without delay.

Resolution of file ID length issue affecting SFTP clearance document processing

An issue was identified where SFTP could not consume clearance documents due to the file ID exceeding the 50-character limit, affecting customers, specifically for Greece-approved invoices. This limitation prevented the successful receipt of approved documents. The issue has been acknowledged, and steps are being taken to address the file ID constraints to ensure smooth document processing.The file ID character limit has been expanded from 50 to 255 characters, facilitating the successful receipt of clearance documents and ensuring efficient document handling.

Resolution of technical error messages for invoice submissions

Issue summary
Customers using ONSOURCE E-Invoicing old API encountered technical error messages when attempting to view logs for invoice submissions. The root cause was identified as an incorrect configuration setting for the inbound format in the application response, specifically related to PDF handling.
Impact
When the user sets the format to PDF, invoice transactions fail to update properly, leading to error messages and potential confusion.
Resolution
  • It is advised that users revert the format setting back to XML. This adjustment will ensure proper functionality and correct the status of affected invoices.
  • After changing the format to XML, users should restart the process to ensure all invoices are updated correctly.
Enhancement
OEI has implemented a solution to address this edge case. Moving forward, OEI will prevent document statuses from changing to error due to this configuration issue, thereby enhancing system reliability and user experience.
Action Required:
 Customers are encouraged to review their configuration settings and ensure the inbound format is set to XML to avoid similar issues. For assistance or further guidance, please contact the support team.

Implementation of Malaysian LHDN mandated scheme IDs to prevent API errors - old APIs

As part of the Malaysian LHDN mandated updates, Scheme IDs [PL:KRS, PL:BDO, PL:REGON, 9925, 9930] have been incorporated into 'partyIdentificationIds' and 'partyLegalEntities' where applicable. This enhancement ensures smooth transaction processing and eliminates 400 Bad Request errors for previous Submit API transactions.

This article applies to:

  • Product: ONESOURCE E-Invoicing