On this page, we explain how to use and set up the single value matching
The single value matching option is designed to match really high volumes often related to payment service providers such as Paypal, Adyen, and Stripe. With the single value matching the system matches a value in a one-to-one relationship. This is only possible if the value from the bank statement transaction line is isolated in the description column or present in a separate column. To import individual data to a specific custom bank statement transaction line column we recommend following the documentation on the page Setup additional fields. The single value matching depends on a map/reduce script that can be scheduled to run as often as once every 15 minutes and does need a separate deployment for each bank account configuration. It's recommended to keep in mind that creating multiple deployments could lead to a processing queue and a dedicated queue is recommended when using multiple deployments.
The single value matching depends on a single map/reduce deployment for each bank account configuration that can match against closed or open transactions. The deployment uses the setting from the bank account configuration to identify potential additional fields, custom matching fields, and payment difference reasons.
To create a new deployment navigate to CUSTOMIZATION->SCRIPTING->SCRIPTS. Set the type filter to “Map/Reduce” and the from bundle filter to “298954”. Locate the script that is named “BS MR Single Value Matching” and press view on the line.
On the page that opens navigate to the subtab “Deployments” and click on the button labeled “Deploy script”. If only one deployment is needed you could also edit the default provided deployment. Further steps will remain equal.
On the script deployment page that opens populate the following fields in section
Name: We recommend using a naming convention that identifies clearly for which account this deployment is. When later multiple deployments exist it's much easier to find the one related to your account
Status: Scheduled
Schedule: Check the radio button “Daily event”
Start time: We recommend setting this an hour before the company opens
Repeat: Chose here how often the script should run.
Check the checkbox “No end date”
Now click on the subtab labeled “Parameters” and set the following information:
Bank statement configuration record id: Enter here the internal id from the bank account configuration. This is visible in the bank account configuration list when navigating to SETUP->BANK RECONCILIATION SETUP->BANK ACCOUNT CONFIGURATIONS. The id is also visible in the URL when you view or edit a bank account configuration.
Saved Search Bank Statement Transactions Lines: Enter here the internal id from the saved search that targets the bank statement transaction lines. When no value is entered the system will be using the default search: Unmatched Bank Statement Transactions and extend this search with the correct parameters. To improve performance or limit date range (due to historical data) we recommend creating a copy of the default search
Bank Statement Matching Field: If matching is wanted on a specific field from the bank statement line then enter here the internal id from this field. If none entered the system will take by default the description field and will take into account all additionally imported fields. If the default description field is used then make sure it holds a single unique value.
Saved search Transactions To Match: Enter here the internal id from the saved search that targets the transaction available in Netsuite to which the system could potentially match the bank statement transaction lines. When no value is entered the system will be using the default search: BS Transactions Available for Single Value Matching and extend this search with the correct parameters. To improve performance or limit date range (due to historical data) we recommend creating a copy of the default search
Enable Matching On Open Transactions: Check this checkbox if the deployment should match open transaction. When not checked the deployment will match against closed transactions.
Enable Debug: Only needed to check if debugging is needed. Leave it unchecked for better performance
Debug Save Transaction Search: Only needed to check if debugging is needed. When enabled the user must remove the created search after each run.
Now save the deployment and the configuration is completed.