...
When a bank statement transaction line isn’t matched, the first step is identifying the expected transaction. If this does exist in Netsuite the next step will be to investigate how the matching for the bank account is set up. To retrieve this information navigate in the main menu to SETUP->BANK RECONCILIATION->BANK ACCOUNT CONFIGURATION. Open in this list the bank account configuration that is related to the bank on which the match didn’t happen. On the bank account configuration, there are several matching options and each of them will have different behavior. As a user, you most likely will see the logic why you were able to find the correct match and this logic must be compared to the applied matching rules. The most common reasons we see as Fast Four are explained below with a suggestion to improve the matching rate.
Resolve no matching
The transaction number in the description from the bank is not containing the prefix used in Netsuite
An example for this would be: INV-000123 is in the description from the bank actually 000123. In this situation, an option could be to extend the Netsuite system and the bank reconciliation matching parameters. We only recommend taking this action when there are multiple occurrences present in the created insights document. Creating this additional matching option exists out of 2 steps.
...
The next step is to extend the bank account configuration so it does take this parameter as a matching value. To do this navigate to SETUP->BANK RECONCILIATION->BANK ACCOUNT CONFIGURATION and open te the related bank account configuration. Now scroll to the bottom of the page and click on the subtab labeled “Additional Parameters&Fields” and press on the button labeled “New Banks Statement Matching Parameter”. In this screen enter the name of the newly created field and after selecting the transaction id field will be automatically populated.
...
Save the configuration and directly create a the next entry. In this entry type directly in the field labeled “Transaction Field Id” the value “tranid” and save. This must be done otherwise the system will only use your newly crated field due to the fact that this custom configuration will overwrite the standard logic. From this moment onward the syste system will check not only the standard transaction ID from Netstuite but also your customized transaction ID field and matching should increase.
Resolve incorrect matching
The description did not hold any kind of transaction number
...