Transaction monitoring is the ongoing, largely automated review of payments to detect patterns that may signal money laundering, fraud, or other illicit activity. It watches how money actually moves over time, flagging unusual behavior for human review rather than judging any single payment in isolation.
How does transaction monitoring work?
Transaction monitoring runs continuously in the background of a financial service, examining payments as they happen and building a picture of what normal looks like for each customer. When activity strays from that baseline, or matches known patterns of abuse, the system raises an alert. A human analyst then reviews the alert to decide whether it is innocent, needs more information, or warrants escalation.
It is a central pillar of any AML program and works hand in hand with KYC and sanctions screening. KYC establishes who the customer is; monitoring watches what they do afterward. Because it deals in behavior over time rather than one-off checks, monitoring is where laundering schemes that survive the front door are most likely to be caught.
What monitoring systems look for
- Amounts just under reporting thresholds, a pattern known as structuring or smurfing.
- Sudden spikes in volume or frequency that do not fit a customer's history.
- Rapid movement of funds in and out of an account with little apparent purpose.
- Transfers involving high-risk jurisdictions or unexpected counterparties.
- Networks of accounts that move money between each other in circular or layered ways.
Most systems start with rules, thresholds and conditions that trigger alerts, and increasingly add models that learn from past cases to spot subtler patterns. Whatever the method, the output is the same: a queue of alerts that people must review, which is why tuning the system to reduce noise is as important as catching genuine risk.
Rules-based vs behavior-based monitoring
Traditional monitoring is rules-based: if a transfer exceeds a set amount, or several transfers cluster just below a threshold, an alert fires. Rules are transparent and easy to explain to regulators, but they are blunt. They generate large volumes of false positives and can be gamed by anyone who learns where the thresholds sit.
Behavior-based approaches add context by comparing activity to a customer's own history and to peers with similar profiles. A large transfer that is routine for one customer might be a red flag for another. These models can catch patterns rules miss and cut false positives, but they are harder to explain and require good data to work well. Most mature programs blend both, using rules for clear-cut cases and models for the subtler ones.
In diaspora corridors, context matters enormously. Regular support payments to family, seasonal spikes around holidays, and pooled savings arrangements like esusu can all look unusual to a naive rule but are entirely legitimate. Monitoring that understands these patterns avoids flagging normal community behavior as suspicious.
Why transaction monitoring matters for money movement
Monitoring is where a compliance program earns its keep, catching the laundering and fraud that slip past initial checks. It is also a legal obligation; firms must be able to detect and report suspicious activity, and failures here draw some of the largest regulatory penalties. For a provider, effective monitoring is what keeps banking partners comfortable and services running.
The hard part is the human cost of false positives. Every alert takes analyst time, and an overly sensitive system buries real risk under noise while delaying legitimate transfers. Tuned well, monitoring protects customers quietly; tuned poorly, it becomes friction that punishes the honest majority and can push people toward informal channels like hawala.
Pros | Cons |
|---|---|
Catches laundering and fraud that get past onboarding checks. | Too many false positives overwhelm analysts and delay honest transfers. |
Meets a core legal obligation and protects banking relationships. | Poorly tuned rules can misread legitimate community patterns as suspicious. |
Can adapt over time as new schemes and patterns emerge. | Effective monitoring requires investment in data, tools, and skilled reviewers. |
For Dara, the aim is monitoring that is sharp on genuine risk and fluent in the realities of diaspora money. Understanding how families actually move money across a corridor is what lets the system separate real threats from the ordinary rhythm of sending support home.
Frequently asked questions
They overlap but are not identical. Transaction monitoring focuses on detecting money laundering and reporting suspicious activity, while fraud detection focuses on catching theft and scams. Many systems handle both, since the underlying signals often look similar.
No. The review is automated, and people only look at the small share of activity that triggers an alert. For nearly all customers, monitoring runs silently and never affects a legitimate transfer.
It is the practice of breaking a large sum into many smaller transfers to stay under reporting thresholds and avoid attention. Monitoring systems are specifically designed to detect this pattern, which is a classic laundering technique.
Activity that differs from your usual pattern, such as a sudden large transfer or a burst of payments, can trigger an alert even when it is entirely innocent. A review usually clears it quickly, sometimes after asking for a little more information.
A well-designed system can. By learning a customer's history and recognizing common diaspora behaviors like regular remittances or holiday spikes, good monitoring avoids treating ordinary support as suspicious while still catching genuine risk.
Updated July 21, 2026
Disclaimer
Dara provides this glossary for general educational purposes only. It is not financial, legal, or tax advice, and availability, fees, and terms vary by country and corridor.
Put the words to work.
One account on both sides, so money moves either way without the markup.