---
title: How to create new scenarios
description: how to create a new alert scenario
---

[Skip to content](https://help.vartion.com/how-to-create-new-alert-scenarios#main-content)

English

Show submenu for translations

[Customer portal](https://portal.vartion.com/tickets-view?hsLang=en)

[![pascal\_logo.png\]](https://help.vartion.com/hs-fs/hubfs/pascal_logo.png?width=160&height=42&name=pascal_logo.png)](https://help.vartion.com/?hsLang=en)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Customer portal](https://portal.vartion.com/tickets-view)
- [Go to Pascal](https://pascal.vartion.com/)

[Go to Pascal](https://pascal.vartion.com/)

 How can we help?

- There are no suggestions because the search field is empty.

1. [Product Documentation](https://help.vartion.com/?hsLang=en)
2. [Transactions](https://help.vartion.com/transactions?hsLang=en)
3. [Settings](https://help.vartion.com/transactions?hsLang=en#settings)

# How to create new scenarios

**Alerts** are a central part of the Transactions module. **Alerts** trigger based on the configured scenarios. This configuration is a vital part in the setup of the Transactions module, ensuring alerts are triggered to inform you of anomalies.

This configuration can be done on the  **Settings** page:

1. Click on your initials in the top right corner.
2. In the newly opened menu, click on **Settings**.
3. Under the **Transactions** section, open the **Scenarios** page.

All configured scenarios are listed here. New alerts can be added by pressing the **New scenario** button.

 

### Configuring a scenario

The top of the page allows you to set some overall rules of the scenario. The following options are present:

- **Priority** - set the priority associated to alerts generated from this alert scenario.
- **Scenario timing** - set the moment the scenario should be checked for new alerts, this can either be **Immediate** or **End of day**.
- **Default assignee** - set a user or group that is by default assigned to generated alerts from this scenario.
- **Time range** - set the time range considered for generating alerts from this scenario.
- **Scenario frequency** - set the frequency for triggering alerts from this scenario.
- **Exemption lists** - set if transactions included in selected exemption lists should be excluded from this scenario.

 

### **Building a scenario**

The **Rule library** shows the list of rules that can be chosen to compose the scenario. Using the **Add** button, adds the rule to this scenario. All rules active in this scenario are presented in the **Rules** section on the left. Active rules can tweaked to the correct values, currency, and more.

Some rules cannot be used simultaneously. Rules that are not possible due to an already active rule, will be greyed out.

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

Some rules are mandatory and serve as Base rules, while others can be added to refine and enrich the alert logic. When no base rule is added to the scenario yet, the **Publish** button will be greyed out. Hovering over the question mark will show you the base rules of which you can add one.

 

#### Creating a new alert can be done by following the below steps:

Only users with the role **Admin** or **Owner** can create and manage scenarios.

1. Click on your organisation name or initials in the top-right corner.
2. Select **Settings** in the newly shown menu.
3. In the left sidebar, scroll down to the **Transactions** section and open the **Scenarios** page.
4. Click on **New scenario** to create a new alert:
5. Click **Rename** besides **Standard Scenario** to give the new alert an appropriate title.
6. Select the appropriate **Priority**, **Scenario timing**, **Default assignee**, **Time range**, **Scenario frequency** and **Exemption lists** in the top configuration section.
7. In the **Rule library**, click **Add** next to the rule you would like to include in your alert scenario.
8. Configure the added rule below the **Rules** on the left side as desired.
9. Add more rules from the **Rule library** via the **Add** button as desired.
10. Once satisfied with your configuration, click **Publish** in the bottom right corner.
11. Click on the cross in the top right to close the scenario editing menu.

 

Each rule includes its own condition(s) to configure. These can be:

- A toggle to apply a specific condition.
- A dropdown with Include or Exclude options, paired with a free-text field.
- A dropdown with Equals, At least, At most, or In range, followed by a numeric input field (with up/down arrows to adjust the value).
- An **Add more** button to extend the rule with more options. This also adds **Match logic**, allowing you to choose if **all conditions must match** or **at least one condition must match** for an alert to trigger.

##### Rule breakdown

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

- **Balance changes (absolute)** - Monitors the absolute change in the bank account balance over a time range.
- **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** - Rule for the age of the client to .
- **Client information changes** - Set the number of times specific client information has been changed
- **Outgoing to incoming ratio** - Set the percentage of outgoing versus incoming transaction value per client bank account.
- **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.
- **Unique counter parties** - Set a number of unique counter parties involved in transactions for a client bank account.

For these rules, Numeric conditions apply. You can choose from the following conditions’ dropdown options: **Equals**, **At least**, **At most**, or **In range**. Each option allows you to input a numeric value. The **Add more** button allows you to set an additional condition in the rule. The **Match logic** allows you to choose if **all conditions must match** or **at least one condition must match** for this rule.

- **Bank account type** - Identifies the type of bank account.
- **Blocked countries** - Include or exclude transactions based on the blocked countries configuration list.
- **Client country** - Indicates the country of an entity client or the nationalities of an individual.
- **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** - Include or exclude specific professions of clients. 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.
- **Transaction type** - Filters transactions based on their type (derived from uploaded transaction data).
- **Transaction counter party bank account country** - Filters transactions based on the country of the counter party bank account.
- **Transaction description keywords** - Monitor transactions based on keywords in the description.

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** - Determine if only new accounts or old accounts should be included in the alert scenario
- **Client type** - Specifies whether the client is an individual or an entity.
- **Client SIC codes** - Selects one or more SIC code 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.

 

Each rule can be combined with others to create powerful, targeted scenarios that align with your organisation’s risk policies and scenario goals.

You can save the scenario by pressing the **Publish** button in the bottom right of the screen. Before publishing a scenario, you can choose whether it should be active or inactive via the toggle **Scenario active** left of the **Publish** button. 

A scenario can be duplicated by opening an existing scenario and pressing the **Duplicate** button in the bottom right of the screen.

 

**This documentation, including images, videos and text, is accurate as of Version 7.18 of Pascal.**

We strive to keep our documentation up to date with each release to ensure it remains a reliable resource for our users. However, given the dynamic nature of our software development, there might be instances where changes introduced in subsequent versions are not immediately reflected in this documentation. We encourage users to refer to [the latest release notes](https://help.vartion.com/knowledge/general?hsLang=en#release-notes) and to use the feedback mechanism for any discrepancies or requests for clarification.

- [General](https://help.vartion.com/general?hsLang=en#main-content)

    - [Release Notes](https://help.vartion.com/general?hsLang=en#release-notes)
    - [What's New](https://help.vartion.com/general?hsLang=en#whats-new)
    - [Risk Classification Settings](https://help.vartion.com/general?hsLang=en#risk-classification-settings)
    - [HubSpot](https://help.vartion.com/general?hsLang=en#hubspot)
    - [User Account Settings](https://help.vartion.com/general?hsLang=en#user-account-settings)
    - [General](https://help.vartion.com/general?hsLang=en#general)
    - [Billing](https://help.vartion.com/general?hsLang=en#billing)
    - [Organisation Settings](https://help.vartion.com/general?hsLang=en#organisation-settings)
    - [Integrations](https://help.vartion.com/general?hsLang=en#integrations)
    - [Zapier](https://help.vartion.com/general?hsLang=en#zapier)
- [Screening](https://help.vartion.com/screening?hsLang=en#main-content)

    - [FAQ](https://help.vartion.com/screening?hsLang=en#faq)
    - [Cases](https://help.vartion.com/screening?hsLang=en#cases)
    - [Clients](https://help.vartion.com/screening?hsLang=en#clients)
    - [Statistics](https://help.vartion.com/screening?hsLang=en#statistics)
    - [Getting Started with Pascal Screening](https://help.vartion.com/screening?hsLang=en#getting-started-with-pascal-screening)
    - [Results in Pascal](https://help.vartion.com/screening?hsLang=en#results-in-pascal)
    - [Notifications in Pascal Screening](https://help.vartion.com/screening?hsLang=en#notifications-in-pascal-screening)
    - [Screening Settings](https://help.vartion.com/screening?hsLang=en#screening-settings)
- [Onboarding](https://help.vartion.com/onboarding?hsLang=en#main-content)

    - [Getting Started with Pascal Onboarding](https://help.vartion.com/onboarding?hsLang=en#getting-started-with-pascal-onboarding)
    - [Onboarding Settings](https://help.vartion.com/onboarding?hsLang=en#onboarding-settings)
    - [Clients](https://help.vartion.com/onboarding?hsLang=en#clients)
- [Transactions](https://help.vartion.com/transactions?hsLang=en#main-content)

    - [Getting Started with Pascal Transactions](https://help.vartion.com/transactions?hsLang=en#getting-started-with-pascal-transactions)
    - [Settings](https://help.vartion.com/transactions?hsLang=en#settings)

[![vartion\_logo@0,5x-1](https://help.vartion.com/hs-fs/hubfs/vartion_logo@0%2c5x-1.png?width=125&height=45&name=vartion_logo@0%2c5x-1.png "vartion_logo@0,5x-1")](https://vartion.com)

 

Copyright © 2025, Vartion B.V.