Version 5.13.0 has been released on 30th of September 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-2675 Enable Connectivity API to EU Countries

This release introduces a major expansion of ZoneReconcile 2.0 Bank Connectivity feature, now enabling users to link bank accounts from supported European institutions. To facilitate this, the "Generate Tokens" screen now features a new “Open Connectivity Quickstart - EU” button, while the existing button has been renamed to “Open Connectivity Quickstart - NOAM” for clarity. ZoneReconcile's system now automatically uses the correct regional credentials for data synchronisation, and all existing bank connections have been defaulted to the "US" region to ensure seamless, uninterrupted service.

BR-2282 CAMT053E> Support OCR Payments

This version release introduces an enhancement with CAMT.053E imports where consolidated lines containing multiple OCR payments were incorrectly displayed as one cumulative transaction. ZoneReconcile's parser has been enhanced to correctly identify and expand these nested payment details, and users can enable this functionality via a new preference on the Bank Account Configuration page. 

When activated, the system will now automatically break down a single entry into multiple, individual statement lines, each displaying the specific amount and OCR reference, which significantly streamlines the reconciliation process.

BR-2654 Identify which account belongs to which configuration

To improve clarity when assigning GL accounts, especially for inactive configurations, we have introduced a new “BC Account Mask” field on the Bank Account Configuration record. This field automatically stores the associated bank account number, making it easy for users to identify the correct account when multiple accounts from the same institution exist. 

For all newly created configurations, this field will be populated immediately upon setup. For existing configurations, the account number will be automatically fetched and stored in this new field during the next transaction sync, ensuring all records are progressively updated with this helpful identifier.

BR-2707 [Bank Connectivity] Display the Update Mode button on Bank Account Level and prevent deletion of Access Token when Update Mode is used

To improve user experience and streamline the process of linking additional bank accounts, the “Update Mode” button on the Bank Account Configuration is now always visible, regardless of the connection status. 

This change allows users to easily add new accounts from an already connected institution without needing to first disconnect their entire configuration. Also implemented is a crucial safeguard to ensure the access token is not inadvertently revoked while Update Mode is active, making the process of managing and adding accounts more reliable and secure.

Bug fixes

BR-2662 CAMT054 > Sublines only > Lines are Missing

This release addresses a critical issue in ZoneReconcile's CAMT.054 import functionality that caused transactions to be missed when using the “Sublines Only” preference. Previously, if a payment entry lacked detailed sublines (e.g., OCR data), it was skipped entirely, leading to incorrect balances and reconciliation failures. We have now implemented a fallback logic that ensures these lines are instead imported using the main entry data, guaranteeing that all payments are captured accurately. This fix eliminates the risk of missing transactions for users and ensures reliable bank reconciliation, while having no impact on other import preferences.

BR-2713 [Bank Connectivity] Initial Download Date not properly formatted when using ad-hoc sync

An issue has been resolved that caused inconsistent results between ad-hoc (manual) and scheduled (Map/Reduce) transaction syncs during the initial download. Previously, the ad-hoc sync could fail to fetch the correct transactions if a user's NetSuite date preference was in a format other than M/D/YYYY, leading to discrepancies. This update applies a consistent date formatting logic to both sync methods, ensuring that the initial transaction download now provides the same complete and accurate set of data, regardless of how it is triggered or the user's local NetSuite settings.