2.4.0.2 integration for NetSuite
The ONESOURCE Indirect Tax Integration for NetSuite 2.4.0.2 is a patch release containing enhancement.
Supported source system versions
- NetSuite OneWorld and ERP
- Built for NetSuite (BFN) Validated
Technical changes
Issue 1:
When user enters duplicate tax code in , under Edit Tax Types and Codes
, an error message is displayed that is not easily understandable to the user.Root cause:
The error message is generated from the script as NetSuite does not allow duplicate tax code in the system. The script error is directly displayed to the user.Solution:
To resolve this issue, we will update the client script. We will catch the error in the script and convert it to a user-friendly message.New error message: "This Tax Code is already available in the account"
Implementation:
We have updated the IDT.TaxTypeUpdateClient_v2.js
script to implement this solution.Release date:
18 May 2026Issue 2:
When a user creates an expense category containing special characters such as Less Than (<) or Greater Than (>), and applies it to a transaction, those characters are automatically converted into escaped characters. This conversion is visible in the request XML sent to OneSource. Since the Expense Category is passed as PART_NUMBER in the XML, the escaped characters cause a text mismatch, which results in an error in OneSource.Solution:
To resolve this issue, we will update the Tax Plugin script.Implementation:
We have updated the IDT.TaxPlugin.js
script to implement this solution.Release date:
18 May 2026Issue 3:
When creating a Vendor Return Authorization (VRA), either as a standalone transaction or from a bill, with VCT selected in the configuration, the transaction is not saved. In the observed scenario, NetSuite throws an error stating that the tax amount changed between the previous value and the current value, and the transaction is not saved. This issue appears to occur only when the configuration is set to VCT. It does not occur when the configuration is set to any option other than VCT.Expected result:
The transaction should be saved successfully in NetSuite.Actual result:
The transaction errors out and is not saved in NetSuite.Sample error message: "Total amount of taxes returned by the tax engine is different from the previous value for the same input data. Previous value: 9.25, current value: 0.0. Contact your tax engine provider for assistance in resolving this error."
Solution:
To resolve this issue, we will update the Tax Plugin script.Implementation:
We have updated the IDT.TaxPlugin.js
script to implement this solution.Release date:
18 May 2026Issue 4:
Payment Hold was not getting automatically triggered on Vendor Bills, even when the feature was enabled in .Root cause:
Two defects in the Transaction User Event Script prevented the Payment Hold logic from running, one affected Vendor Bills saved through the UI, and the other affected Vendor Bills created programmatically by copying an existing bill.Solution:
Both defects have been fixed so that the Payment Hold logic now executes reliably for Vendor Bills, whether created through the UI or via script.How Payment Hold works:
The Vendor Bill's Payment Hold
checkbox is automatically checked by the script if any tax code on the Tax Detail lines is among the tax codes designated to trigger Payment Hold (configured in ).Implementation:
We have updated the IDT.TransactionUserEventScript_v2.js
and IDT.Transaction.Module.js
scripts to implement this solution.Release date:
18 May 2026Related Content
-
NetSuite SuiteTax
Format:
Article