General Release Information

Release 5.7.2 has been released on the 14th of October 2022 and contains several bug fixes. Below you can find more information related to 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-1423 PAIN002 uses the identifier from the initiator

In the PAIN002 file, the transactions can hold 2 types of identifiers. One can be related to the initiator and one can be related to the receiving party. Depending on the starting point it can be that one or the other is the actual bank account of the company. To allow a switch in this the Bank Reconciliation has been extended with a new option in the bank account configuration. This new option becomes available when the configuration is set to the PAIN002 file type. When this is done a new checkbox becomes visible named “Use Bank Account from Initiator as parsing Identifier”. When checked the system will use the bank account from the initiator as the bank identifier.

BR-1460 Newly added date format

This version introduces a new supported date format that is mainly used by the marketplace eBay. This format is in the format “01. Jan 2022” and can be found in the dropdown named “Date Format” on the bank account configuration. This option is labeled in the dropdown as “DD. MMM YYYY”.

BR-1464 Extension of the “When matching a closed transaction”

In version 5.7.0 a new configuration option was introduced for the setting “When matching a closed transaction”. This option new option “Link the transaction and change only the GL account if an in-transit account is configured” will not change the date of the transaction but will change the GL account if needed. The logic behind this new function was implemented for individual transaction line reconciliation only and not for EFT batch processing. This version introduces also full support for the EFT batches.

BR-1466 Hide transactions per statement if not applicable

In the Bank Reconciliation SuiteApp the user can create automated imports and define for certain file type the number of transaction per statement. This logic will split the imported statement into smaller statements so that they become better handleable in the browser. The option to define the number of transaction lines per statement was always visible on the configuration and this release hides the field automatically when not applicable for the selected file type.

BR-1475 Improvement in processing speed for closed transactions

When the bank reconciliation processes closed transactions the SuiteApp performs on the background several checks to confirm if it's possible to process the selected closed transactions. When the account has a lot of subsidiaries this logic did consume a lot of time what resulted in slow processing of submitted bank statements. This release improves the logic for closed transactions processing that will result in faster processing for accounts with a high number of subsidiaries.

Bug Fixes

BR-1452 Run match not applying newly found matches

The user would like to re-match open lines on the bank statement in specific situations. The Bank Reconciliation SuiteApp allows this (when enabled) by pressing the button run match. In specific situations, the user would see the “Matching in progress” bar but no actual matching happened and the matching message would not disappear. In the background, the application did encounter a line to be matched that was already partially matched which cause a general error and due to this, no actual action was taken by the application. In this release, the “Run Match” logic has been altered in such a way that these situations are escaped correctly and will assure that all lines are matched as expected.

BR-1471 Customise matching logic not respected during auto import

The Bank Reconciliation SuiteApp offers an option to customize the order of the matching logic. When this order of matching logic was adjusted it worked as expected for manual imports but didn’t respect the new order matching order when performing an automated import. This version resolves the issue so that an automated import also respects the newly configured matching order.

BR-1477 Additional XML data is parsed into on value

The Bank Reconciliation SuiteApp provides the option to parse additional data while importing CAMT.053 or CAMT.053E files. When this was set up for the CAMT.053 or the CAMT.053E file the system did not pull the data into each line but did import the additional data as one string into the first line. This version resolves this issue so that each bank statement transaction line holds the correct additional data.

BR-1461 The BAI2 file format doesn't update the Enter Statement Balance

Within the BAI2 file format, there are several versions and some of them didn’t auto-populate the bank statement field named “Enter Statement Balance”. This field is used in bank reconciliation to calculate potential statement differences. In this version, the support for the different BAI2 file formats has extended so that the “Enter Statement Balance” field is auto-populated during the import of a bank statement

BR-1465 Exclude rejected a bill from auto-matching

The automated matching algorithm didn’t exclude rejected bills from matching that could lead to the situation that a bank statement transaction line could be matched against it. This version resolves this issue and will exclude rejected bills in full from the automated matching algorithm.

BR-1479 Disable automatic matching still triggers custom matching rules

The Bank Reconciliation SuiteApp allows the user to configure the SuiteApp in such a way that no matching will be triggered during import. This can be done by checking the checkbox named “Disable Automatic Matching” on the bank account configuration. When this checkbox was enabled the SuiteApp still applied defined custom matching rules. This release resolves this issue so that also the custom matching rules aren’t applied anymore when this configuration option is enabled.