High volume matching
On this page, we explain the available options for high volume matching
Introduction
The Bank Reconciliation SuiteApp is designed to have an extensive, flexible, real-time, and configurable matching of bank statement data against NetSuite transactions. The matching runs normally during statement load. Sometimes the number of transactions in the NetSuite system, combined with the amount of data in the statement, is too much for NetSuite to run during statement load. In these cases, the loading of the statement is extremely long or the user gets a time-out error. For these situations, we offer two alternatives. Configuring these alternatives should be done by administrators or implementation consultants.
Scheduled Matching
The scheduled matching option is recommended to be used when working with regular bank statements that should be able to match against all transaction types in Netsuite and do not have an isolated matching parameter. This option should be used only if the user encounters issues during import like timeouts or extremely long loading times.
To set up scheduled matching please read the step-by-step guide on the page Scheduled Matching
Single Value Matching
The single value matching option is recommended to be used when matching can be performed on a single isolated value. This means that the import file must have an isolated value that is 100% equal to a value that can be found in a custom field on the transaction within the Netsuite environment. In many cases, this is the situation when reconciling payment service providers such as Paypal, Adyen, and Stripe.
To set up single value matching please read the step-by-step guide on the page Single value matching