Fast Four Bank Reconciliation is designed to have 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
When using scheduled matching, existing bank statements are re-matched using the settings on the Bank Account Configuration (Setup>Bank Reconciliation Setup> Bank Account Configuration) record. The result is the same as matching on import, but it can handle more data.
On the configuration record, check ‘Disable Automatic Matching on Import’
On the configuration record, check 'Enable re-matching of existing statements
Go to the scheduled script ‘BS Scheduled Matching’. On the deployment record, set an appropriate schedule (f.i. every hour).
Now all statements not fully matched will be automatically evaluated for re-matching. Also on the statement record a button appears to run the matching in the background.
Single Value Matching
When the Description on the statement line contains the exact value to be matched (i.e. when the description is a payment service provider reference), the statement is eligible for single-value matching. This is a very efficient way of matching and it can handle virtually unlimited volumes of data.
Single Value Matching is most often used for online payment gateways such as Paypal, Adyen and Stripe.
Every statement line is matched against NetSuite transactions based on the Matching Parameters listed on the statement (if no matching parameters listed, only the Document Number is taken into account), similar to the behavior of Match Open Transactions on Document Number or Parameters and Match Closed Transactions on Document Number or Parameters.
Other matching options and matching preferences are excluded.
To configure Single Value Matching:
On the configuration record, check ‘Disable Automatic Matching on Import’
If you wish to limit the Bank Statement Transactions that are matched, create a saved search based on this default search: Unmatched Bank Statement Transactions (customsearch_bs_unmatch_bs_trans) (do not remove column). For most use cases, the default search will suffice.
Go the the Map/Reduce script BS MR Single Value Matching
Create a deployment (button Deploy Script) with an appropriate schedule to run (you may also create an After Submit script on the Bank Statement record that automatically triggers this M/R script). Please note the different type of IDs requested on the deployment>Parameters subtab section - the internal ID of the Bank Account Configuration is a number, whereas the saved search ID is usually a string of text. The internal ID of the Bank Account configuration can be found at Setup>Bank Reconciliation Setup>Bank Account Configurations. If the list of the Bank Account Configurations do not display the internal ID, go to Home>Set Preferences and in the Defaults section mark the checkbox “Show Internal IDs“, save the changes and return to the previous page.
On the deployment > Parameters, enter the internal ID of a Bank Account Configuration record. Only Bank Statement Transactions linked to this configuration record will be auto-matched.
On the deployment > Parameters, enter the saved search ID ‘customsearch_bs_unmatch_bs_trans’ or a search you defined based on the default search.
Repeat the above steps for other bank account configurations. So each bank account configuration will get its own deployment record.