General Release Information

Release 5.9.7 has been released on the 28th of December 2023 and contains two enhancements and a bug fix. Below you can find more information related to the improvements 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-1742 Process more than 30 files of Unprocessed folder, avoid usage limit exceeded error

In previous versions, the auto import scripts were only able to process about 30 statements from one folder to another, therefore creating a small set of auto-import records ready to be converted to Bank statements. If a user had more than 30 statement files in the Unprocessed folder of the File Cabinet, an await of another script execution to process the remaining files was needed.

This version introduces an enhancement allowing users to process more than 30 statements and significantly speed up the auto import record creation.

BR-1753 Import of MT940, Support Account Identifier ":25P:"

ZoneReconcile supports upload of a single statement file holding multiple bank accounts. The account identifiers stored in statements are coded and these codes are used to parse the statement lines into as many bank statements as there are accounts.

In earlier versions, the Account Identifier “:25:” was exclusively supported within MT940 statement files. In the latest release, the support has been expanded to include the Account Identifier “:25P:”. This enhancement introduces import compatibility of alternative MT940 statement files allowing seamless import compatible with both, single and multi import.

Bug Fixes

BR-1745 Delete Bank Statement resulted in incorrect transactions deleted

A corner case was present in deleting statement transactions, when a user was attempting to delete an entire statement. In the event when a Journal Entry was manually created as a payment and linked together with a Customer Invoice on a statement, a Customer Payment was created. The Customer Payment was only closing the remaining balance of the open Customer Invoice, as a partial balance was reduced by the payment recorded with the Journal Entry. The Journal Entry was only linked to the Customer Invoice and the system stored only a Bank statement link, for the purpose to confirm the Payment.

Nevertheless, when a user would use the Delete button of the statement (with aim to delete the entire statement) the system not only deleted the Customer Payment created by the statement, but also the Journal entry created manually by the user.

This version introduces further control of parameters to define whether transactions should be deleted or not, protecting end users from this unintended behavior.