General Release Information

The release 5.6.2 has been released on the 14st of March 2022 and contains several enhancements and several bug fixes. Below you can find more information related to the bug fix. 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-1293 Added comma decimal support for OFX

The OFX parser is now extended with additional logic so it allows the user to define the decimal separator on the bank account configuring. Due to this new setting users are now able to also import OFX files that contain comma-separated amounts.

BR-1292 Extenstion of supported transaction types OFX

In this version, we have extended the supported transaction types for the OFX file type. The newly added transaction types are:

• Cash (Debit transaction)

• Dep (Credit transaction)

BR-1287 Run Match button visible during editing

The run match button allows users to trigger a rematching on an existing statement and this button was also visible during the editing of the statement. This version enhances this button so it is only visible during viewing a bank statement.

Bug Fixes

BR-1305 Amount with the minus sign as a suffix

On the bank account configuration, the user can select the debit/credit identifier and one of the options is that the system checks if the amount is negative or positive and based on this will set the transaction to a debit or credit. Negative amounts that are indicated with the minus sign as a suffix didn’t import as a debit and causes an error message. This version introduces extended logic so that amounts that are holding a minus sign as a suffix are also imported correctly.

BR-1303 Dates with a zero prefix can not be imported

Certain banks could provide a CSV file with a date format that is prefixed with an additional zero. Due to this additional zero, the date wasn’t passing the date format checks and caused an error during import. This version adds additional logic to consider this situation so that the import of these date formats is possible.

BR-1297 Empty value additional fields blocks bank statement import

The additional fields feature allows the user to import additional data besides the main data that the Bank Reconciliation SuiteApp imports. This additional data could populate a standard text field on the bank statement transaction line, but can also be used to populate a dropdown field. When the bank statement import data did not contain a value for this dropdown during import it resulted in an error message because the application couldn’t set an empty value for the dropdown field. This version introduces a new logic that handles empty values correct so when encountered the import doesn’t stop

BR-1290 Inactive additional field setups are used

The Bank Reconciliation SuiteApp provides support to configure additional fields that should be captured during the import of bank statement data. These configurations could be set to inactive and when this was done the application still used the configurations. This release extends the logic so that inactive additional fields configuration isn’t used during the import of bank statement data.

BR-1289 Hybrid entity triggers an error message

Netsuite provides the option to create hybrid entities that can act as a vendor and customer at the same time. When a hybrid entity was chosen in the situation of a pre-payment the system displayed an error message and on the bank statement line no transaction was visible but on the background, a transaction was created.

BR-1285 Mandatory fields on vendor payments are ignored

In Netsuite it is possible to set mandatory fields on transactions and when these are present this information must be populated to submit the transaction. When mandatory fields were used on vendor bills the Bank Reconciliation was able to post transactions even if the mandatory information wasn’t present. In this version, we have altered the behavior so that this follows standards and will block the creation of vendor bills where not all mandatory fields are populated

BR-1266 Journals aren’t automatically matched

The matching algorithm wasn’t able to match automatically journals that were AR-related. In this release, we have introduced an improved matching logic that now also is able to match these types of journal postings.

BR-1264 Bank statement is editable during processing

The bank reconciliation SuiteApp has a build-in logic that decides if the statement can be processed on-screen or should be processed in the background. When the processing is done in the background the system uses a scheduled process and during this time the bank statement will be locked to prevent further changes while being processed. This protection mechanism sometimes did unlock the bank statement too early and when a user was quick this could lead to unexpected postings. This version improves the locking mechanism so that the bank statement is locked during the full process so that the user is protected in full.

BR-1117 CAMT.053 displays amounts in foreign currency

In some cases, a CAMT.053 import did show the transactions values in the foreign currency instead of the bank account currency. This release brings a new import logic that correctly identifies foreign currency transactions and switches at that point so it imports the amounts in the bank statement currency.