General Release Information

Release 5.8.0 has been released on the 21st of December 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-1284 Closed transactions support of Payment Difference Reason Automation

The Bank Reconciliation SuiteApp provides the option to apply Payment Difference Reasons to transactions subject to overpayment or underpayment. Differences can be handled directly from the bank statement. Users handling high-volumes can setup automation of Payment Difference Reasons, allowing automatic application of differences, without user’s interaction. This setup is handled by the Bank Account Configuration. In previous versions, this feature was only available to Open Transactions. This release introduces the support of Closed (Payments, Cash Sales etc.).

BR-1351 BS SC Import not to process manually imported statements

In this version, a new auto import processing logic is introduced. This logic is making a distinction between manual and automated import, allowing users to enable different behaviors. The BS SC Import script can now process ONLY bank statements that were created from files inserted to the File Cabinet (by ignoring manually imported). Previously, the auto import functionality did import all statements located at the Statement to Process list.

Open

BS SC Import deployment

BR-1494 Import Batch details of a CAMT.054 statement file

In this new release, D-level (detailed level) of CAMT.054 file formats is introduced. This support is providing more flexibility of importing a CAMT.054 statement, by allowing users to configure import preferences. Two options are available: import statement as one batch transaction line or import statement with detailed/itemized transaction lines.

Open

CAMT.054 Bank Account Configuration

BR-1516 Newly added date format (MMM DD, YYYY)

This version introduces a new supported date format that is mainly used by users located in Australia. This format is present in CSV statement file as “Jan 01, 2022” and can be found in the dropdown named “Date Format” on the bank account configuration. This option is labeled in the dropdown as “MMM DD, YYYY”.

BR-1537 MT940 statement format, ignore transactions with 0 value amounts

A new enhancement is present in this version release by introducing a new import logic for MT940 statement formats. MT940 statements that hold 0 amount values in their statement content, will now be ignore on import. Previously, the MT940 parser was reading all transaction lines by ignoring the line amounts, bringing no value to an end user.

BR-1542 Newly added Date format (DD MMM)

This version introduces a new supported date format that is mainly used by users located in South Africa. This format is present in CSV statement file as “01 Jan” 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”.

BR-1552 Newly added Date format (MM-DD-YYYY)

This version introduces a new supported date format. This format is present in CSV statement file as “01-31-2022” and can be found in the dropdown named “Date Format” on the bank account configuration. This option is labeled in the dropdown as “MM-DD-YYYY”.

BR-1565 Show System Notes on Custom Matching Rule custom record

This version introduces support of displaying System Notes on Custom Matching Rules. This new extension is providing users with extensive setup story line, helpful to identify and track changes made to a record.

Bug Fixes

BR-1211 OFX import error - TRNTYPE = "POS"

The Bank Reconciliation supports the import of OFX files and specific banks are using the transaction type POS which dependant on the amount sign, the transaction can be either Debit or Credit. When a bank statement was imported with this transaction type inside the data the import would fail. This release introduces the support for POS transactions.

BR-1455 Support additional custom matching (rule) logic for MT940 files

In version 5.7.0 we introduced a few additional configuration options for Custom Matching Rules. The application logic of Custom Matching Rules has been adjusted in such a way that the condition of "IF DESCRIPTION - VALUE (DESCRIPTION)" for "Is" and "Starts with" is now fully supported for MT940 statements too.

BR-1474 Support additional custom matching (rule) logic for CODA files

In version 5.7.0 we have introduced a few additional configuration options for the Custom Matching Rules. The application logic of Custom Matching Rules has been adjusted in such a way that the condition of "IF DESCRIPTION - VALUE (DESCRIPTION)" for "Contains" is now fully supported for CODA statements too.

BR-1488 Show "Transactions per Statement" field for CAMT type of configurations

In the Bank Reconciliation SuiteApp users can create automated imports and define for certain file types the number of transactions per statement. This logic is splitting the imported statement into smaller statements so that they become better handleable in the browser. This import preference is this version is fully supported for CAMT type of statements.

BR-1491 Disabled "Allow posting to other bank account" checkbox not retrieving error

“Allow posting to other bank accounts” allows users to select an account of type Bank on a bank statement line. This setup is present in the General Preferences (Fast Four Bank Reconciliation) section. In previous versions, when "Allow posting to other bank account" checkbox was disabled, no error notification was triggered for end users. The new version is disallowing users selection of Bank type of account, unless the dedicated feature is enabled.

BR-1496 BS Custom Matching Library triggers unexpected "import statement" behaviour

In version 5.7.3 we did find a relationship within custom matching rules created for a particular statement lines and the Tax Codes used within the Custom Matching Rule setup. This relationship triggered unexpected behaviour upon import of bank statements. This issue is fully removed in this release version.

BR-1512 Sales Orders processed via BS SC Import > Error creating payment: ReferenceError: "Big" is not defined

The Bank Reconciliation SuiteApp provides options to import statements manually and auto-process statements stored in the File Cabinet. In previous versions when bank statements were auto-processed from the File Cabinet, matched Sales Order’s payment could not be processed due to a Script error. This release resolves this issue and Customer Deposits are created as expected.

BR-1517 Select Account is disabled

By resolving BR-1491, we did face an issue with the General Ledger Accounts, triggering inability to select a GL account on a statement transaction line. The issue was fully handled and manually selecting GL accounts is available as expected.

BR-1518 Exclude Pending Approval Journals from auto-matching

The automated matching algorithm did not exclude Journal entries with status Pending Approval 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 Pending Approval Journals in full from the automated matching algorithm.

BR-1522 Custom matching rules containing incomplete parentheses : "Script Error: UNEXPECTED_ERROR null" when importing a statement

In version 5.7.2 (and also 5.7.0) when some matching rule contains “(“, the import of all the statements are interrupted due to an error: Script Error: UNEXPECTED_ERROR. This version introduces a full control and stabilisation of the Custom Matching Rules setup.

BR-1530 Apply Default tax code to all transaction lines is not working

The Bank Account configuration allows the setup of a Default Tax code. Once the Default Tax Code is populated with a corresponding Tax Code, the SuiteApp would assign the exact same Tax Code to all statement transaction lines. On import, the logic was not executed as expected and this version resolves this issue by applying Default values of Tax Codes as expected.

BR-1532 Vendor Credit with underpayment difference reason > Journal is created with incorrect GL impact

The Bank Reconciliation SuiteApp allows the user to create payment different reasons that can write off differences that could exist when receiving payment or making a payment. When funds are received for a Vendor Credit and underpayment Payment Difference Reasons needs to be used, two Journals entries are created. One related to the Vendor Credit, the other one related to payment differences. Combining the GL impact of both Journals, triggered an incorrect posting. Posting is fully handled in this version release. General Ledger Impact is taking place as expected.

BR-1535 Rename the bank file format CAM.053E into CAMT.053E

In this release, we renamed the Bank file format from CAM.053E into CAMT.053E.

BR-1536 Enabled "CREATE VENDOR CREDIT" on Payment Difference Reasons triggers incorrect posting

The Bank Reconciliation SuiteApp provides the support to create payment difference reasons that can automatically post payment differences. In one specific situation, the user could configure the system in such a way that the payment difference rule is set to “Create vendor credit”. In this situation, the SuiteApp wasn’t able to correctly select the account payable, which did lead to an incorrect posting. This version introduces new logic that will first check if the related Vendor has accounts payable assigned on the Vendor card and will use this account. When this is not assigned the SuiteApp will use the defined accounts payable from the bank account configuration.

BR-1551 Populate check line description with bank description

When creating a Bank statement transaction, the SuiteApp populates the Header and the Line level Memo with data stored on the Description column of the statement. In previous versions, when a Check as transaction type was created, the system would only store Description data at the Header level. This version introduces support for Checks, by storing Description data on the Header, but also on the line level too.

BR-1558 OFX import error - TRNTYPE = "DIV"

When an OFX file was imported that originates from the ANZ region it happened that a Script error was triggered on import. In this version, we have improved the import logic so that it eliminates the error, allowing for successful import of an OFX statement.

BR-1560 Instruction Count Error

This version release introduces an improved logic of matching closed transactions. Users handling high volume of transactions subject to be matched, will now experience a faster processing of statements.

BR-1564 Import of CAMT053E > Script Error: ReferenceError: "AddtlTxInf" is not defined

In version 5.7.3 when importing a CAMT.053 Extended file, the import was not success due to a Script error. This version introduces a new logic that will import the statement file format as expected.

BR-1569 Script Error: UNEXPECTED_ERROR on import statement

A relationship of custom matching rules and statement’s content triggered a Script error on import. This version introduces an improved logic of supporting custom matching rules and their combination of different data types.