...

The most common reasons we see as Fast Four are explained below with a suggestion to improve the matching rate.

Investigation incorrect match

When an incorrect match is encountered the first step is checking which setting was responsible for this match. Each bank statement transaction line holds a column the explains why a line did match. Based on this information the user can check if the enabled option does make sense or could investigate what could lead to the outcome data or data present in the description is resulting in an unexpected match of that information inside Netsuite is too general.

...

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.

...