AML Transaction Monitoring - Administration Panel Overview
The AML Transaction Monitoring GUI enables operators to configure custom rulesets, define value sets and actions for transaction monitoring, and manage user watchlists. The system is currently being enhanced with a testing feature for dry‑run ruleset validation and an analytics dashboard for monitoring AML transaction patterns and statistics.
Purpose & scope
This documentation covers the primary processes within the AML configuration module of the partnerbank Admin Panel.
| Name | Description |
| Ruleset management | Creating and managing rule configurations for transaction monitoring. |
| Actions management | Defining actions returned by the AML system. |
| Value set management | Managing internal variables and stored values. |
| Watchlist management | Adding and removing users from blacklists and greylists. |
Terminology
| Name | Description |
| End user | Cardholder performing transactions. |
| Operator | User working with the Administration Panel. |
| Ruleset | A collection of rules stored together. |
| Rule | Predefined sets of conditions checked and processed after receiving a transaction verification request. |
| Action | Response returned by the AML system that must be processed by the external product sending the verification request. |
| Value set | Internal variable storing multiple values (for example: UHRC country codes in ISO Alpha‑2 format). |
| Watchlist | Internal storage for suspicious users, checked during transaction verification to determine appropriate decisions and actions. |
RULES
This section of the GUI is responsible for managing rulesets, value sets and actions.
Rule sets
Defining a ruleset
To create a new ruleset, follow these steps. On the right you can insert a screenshot of the Add ruleset page to illustrate the process.
|
|
Note: A traditional YAML builder using forms and blocks is under development. In the final version, rulesets can be defined either with the text editor or with an easy-to-use form.
Ruleset list
You can view all configured rulesets in the Rule sets tab. The list displays:
| Column | Description |
| ID (uuid) | Unique internal identifier of the ruleset. |
| NAME | Descriptive name of the ruleset. |
| CREATED_AT | Date and time when the ruleset was created. |
| UPDATED_AT | Date and time when the ruleset was last modified. |
| ACTIVE | Indicates whether the ruleset is enabled (blue switch) or disabled (grey switch). |
| ACTION | Menu containing actions such as view details, edit or delete. |
Ruleset details
When you click a ruleset row, a detailed view opens showing all configuration fields. The table below summarises these elements.
| Element | Description |
| Basic data | The panel that summarises the ruleset’s ID (uuid), Name, Created_at and Updated_at values. |
| ID (uuid) | Unique identifier of the ruleset, displayed in the Basic data panel. |
| Name | The descriptive name of the ruleset, shown in the Basic data panel. |
| Created_at | The date and time when the ruleset was created. |
| Updated_at | The date and time when the ruleset was last modified. |
| Ruleset definition tab | The tab that displays the YAML definition of the ruleset, including conditions, triggers, decisions and actions. |
| Ruleset tests tab | The tab used for running and viewing test results for the ruleset. |
| Edit button | A button that opens the ruleset edit form. |
| Test ruleset button | A button that runs a dry‑run test on the ruleset using historical transaction data. |
Ruleset activation / deactivation
When creating a ruleset, the operator chooses whether the ruleset should be active right away or saved in a disabled state by selecting Save as enabled or Save as disabled. Once the ruleset exists, its state can be toggled on or off at any time from the list view: use the status switch to enable or disable the ruleset and confirm the change. Changes take effect immediately after confirmation.
| Status indicator | Description |
| Blue switch | The ruleset is enabled. The toggle switch is coloured blue and positioned to the right. |
| Grey switch | The ruleset is disabled. The toggle switch is grey and positioned to the left. |
Ruleset testing (dry‑run)
Note: Feature under development. The dry‑run engine will allow operators to run rulesets against historical transaction data and view the result that the ruleset would return without impacting live processing.
Value sets
Defining a value set
Follow these steps to create a new value set. Use the right column for a screenshot of the “Add value set” page.
|
Value sets list
The Value sets tab lists all defined value sets. Each row includes the following columns:
| Column | Description |
| ID (uuid) | Unique identifier of the value set. |
| NAME | The name of the value set. |
| ACTION | Menu containing available operations such as view details, edit or delete. |
Value set details
Selecting a value set opens a detailed view where you can add or remove individual values. The elements are described below:
| Element | Description |
| Basic data | A panel summarising the value set’s ID (uuid) and Name. |
| ID (uuid) | Unique identifier of the value set. |
| Name | The name of the value set. |
| Value set | The list of values stored in the set. Each value appears as a tag with an option to remove it; new values can be added using an input or the add value + button. |
| Edit button | A button in the top‑right corner that opens the value set edit form. |
Actions
Defining an action
The table below outlines the steps for creating a new action. A screenshot of the “Add action” page can be placed in the right column.
|
Action list
The Actions tab lists all configured actions. Each row shows:
| Column | Description |
| ID (uuid) | Unique identifier of the action. |
| NAME | The name of the action. |
| GROUP | The group to which the action belongs. |
| ACTION | Menu containing available operations such as view details, edit or delete. |
Action details
Clicking an action opens a details page that displays its configuration. The table below describes each element.
| Element | Description |
| Basic data | A panel summarising the action’s ID (uuid), Name and Group. |
| ID (uuid) | Unique identifier of the action. |
| Name | The name of the action. |
| Group | The group to which the action belongs. |
| Property | Details for each property defined in the action. Each property contains a name, a required flag and a list of values. |
| Property name | The name of the property (e.g. resource_type). |
| Required | Indicates whether the property is mandatory (true) or optional (false). |
| Values | The allowed values for the property, shown as tags (e.g. FRAUD_SUSPECTED, DOCUMENT_EXPIRED). |
| Edit button | A button that opens the action edit form. |
WATCHLISTS
The system supports two watchlist types: Blacklist and Greylist. Both lists are managed identically; you can switch between them using the tabs at the top of the watchlist management page.
Blacklist
Adding a user
|
User information fields:
| Field | Description |
| Name | User’s first name (required). |
| Surname | User’s surname (required). |
| Full name | The person’s full name (first and last names together). |
| Birth date | Date of birth (required). |
| Pesel | Personal identification number (PESEL) (required). |
| Document number | Identification document number (required). |
| Document type | Select from dropdown (Passport, ID card, etc.). |
| Country | Select country from dropdown. |
| City | Enter city name. |
| IBAN | Bank account number (if applicable). |
Important: Adding a user to a watchlist does not automatically trigger any actions. A ruleset must reference the watchlist to determine whether to approve, decline or place a transaction on hold.
Removing a user
|
Searching and filtering
The watchlist management page includes filters to narrow down the list of users:
| Filter | Description |
| Name | Filter by name (first name). |
| Surname | Filter by surname. |
| Full name | Filter by full name (first and last names together). |
| Pesel | Filter by personal identification number (PESEL). |
| Document number | Filter by identification document number. |
| Country | Filter by country (dropdown). |
| City | Filter by city. |
Blacklist table
The blacklist displays the following columns for each entry:
| Column | Description |
| ID | Internal identifier for the entry (UUID shown truncated). |
| NAME | First name of the user. |
| SURNAME | Surname of the user. |
| BIRTH DATE | Birth date of the user. |
| PESEL | Personal identification number (PESEL for Polish users). |
| DOCUMENT TYPE | Type of identification document. |
| COUNTRY | Country. |
| ACTIONS | Menu for managing the entry (delete). |
Blacklist record details
To view detailed information about a specific entry on the blacklist, click on the row in the table. An expanded section will appear below the row showing additional details about the user:
| Field | Description |
| Full name | The user’s full name. |
| Document number | The identification document number associated with the user. |
| City | The user’s city. |
| IBAN | The user’s bank account number, if provided. |
Greylist
The greylist is functionally identical to the blacklist.
All operations — adding users, removing users, filtering and managing entries — are the same.
Refer to the Blacklist section above for full instructions.


















