Version 5.12.1 has been released on 9th of September 2025 and contains a couple of enhancements and bug fixes. Below you can find more information related to the enhancements and the 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-2628 [Bank Connectivity] Map JSON's 'Available balance' with 'Enter statement balance' field
Bank statements imported via Connectivity API will now auto-populate the ‘Enter Statement Balance’ field of the corresponding bank statements using the ‘Available’ balance which is now part of the synced transactions. In previous version releases the ‘Enter Statement Balance’ field remained empty upon import:
BR-2620 CAMT.053.001.08 > Support new Counterparty tag
Various bank will continue supporting CAMT.053 statements, but this time with version 8. ZoneReconcile's parsers have been updated to ensure Counterparty information is correctly extracted from the new file format. No action is required from user's end. Statement uploads will continue to parse and display data as expected.
BR-2609 [Bank Connectivity] Calculate 'Bank Balance' and display values accordingly to the Bank Connectivity Dashboards
Bank balances displayed in the Global Balance Dashboard and Bank Accounts Dashboard are now dynamically updated based on the latest synced transactions. A new field, BC Last Calculated Balance, has been introduced to reflect real-time balances, calculated using the initial balance and all synced transactions. This ensures users always have the most accurate bank balance displayed, with full audit tracking enabled for transparency.
BR-2608 [Bank Connectivity] Provide the option of filtering list results based on text input
This version release introduces an improved search experience when linking NetSuite GL accounts—especially helpful for users managing many GL accounts. Users can now type any part of a GL account’s name or number to instantly filter and find matching results in the NetSuite GL Account column. If no text is entered, all ‘Bank’ type accounts will continue to be displayed in the list by default.
BR-2586 [Bank Connectivity] Improved Error Handling
To improve transparency during sync failures, this version release introduces a new Error Details column to the Bank Connectivity Dashboard audit trail. This column displays the error code and a clear message, along with recommended next steps—such as re-linking a bank account or retrying the sync later. This update helps users quickly understand and resolve common connection issues without digging into hidden logs.
BR-2564 [Bank Connectivity] Improve the generation of Bank Account configuration
When creating a bank account via the Bank Connectivity wizard, two fields are now pre-populated to save time:
- Create vendor prepayment as journal is now automatically enabled
- Default Payables Account is auto-filled with the first available account
Navigate to Setup > ZoneReconcile Setup > Bank Account Configurations to alter preferred settings.
BR-2562 [Bank Connectivity] Introduce a new column to store child level subsidiary name
A new column is now present at the Bank Accounts table to show the child-level subsidiary name for clearer visibility. Additionally, hovering over any subsidiary now displays the full subsidiary chain for easier navigation and context.
BR-2557 [Bank Connectivity] Retrieve transaction's button improvements
This version release is simplifying the bank account drill-down view to make it clearer and more efficient. The following improvements have been executed:
- 'Actions' column is now removed from the account drill-down view as it is only applicable based on a bank accounts
- New 'Error' column is introduced, displaying helpful messages (e.g., "Token needs updating") when an issue takes place
- 'Retrieve Transactions' button is now available at the main table level next to 'Disconnect', making it easier to sync your data
- This button is now available even during the first sync of a bank account
BR-2556 [Bank Connectivity] 'As of' date in the drill down Bar of a brand new Bank account has no audit logs
The Global Balance Dashboard has been updated to improve the accuracy of the "As of Date" displayed in the subsidiary drill down for newly linked bank accounts. Previously, when audit logs had not yet been generated, the drill down incorrectly defaulted the "As of Date" to the current date.
With this enhancement, the system will now:
- Leave the "As of Date" field empty if no audit logs are available, or
- Display the date the bank account was first linked
This change ensures that users are presented with more accurate and reliable information when reviewing account data prior to the first synchronisation.
BR-2465 BS with 10+ large BSTs: keep the bank statement locked until all MR deployments completes execution
The processing behaviour for bank statements containing more than 10 large BSTs is improved. Previously, when processed in batches, the bank statement would become editable after the first batch completed — even if additional processing was still underway.
With this update, the bank statement will remain locked until all deployments of the "ZR Process Large BST MR" script have completed. This ensures data consistency and prevents unintended edits during processing.
BR-2429 [Bank Connectivity] Provide an option to filter data of the Bank Accounts dashboard
The 'Bank Accounts' dashboard has been enhanced to support sorting by Subsidiary, Bank and Status. This update gives users greater flexibility and control when viewing and organising their bank account data, making it easier to locate and manage accounts across different entities and institutions.
BR-2365 Link to the original statement file (file cabinet) manual import
Building on the functionality introduced in version 5.10.3, the system now supports storing the original bank statement file for manually imported bank statements as well, not just auto-imported.
With this enhancement, the original import file is automatically saved to the Original file field on the Bank Statement record, ensuring consistent traceability and easier access to the source document, regardless of the import method used.
BR-2281 Support Payment Difference Reasons for Direct Debit reversals
ZoneReconcile now supports Payment Difference Reasons for Direct Debit Reversals. A new configuration option has been added to the Payment Difference Reason record:
Auto-generate Journal for Overpayment (Direct Debits) - when enabled, this setting triggers an automatic journal entry if a direct debit transaction results in an overpayment. This ensures the overpaid amount is properly recorded for accurate reconciliation and reporting.
Depending on the configuration:
- If no account is selected, the system defaults to:
Debit: Accounts Receivable
Credit: Bank
- If an account is selected, the system will:
Debit: Selected account
Credit: Bank
Note: This feature applies only to overpayments and base currency scenarios (Subsidiary, Transactions, Bank Statement - all in Base currency).
This update enhances accounting accuracy when initiated Direct debits are bounced, incorporating bank charges for the attempted action.
BR-2211 Connectivity SFTP: Adjust the description of private key generated by SFTP
The default description for newly generated SFTP private keys has been updated for clarity and alignment with the ZoneReconcile branding.
When a user generates a new private key via the "New SFTP Private Key" button on the Connection Setup record, the key is saved under Setup > Company > Keys. The updated description now reads:
"This key was securely generated by the ZoneReconcile SFTP Connector. Both public keys that are shown here are identical, however, each is saved in a different format."
BR-2145 CAMT053 Parent / Child support
ZoneReconcile now supports line-level import preferences for the CAMT.053 file format, offering users greater flexibility when importing bank statement files that contain parent/child transaction structures.
The “Import Preference” dropdown, previously available only for CAMT.054, is now also displayed when CAMT.053 is selected in the Bank Account Configuration. This allows users to choose whether they want to import mainlines only (top-level transactions) or sublines only (nested transaction details), depending on their reconciliation needs.
When “Mainlines only” is selected and the file includes nested transaction details (TxDtls), the system will import just the main transactions. If “Sublines only” is selected, the system will import the detailed child lines instead.
This enhancement ensures consistent and accurate reconciliation behavior for CAMT.053 files across both the instant and legacy upload flows.
BR-1272 CAMT053E (Extended) Parent / Child support
Following the behaviour of CAMT053, this version also is extending the support for the CAMT.053 Extended (CAMT.053E) file format, by improving import accuracy for users working with Nordea Sweden and similar banks.
Previously, if a single transaction in a batch was missing the <RltdPties> (Related Parties) tag, the parser would default to importing only the cumulative batch line, omitting all detailed transaction lines. While this tag is optional according to Nordea's CAMT.053E documentation and the ISO 20022 standard, its absence led to unintended behavior and incomplete data import, making reconciliation impossible.
With this enhancement a new Import Preference option is now visible in Bank Account Configuration when CAMT.053E is selected under Bank File Format, in line with existing support for CAMT.053 and CAMT.054 formats.
A new option has been added in the drop down list, named Sublines only – counterparties optional. When selected, the system will treat the <RltdPties> tag as optional and proceed with importing sublines even when this data is missing—provided that each subline contains amount and currency.
The existing options enforce the presence of <RltdPties>:
Mainlines only — Imports only the batch line
Sublines only — Imports sublines only if all required party data is present
This change ensures that all valid transactions in a batch are imported, even if some lack related party details, providing more accurate reconciliation and improved support for Nordic banking formats.
Bug fixes
BR-2188 New Auto Import functionality > custom matching rules are no longer working when matching order is customised
An issue affecting users of the new auto-import functionality in ZoneReconcile version 5.10.2 has been resolved. The problem occurred when a custom matching order was configured—causing lines from imported bank statements not to be matched against custom matching rules, despite rules being correctly set up.
This behavior impacted customers relying on prioritised matching logic, such as matching rules before standard parameter-based matching. The system worked as expected only when the default matching order was used or when the legacy auto-import method was enabled.
With this fix:
- Custom matching order configurations are now fully supported during auto-import.
- Custom rules will be applied correctly as part of the automated matching process.
- There is no longer a need to switch back to the legacy processing feature.
This update ensures that auto-import continues to support flexible matching strategies without manual intervention or configuration rollbacks.
BR-2629 System Retains Error Even After Correct Vendor/Customer Is Selected on Bank Statement
A validation issue affecting bank statement processing has been identified and addressed. Previously, when a user selected an incorrect vendor or customer on a bank statement, the system correctly threw an error. However, after correcting the selection, the error continued to persist—blocking further processing. With this fix:
Once the correct vendor or customer is selected, the system properly revalidates the input.
Users can proceed without needing to delete and recreate the bank statement.
This resolves the error persistence issue and improves the overall user experience during bank statement reconciliation.
BR-2625 [Bank Connectivity] Unable to retrieve transactions as system throws error
An issue affecting the retrieval of transaction data via the “Retrieve Transactions” button has been resolved. Previously, clicking this button in the Connectivity API setup would result in an error, preventing any transactions from being retrieved or displayed. With this fix users can successfully retrieve transaction data.
The Retrieve Transactions button now completes without errors, ensuring data is accurately imported and visible in the system.
BR-2622 Cannot Delete Bank Statement Line for Reconciled Vendor Prepay That Generated Check and Vendor Bill Credit
ZoneReconcile has enhanced the deletion process for Bank Statement Lines (BST) linked to vendor prepayments. Previously, when a vendor prepayment was reconciled, the system generated both a Check and a Vendor Bill Credit. However, if users attempted to delete the associated Bank Statement Line afterward, the system would silently block the deletion without providing any error or validation message.
The system now properly detaches and deletes the Vendor Bill Credit and Check created during reconciliation when the related Bank Statement Line is deleted.
BR-2600 Created transaction not linked to Payment Number when there is a background error
In version 5.12.0, payments created with custom roles having view-only permission for Customer records were not linked in the Payment Number field when the Auto Update Counterparty Name preference was enabled. This caused confusion and duplicate payments.
With this fix, all created payments will correctly populate the Payment Number field—even if background errors occur—ensuring transactions are properly marked as reconciled and preventing duplicates.
BR-2565 Next retrieval date set incorrectly on BA Dashboard
When users perform an ad-hoc transaction retrieval, the system now correctly generates audit logs and updates the next retrieval date based on the bank institution’s import schedule. For example, if the schedule is weekly, the next retrieval date will be set to the same day next week—not the following day as before. This ensures accurate scheduling and better visibility in the Bank Account dashboard.
BR-2421 Vendor Credit - Payment can not be processed if partial
In cases where Vendor Credits are partially paid, the system now correctly generates only a standalone Journal Entry as payment without attempting to link it to the Vendor Credit. This resolves errors caused by NetSuite restrictions on linking partial payments, ensuring smoother processing and accurate transaction records.
BR-2022 Rename the checkbox 'Record DDR Reversals' to 'Record DD Reversals'
The checkbox “Record DDR Reversals” on the Bank Account Configuration has been renamed to “Record DD Reversals”.
BR-1795 Import of CAMT053E > Recognise all the values within Ustrd tag
The CAMT053E bank statement import, now correctly handles multiple <Ustrd> tags within a <RmtInf> section. Previously, only the first <Ustrd> value was imported into the Description field. This update captures and concatenates all <Ustrd> values, ensuring more complete transaction descriptions and improving matching accuracy.
BR-1781 CODA descriptions are concatenated without space
This version introduces a fix to an issue in the CODA multi-import process where multiple description lines were concatenated without spaces. This caused invoice references to merge with adjacent text, preventing auto-matching. The import now inserts spaces between description lines to ensure invoice references are correctly recognised during matching.
Note: This fix applies only to multi-import; single import remains unchanged.
BR-1526 CAMT053 Extended > Batch Details are not visible when <TxAmt> tag is missing in one of the lines
In previous version releases, the CAMT053 Extended file parser where transaction lines missing the standard <TxAmt> tag but containing amounts in the <PrtryAmt> tag, were not imported. Previously, this caused batch details (especially debit lines) to be partially or completely missing in bank statements.
With this fix, all batch lines using <PrtryAmt> for amounts will be correctly imported and displayed, ensuring complete visibility of transaction details.