General Release Information

The release 5.5.0 has been released on 1st of September 2021 and contains several enhancements and several bug fixes. Below you can find more information related to the enhancements 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-1162 Option to change the import behavior for CODA files

In this version, we introduce a new setup option that allows the user to define what kind of data the CODA file parser should import into the bank statement. In certain CODA files, banks can provide the main transaction line with also detailed sublines that explains the mainline in detail. On the bank account configuration, the user can now define if they would like to import

• Mainline and the sublines - creates a statement with all lines within the file, regardless of the type of line.

• Mainlines only - creates a statement with only lines that have the character of a “main” line.

• Sublines only - creates a statement with mainlines and sublines, mainlines that do contain sublines are left out and only sublines are displayed.

By default, the system will be set to import “Mainline and the sublines”. The configuration option can be found under the section “Preferences” and will only be visible if the file format is set to CODA.

BR-1158 Automatic matching for journals related to debit on the bank

This version introduces a new matching logic that allows the system to also match against journal postings recorded in Netsuite when the bank statement transaction line is a debit. In the previous version, the system was only capable of matching credit-related bank statement transaction lines.

BR-1090 N43 parser

In version 5.5.0 we have introduced a new parser that can parse N43 files (Norma 43). The new parser can be found in the default “Bank File Format” selection field. This parser also supports a multiple statement import configuration. All supported formats are listed in https://fastfour.atlassian.net/wiki/spaces/BankRec/pages/1674313856.

Open

BR-1146 Single value matching supports now Customer Refund

We have added support for Customer Refund, so this type of transaction is now being matched if Single Value Matching is utilised.

BR-1154 New Credit/Debit identifier (Dr/Cr)

We have added a new Credit/Debit identifier - Dr, Cr - option in Bank Account Configuration. Customers who use CSV import can use this new identifier from version 5.5.0.

BR-1038 Ability to match multiple sales orders

In this version, we have introduced full support to match one statement line against multiple sales orders. In the previous versions, the matching was already possible but this didn’t create for all the sales orders a deposit, only for the first sales order selected in the popup. From this version on the system will create a separate deposit for each selected sales order

BR-1029 Extended support for Instalments

In this version, we add partial support for instalments. In the previous version reconciliation of instalments was possible but this resulted in a particular situation in full payment of the instalment or a higher payment than the actual amount on the bank statement. This version alters this behaviour so that on the instalment the generated payment does respect the total value present on the bank statement transaction line. This enhancement does not support selecting which instalment is paid, the system will automatically select the first open instalment and apply the payment to it.

Bug Fixes

BR-1155 Automatic import does not process statement lines

In the previous version, the automated import was not automatically processing the matched statement lines. In this version, the system will correctly process the automatically matched statement lines and will also update again correctly the remaining lines and balances

BR-1148 Error: [big.js] Invalid number

When importing a statement in certain scenarios it could happen that while opening the statement the error “Error: [big.js] Invalid number” was shown that blocked further processing. This version resolves this issue so that import is working again for all scenarios without any error messages.

BR-1075 CAMT.054 defaults to credit

In certain CAMT.054 files is could be that the data contains also debit lines and these were imported as credit lines. This version supports now also the debit lines so they import correctly as debits.

BR-1138 Not all customers present in the name field

If the Netsuite system is set up to have a customer structure with main and sub-customers, in case there were significant numbers of sub-customers this resulted in an incorrect display of the customers under the NAME field. In this version, a new logic is implemented so that all customers will be visible as expected.

BR-1140 Single value matching is linking invoice paid in full

We have changed the filtering for the Single Value matching option so it does not match on invoices that are already paid in full.

BR-1143 Payment difference reason Journal Entry with incorrect GL impact

In certain situations when the Payment Difference Reason was used during the reconciliation, a Journal Entry has been generated with incorrect GL impact. This has been now corrected so the Journal Entry correctly holds the Debit and Credit GL accounts.

BR-1109 Selecting a sales order triggers a popup error

In certain accounts, the user could face the issue that the system did trigger an error warning after selecting a sales order to reconcile. Due to this error, the user could not proceed with the reconciliation and had to use a workaround. This version resolves this issue so that in all scenarios the sales order can be reconciled as expected.