Version 5.17.0 has been released on 4th of March 2026 and contains a couple of enhancements and bug fixes. Below you can find more information related to the enhancements and bug fixes. We will update your Production account automatically and the Sandbox account can be updated from your (the customer's) end at any given time.
Enhancements
BR-2948 [BankConnectivity] Support Single-Currency Accounts
The Bank Connectivity module has been updated to ensure a smooth setup process for Single Currency Accounts. Previously, the system encountered an error when attempting to load the Bank Accounts information in environments where the 'Multi-Currency' feature was disabled.
In this version, the ZR Bank Connectivity logic has been refined to auto-detect the account type. If an account is set to a single currency, the system now automatically adapts, preventing the 'Field not found' error and allowing bank details to load successfully.
BR-2966 Remove 'Available Without Login' from ZR Old Auto-Import Bridge SL
To align with NetSuite security standards and eliminate unauthenticated HTTP dependencies, this version release deprecates the legacy external Suitelet trigger. The architecture now utilises a decoupled, record-based queue system powered by SuiteScript 2.1.
The process transition from file generation to final record creation is now governed by an internal queue:
The BS MR File Processing script continues to generate the "Bank Statement to Import" record
Upon execution of the BS SC Import, the system generates a tracking entry in the ZR Bank Statement Processing Queue custom record
The new ZR Process BS Import Queue MR (a lightweight SuiteScript 2.1 "Bridge" script) monitors this queue
Once Bank Statement IDs are identified, the Bridge script creates the final Bank Statements based on the pre-defined Bank Statement File Processing rules
Impact to existing users: If using the old auto-import process (BS MR File Processing & BS SC Import schedules) and upgraded to 5.17.0, the changes from above will automatically take place. Accordingly, no action is required. Bank Statements and Bank Statements to Process will be generated as usual.
Recommendation: To benefit from performance enhancements, it is highly recommend migrating from the legacy auto-processing schedule to the updated version. Instructions are available on the following link AutoImport migration and multi-queue enablement.
BR-2986 ZR Auto Import Bank Statements MR > Add more Deployments for Processing
To improve reliability for high-volume users, the ZR Auto Import logic has been enhanced to prevent processing bottlenecks. Previously, if the customdeploy_zr_process_bst_autoimport deployment was still active from a previous hourly run, subsequent imports would fail with a "deployment in progress" error, leaving statements stuck in a "To Process" status.
With this version, the system now intelligently detects the availability of the primary Map/Reduce deployment. If the specific deployment is busy, the system will dynamically allocate an available deployment or queue the task to ensure every imported statement is processed without manual intervention. This update effectively supports multi-queue processing and eliminates the "stuck" status caused by overlapping scheduled imports.
BR-1764 'Partner-Customer-Vendor' hybrid entity; Provide an option to choose default entity
The bank statement processing logic has been updated to support "hybrid entities" that function as Partners, Customers, and Vendors simultaneously. Previously, these records defaulted to Vendor behavior, which blocked sub-customer invoice visibility and incorrectly triggered AP deposits.
Users can now view Partner-typed transactions in the Bank Statement popup by selecting the new "Show Sub-Customer Transactions for Hybrid Entities" checkbox. This feature is disabled by default to maintain a clean view but can be toggled on whenever sub-customer visibility is required.
BR-1710 CODA Import Structured Description
The CODA bank statement parser has been updated to handle structured communications and eliminate "UNDEFINED" descriptions caused by missing optional records.
A new "Import Structured Communication" checkbox is now available in the Bank Account Configuration. When enabled, the parser identifies Communication Code 1 in records 2.1 and 3.1 to extract clean document references (e.g., "283446067") instead of raw unstructured strings (e.g., "101283446067"). The update also ensures that missing 3.1 information records default to an empty string, removing visual clutter from the statement import.
To enrich the 'Description' data to your CODA imports, enable the check box below. Please note, this change will be applicable to new imports only.
Bug fixes
BR-2798 Checks are created in vendor's primary currency instead of bank's currency
Previously, when processing payments for vendors who held a different "Primary Currency" than the bank account, the system would incorrectly default the check to the vendor's primary currency. This resulted in incorrect General Ledger impacts due to unintended currency conversions. The transaction logic has been refined to prioritise the bank account's currency during the automated creation process. This fix ensures that if a bank statement reports a transaction in USD, the resulting check is generated in USD, regardless of the vendor's default currency settings.
BR-2797 Error when creating a Check: You have entered an Invalid Field Value "x" for the following field: currency
A critical fix has been implemented to resolve a currency validation error (INVALID_FLD_VALUE) that occurred during automated check creation. This issue was primarily seen in environments where users switched between bank accounts with different currencies, causing the system to conflict with "sticky" field values from previous sessions.
The update reorders the background processing logic to match the standard NetSuite UI behavior: the Bank Account is now set before the Currency. This ensures the transaction context is correctly established, allowing checks to be generated reliably without manual intervention.
BR-2795 Reconciliation of Multiple Closed Transactions > Error: Record has been changed
The reconciliation logic has been updated to resolve a "Record has been changed" error that occurred when matching multiple closed transactions (such as a payment and a refund) against a single bank statement line. This issue previously surfaced when the system was configured to automatically update the date and exchange rate of matched records, causing subsequent transactions to fail to link after the first one was processed.
The system now handles multiple records sequentially, ensuring that every selected transaction is updated with the statement date and successfully linked. This update restores full functionality for complex reconciliations, ensuring the Payment Number is correctly populated across all records without requiring manual adjustments to account settings.
BR-1855 Matching Closed Based on Parameters > Exchange Rate is not changed
Previously, the system could fail to update the exchange rate on foreign currency transactions (such as a EUR Bill Payment matched against a USD bank account) if a user opened and saved the reconciliation popup without making manual changes. This resulted in a discrepancy between the bank statement amount and the General Ledger impact.
In this release, the processing engine has been updated to ensure these parameters are always applied when a transaction currency differs from the base or bank currency. The system now correctly references the foreign amount (fxamount) and ensures the exchange rate is updated as per bank statements', regardless of whether the user interacts with the reconciliation popup.
BR-1768 CAMT053: Amount is not read from NtryDtls > TxDtls > Amt path
The CAMT.053 bank statement parser has been enhanced to ensure full compatibility with version 001.04, specifically improving how transaction details are extracted when amounts are mapped via the <Amt> tag. Previously, files utilising the <Amt> tag instead of <AmtDtls> within the transaction details block would incorrectly import as a single cumulative entry; this update enables the system to correctly identify and split these into multiple line items as intended. Additionally, the sourcing logic was refined to prioritise detailed amount paths, ensuring accurate data capture for both standard and counter-value transactions.
BR-1580 Foreign Currency Tolerance % Setting to be Respected in the Popup
The bank statement processing logic has been updated to ensure the Foreign Currency Tolerance % defined in the Bank Account Configuration is consistently applied across all matching scenarios.
Previously, a hardcoded 5% limit was automatically applied in the selection popups whenever an entity was selected, overriding any custom settings. This update synchronises the BS SL and BS CL popup scripts, allowing the system to dynamically respect the user-defined tolerance. Consequently, foreign currency transactions are now successfully matched only when the variance falls within the specifically configured percentage, providing greater control over exchange rate fluctuations during the reconciliation process.
BR-3038 ZR Auto Import Bank Statement MR throwing SSS_IVALID_SRCH_FILTER error
The bank statement auto-import logic has been updated to resolve a script error that caused concurrent imports to stall or fail.
Previously, the ZR Auto Import Bank Statement MR script encountered a search filter error when attempting to identify available script deployments. This caused the system to incorrectly report that a process was already running, leaving subsequent bank statements stuck in a "locked" state. The fix ensures the search filter correctly handles deployment IDs and allows the system to dynamically utilize multiple deployments of the ZR Process Bank Statement Transaction MR script. This allows multiple bank statements to be processed simultaneously without manual intervention or "Map/Reduce Already Running" errors.