Version 5.13.2 has been released on 10th of November 2025 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-2749 New In-App banner on the bank statement page
A new informational banner has been implemented on the Bank Statement record page. This banner is visible to all user roles in both view and edit modes, notifying them that direct bank connections for US, CA, and EU accounts are now available. Users can click the link, which opens a new browser tab to a marketing page with their details (first name, last name and email) pre-populated.
Alternatively, users can permanently dismiss the banner by clicking "Do not show again," which saves this choice in their user preferences and fully removes the notification of the bank statement page.
BR-2086 Alerts on Bank Statement Lines > Specify Line Number of erroneous line
An enhancement has been made to the bank statement import process to improve error handling and overall user experience. Previously, when importing large statements, line-level validation errors (e.g., "Invalid date") would trigger an alert, but the message would not specify which line was impacted. This forced users to manually search the entire statement to find the problematic line, which was a significant point of frustration. The client-side validation logic has now been updated to prefix all line-level error alerts with the corresponding line number (e.g., "Line 5: Invalid date"), enabling users to immediately identify and correct issues.
Bug fixes
BR-1321 Journal with hybrid entity (customer - vendor) : Error creating payment: INVALID_KEY_OR_REF: Invalid aracct reference key xx for subsidiary xx.
An issue has been resolved that occurred when processing bank statement lines against Journal Entries for hybrid entities (entities that are both a Customer and a Vendor). Previously, when matching a statement line to an AP Journal for one of these entities, the system incorrectly executed customer-related logic, which resulted in an INVALID_KEY_OR_REF error and prevented the creation of a Bill Payment. Following this fix, the system correctly processes the Journal as a vendor transaction, ensuring that the Bill Payment is created successfully upon saving the bank statement.
BR-1775 Processing of Vendor Credit: Journal and Credit are not linked due to mandatory segmentation
An issue has been resolved for customers who have standard segmentation mandatory enabled in their accounting preferences. Previously, when matching a bank statement credit line (such as a vendor refund) against an open Vendor Credit, the system successfully created a Journal Entry but failed to link it to the Vendor Credit. This was caused by a background error where the mandatory segmentation values from the statement line were not being passed to the payment application process.
This fix ensures that the Department, Class, and Location values are now correctly passed, allowing the Journal Entry to be created and successfully linked to the Vendor Credit, thereby closing the open balance as expected.
BR-2225 Hybrid entity (Vendor + Customer) > Incorrect type (Deposit) is created instead of Customer Deposit
A fix has been implemented for transactions involving hybrid entities (entities that are both a Customer and a Vendor). Previously, when processing a credit line for a hybrid entity that was first created as a Vendor, the system incorrectly defaulted to the vendor record and created a standard Deposit impacting the AP account. This occurred even when the user intended to create a Customer Deposit, resulting in an incorrect financial position and requiring manual correction.
The processing logic has now been updated to correctly distinguish the user's intent in this scenario, ensuring that a Customer Deposit is created and properly booked to the AR account as expected.
BR-2656 Number of BA configurations in the account appears as 0 after license is updated and retrieved
Previously, when a user clicked the "Retrieve License" button, the system would correctly update the license tier limits (e.g., max number of bank accounts) but would incorrectly display the current number of active Bank Account Configurations as "0". This was a display issue that required a page reload to show the correct count.
The retrieval logic has been updated to ensure that both the license limits and the actual count of active Bank Account Configurations are correctly fetched and displayed immediately after the button is clicked.
BR-2664 Inactive Bank Statement File Processing Rules are considered in processing
An issue has been resolved in the ZR AutoImport feature related to Bank Statement File Processing Rules. Previously, the system would incorrectly evaluate inactive matching rules during the auto-import process, causing files that should have been ignored to be moved from the "Unprocessed" folder to the "Processed" folder. This fix ensures that the auto-import logic now only considers active matching rules.
Files in the "Unprocessed" folder that match only an inactive rule will now be correctly ignored and will not be processed.
BR-2705 Transactions with Different AP / AR account > System Creates Incorrect Transactions
An issue has been resolved that caused the creation of incorrect and duplicated transactions when a user attempted to match a combination of open items (such as a Vendor Bill and a Bill Credit, or an Invoice and a Credit Memo) that had different AP or AR accounts.
This scenario, which NetSuite cannot process in a single payment, previously resulted in duplicated payment difference journals and incorrect payment records, while failing to properly reconcile the bank line. To prevent this data integrity issue, a new validation has been added.
The system will now display an error message in the matching popup if the selected transactions do not share the same AP/AR account, blocking the action and instructing the user to correct the transaction accounts in NetSuite before proceeding with the reconciliation.
BR-2724 5.12.x > No Journal is created when Hybrid entity is selected
An issue has been resolved that affected the processing of bank statement lines for hybrid entities (entities that are both a Customer and a Vendor sharing the same internal ID). Previously, when a user selected one of these hybrid entities along with a GL account (the "no-match" scenario), the system failed to create the expected Journal Entry.
This left the bank line unreconciled and was a regression from previous versions. The processing logic has now been updated to correctly identify and handle hybrid entity types, ensuring that a Journal Entry is now created successfully when this combination is used.
When processing a bank statement payment using a Hybrid entity, please make sure to specify the type of entity ZoneReconcile should use when generating a payment:
BR-2726 5.12.x > Bank Balance NetSuite for Credit Card statement is inverted
A fix has been implemented to correct the calculation of the Bank Balance NetSuite field on the bank statement record. This field was displaying a reversed sign (e.g., 20 was shown as -20) for all statements, particularly noticeable on credit card accounts.
This unnecessary inversion logic has now been removed, ensuring the Bank Balance NetSuite value is accurate and correctly reflects the sum of the statement's transactions.
BR-2741 Comparison Role: SSS_SEARCH_ERROR, Message: Search error occurred: Record 'AcccountingBook' was not found.
When a custom role, such as the ZoneReconcile Comparison role, attempted to create a Journal Entry from a bank statement credit line, the system would throw an SSS_SEARCH_ERROR_OCCURED (Message: Record 'AcccountingBook' was not found) because the role lacked "View" permissions for the Accounting Book record.
To remove this error and continue with reconciliation, ask your Administrator to alter your custom role and the 'AcccountingBook' permission within the Setup sublist. 'View' as level is sufficient.
An additional use case applies to SuiteTax-enabled accounts where Multi-Book Accounting is disabled. In this specific configuration, the 'Accounting Book' permission is no longer required; instead, users must be granted the 'Set Up Company' permission to proceed.
BR-2742 Fix generated statement account balance amount
A fix has been implemented within the Bank Connectivity feature to resolve an issue where generated bank statement JSON files were being saved with an incorrect account balance. The system was previously pulling a stale, previously saved balance from the Bank Account Configuration record instead of the most current balance.
The processing logic has been corrected to use the fresh account balance retrieved directly from the Plaid API, ensuring the balance in the JSON file is now accurate and matches the current bank account balance.
BR-2747 5.13.1 > GL account + Customer + Credit line > System creates Customer Deposit / Customer Payment instead of a Journal
An issue has been resolved that occurred when processing a credit line where both a Customer and a GL Account were selected. The system was incorrectly prioritising the customer selection and creating a Customer Deposit instead of the expected Journal Entry. This was a regression from version 5.10.5, as the selection of a GL account should always result in a Journal Entry. The processing logic has now been corrected to prioritise the GL account selection, ensuring a Journal Entry is created as expected in this scenario.
BR-2752 5.13.1 > ZR Process Bank Statement Transaction MR does not re-trigger
An issue has been resolved within the ZR Auto Import feature that affected customers importing a large volume of statements (100+) at one time. Previously, the "Process Bank Statement Transaction" map/reduce script had a hard limit of 50 statements per run. Any statements created beyond this limit were left locked and "In Progress," requiring manual intervention to be processed. The processing logic has now been corrected to ensure the script automatically re-triggers itself, allowing it to process the entire queue until all imported bank statements are complete without getting stuck.
BR-2756 Improve performance of ZR Auto Import Bank Statements MR by adjusting updateBalances function
A performance optimisation has been implemented for the ZR Auto Import feature to significantly improve high-volume bank statement creation. Previously, the import process used the same resource-intensive logic as a manual UI edit, which limited the number of statements that could be created for a single bank account in one run. The system logic has been updated to differentiate between UI and Auto Import actions:
During Auto Import, the system now updates the running balance on transactions without triggering the full processing script for each line.
This change reduces the processing load so that it is dependent on the number of Bank Statements, not the total number of individual transactions.
This optimisation allows the system to now correctly create a much higher volume of statements (e.g., 70 or more per bank account) in a single, sequential run. Manual editing of a bank statement from the UI remains unaffected and will trigger processing as normal.