Queues show a list of potentially risky transactions assigned to compliance and security officers for manual review.

Risky transactions may include:

• Transactions with the risk score close to the threshold you set.
• Big money transfers to high-risk countries.
• Transactions to/from a counterparty with a potential AML match.
• User account logins from unusual APIs or devices.
• And many more.

For example, transactions can be put on hold by certain rules that assign the Requires action status during monitoring. Such transactions are automatically distributed to the officers according to the following:

• By default, all suspicious transactions with the Requires action status are distributed to the Requires action (unassigned) queue. From this queue, transactions can be delegated manually to a proper expert for further investigation.
• If you have configured custom queues, all suspicious transactions are distributed to the officers in accordance with the queue settings.

The Assigned to me queue shows a list of transactions assigned to you explicitly.

📘

Note

When a transaction is being put on hold manually by a team member who has the Can moderate permission, such a transaction is automatically added to the Assigned to me queue; that is, — distributed to the team member who puts the transaction on hold.

Configure custom queues

You can set up custom queues to track risky transactions according to your business specifics:

1. Open the Queue settings and click Create queue.
2. Provide a queue title and optional description.
3. Select the officers to whom transactions should be assigned once they receive the Requires action status.
4. Select rules upon which transactions should be put into queue.
5. Select tags that should be present in the transaction in order to put it into queue.
6. Select a review status that should be met in order to put the transaction into queue.

Once a new queue is saved, you can find it in the tab section located at the top of the page.

Handle transactions in queues

Thoroughly study each transaction that you receive in your queue and make an appropriate decision.