Ylem documentation
  • 🗒️General information
    • Introduction to Ylem
    • Quick start guide
    • Release notes
  • 🔬Open-source edition
    • Installation
    • Usage of Apache Kafka
    • Task processing architecture
    • Configuring integrations with .env variables
  • 💡Integrations
    • Connecting an integration
    • Library of integrations
      • Amazon Redshift
      • Apache Kafka
      • APIs
      • Atlassian Jira
      • AWS Lambda
      • AWS RDS
      • AWS S3
      • ClickHouse
      • ElasticSearch
      • E-mail
      • Google Big Query
      • Google Cloud SQL
      • Google Pub/Sub
      • Google Sheets
      • Immuta
      • Incident.io
      • Jenkins
      • Hubspot
      • Microsoft Azure SQL
      • MySQL
      • OpenAI ChatGPT
      • Opsgenie
      • PostgreSQL
      • PlanetScale
      • RabbitMQ
      • Salesforce
      • Slack
      • Snowflake
      • Tableau
      • Twilio. SMS
      • WhatsApp (through Twilio)
    • Initial demo data source
  • 🚡Pipelines
    • Pipeline management
    • Tasks
      • Aggregator
      • API Call
      • Code
      • Condition
      • External trigger
      • Filter
      • For each
      • GPT
      • Merge
      • Notification
      • Query
      • Pipeline runner
      • Processor
      • Transformer
    • Running and scheduling pipelines
    • Library of templates
    • Environment variables
    • Mathematical functions and operations
    • Formatting of messages
  • 📈Statistics and profiling
    • Statistics of runs
    • Slow tasks
  • 📊Metrics
    • Metric management
    • Using previous values of a metric
  • 💼Use cases, patterns, templates, examples
    • Use cases
    • Messaging patterns
      • Datatype Channel
      • Message Dispatcher
      • Messaging Bridge
      • Message Bus
      • Message Filter
      • Message Router
      • Point-to-Point Channel
      • Publish-Subscribe Channel
      • Pull-Push
    • Functional use cases
      • Streaming from Apache Kafka and messaging queues
      • Streaming from APIs
      • Streaming from databases
      • Data orchestration, transformation and processing
      • Usage of Python and Pandas
      • KPI Monitoring
      • OKRs and custom metrics
      • Data Issues & Incidents
      • Reporting
      • Other functional use cases
    • Industry-specific use cases
      • Finance and Payments
      • E-commerce & Logistics
      • Customer Success
      • Security, Risk, and Anti-Fraud
      • Anti-Money Laundering (AML)
  • 🔌API
    • OAuth clients
    • API Reference
  • 👁️‍🗨️Other resources
    • FAQ
    • Our blog on Medium
Powered by GitBook
On this page
  • Streaming monitoring information about large transaction amounts
  • A high volume of transactions within a short time
  • Too many transactions between the same accounts in X days
  • Other AML use cases

Was this helpful?

Edit on GitHub
  1. Use cases, patterns, templates, examples
  2. Industry-specific use cases

Anti-Money Laundering (AML)

PreviousSecurity, Risk, and Anti-FraudNextOAuth clients

Last updated 8 months ago

Was this helpful?

Anti-Money Laundering (AML) regulations require businesses to monitor transactions and report suspicious ones to authorities.

Ylem can help you with automating the data streaming for the following critical processes:

  • Unusual transaction amounts;

  • Unusual series of transactions (e.g., too many cash credits);

  • Unusual geographic destination or origin of a payment;

  • Known threats or typologies.

Streaming monitoring information about large transaction amounts

Here is an example of the pipeline to monitor large transaction amounts

A high volume of transactions within a short time

Too many transactions between the same accounts in X days

Other AML use cases

The idea is clear. Using the following examples and templates from our library you can set up your own AML monitoring pipelines with SQL queries of any complexity.

Some other examples of what you can monitor with Ylem:

  • Users with a high volume of transactions every day

  • Transactions from or to suspicious or dangerous locations, which you can define on your own

  • Suspicious reference data

  • Suspicious bank account owners

  • Suspicious and inconsistent activities. For example, a high volume of transactions but following the long breaks

  • Unusual amounts per user

  • Etc.

💼
Query example to detect large transactions
Possible pipeline
SQL query example to retrieve the number of transactions today grouped by bank account
Message to the responsible team
Possible pipeline
SQL query to retrieve number of transactions between two accounts
Message to the responsible team