Main workflow Pascal Transaction monitoring

Introduction

Pascal Transaction monitoring is a dynamic tool designed to help you efficiently manage and review financial activity. Instead of manually checking each transaction, Pascal uses client profiles and custom alert configurations to automatically flag deviations from expected patterns, bringing relevant alerts directly to your dashboard. This allows you to concentrate on investigating and resolving risky or unusual activity. With an intuitive friendly interface and additional features like notes and reports, Pascal supports a clear audit trail and improves overall client handling and transaction monitoring.

 

Creating a client

Creating a Client begins with building a client profile, which is a crucial first step in Transaction monitoring. It lays the foundation for accurate client risk assessment and effective alert triggering and resolvement. Every client must be categorised as either a Person or a Business, which determines the structure and available fields in their profile.

Each client profile is built from two main components: a General settings card and a Risk profile card. Depending on the selected client type, Pascal displays both shared and type-specific fields. Shared fields include Address, Email, Phone number, Account creation date, and Risk indicators. Person-specific fields include Date of birth, Gender, and Nationalities, and Business-specific fields include Date of incorporation, Country, and SIC codes. This classification ensures Pascal applies tailored logic and monitoring rules based on the client type.

The Risk profile card automatically calculates an overall risk score using predefined settings configured in Pascal Transaction monitoring. This score reflects the client's risk level based on the data provided. If needed, you can manually override this score using the Modify overall client risk field to better reflect a different risk score, if needed.

 

 

Client profiles can be updated at any time to reflect changes and updates. It is highly recommended to complete all relevant fields, even those not marked as mandatory. A fully populated profile enriches the client’s data and enables Pascal to apply its risk assessment features more effectively, resulting in more accurate and meaningful alerts.

 

A new client can be created from the Home page and the Clients page. The instruction below covers how to do this:

1. Click on the button New client.
2. In the new side panel, enter the Client name or choose one from the dropdown options, and optionally enter a Description. Note that you cannot choose to use existing clients' names as new ones.
3. Click Next to continue.
4. In the next step, choose between a Person or a Business as your client type.
   1. For a Person, the following fields can be provided: Address, Email, Phone number, Date of birth, Gender, Profession, Nationalities, Account creation date, Risk indicators, and the overall client risk can be modified with the option Modify the overall client risk.
   2. For a Business, the following fields can be provided: Address, Email, Phone number, Date of incorporation, Country, SIC code, Account creation date, Risk indicators, and the overall client risk can be modified with the option Modify the overall client risk.
      
      It is recommended to provide the client with as much relevant information as possible.
5. Click Next to continue.
6. Add one or more bank accounts of the client by using the Add bank account
   1. Fill in the Account name, Bank account, SWIFT code, optionally a Bank name can be provided, Currency and select an Account type from the dropdown or insert your own.
      By default, all newly added accounts are marked as Active. Only by click on the toggle the bank account can be marked Deactivated, or visa versa. 
   2. Press the button Add bank account. Hereafter, more bank accounts can be added to the client following the same process. If needed, click on the pencil icon to edit the information.
      After all bank accounts of the client are provided, the button Next can be pressed.
7. On the next page, Legal ownership of the client can be added.
   1. Select via the dropdown the Assignee and optionally a collaborators.
   2. Optional step: Select a Date of signed structure chart via the date picker is presented.

 

 

Creating transactions

After the client is created, transactions can be added to this client. This can be done in bulk via an import file or manually for singular transactions.

The instructions below indicate how to add transactions via an import file:

1. Head to the Transactions  card on the client overview page and  press the button New transactions.
2. In the newly opened side panel, the options Enter manually and Import from file are given. Select the Import from file option to import multiple transactions at once.
3. An example of the import file can be downloaded by pressing the CSV, Excel, or JSON options. Representing each file type's example file.
4. Within the Excel import file the columns titled ID**, transaction_date*, client_account_number*, client_swift_code*, client_bank_account_country, direction*, counter_party_account_number*, counter_party_swift_code*, counter_party_bank_name, counter_party_name, counter_party_bank_account_country, counter_party_currency, amount*, currency*, balance_after_transaction, description, and type are present.
   
   Columns marked by an * are mandatory fields, while those which are not marked are optional fields. This information is shown as red invalid error in the Import transactions screen which is automatically opened once you attach a file.
   
   ID - If provided and a transaction with the same identifier already exists, it will be skipped. If not provided, an ID will be generated automatically in an ascending order starting with 1,2,3,... . 
5. With the imported file filled in and ready, the file can be imported via the click to upload button in the open dialog. 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 transactions.
6. After importing the Transactions, Pascal will create all valid transactions and match them with the Bank accounts associated in the system. These transactions can be found in the Transactions table in the client's overview page. Transactions that did not have a known bank account present in the system will not be visible until the associated bank account is created.
   

 

 

From here, you will go through the basics of how to review and resolve these alerts efficiently.

 

Resolving alerts

Resolving alerts is a core part of Transaction monitoring, enabling you and your team to assess and respond to potential risk bearing client activity. Alerts are automatically triggered when client behaviour matches predefined criteria set in the Alert builder. Once triggered, alerts are to be reviewed, judged, and resolved appropriately to maintain compliance and ensure accurate risk tracking.

Each alert follows a lifecycle from creation to resolvement which can be viewed across multiple views. Alerts are assigned with statuses that reflect their current state. You can resolve alerts manually or in bulk, depending on the situation. Understanding how alerts behave, where they appear, and how to resolve them is essential for effective monitoring.

Alert views

Alerts in Transaction monitoring are automatically generated when client activity matches the criteria defined in the Alert builder. Each alert contains key information that helps assess its relevance and urgency:

• Created at – Timestamp of alert execution.
• Reason – Name of the alert and an explanation of why it was triggered.
• Client – The associated client.
• Status – Only one status can be active at a time: Open, False positive, Suspicious, Under investigation, Escalated, or Closed.
• Assignee – The name of the user or group assigned for resolving the alert. Can also appear as Unassigned.
• Priority – Set in the Alert builder, ranging from Very low, Low, Moderate, High, to Very high.

Alerts are displayed across three main views, each offering a different level of insight, overview, and interaction. By clicking on any alert, you open the Alert dialog screen that shows the relevant transactions and other key details. (To read more on the Alert dialog click here).

Below is a breakdown of the three main alert views:

1. Dashboard (Home page):
   • The Dashboard provides a centralized overview of all alerts assigned to you or your group. The Dashboard includes a table of the Open alerts with Created at, Reason (alert name and trigger explanation), Client, and Priority.
     
     Inside the table All and High priority buttons act like Quick filters can be found:
     • All button - Active by default, displayed All alert in chronological order, with the newest alerts shown at the top.
     • High priority button - Filters and displays only alerts marked as High or Very high priority.
       
       
   • On the right hand side, you can find the Under investigation and Escalated preview cards. As previews, these cards display limited but valuable information to give you a quick overview of alert requiring your attention:
     • Under investigation card - Shows a preview of the last four alerts you have marked as Under investigation. The first alert inside the card (from top to bottom) is the oldest, and with the help of a visual colour-coded indicator, you can immediately see how many days alerts have been under investigation as the colour changes from green to orange to dark red, helping you stay informed and reminding you to resolve alerts in a timely manner.
     • Escalated card - Shows a preview of the last three alerts escalated to you for further review. The first alert inside the card (from top to bottom) is the oldest, and each alert displays the most recent comment and a timestamp, giving you quick access to the latest information shared on those alerts.
       
     
     In the bottom part of the dashboard and each card, a Show all button can be found. By clicking on it you will be redirect to the Alerts page, in which filters are applied to display all the relevant alerts matching the selected segment. 
     
     
2. Alerts card (inside client page):
   Located within each client’s page, this card displays all alerts related to that specific client. It includes a table built from Date, Name (of the alert), Reason, Assignee, Status, and Priority.
   These Filters can be applied to narrow the view for specific alert: Status, Priority, or Assignee.
   
   
3. Alerts page:
   This page provides a complete overview of all alerts across all clients. It displays a table including Created at, Reason (alert name and trigger explanation), Assignee, Status, Client, and Priority It offers you filtering options that align with the columns' headers.
   
   

Now that you have seen how and where alerts can be viewed, it is important to understand the Alert lifecycle and how alerts behave from the moment they are triggered until they are resolved.

 

Alert lifecycle

Each alert begins its lifecycle when triggered by client activity that matches the rules set in the Alert Builder. The initial Status is always Open, and the alert remains active and continues to update as long as its status is not changed.

While an alert is Open, it collects and reflects ongoing client activity within its defined Time range. Once the status is changed to any other value such as False positive, Suspicious, Under investigation, or Escalated, the alert stops updating, even if new activity occurs within the same time range.

A new alert will only be triggered once the time range has passed. For example, if an alert is configured with a Weekly time range, it will gather all relevant activity during that week. If its status is changed mid-week, it stops updating. A new alert will be triggered at the start of the next week based on new client activity.

Alerts marked as Closed indicate that the alert rule was modified after the alert was triggered. These alerts are no longer editable and are closed via Mass closure action made by an Owner or Admin roles only. In such case an audit trail is recorded for transparency.

 

Once you understand how alerts behave throughout their lifecycle, the next step is knowing how to respond to them. This is where judgment comes into action.

 

Alert judgment

A Judgment is the decision you make about an alert after reviewing its details. It reflects your assessment of whether the alert is valid, needs further investigation, or should be escalated. Applying a judgment updates the alert’s status and determines how it will be managed going forward.

Each alert can be resolved using one of four Judgment buttons, each representing a specific outcome:

False positive:
The alert was triggered based on the predefined rules, but upon review the transaction is legitimate and aligns with the client’s expected activity.

Once selected, this status is final and cannot be changed.

Suspicious:
The alert was triggered as predefined by the rules, flagging activity that may deviate from the client’s typical behaviour. This can involve one or multiple transactions, and/or other potential risk factors. It should be reviewed to determine whether it is indeed suspicious. After you resolve the alert as Suspicious, a report with the relevant transactions can be downloaded, if applicable.

Once selected, this status is final and cannot be changed.

Under investigation:
The alert is currently being reviewed to determine whether it poses a potential risk.
Escalate:
The alert is considered serious and should be forwarded to a higher authority or specialized team for further action.

Important to note:

The Under investigation and Escalate buttons can be used more than once on the same alert, depending on the situation.
Alerts marked as False Positive or Suspicious are considered resolved and cannot be changed.
Alerts can be reassigned to other users or entities at any stage. Each reassignment is recorded in the audit trail.
An automatic email is sent to the assignee to whom the alert was escalated.

Alert dialog

The Alert dialog is the detailed view that automatically opens when you click on any alert, regardless of its status. It provides a comprehensive display of all the information available in the alert views, but in a larger layout.

At the centre of the screen, you can find a table listing the relevant transaction or transactions associated with the alert. In some cases, the table may be empty if the alert was triggered without specific transaction data.

Below the transaction table, you will find the Judgment buttons used to resolve the alert. Underneath these buttons is a required comment field, where you must enter your explanation or assessment before saving or submitting your judgment. This ensures that every resolution is supported by context and reasoning. You can attach one file as a supporting document when you submit your judgment.

 

Now that you have explored the theory behind alert judgments and what each status represents, the next step is applying that knowledge in practice.

 

Manual alert resolvement

To manually resolve an alert, follow these steps:

1. Click on the alert to open the Alert dialog.
2. Review and evaluate the alert and its associated transaction, if applicable.
3. To initiate the process, scroll down to the Judgment buttons section.
4. Choose the appropriate status:
   1. False Positive:
      Click the button, add a clear explanation, attach a supporting file if needed, and click Save & close alert.
   2. Suspicious:
      Click the button, provide a meaningful explanation, attach a file, and click Save & report alert.
      
      A Download transaction button will appear under Related transactions to download the alert report.
   3. Under Investigation:
      Click the button, add your explanation and attachments, and click Save.
   4. Escalate:
      Click the button, select an assignee, add your explanation and an attachment, and click Comment to forward the alert.

You can use the Judgment buttons at any point during the review process, except for alerts already resolved as False positive or Suspicious.

 

 

Bulk alert resolvement

Transaction monitoring also supports bulk alert resolvement, limited to alerts being resolved as False positive or Suspicious.

To perform a bulk resolution, the steps below can help:

1. Click the Edit button in the Alerts card.
2. In the bottom panel, click Resolve alerts.
3. A side panel will open with two Judgment buttons: False positive and Suspicious.
4. Choose the appropriate status:
   1. False Positive:
      Click the button, provide a clear explanation in the Add your explanation field, attach a supporting file if needed, and click Save & close alert to complete the action.
      
      Once marked as False positive, the alert cannot be changed to another status.
      
      
   2. Suspicious:
      Click the button, provide a meaningful explanation, attach a relevant file, and click Save & report alert to complete the action.
      
      A Download transaction button will appear under Related transactions to download the alert report.
      
      Once marked as Suspicious, the alert cannot be changed to another status.

 

 

Creating notes

Notes in Pascal are a valuable tool for capturing and sharing relevant information about clients and their transactions. They help you and your colleagues stay informed about a client's background, history, and any important context that may influence decision-making. These notes are visible per each client across your organisation. Up to five files can be upload to a note, providing you the ability to include supporting documents and information if needed.

While Pascal generates automatic notes for alerts resolved as Suspicious, you can manually add two types of Notes:

• General notes: use this option to add general information about the client, such as observations, findings, and insights.
• Transaction-specific notes: use this option to link a note to one or more transactions to share comments related to specific transaction.

Whether general or specific, notes help maintain transparency, support collaboration, and ensure a clear audit trail for future reference.

The below steps can be used to create a General Note:

1. Select a client to get inside the client's screen. Scroll the page to the bottom part.
2. Click on Add note
3. In the new side panel, enter a Comment, and optionally add up to five files. To add a file, select your file and Drag and drop it into the designated file box, or use the Click to Upload
4. Click Apply to post the note.

To create a Transaction note, follows these guidelines:

1. Select a client to get inside the client's screen. Scroll the page to the Transactions
   card.
2. Click on Edit button.
3. In the newly appearing checkboxes, mark the relevant transactions. If needed, use the pagination to move in between the transactions list. Select all the transactions that are relevant for the note. The total number of selected transactions will be displayed on the bottom panel.
   Alternatively, you can click on select all to automatically select all the transactions in your client's list.
4. Click on Add note button.
5. In the new popup dialog, enter a Comment, and optionally add up to five files. To add a file, select your file and Drag and drop it into the designated file box, or use the click to upload Note that you cannot choose to use existing clients' names as new ones.
6. Click Apply to post the note.

The posted notes will automatically appear at the bottom of each client’s screen in the Notes card. By default, the All button is active, displaying every note. You can click the With attachment button to filter and view only notes that include file attachments.