3.1 Setting up Jurisdiction Codes, Scenarios, and Thresholds

This section outlines the steps to duplicate your transaction monitoring system in OFSCA. You'll specify jurisdiction codes or segments at your institution, choose the scenarios that will be monitored, and set thresholds for each scenario.

Figure 3-3 Set up Jurisdiction Codes, Scenarios, and thresholds

Description of "Figure 3-3 Set up Jurisdiction Codes, Scenarios, and thresholds"

To set up jurisdiction codes, scenarios and thresholds, follow these steps:

Note:

Click Download SQL Script to download SQL script and execute the script against data in Oracle's Financial Crime Data Model to extract the required data

1. Click Download Template to download the template and format the extracted data into CSV file.nn

   Note:

   • You should not modify jurisdiction, scenario_name, and scenario_id in the CSV file.
   • If you are not using the default risk tiers (RR/MR/HR) at your institution, each of these thresholds (for example, Min_Amt_RR, Min_Amt_MR and Min_Amt_HR) should be set to the same value.
2. To upload the CSV file with the necessary data, simply drag and drop it into the designated field or click on the icon to open the file selector dialog box and choose the file. Once the CSV file is loaded, the following window is displayed.

   Figure 3-4 Uploaded CSV File

   
   

   
   Description of "Figure 3-4 Uploaded CSV File"

   
   

   Note:

   You can remove the uploaded CSV file if required by using the Clear button.
3. Click Continue to navigate to the Map jurisdiction codes to segments step.
   Or Click Discard to discard the current activity and return to the Configure your Transaction Monitoring System window. Click Start to start the Configure your Transaction Monitoring System from the initial steps again for configuration