Version 5.21.1 has been released on 30th July 2026 and contains a couple of bug fixes. Below you can find more information related to said 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.
Bug fixes
BR-3226 Import of MT940 > MT940_PARSING_ERROR: parseTag62F: unable to parse closingBalance value in current line
This version updates the MT940 statement parsing to ensure smooth imports even when bank files contain trailing characters at the end of the file. Previously, unexpected extra characters following the closing balance tag could trigger an MT940_PARSING_ERROR during processing, preventing successful file ingestion. With this enhancement, the parser now handles and strips non-standard trailing strings, allowing MT940 files with valid closing balances to be imported without requiring manual file cleanup.
BR-3449 ZR Process Bank Statement Transaction MR: Transactions are booked in Incorrect Period
Map/Reduce statement processing is refined to strictly honor accounting period lock restrictions for roles without override permissions. Previously, when an accounting period was only partially locked, such as when tasks were locked for the statement's target subsidiary but unlocked for others, transactions processed via Map/Reduce script (including auto-processing and Vendor Payments) were inadvertently posted to the locked period instead of rolling forward. With this fix, automated and background processing now correctly validates subsidiary-level period locks and routes generated transactions, such as Vendor Payments and Customer Payments to the next open period whenever the processing role lacks the "Override Period Restrictions" permission.