AML/KYC Framework for Financial Services

Type: Decision Rule Confidence: 0.92 Sources: 8 Verified: 2026-03-02 Applies to: Financial institutions, banks, fintechs, VASPs, insurance companies, investment advisers, DNFBPs

Rule

Every financial institution and designated obliged entity must implement a risk-based Anti-Money Laundering (AML) and Know Your Customer (KYC) program comprising five core pillars: (1) a written AML/CFT policy approved by senior management, (2) a designated compliance officer, (3) risk-based Customer Due Diligence (CDD) with Enhanced Due Diligence (EDD) for high-risk relationships, (4) ongoing transaction monitoring with Suspicious Activity Report (SAR) or Suspicious Transaction Report (STR) filing, and (5) independent testing and staff training. This framework is mandated by FATF Recommendation 10 globally, the US Bank Secrecy Act (BSA) domestically, and EU Regulation 2024/1624 (AMLR) across the European Union. [src1, src2, src3]

Evidence

Global AML enforcement penalties totaled $4.6 billion in 2024 and $3.8 billion in 2025, with TD Bank receiving a $3.09 billion fine for systemic AML compliance failures — one of the largest AML penalties in history. [src5, src8] In the first half of 2025, regulators levied approximately 139 financial penalties totaling $1.23 billion — a 417% increase over the same period in 2024 — with OKX paying $504 million for failing to maintain an effective AML program. [src5, src8] FATF's fifth round of mutual evaluations (2024-2027) places heavy weight on effectiveness outcomes rather than technical compliance, and the EU's AMLR doubles maximum pecuniary sanctions to EUR 10 million or 10% of total annual turnover. [src1, src3] The EU has lowered the beneficial ownership threshold from over 25% to 25% or more, with 15% in high-risk cases. [src3] AMLA must deliver Regulatory Technical Standards on CDD and minimum data standards by July 10, 2026. [src3] On February 13, 2026, FinCEN issued Order FIN-2026-R001 granting exceptive relief from beneficial ownership identification at each new account opening. [src2]

Key Properties

Conditions

Constraints

Rationale

AML/KYC frameworks exist because the UN estimates that 2-5% of global GDP ($800 billion to $2 trillion) is laundered annually. Without mandatory identification, due diligence, and transaction monitoring, financial institutions become conduits for drug trafficking, terrorist financing, tax evasion, and sanctions circumvention. The risk-based approach — rather than prescriptive rules — recognizes that ML/TF risk varies by customer type, geography, product, and delivery channel, and that compliance resources should be allocated proportionally to actual risk. [src1, src3]

Framework Selection Decision Tree

START — User needs AML/KYC compliance guidance
├── Which jurisdiction?
│   ├── United States (BSA/AML) → AML/KYC Framework ← YOU ARE HERE
│   ├── European Union (AMLR/6AMLD) → AML/KYC Framework ← YOU ARE HERE
│   ├── United Kingdom (MLR 2017) → AML/KYC Framework (UK aligns with FATF)
│   └── Multiple jurisdictions → Use FATF baseline + jurisdiction-specific add-ons
├── Is the entity a "financial institution" or "obliged entity"?
│   ├── YES → Apply this rule: implement 5-pillar AML program
│   └── NO → Check if entity is a DNFBP or newly designated obliged entity
├── Does the entity handle virtual assets or crypto?
│   ├── YES → Apply this rule + FATF Travel Rule (Rec. 16) + VASP registration
│   └── NO → Standard AML/KYC program under this rule
└── Does the entity have an existing AML program?
    ├── YES → Audit against this rule: check 5 pillars, risk assessment, SAR filing
    └── NO → Start with risk assessment, then build per Application Checklist

Application Checklist

Step 1: Determine applicability and scope

Step 2: Conduct enterprise-wide risk assessment

Step 3: Implement CDD/EDD procedures

Step 4: Build transaction monitoring and SAR/STR filing

Step 5: Validate, train, and independently test

Anti-Patterns

Wrong: Treating KYC as a one-time onboarding check

Many institutions collect identification documents at account opening and never revisit them. This approach fails to detect changes in customer risk profile, PEP status, or beneficial ownership structure, and was cited as a primary deficiency in TD Bank's $3.09 billion enforcement action. [src5]

Correct: Implement ongoing CDD with risk-based refresh cycles

CDD must be continuous. High-risk customers should be reviewed at least annually, medium-risk every 2-3 years, and low-risk every 5 years. Trigger events (large unusual transactions, adverse media, sanctions list changes) should prompt immediate review. [src1, src2]

Wrong: Filing SARs based on transaction amount alone

Some compliance teams file SARs on every transaction near the $10,000 CTR threshold, creating massive volumes of low-value reports that overwhelm FinCEN and dilute intelligence value. [src4]

Correct: File SARs based on suspicious activity indicators, not amount thresholds

FinCEN's October 2025 FAQs explicitly clarified that institutions are not required to file SARs solely because a transaction is at or near the $10,000 threshold. SARs should be filed when there is knowledge, suspicion, or reason to suspect involvement of illegal activity or BSA evasion. [src4]

Wrong: Applying identical CDD to all customers regardless of risk

A one-size-fits-all approach wastes resources on low-risk customers while under-scrutinizing high-risk relationships — this failure pattern led to multiple enforcement actions against banks processing correspondent banking from high-risk jurisdictions. [src5]

Correct: Apply tiered CDD based on documented risk assessment

Use Simplified Due Diligence (SDD) for demonstrably low-risk customers, standard CDD for medium-risk, and Enhanced Due Diligence (EDD) for high-risk categories including PEPs, correspondent banking, high-risk jurisdictions, and complex ownership structures. [src1, src3]

Counter-Arguments

Common Misconceptions

Misconception: AML/KYC programs only apply to banks and traditional financial institutions.
Reality: FATF Recommendations and most national laws extend AML obligations to DNFBPs including real estate agents, dealers in precious metals/stones, lawyers, notaries, accountants, and trust/company service providers. The EU AMLR further expanded scope to crypto-asset providers, crowdfunding platforms, and professional football clubs/agents. [src1, src3]

Misconception: Institutions must document their decision not to file a SAR.
Reality: FinCEN's October 2025 FAQs explicitly state there is no legal or regulatory requirement to document decisions not to file a SAR, though institutions may do so for internal risk management. [src4]

Misconception: The FATF Travel Rule for virtual assets is universally implemented and enforceable.
Reality: As of 2025, only 85 of 117 surveyed jurisdictions (73%) have passed Travel Rule legislation, and over 75% of jurisdictions remain only partially compliant with FATF's AML standards for virtual assets. [src6]

Misconception: The EU's new AML Regulation (AMLR) is already in effect.
Reality: Regulation 2024/1624 was published on July 9, 2024, but does not apply until July 10, 2027. The existing 5AMLD and its national transpositions remain applicable law until then. [src3]

Comparison with Similar Rules

Rule/FrameworkKey DifferenceWhen to Use
AML/KYC Framework (this unit)Global overview covering FATF, US BSA, and EU AMLR — the three primary regulatory pillarsWhen the user needs comprehensive AML/KYC guidance across jurisdictions
GDPR / Data PrivacyData minimization and right to erasure may conflict with AML record-keeping (5-7 year retention)When balancing AML data retention against privacy obligations
Sanctions Screening (OFAC/EU)Focuses on prohibited parties/countries rather than transaction patternsWhen the question is about blocked persons, SDN lists, or embargo compliance
FATCA/CRS Tax ReportingTax information exchange — overlaps with but distinct from AML beneficial ownershipWhen the question is about tax transparency and cross-border account reporting

When This Matters

Fetch this when a user asks about AML/KYC compliance obligations, anti-money laundering program requirements, customer due diligence procedures, suspicious activity reporting, beneficial ownership requirements, or when a financial institution, fintech, or VASP needs to understand its regulatory obligations for preventing money laundering and terrorist financing.

Related Units