Controls & evidence

Transaction monitoring

Continuous, rules- and model-based detection of suspicious patterns in transaction flows.

Overview

Monitoring systems generate alerts that analysts review, escalate and, where warranted, report as suspicious activity. Tuning and documenting the rules is itself examined.

It connects most directly to Anti-money laundering, SAR / STR and Bank Secrecy Act.

Check the official sources below for legal scope, applicable dates and exceptions. This entry is an explanatory reference, not legal advice.

Why it matters

Poorly tuned monitoring either misses crime or drowns analysts in false positives.

Who it affects

Banks, payment firms and crypto businesses.

Where it sits

Ten linked steps connect where you operate to the proof that you complied.

  1. 01Jurisdiction
  2. 02Industry
  3. 03Activity
  4. 04Authority
  5. 05Regulation
  6. 06Requirement
  7. 07Guidance
  8. 08Control
  9. 09Evidence
  10. 10Enforcement

Connections

The terms most closely tied to Transaction monitoring. Select one to open it.

This term

What to do about it

  1. 1Define the owner, frequency, data and pass condition.
  2. 2Automate the test on source data where you can.
  3. 3Capture evidence on every run, including exceptions.
  4. 4Review exceptions and failures and record the decision.
In Regulation Layer

From requirement to evidence.

Monitoring controls run on live data with alert dispositions sealed as evidence.

Request early access →

Related terms

Request early access →