Sanctions
Restrictive measures imposed by international bodies or national authorities against named persons, entities, sectors or countries, prohibiting or restricting dealings with them.
Sanctions compliance is an absolute obligation rather than a risk-based one: a prohibited dealing is prohibited regardless of the institution's own risk assessment. This is the main respect in which it differs from the rest of the AML/CFT programme.
In the platform: Screening and watchlists
See also: Name screening, Watchlist, Sanctions evasion, Proliferation financing
Sanctions evasion
Conduct designed to circumvent restrictive measures — using intermediaries, front companies, altered payment messages, mislabelled goods or third-country routing to obscure a designated party's involvement.
Detection generally depends on network and behavioural signals rather than name matching alone, because a successful evasion scheme is one where the designated name does not appear.
In the platform: Screening and watchlists · Transaction monitoring
See also: Sanctions, Shell company, Trade-based money laundering
SARSuspicious activity report
The term used in some regimes for a report of suspicion to the financial intelligence unit, broader in name than a transaction report because the suspicion may arise from conduct rather than from a specific transaction.
See also: STR, MLRO
SCUMLSpecial Control Unit against Money Laundering
The Nigerian body responsible for the registration and AML/CFT supervision of designated non-financial businesses and professions.
Registration requirements, the categories in scope, reporting obligations and identifier formats are set by the operative Nigerian instruments and supervisory instruction. Confirm them directly rather than inferring from an international category list.
In the platform: SCUML and DNFBPs
See also: DNFBP, NFIU
SDDSimplified due diligence
A reduced set of due diligence measures applied where the institution has assessed and can demonstrate that the risk in a given category is lower.
Simplified is not absent. The identification obligation and ongoing monitoring still apply; what is reduced is the extent, timing or intensity of specific measures, and the reduction has to be justified by the risk assessment.
In the platform: Customer and CDD
See also: CDD, EDD, Risk-based approach
Segmentation
Grouping customers into populations that behave alike — by entity type, occupation, product mix, expected turnover — so that detection thresholds and expectations can be set per population rather than across the whole book.
Poor segmentation is the largest single source of monitoring noise in most programmes, and improving it is a data exercise rather than a modelling one.
In the platform: Transaction monitoring · Customer and CDD
See also: Rule tuning, False positive, Purpose and intended nature of the relationship
Segregation of duties
Splitting a sensitive process so that no single person can both initiate and complete it — the general control of which maker-checker is the most common specific form.
In the platform: Security architecture · Investigation and casework
See also: Maker-checker, Audit trail
Shell company
A company with no significant operations, employees or assets of its own, existing primarily to hold assets, receive payments or sit in an ownership chain.
Shell companies have lawful uses. What matters is whether the structure is explained by the customer's stated business, and whether the beneficial owner behind it can be established.
In the platform: Customer and CDD
See also: Beneficial owner, Nominee arrangement, Layering
Smurfing
Splitting a larger sum across multiple people acting as depositors or senders, so that no individual transaction looks notable and no single person appears to move the whole amount.
Closely related to structuring; the distinguishing feature is the use of multiple individuals rather than only multiple transactions. Detection depends on linking the participants, not on examining any one of them.
In the platform: Transaction monitoring
See also: Structuring, Placement, Typology
Source of funds
The origin of the specific money used in a particular transaction or relationship — which account it came from, and what generated it.
Frequently confused with source of wealth. Source of funds explains this money; source of wealth explains how the customer came to have money at all. A high-risk relationship generally needs both.
In the platform: Customer and CDD
See also: Source of wealth, EDD, PEP
Source of wealth
How the customer's overall wealth was accumulated — business ownership, employment, inheritance, investment, disposal of assets — and whether that is consistent with what is observed.
Establishing it means obtaining evidence, not recording an assertion. A file stating that wealth derives from business income, with nothing behind it, has documented the customer's answer rather than the institution's finding.
In the platform: Customer and CDD
See also: Source of funds, EDD, PEP
STRSuspicious transaction report
A report made to the financial intelligence unit where the reporting entity knows, suspects or has reasonable grounds to suspect that funds are the proceeds of crime or are related to terrorist financing. In some regimes the equivalent is called a suspicious activity report.
The obligation is triggered by suspicion, not by proof, and once suspicion is formed the regime will generally impose a time limit and confidentiality restrictions. Take the trigger point, the deadline and the confidentiality rule from the operative instrument in your jurisdiction.
In the platform: Governed reporting · Investigation and casework
See also: SAR, CTR, MLRO, Tipping off, goAML
Structuring
Deliberately breaking a sum into smaller transactions so that no individual one meets a reporting or review threshold.
Structuring is defined by intent to evade a threshold, which is why it is detected through pattern — repeated amounts sitting just below a level, across accounts or days — rather than by examining any single transaction.
In the platform: Transaction monitoring
See also: Smurfing, Threshold reporting, CTR, Typology
Suppressionalso: whitelisting
Configuring a control to stop raising a known, previously adjudicated match or alert pattern, so that reviewers are not asked the same answered question repeatedly.
A suppression is a decision that a category of activity does not need looking at. It needs an owner, a documented reason, an expiry and a review — a permanent, unreviewed suppression removes coverage as effectively as deleting the rule, and does it invisibly.
In the platform: Screening and watchlists · Transaction monitoring
See also: Rule tuning, False positive, Audit trail