Release 5.7.1
- 1 General Release Information
- 2 Bug Fixes
- 2.1 BR-1249 Exclude non-GL impact transaction statuses
- 2.2 BR-1418 In-transit Bill Payments created from Expense Reports are not confirmed
- 2.3 BR-1421 Custom matching rules are not applied on statement Import unless APPLY TO D/C logic is set to Both
- 2.4 BR-1433 BAI2 Format - Capture additional details
- 2.5 BR-1439 Update the bank statement "warning" when informing of balances mismatch
- 2.6 BR-1442 Bank statement invalid field value - BAI2 file
- 2.7 BR-1445 Extend the Custom matching rule's VALUE (DESCRIPTION) logic to support multiple strings
- 2.8 BR-1446 Additional transaction code support for NAI (BAI) file formats
- 2.9 BR-1457 Matching Rules no longer working when Matching Order is customized
General Release Information
Release 5.7.1 has been released on the 7th of September 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.
Bug Fixes
BR-1249 Exclude non-GL impact transaction statuses
The Bank Reconciliation SuiteApp uses in the application a pop-up that allows users to select one or multiple transactions to reconcile. This pop-up didn’t filter out by default all the non-GL-impacting transactions. In this release, the filter logic is further extended so that the following statuses are excluded from the pop-up:
Bill Payment:Declined
Bill Payment:Voided
Bill:Pending Approval
Invoice:Pending Approval
Journal:Pending Approval
BR-1418 In-transit Bill Payments created from Expense Reports are not confirmed
The Bank Reconciliation SuiteApp supports In-transit Bill Payments created from Expense report. When such a transaction is created, the script should automatically set the status of the payment to Confirmed. This was not happening due to an error. This release fixes the logic so bill payments are marked as Confirmed and GL posting is set to Yes.
BR-1421 Custom matching rules are not applied on statement Import unless APPLY TO D/C logic is set to Both
The Bank Reconciliation SuiteApp provides an option to apply custom matching rules either only to debit lines or to credit lines. This logic didn’t work correctly on statement import. This release fixes the logic so the expected match is generated and will apply the created Custom Matching Rule as defined.
BR-1433 BAI2 Format - Capture additional details
When a BAI2 file was imported it happened that with specific banks the description of one statement line is split into multiple lines. Only the first line was read by the parser resulting in not detailed information in the statement for the end user. This release extends the logic so that the parser is able to read the description from multiple lines, concatenate it, and therefore the bank statement transaction line presents a full description on the bank statement line.
BR-1439 Update the bank statement "warning" when informing of balances mismatch
The Bank Reconciliation SuiteApp displays a warning message on the top of the bank statement in case of processing errors. The warning message contained a typo. This release fixes the typo in the warning message.
BR-1442 Bank statement invalid field value - BAI2 file
When a BAI2 file was imported it happened that with specific banks the negative value of the balance is holding minus character in the front the value: “-value”, which resulted in an error notification. In this version, the parsing logic has been adjusted so that the negative balance holding minus in the front of the value is correctly imported.
BR-1445 Extend the Custom matching rule's VALUE (DESCRIPTION) logic to support multiple strings
The Bank Reconciliation SuiteApp provides the option to create custom matching rules where one of the options is to compare a defined string with the description on the bank statement line. This option didn’t work correctly if the field to be matched contained multiple strings. This release fixes the logic so the expected match is generated and will apply the created Custom Matching Rule.
BR-1446 Additional transaction code support for NAI (BAI) file formats
The BAI2 file format is extended in this release so that it is capable of importing transaction lines that are related to the BAI2 transaction code 910. In the previous version lines with this transaction code were skipped.
BR-1457 Matching Rules no longer working when Matching Order is customized
The Bank Reconciliation SuiteApp allows the user to change the order of matching. Whit this functionality the user can reorder so that for example the SuiteApp will first match open transactions or apply for example custom matching rules. When a reordering was applied the user would face the situation that no matching was applied. This release resolves this issue and when a reordering has been applied the SuiteApp will match as expected again.