General Release Information

The release 5.1.83 has been released on 05-07-2020 and contains several new features and some minor bug fixes. Below you can find more information related to the new features and bug fixes. We will update your live account automatically and the sandbox account can be updated from the customer's end at any given time.

New Features

Native Netsuite payment in transit support

In this release, we have introduced full support for the Native Netsuite Payment In Transit feature. This newly supported feature does not require any configuration and will work automatically if the In Transit feature is enabled. When a payment or payment batch is created with the checkbox “in transit” enabled the Bank Reconciliation will notice this automatically and after reconciliation, the system will automatically confirm the transit payment so it is transformed from in transit to actual payment and will impact the bank account. The pop-up will identify these payments by showing a checked checkbox labeled “in transit”.

Support for custom fields in custom matching rules

With the custom matching rules, it was possible to set a default for the Netsuite fields department, location, and class. This can not be extended and can set now default values for all fields present on the bank statement transaction line. Documentation can be found on the link below.

https://fastfour.atlassian.net/wiki/spaces/BankRec/pages/1007136

Single value matching

The Single Value Matching is a one-to-one matching algorithm that is very efficient and can handle almost an unlimited amount of transactions. This matching option expects that a single value from the bank statement transaction line is fully equal to a single value on the transaction that should be matched. This algorithm is most often used with online payment gateways such as PayPal, Adyen, and Stripe. Documentation can be found on the link below

https://fastfour.atlassian.net/wiki/spaces/BankRec/pages/1104085005

Auto import for non-one-world account

The auto-import option for bank statements was limited to be used only in the One-World accounts. With this release, we have extended the auto-import option logic so it can also be used in non-one-world accounts from now on. Documentation regarding the feature can be found on the link below.

https://fastfour.atlassian.net/wiki/spaces/BankRec/pages/549879830

Support for the file type BAI2

This release brings full support for the BAI2 format. This new format can be found in the “bank file format” dropdown selection.

Auto process (select) of underpayments

When the Bank Reconciliation matches a transaction and the payment amount is less than the transaction by default the solution would only purpose the matched transaction, but won’t process it automatically. This release brings a new configuration that will allow autoprocessing of underpayments. This new configuration can be set individually on each bank account configuration and can be found in de section “Matching Preferences” labeled as “Auto select underpayments”.

Enhancements & Bug fixes

BR-915 Multiple import doesn’t split on currency

The multiple import option allows the user to split the statement data based on the account identifier, but can also split within this identifier on the currency. This option is used when the user has one bank account that handles multiple currencies. During the splitting, the system did not correctly split the data on currency if there was also a split activated to limit the number of lines per statement.

BR-911 Auto import isn’t populating statement currency

When using the auto-import feature the system did not populate the statement currency correctly and did leave it blank. Due to this foreign currency transactions could not be processed correctly. This version will now correctly populate the statement currency.

BR-622 Additional delimiters logic extended

The bank account configuration allows you to set an additional delimiter that the import will use to split data from the description and additional fields. The additional split option was designed to work with CSV imports only but is now extend and will work on all file types.

BR-861 Use this field only for foreign currency payments

When reconciling foreign currencies it could happen that the exchange rate was exactly 1 and when this happend the user could not proceed. An exchange rate of 1 is now supported in the Bank Reconciliation

BR-891 Incorrect “Enter Statement Balance” when importing CODA files

After importing a CODA file the Bank Reconciliation Suite App automatically populates the “Enter Statement Balance”. In certain circumstances, the pre-populated value wasn’t correctly entered. This will now populate the expected value.

BR-893 OFX file format now support checks

The OFX file format could contain a transaction type “Check”. This transaction type is now supported and will import correctly.

BR-895 Additional options for the debit/credit identifier

This release brings a new debit/credit identifier that can exist of three separate values

• SALE (credit)

• RETURN (debit)

• FEES (debit)

BR-908 Parsing issue MT-940 files

In certain MT-940 files, it could happen that data inside the file wasn’t correctly escaped by the data provider (Bank/PSP). This could lead to the situation that the imported data could not be transformed into an actual statement. This release will enhance the MT-940 logic so that the import can escape this data so it can still be imported correctly and transformed into an statement.

BR-922 Additional fields from the CAMT.054 file

When the configuration was set to pull additional data from the CAMT.054 file the system concatenated the data from all statement lines into one that resulted in the same data on all the bank statement transaction lines. This release fixes this and now the system will correctly pull the additional data and shows it on the bank statement transaction line.