Getting started with Pascal Transaction monitoring – Full configuration manual

Introduction 

Pascal Transaction monitoring helps you quickly identify unusual financial activity without manually reviewing every transaction. It uses Client profiles and custom Alerts to automatically detect deviations from expected client's activity and behaviour and bring them straight to your Dashboard. 

In Transaction monitoring, you define Rules designed to detect irregularities that deviate from your client's typical activity, specifically within their transactions. These rules help flag unusual behaviour, allowing you to review alerts and make inform decisions on how to proceed. 

This focussed approach helps reduce irrelevant noise and saves time by directing your attention to what matters most. You can assess each alert individually or in bulk, ensuring that potential risks are properly evaluated. 

With additional features like Notes and Reports, a clear audit trail, and more, Transaction monitoring supports accurate, efficient, and compliant reviews.

 

 

Initial setup 

Before you can start using Transaction monitoring, a few essential configurations need to be completed. These setup guidelines and inputs ensure the system is properly configured and aligned with your monitoring goals and client data. 

The sections below will guide you through the required setup process.  

  

Transaction monitoring Policies 

Policies define the core rules of how Transaction monitoring operates for you. Here you can configure Maximum amount for the weekly Objective transaction report, General settings and rules for Dormant bank accounts and Timezone, and create your Alerts configuration. 

 

Maximum amounts

The Maximum amounts Policy allows you to define default threshold values using different currencies. When a client's transactions exceed these predefined limits, Pascal automatically generates a weekly Objective transaction report which is sent to you via email depending on your account settings. This report highlights all relevant transactions, and the clients involved. 

In addition to the direct clients, the report also highlights related entities such as clients sharing bank accounts details (also known as a joint account) or marked as Linked clients. This gives you a broader view of potentially connected activity and helps you assess risk more effectively. 

To add Maximum amounts the below steps can be followed: 

1. Press on the Organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Click on the Transaction monitoring tab in the top bar of the window. 
4. In the Maximum amounts card, press the Add maximum amount button. 
5. In the new side panel, fill in the name of a client type. If this should be the standardly chosen client type, turn on the option Default maximum amount. 
6. In the Currency section, select the currency this amount should be in, to conform to the rule. You can type in this section to filter towards the correct currency. You can add multiple currencies per each client type you create.  
7. In the Amount field, fill in the amount you would like to be set as the threshold. 
8. Click on the Add maximum amount button, if more maximum amounts in other currencies should be included. 
9. Press the Save button when you are done. 
10. To edit your input, click on the pencil icon, and repeat steps 6 until and including 9.  

Once configured, an Objective transaction report will be sent to you every Monday at UTC+0. The report covers transactions from the previous week, starting Monday at 00:00 and ending Sunday at 23:59. This means that each Monday’s report reflects all client transaction activity from the week before. It includes all transactions made during that period and highlights any activity that exceeds the defined Maximum amounts thresholds. If you have opted to receive reports even when no relevant activity is found, you will receive an email confirming that no reportable activity occurred. 

To enable the auto-send of the Objective transaction report, follow these steps: 

1. Press on the organisation name or your initials in the top right corner. 
2. Click on Account settings besides the organisation name. 
3. Click on Configuration tab in the top bar of the window. 
4. Head to the Transactions card, click on the dropdown, and select Yes to activate the report delivery. Then, in the other dropdown select Yes if you wish to receive an email notification when no reportable activity occurred. 

 

 

In the General card you can define the number of days after which Bank accounts are considered Dormant and set the Timezone that Transaction monitoring should follow when evaluating End of day alert rules.  

 

Dormant

To define when your clients Bank accounts should be considered as Dormant: 

1. Press on the organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Click on the Transaction monitoring tab in the top bar of the window. 
4. Scroll to the General card and locate the Bank accounts become dormant after option. 
5. Click inside the input field and enter the desired number of days. Use whole numbers only. 
6. The arrows can be used to mark up or down the value entered. 

 

Timezone

Transaction monitoring uses UTC+0 as the default reference point for End of day alert rules. However, if you are operating in a different timezone, alerts may be triggered before your actual end of day. To ensure alerts are evaluated at the correct time for your region, select your local timezone in the Policies. This ensures alerts are triggered in line with your operational hours and reduces the chance of premature or inaccurate alerts. 

To select the Timezone follow these steps: 

1. Press on the organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Click on the Transaction monitoring tab in the top bar of the window. 
4. Scroll to the General card and locate the Timezone dropdown. Click on it, and in the search type the name of the region/area or the major city associated with it and select it to save. You can also scroll through the list.

 

Alerts 

The Alerts section is the core of the entire Transaction monitoring system. Once configured, it determines when alerts are triggered and how they appear in each Client’s profile. You can access the full configuration at any time, providing a clear overview of both Active and Inactive alerts across your organisation.  

To set alerts, Pascal offers the Alert builder - a flexible tool designed to support a wide range of alert types, from simple to complex, depending on your monitoring strategy. Each alert is modular and customisable, built using components from the Rule library. Some rules are mandatory and serve as Base rule, upon which additional rules can be also used independently.  

 

The Alert builder is divided into two main parts: General settings and Rules and conditions. Below is a breakdown of each part. 

 

General settings 

This section includes key configuration options:

• Name: Alerts are initially named “Standard Alert,” but this can be changed to suit your needs. 

• Time range: Defines the period the system evaluates when applying rules. Options include Daily, Weekly, Monthly, Quarterly, Yearly, and None. Each Time range compares the current and previous equivalent period, for example, Daily checks today and yesterday, Weekly checks this week and the pervious, and so on. Selecting None disables time-based filtering, allowing alerts to trigger regardless of date. 

• Alert timing: Automatically set and not editable. By default, alerts are set as Immediate. Adding specific rules, such as Account balance and Dormant rules, the Alert timing will switch to End of day. (Click here to read more in the Alert timing). 

• Default assignee: Alerts are Unassigned by default but can be automatically assigned to a specific user or group. 

 

 

Rules and conditions 

This section defines the specific conditions that trigger an alert. 

To create a new alert, you must start by selecting a Base rule. Available base rules include: 

• Transaction value 

• Transaction volume 

• Bank accounts 
   

These rules form the foundation of your alert logic. If you choose Transaction value or Transaction volume as your base, you can attach any additional rules except Bank accounts. If you start with Bank Accounts, some rule options will be disabled (greyed out), and a visual indicator will guide you accordingly.  

This structure ensures that alerts are built on a logical and compatible rule set, maintaining consistency and reliability in your monitoring process. 

 

Rule library 

The Rule library contains all available rule types that can be used to build new alerts or add to existing ones. These rules define the specific conditions under which an alert will be triggered, enabling flexible and targeted monitoring. 

Some rules are mandatory and serve as Base rules, while others can be added to refine and enrich the alert logic. Each rule includes its own Condition(s), which may take one of the following forms:  

• A toggle to apply a specific condition. 

• A dropdown with Include or Exclude options, paired with a free-text field. 

• A dropdown with Equals, More than, Less than, or Between, followed by a numeric input field (with up/down arrows to adjust the value). 

Each rule can be added only once per alert. If you wish to create multiple alerts using the same rule, you must configure them individually. To streamline this process, you can use the Duplicate Alert feature (read more here insert link). 

 

Alert timing 

Alerts triggered by the Bank account balance and Dormant bank account rules follow End of day timing. This means the rule evaluates data from the previous calendar day, and the alert is triggered at 00:00:00 on the following day, based on the selected time zone. A slight delay may occur due to processing time. All other rules trigger alerts follow ‘Immediate’ Alert timing, meaning they are generated as soon as a relevant transaction is added to the client’s profile. Alerts will only activate within their defined Time range. 

 

Rule breakdown 

Below is a list of all available rules in the Rule Library, along with a short explanation of what each rule monitors: 

• Bank accounts: Tracks the number of different bank accounts held by a client. 

• Bank account balance: Monitors the most recent balance of a client’s bank account.  

• Client age: Calculates the age of a client based on their date of birth (applies only to Person-type clients). 

• Transaction value: Sets a threshold for the total monetary value of transactions. You can specify one or more currencies in the same condition. 

• Transaction volume: Sets a threshold for the total number of transactions. 

For these rules, Numeric conditions apply. You can choose from the following conditions’ dropdown options: Equals, More than, Less than, and Between. Each option allows you to input a numeric value. The up and down arrows can be used to adjust the value incrementally. Only one option from the dropdown can be applied per rule. 

 

• Bank account type: Identifies the type of bank account (For example: Savings, Checking, Loan, Fixed deposit). Custom types can also be added. 

• Client country: Indicates the country of a Business client or the nationality/-ies of a Person. 

• Client risk: Reflects the overall risk level based on the client's profile. 

• Client risk indicator: Flags specific risk indicators associated with the client. 

• Client profession: Indicated the profession of the client using free-text input (applies only to Person-type clients). 

• Tax haven risk: Assesses risk based on the transaction associated with the country of the client or the counter party's. 

• Transaction type: Filters transactions based on their type (derived from uploaded transaction data). 

For these rules, Include or Exclude dropdown apply. You can choose whether to Include or Exclude the specified values entered by you as free-text input in the relevant field. 

 

• Dormant bank account: Detects when a previously dormant account becomes active. 

• Client account age: Evaluates the age of the client’s account based on its creation date (for both Person and Business types). 

• Client type: Specifies whether the client is a Person or a Business. 

• Client SIC codes: Selects one or more SIC codes risk levels to include. 

• Transaction direction: Filters transactions by direction as either incoming or outgoing. 

For these rules, a dropdown or a toggle button applies, with which you can select the desired condition. 

Conveniently, the Rule Library includes a Search function to help you quickly locate specific rules. Each rule can be combined with others to create powerful, targeted alerts that align with your organisation’s risk policies and detection goals. 

 

Alert creation 

The Alert builder is used to create new alerts, update existing ones, or duplicate alerts for reuse. Alerts are considered Active only after they have been Published. All published alerts, both Active and Inactive, can be found in the Alerts table at the bottom of the Transaction monitoring policies page. 

 

Create a new alert  

By default, newly created alerts are marked as Active, but you can manually set them to Inactive if needed. Regardless of status, an alert must be Published to be saved and added to your configuration. 

To publish an alert, the following conditions must be met: 

• At least one Base rule must be added: Transaction Value, Transaction Volume, or Bank Accounts. 

• All required fields must be completed, and there must be no validation errors on the screen. 

Only then will the Publish button become clickable. 

 

Creating a new alert can be done by following these steps: 

1. Click on your organisation name or initials in the top-right corner. 
2. Select Settings next to the organisation name. 
3. Navigate to the Transaction monitoring tab in the top bar. 
4. Scroll down to locate the Alerts section. 
5. Click Create alert to open the Alert Builder. 
   
   Configure the Alert:
   • Click Rename next to the default alert name to give it a meaningful title. Enter the new name in the popup and click Rename to save.
   • Select the appropriate Priority from the dropdown.
   • Choose the desired Time range from the dropdown.
   • Set the Default assignee by selecting a user or group from the dropdown (default is Unassigned).
   • Go to the Rule Library and click Add next to any rule you wish to include.
     
     You must include at least one Base rule. Some rule combinations are not allowed. Visual indicators will guide you when this occurs.
     
     Each added rule appears under the Rules section in its own card, showing its name and editable conditions. Use the Trash icon to remove any rule.
6. Once satisfied with your configuration, click Publish in the top-right corner.
   If required fields are missing, the screen will automatically focus on them and display red validation errors. Correct these and click Publish again. 
7. A green popup will confirm: “Your alert has been successfully saved.” 
8. Click Back to return to the Transaction monitoring Policies view. 

 

Edit an existing alert 

To keep your alert configuration up to date, you can edit existing alerts at any time. To edit an existing alert, follow these steps: 

1. Click on your Organisation name or initials in the top-right corner. 
2. Select Settings next to the organisation name. 
3. Navigate to the Transaction monitoring tab. 
4. Scroll down to the Alerts section. 
5. Click on the name of the alert you wish to edit. the Alert builder will open with the alert’s current configuration. 
   
   Make your changes: 
   • Click Add next to any new rules you want to include. 
   • Use the Trash icon to remove irrelevant rules. 
   • Edit any fields or rule conditions as needed. 
6. Click Publish to save your changes. 
7. If required fields are missing, validation errors will appear. Correct them and click Publish again. 
   
   Mass Closure Prompt:
    
   If the alert has already been triggered and has pending Open alerts, a pop u will appear with the Mass closure option: 
   • Check the box to close all open alerts. 
   • Leave it unchecked to keep them open. These alerts will display a small question mark icon with a tooltip indicating the alert was removed or changed. 
   Provide a meaningful comment explaining the changes made, then click Continue to save and publish. 
   
   If the alert: 
   
   • Was triggered but has no open alerts, or 
   • Was never triggered, 
   You will still be prompted to add a comment before publishing. 
   The alert’s status (Active/Inactive) will remain unchanged unless you manually update it. 
8. A green popup will confirm: “Your alert has been successfully saved.” 
9. Click Back to return to the Transaction monitoring Policies view. 

 

Duplicate an alert 

Duplicating an alert is a quick way to create similar alerts without starting from scratch. You can only duplicate saved alerts. 

When duplicated: 

• The alert’s full configuration is copied. 

• The new alert is marked as Inactive. 

• “– Copy” is added to the alert name. 

• The alert is not saved or published until changes are made. 

A green popup will confirm: “Your alert [alert name] has been successfully duplicated.” 

Duplicating an alert can be done by following the below instructions: 

1. Click on your Organisation name or initials in the top-right corner. 
2. Select Settings next to the organisation name. 
3. Navigate to the Transaction monitoring tab. 
4. Scroll down to the Alerts section. 
5. Click on the name of the alert you wish to duplicate. 
6. Click Duplicate, then confirm in the popup. 
   
   Finalise the Duplicated alert process: 
   • Optionally, click Rename to update the alert name. 
   • Make any necessary changes to rules, conditions, or settings. 
   • Toggle the alert to Active if needed. 
   At least one change is required before the alert can be published. 
7. Click Publish to save the duplicated alert. 
8. If required fields are missing, validation errors will appear. Correct them and click Publish again. 
   
   Add a comment in the Update alert popup for audit purposes and click Continue. 
9. A green popup will confirm: “Your alert has been successfully saved.” 
10. Click Back to return to the Transaction monitoring Policies view. 

 

Remove an alert and Mass closure  

When alerts become irrelevant, you can remove them to reduce noise. Removed alerts cannot be restored. The removal affects only alerts with an Open status. Alerts with the following statuses are not affected: 

• Under investigation or Escalated: These are actively being reviewed. 

• False positive or Suspicious: These are considered resolved. 

Removing alert, depending on the situation, can trigger a Mass closure of alerts.  

• If the alert has been triggered and has Open alert status at the time of removal, a popup will appear: 

• • Check the box to Mass close all open alerts. 

• • Leave it unchecked to keep them open. These alerts will display a question mark icon with a tooltip indicating the alert was removed. 

• If the alert was never triggered, it will be removed with a confirmation popup. 

Removing an alert from the configuration does not delete the alerts themselves, regardless of their status. 

To Remove an alert, follow these steps: 

1. Click on your Organisation name or initials in the top-right corner. 
2. Select Settings next to the organisation name. 
3. Navigate to the Transaction monitoring tab. 
4. Scroll down to the Alerts section. 
5. Click on the name of the alert you wish to remove. 
6. Click the Remove button (marked in red) in the top-right corner. 
7. In the Remove alert popup, click Confirm. 

If open alerts are detected, Pascal will prompt you to choose whether to mass close them or leave them open, and how many alerts can be affected. Select your preferred option and click Confirm to finish. 

 

 

Resolve an alert 

To resolve your alerts, please refer to the Resolving alerts section found in Main work flow (insert link) 

 

Transaction monitoring Risk 

The Risk section is a flexible configuration that allows you to create a custom-made client risk evaluation score within the transaction monitoring system. In this framework you can set the Risk profile, where you define how long a client accounts are considered "new" and assign a risk score to it. You can then configure Risk indicators, which include default options like Sanctions and PEP, and also allow you to create custom indicators with their own scores. A direct link to Screening risk settings is provided for quick access if adjustments are needed on that matter. 

For Business type clients, SIC codes let you group industries under unified labels and assign risk levels to each. In addition, you can find the customizable Country risk classification settings, where you can mark Tax haven countries and visualize them on a global map for easy reference. Lastly, there is also the Risk scores system that enables you to assign values to each risk factor and define Breakpoints, which determine the overall client risk level displayed in their profile. 

Each of these elements contributes to a flexible and comprehensive risk framework. Together with the Policies, they support accurate alerting and informed decision making within your transaction monitoring process. 

 

Risk profile  

The Risk profile card allows you to define key parameters that influence how client risk is calculated. It includes settings for Account creation, Risk indicators, and Screening related risk factors, all of which contribute to the overall client risk score. 

 

Account creation 

Use this setting to define within how many days a client’s account is considered a new account. After this period, accounts are automatically classified as old accounts. This important distinction influences how alerts are triggered based on account age. Once the number of days is decided, you can assign a risk level to new accounts according to your risk strategy. 

As long as the Account creation date falls within the defined timeframe, the assigned risk score will apply. Once the number of days is exceeded, the account’s risk score will automatically switch to Very low. For the former, a small red label “Less than [number of days] day/s” will appear as an indication. 

To apply these setting, the below steps can help: 

1. Press on the Organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Click on the Transaction monitoring tab in the top bar of the window. 
4. Just below it, click on the Risk tab to reveal the Risk profile card and locate the Account creation.  
5. Click inside the input field and enter the desired number of days. Use whole positive numbers only. The arrows can be used to mark up or down the number entered. 
6. Below click on the associated risk dropdown and select the desired risk level match your days selection. 
7. Once applied, click on the Save button located at the top of the card. The Undo button becomes available only when there are unsaved changes, which is also indicated by a visual warning massage on the card.  

 

Risk indicators 

Risk indicators are specific labels used to assess the potential risk associated with a client. They help identify clients who may require closer scrutiny based on predefined or custom criteria. 

This feature includes two default risk indicators, Sanctions and PEP, each with a default assigned risk score. You can choose to use them as is, modify their scores, or remove them entirely. Additionally, you can create your own custom indicators to reflect your organization’s unique risk considerations. These custom indicators can be edited at any time to adapt to changing policies or regulatory requirements. 

It is important to note that no matter how many indicators a client has, the highest risk score among them will determine the overall risk score for the Risk indicators input shown in the client’s profile. 

To add new Risk indicators and edit existing, these steps can help: 

1. Press on the organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Click on the Transaction monitoring tab in the top bar of the window. 
4. Just below it, click on the Risk tab to reveal the Risk profile card and locate the Risk indicators section. 
5. Click on Add risk indicator button. 
6. In the new empty field-box that has just appeared, type your new risk indicator name. 
7. Then, on the right side next to it, click on the dropdown button and select the desired risk level to assign to your new risk indicator.  
8. Once added, click on the Save button located at the top of the card. The Undo button becomes available only when there are unsaved changes, which is also indicated by a visual warning massage on the card. The Undo button appears every time there are unsaved changes, such in the case of Update and Remove are made yet not saved. 

You can update your existing risk indicators list at any time. Follow the below steps: 

1. Click on the name of the relevant risk indicator and make the necessary change. The dropdown of the risk level score can modified if needed. 
2. To finish, click on the Save button located at the top of the card. 

You can also remove existing risk indicators when they are no longer needed or relevant to your risk assessment process. These steps can help: 

1. Click on the Trash icon button next to the relevant risk indicator. Should you wish, Sanction and PEP can be removed as well. 
2. To finish, click on the Save button located at the top of the card. 

It is important to point out that removing a risk indicator from the settings does not remove its label from a client’s profile. It only removes its associated risk score, which may trigger a recalculation of the client's overall risk depending on the configuration. In some cases, this change may not affect the overall score. To fully remove the label, you must manually edit the client’s profile. 

• If you choose to keep the removed label in the client's profile for record-keeping purposes, it will no longer influence the client’s profile risk score. However, if you later re-add the same risk indicator, whether with a new score or the original one, the client’s risk profile will automatically update. The system will then apply the highest applicable score from all the risk indicators applied to the client, which may affect the overall client risk calculation and result in a different risk level. 
• If you manually removed the label from the client’s profile before re-adding the risk indicator, you will need to manually re-add it to the client. Once added, the overall risk score will be recalculated to reflect the changes. 

Any changes made to the settings of the Risk indicators can impact alert rules tied to them and may also affect the client’s overall risk level, depending on your configuration. 

 

SIC codes 

Standard Industrial Classification (SIC) codes are used to categorize businesses by industry and apply only to Business-type clients. Since most SIC codes follow a recognizable pattern, Pascal  allows you to group similar codes under a single label using special operators. This makes it easier to manage and assign risk levels across related industries. 

in Pascal, SIC codes are built from a defined base code, a label of your choice, and an assigned risk level. Both the code and its label are displayed in the client’s profile when the code is recognized and configured. If a SIC code is entered but not set in the configuration, it is considered Unknown and only the code itself will appear, without a label, and it will automatically be associated with a Very low risk level (this default cannot be changed). When multiple SIC codes are present, the client’s overall risk level is determined by the highest risk level among all known codes. 

To help you with the implementation, Transaction monitoring was designed to support special operators that make pattern matching more intuitive and powerful. These operators are the percent sign % and the underscore sign _, each serving a distinct purpose. 

 

The % (precent) operator - flexible matching 

The % operator is inclusive and allows for flexible matching. You can place it before, after, or within a sequence to match any number of letters or digits. 

Examples: 

• Using 50% with the label Retail and a risk level of Low will match codes like 50, 500, or 501b, but not 05 or 5. 
• Using %007 with the label Bond and a risk level of High will match codes like 555007 or JB00771, but not 1073 or 0DR07. 
  
  

The _  (underscore) operator - strict matching 

The _ operator is strict and matches exactly one character in a specific position. 

Examples: 

• Using _MI5 with the label James and a risk level of High will match 1MI5 or BMI5, but not NNMI5 or MI5 alone. 

• Using 777_ with the label Triple and a risk level of Low will match 7771 or 777B, but not 1777 or 17775.   

 

 

To add SIC codes, follow these instructions: 

1. Press on the Organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Click on the Transaction monitoring tab in the top bar of the window. 
4. Just below it, click on the Risk tab. 
5. Scroll the page down, until you see the SIC codes card. 
6. Click on Add code. In the newly appearing blue card component appearing above, type in the Code, the label and select from the dropdown the risk level. 
7. To finish and save click on the Add button. 

Once a SIC code is added, it cannot be edited. To make changes, you must delete the existing entry using the Trash icon and re-add it with the desired configuration. 

It’s important to note that no matter how many SIC codes a client has, the highest risk score among them will determine the SIC codes risk input shown in the client’s profile.  

To remove a SIC code, see the below steps: 

1. Press on the Organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Click on the Transaction monitoring tab in the top bar of the window. 
4. Just below it, click on the Risk tab. 
5. Scroll the page down, until you see the SIC codes card. 
6. Click on the Trash icon next to the name of the SIC code you wish to remove. 

Removing a SIC code from the settings/configuration removes only the label and score, but the original SIC code entries remain as is in the Client's profile. If you re-add the same code with a new or previously used score, Pascal will automatically update the Client’s profile and recalculate the risk based on the highest applicable SIC code score.  

These changes can impact alert rules tied to SIC codes and may also affect the client’s overall risk level, depending on your configuration. 

 

Tax haven risk 

Tax havens are jurisdictions known for offering low or no tax rates, often used to shelter assets or conduct financial activities with minimal regulatory oversight. In the context of transaction monitoring, identifying these countries is essential for assessing potential risk exposure. 

Since every transaction includes both the Client’s bank country and the Counter party’s bank country, this setting allows you to assign a specific risk level to either or both. You can select any country to mark as a tax haven and define its associated risk score. By default, all countries are set to Unknown risk, and alerts will be triggered based on your configuration, whether a match is found on one side or both. 

All configured country risks are visually represented on a dynamic world map with a colour coded risk legend, making it easy to review and adjust your classifications. 

To define the Tax haven risk, follow these steps: 

1. Press on the Organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Click on the Transaction monitoring tab in the top bar of the window. 
4. Just below it, click on the Risk tab and scroll downward to the Country Risk Classification section. 
5. On the right hand side, click on the Edit button. 
6. In the new open page, a table with a country list and Risk. Locate the Search countries field box on the top part and type inside it your requested country.  
   
   Alternatively, page through the countries list by clicking on the page numbers at the bottom of the table, and use the right and left arrows to locate the requested country. 
7. Once the requested country is found and shown, assign the relevant Risk level by clicking on the risk dropdown button.  
8. To finish, click on the Save button on the top right side.  
9. To edit your selection or add risk level to additional countries, follow these steps from the start. 

 

Risk scores 

Pascal allows you to define your own Risk score system by assigning values to evaluate client risk levels. These levels include: 

• Very low 
• Low 
• Moderate 
• High 
• Very high 

The Risk score system is built from two components: Risk classification and Breakpoints. 

Risk classification 

Risk classification involves assigning a numeric value to each risk level. These values: 

• Must start at 0 and increase consecutively. 

• Cannot be repeated or negative. 

Each risk entity in a client's profile contributes its assigned value to the overall score. This cumulative score is then used to determine the client's final risk level. 

 

Breakpoints 

Breakpoints define the score ranges that correspond to each risk level. Using the same five levels, Very low to Very high, you assign a minimum score for each category: 

• The first breakpoint must start at 0. 

• Each subsequent level must have a higher minimum score than the previous one. 

This setup allows Pascal to automatically calculate a client’s risk level based on the sum of all individual risk scores. 

 

Setting up Risk values and Breakpoints 

To configure your risk scoring system: 

1. Navigate to Transaction monitoring Settings. 
2. Within the Risk card, click the Edit button. 
3. In the Risk classification section, assign numeric values to each risk level. 
4. In the Breakpoints section, define the score thresholds that determine each risk level based on the total score from answered risk questions. 

This configuration gives you full control over how risk is evaluated and ensures that client onboarding aligns with your organisation’s risk policies. 

 

Clients and Bank accounts bulk imports 

While Main workflow Pascal Transaction monitoring helps cover the basic of creating Clients and Bank account individually, this section focusses specifically on how to add multiple Clients and Bank Accounts in bulk using Importing. 

 

Import bank accounts 

To ensure a smooth bulk import process, it is highly recommended to start by importing bank accounts first. 

To successfully import bank accounts in a fast and efficient way, you must use a CSV or Excel template, which can be downloaded at any time from the Importing tab within the Organisation Settings section. 

To import bank accounts, follow these instructions: 

1. Press on the Organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Confirm the Organisation tab is marked, at below click on Importing, and locate the Import bank account card below it. 
4. An example of the client import file can be downloaded by pressing the CSV or Excel options.  
5. Within the Excel bank account’s import template file, the columns account_type, account_name, account_number, swift_code, currency, bank_name, clients_1, and clients_2 are present. 
6. Use the example data provided inside the template file to correctly populate each field. Once completed save the file. 
7. With the imported file filled in and ready, the file can be imported via Drag and drop or by the using the click to upload button.  
8. After the preview of the file is reviewed and it is ensured the validation states valid, the button Import can be clicked to import all bank accounts. 
9. After importing the bank accounts, Pascal will Pascal automatically checks for matches with existing known bank accounts and known clients in the system using the Bank account number. 
   1. If no match is found: the imported bank account is added as new to both new clients and existing clients. 
   2. If a partial match is found (only Bank account number match, but other fields differ): Pascal copies the existing known bank account details from the old client to the new client, ignoring the imported data. 
   3. If a full match is found: the bank account is added to the new client using the existing data from the system. 
      
      Invalid Bank accounts rows will not be imported. 

 

Import clients 

Importing clients in bulk is a fast and efficient way to add multiple client profiles to Pascal at once. To successfully import clients, you must use a CSV or Excel template file, which can be downloaded anytime from the Importing tab within the Organisation Settings screen. 

These templates contain multiple fields required to create client profiles. Ensuring that all fields are properly populated will result in well-structured profiles, which significantly enhances the efficiency of transaction monitoring. 
 

To import clients, the following steps can be used: 

1. Press on the organisation name or your initials in the top right corner. 
2. Click on Settings besides the organisation name. 
3. Confirm the Organisation tab is marked, at below click on Importing. 
4. Scroll down to reach the Import clients card. 
5. An example of the client import file can be downloaded by pressing the CSV or Excel options.  
6. Within the Excel client’s import template file the columns titled type, name, address, phone_number, email, profession, gender, incorporation_date, company_number, country, nationalities_1, nationalities_2, date_of_birth, standard_industry_classifications_1, standard_industry_classifications_2, account_creation_date, risk_indicators_1, risk_indicators_2, estimated_incoming_amount, estimated_incoming_currency, estimated_outgoing_amount, estimated_outgoing_currency, international_transfers, assignee, collaborators_1, collaborators_2, user_risk_score, and description are present. 
    
   Use the example data provided inside the template file to correctly populate each field. Once completed save the file. 
7. With the imported file filled in and ready, the file can be imported via Drag and drop or by the using the click to upload button.  
8. After the preview of the file is reviewed and it is ensured the validation states valid, the button Import can be clicked to import all clients. 
9. After importing the clients, Pascal will create all the clients in the system. Clients that did not have a known bank account present in the system will not be visible in Transaction monitoring until their associated bank accounts are created. 
   
   To ensure complete visibility and a smooth workflow, it is highly recommended to import bank accounts first and then use the import clients.