General Release Information

Release 5.7.0 has been released on the 12th of August 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-1176 Custom user role needs Accounting Preferences to use “Multi-line Journal”

The Bank Reconciliation SuiteApp provides the option under “Alt Match” to create multi-line journal postings. When a custom user role wanted to use the functionality the permission “Accounting Preferences” had to be added otherwise the option didn’t work and did throw an error notification regarding this missing permission. In this release, a new logic has been introduced that overcomes this permission requirement so that users without this permission can use the multi-line journal functionality without any issues. If this permission was temporarily added to your custom user roles we recommend removing this permission again.

BR-1238 Support for “starts with” and “ends with” for custom matching rules

In this new release, two new comparison options are introduced that will provide more flexibility when using custom matching rules. In this release, the option “Starts with” and “End with” are introduced. These options are available for the description comparison and the counterparty comparison.

BR-1273 Slow processing of customer payments

The processing logic for customer payments has been adjusted in such a way that the processing time in specific situations is reduced by more than 80%.

BR-1314 Lock statements during auto import

In the version, new logic has been introduced that better protect end users when the Bank Reconciliation is configured to import bank statements automatically. Before this release automatically imported statements were not locked during the automatic import and reconciliation process. This did provide the option to already reconcile the statement while it was also still processing. In specific situations, this could lead to duplicated transactions. In this release, a new logic is introduced that will keep these automatically imported statements fully locked until the import and reconciliation process is fully completed. With this change, the end user will not be able anymore to prematurely edit an auto-imported statement.

BR-1346 Process DDR batches before other transactions

In this version, the general order of processing transactions has been altered so that DDR reversals can always be reconciled correctly. It did happen that on a statement a DDR batch was present but also did contain DDR reversals for the same batch. In this situation the DDR batch must be reconciled before the reversals can be processed, otherwise, the payment is not yet confirmed and can not be reversed. To correctly support this scenario the order of processing is adjusted so that the DDR batch will always be processed before other lines on the bank statement.

BR-1356 OFX transaction type XFER support

The Bank Reconciliation supports the import of OFX files and specific banks are using the transaction type XFER that does not default to a debit or credit transaction. When a bank statement was imported with this transaction type inside the data the import would fail. This release introduces the support for XFER transaction posting and will automatically determine if the XFER transaction is a debit or credit line.

BR-1347 New behavior option for “When matching a closed transaction”

In version 5.7.0 we have introduced an additional configuration option for the “When matching a closed transaction”. The option is present on the bank account configuration in the subtab “Preferences” and allows the user to select what the SuiteApp will do when it is processing closed transactions. The new option is “Link the transaction and change only the GL account if an in-transit account is configured”. With this new option, the date from the transaction will not be changed at all.

This option can be used for specific use cases for example when reconciling Payment Service Provider (PSP) accounts, where the sales transactions was recorded to the undeposited cash account and you do not wish to change the original sales date of the transaction when moving the transaction to the correct bank account during reconciliation.

BR-1365 Support for “Apply Payments Through Top-Level Customer Only”

When in Netsuite the feature “Consolidated Payments” is used it is possible to set the Netsuite preferences so that received payments are processed through the top-level customer only. The Bank Reconciliation SuiteApp did not support the feature and in this release, the SuiteApp will automatically follow this preference. When enabled the SuiteApp will create the payment through the top-level customer automatically.

BR-1366 Chronological order when auto importing bank statement files

In this version, a new auto import processing logic is introduced that will process bank statements in the chronological order of how they were put into the file cabinet. Previously the auto import functionality did import the pending statements randomly.

BR-1377 OFX transaction type SSD support

The Bank Reconciliation supports the import of OFX files and specific banks are using the transaction type SDD which is a debit transaction. When a bank statement was imported with this transaction type inside the data the import would fail. This release introduces the support for SDD transactions.

BR-1380 Additional field support for PAIN file formats

In this release, we introduce additional field support for PAIN file formats. The additional field feature allows the user to capture additional data from the PAIN file if present. This information can be copied to the bank statement transaction line and from here further logic can be created that for examples copies this additional information to the created transaction but also it allows to process DDR reversals. More information regarding the additional field feature can be found on the page Setup Additional Fields

BR-1415 Field-level help in the general preferences

The Bank Reconciliation SuiteApp provides the option to set some global preferences under SETUP->COMPANY->GENERAL PREFERENCES->subtab “Custom Preferences”. The provided configuration options did not yet hold proper field-level help. Version 5.7.0 introduces field-level help for all the configuration options.

Bug Fixes

BR-1009 Unable to create a customer deposit for an overpayment

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 a customer deposit, but has set the bank account configuration to create a journal. In this situation, the SuiteApp wasn’t able to correctly select the account receivable which did lead to an error notification. This version introduces new logic that will first check if the related customer has accounts receivable assigned on the customer card and will use this account. When this is not assigned the SuiteApp will use the defined accounts receivable from the bank account configuration

BR-1034 Unable to use journals during reconciliation

The user has the option to select in the popup several transaction types to be reconciled. When a combination of credit transactions and debit journals was selected the user would see an error on the bank statement that the amount wasn’t equal while the popup did show that the transaction was balanced. This release resolves this issue so that the user is not blocked anymore by the notification message and can reconcile these types of selections without any issues.

BR-1106 Bank statement processing skips nonsequential lines

In specific situations, it happened that the processing of a bank statement skipped lines when not all lines did hold values to reconcile. The skipping of bank statement transaction lines during processing only did happen when an additional value setup was configured. In this version, the processing logic has been enhanced and the processing will not stop anymore while encountering a bank statement transaction line that should not be processed or when a bank statement transaction line isn’t holding all the needed values to reconcile.

BR-1202 MT-940 doesn’t correctly import Japanese characters

When the user imported an MT-940 bank statement that did contain Japanese characters the characters were transformed into unreadable data. This version introduces a new logic that will import the Japanese characters as expected.

BR-1240 Incorrect exchange rate change while reconciling closed foreign currency transactions

In the previous version, the exchange rate did default to Netsuite’s day exchange rate when reconciling closed foreign currency transactions while it was expected that the exchange rate would represent the exchange rate from the bank. This release resolves this issue and the closed transaction will have the exchange rate that was used by the bank.

BR-1243 Foreign currency transactions not selected for auto processing

The Bank Reconciliation SuiteApp is capable of automatically matching transactions during the import of a bank statement. When the user imported a bank statement with foreign currency transactions the system did correctly find the match but didn’t select these transactions for automatic processing when the differences were within the set thresholds. In this version, the logic has been adjusted so that these foreign currency transactions aren’t only matched but will also auto-process when they are within the set thresholds.

BR-1274 Incorrect posting while using underpayment different reasons on closed transactions

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. In the previous version, the support for the closed transactions was added, but the created journal wasn’t correctly impacting the bank and the defined difference account. This version resolves this issue and the difference will correctly impact the bank account and the defined difference account.

BR-1283 Incomplete data while importing a BAI2 file from the ANZ region

When a BAI2 file was imported that originates from the ANZ region it happened that with specific banks, not all the expected information was visible in the description from the bank statement transaction line. The data present in file type can be different per region. In this version, we have optimized the import logic so that all the expected information within the BAI2 file is imported when it is originating from the ANZ region.

BR-1291 CODA import fails when it contains special characters

When the CODA bank statement did contain special characters it happened that the bank statement wasn’t imported and did result in error notification. In this version, the parsing logic has been adjusted so that special characters do not block the import anymore and do result in a correctly imported CODA bank statement.

BR-1294 CODA import fails with the preference “Sublines Only”

On the bank account configuration, it is possible to alter the import behavior for CODA bank statements. The user can choose to import only main lines, sublines or both of them. When the import preference “Only Sublines” was chosen it resulted in an error notification and the statement could not be imported as expected. In this version, the parsing logic has been adjusted and CODA statements can be imported as expected when this preference “Only Sublines” is enabled.

BR-1295 Unable to create DDR reversals in closed periods with non-GL changes allowed.

The Bank Reconciliation SuiteApp provides full support to automatically DDR transactions. DDR transactions are direct debit reversals for automatically extracted payments from customers' bank accounts. When the original payment was in a closed accounting period where non-GL impacts were allowed the expected DDR transaction was not created and did throw a warning that the transaction couldn’t be created in the closed accounting period. This behavior wasn’t correct because the reversal didn’t actually create a financial impact in the closed period. In this version, the logic has been adjusted so that the DDR transaction is created in the current open period and the original payment is correctly linked with the direct debit reversal.

BR-1296 Mandatory segmentation triggers an error while creating advanced intercompany transactions

When the Netsuite environment is configured with mandatory segmentation fields on the advanced intercompany transaction the user did encounter an error stating “USER_ERROR: Please enter value(s) for: Department, Class”. This error did block the creation of the advanced intercompany in full. In this version, we have resolved this error so that the application supports the mandatory segments department and class. The segment location is not yet supported.

BR-1308 Additional XML data is parsed into on value

The Bank Reconciliation SuiteApp provides the option to parse additional data while importing CAMT.054 files. When this was set up for the CAMT.054 file the system did not pull the data into each individual line but did import the additional data as one string into the first line. This version resolves this issue so that each bank statement transaction line holds the correct additional data.

BR-1313 Incorrect posting while using payment difference reason on customer credit notes

The Bank Reconciliation SuiteApp provides the option to use payment difference reasons while reconciling customer credit notes. When this was done the financial impact was not correct and the created customer refund was including the underpayment. In this release, the logic for this situation has been adjusted in such a way that the created customer refund is representing the actual paid amount and an additional journal will be created to post the difference. This journal will also be connected to the customer credit note so that the postings are correctly visible within Netsuite.

In the previous version, the Bank Reconciliation SuiteApp created an incorrect posting for underpayment situations when the original payment was still in transit. The created underpayment journal would in this case target the transit account from the payment while it should target the bank account where the reconciliation is performed on. This release fixes this incorrect posting so that the underpayment will use the bank account and not the transit account.

BR-1320 Journal entry can not be created while using custom segments and matching rules

When the user had the situation that on the bank statement a custom segment was used along with a custom matching rule the posting would fail if the custom segment was mandatory. In this version, this situation is correctly supported so that the created transaction will be created correctly with the mandatory custom segment populated on the journal.

BR-1330 If the counterparty contains a partial value the rule is not applied

The Bank Reconciliation SuiteApp provides the option to create custom matching rules where one of the comparison operators is “Contains”. This option didn’t match if the matching string was in the middle or end of a value. This release extends the “Contains” so the expected match is generated and will apply the created Custom Matching Rule.

BR-1337 CSV bank statements ignore lines when ending with a backslash

When a CSV bank statement was imported that did contain transaction lines where the description was ending with a backslash the bank statement transaction line was skipped and not imported. This release resolves this issue so that when the description is ending with a backslash the line is still imported and becomes visible on the bank statement.

BR-1354 Custom Matching rule reason contains with counterparty isn’t triggered as expected

On the custom matching rule, the user has the option to define matching criteria that state if the counterparty contains a specific value then I want to apply this custom matching rule. The counterparty contains criteria that didn’t work if the values were in the middle of the description. This version resolves this limitation and provides an actual contains behavior.

BR-1357 Inactivated bank statements to process are being processed

When the system is configured to automatically import bank statements it creates in the background statements to process. These statements to process are transformed into actual bank statements. It could happen that for a reason a bank statement to process is inactivated. This resulted in an error during the auto importing of bank statements. In this version, this issue has been resolved so that auto import ignores correctly inactivated statements to process records.

BR-1359 Matching and processing foreign currency sales orders

The Bank Reconciliation SuiteApp provides full support to match sales orders so that deposits are created. This worked as expected for base currency transactions but didn’t provide the expected result for foreign currency sales orders. In this release, we introduce a fix for this scenario so that the Bank Reconciliation SuiteApp is capable of automating these transactions. Also, the popup has been enhanced so that the values are displayed in the foreign currency values which removes the error notification that amounts aren’t equal.

BR-1371 Document number changes when matching closed transactions

When a user reconciled a closed transaction while the preference “Link the transaction and change date and exchange accordingly” is enabled the document number from the closed transaction changed in many situations. In this release, the processing logic has changed in such a way that the document number will only change when there is an actual change in the accounts from the closed transaction. When the transaction is only linked or when only exchange rates are set the document number will not change anymore as it use to.

BR-1390 CODA adds a space between 2 lines

In the CODA statement files, it can happen that the transaction line level data is divided over 2 data lines and when this happened the Bank Reconciliation did automatically add a space between the two lines while from the bank site it could be actually splitted in the middle of a word or value. In this release, the CODA parsing behavior has been changed so that the space is not added anymore.

BR-1392 Multi-Journal transactions lines are not deducting the remaining lines

When a user did reconcile bank statement transaction lines with multi-line journal postings the remaining lines to be processed did not reflect the reconciled lines. This did lead to statements that were fully reconciled but did still highlight that there were unprocessed lines. In this release, the processing logic has been adjusted so that multi-line journal postings are correctly deducted from the remaining lines to process.

BR-1420 Selecting a tax code gives an error

In certain situations selecting a tax code for a bank statement transaction line resulted in an error message. In this version, the logic has been adjusted so that in all scenarios the tax code selection works as expected.

BR-1427 Custom matching rules with custom segments aren’t setting the values on the transactions

The Bank Reconciliation SuiteApp provides the option to create custom matching rules that a triggered base on the description from the bank statement transaction line and will then default specific values. These custom matching rules can be extended with custom segments if needed but the logic didn’t set the custom matching rule on the created transaction. This version resolves this issue so that the custom segmentation selection on the bank statement transaction line is correctly taken over to the created transaction.