...
On the page that opens navigate to the subtab “Deployments” and click on the button labelled labeled “Deploy script”. If only one deployment is needed you could also edit the default provided deployment. Further steps will remain equal.
...
Bank statement configuration record id (custscript_bs_mr_configid): 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 (custscript_bs_mr_searchid): 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 (custscript_bs_mr_match_field_stmt): 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 (custscript_bs_mr_searchid_tran): 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.
| Note |
|---|
If you provide ID of your custom saved searches (Saved Search Bank Statement Transactions Lines & Saved search Transactions To Match) on the Parameters subtab, please make sure that your custom saved searches contain all the columns from the Results section of our default saved searches. Your custom saved searches can be extensions of our default saved searches and the default columns shall not be removed. |
...
Now save the deployment and the configuration is completed.
Behavior
The single value matching uses the setting from the bank account configuration. The following settings are taken into account when the script tries to match against transactions
Payment Difference Reason Automation: The matching will be using the setting defined here to match also transactions that are within the threshold from the payment difference threshold settings and will then apply the defined logic from the selected payment difference reason
Bank Statement Matching Parameter: When matching parameters are set the system will use only these matching parameters. When multiple are set the system will be using all options defined
Matching Preferences: The preferences defined here won’t be respected, the algorithm is matching only bases on the one-to-one relationship with the single value.