FATF 40 Recommendations — International AML/CFT Standards
FATF 40 Recommendations — International AML/CFT Standards — 100% of in-scope requirements covered.
5 requirements · 5 in scope (5 enforced). The 100% is weighted over the in-scope base.
FATF 40 Recommendations: requirement → the KYE™ artefact that enforces it
Demo dataYou learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.
-
r1-risk-based-approach · enforced
Risk-based approach (R.1): an AI AML action proceeds under a named-authority decision proportionate to…
Rule packs: kye:rule-pack:aml-financial-crimes · Constitution: 12 purpose permission
-
r10-customer-due-diligence · enforced
Customer due diligence & beneficial ownership (R.10): CDD/KYC result recorded before an AI KYC/CDD action…
Rule packs: kye:rule-pack:aml-financial-crimes · Constitution: 12 purpose permission
-
r11-record-keeping · enforced
Record-keeping (R.11): a replay-provable provenance pin preserves the AI AML decision lineage
Rule packs: kye:rule-pack:aml-financial-crimes · Constitution: 13 resilience loop
-
r16-travel-rule · enforced
Travel Rule (R.16): originator/beneficiary data and counterparty VASP due diligence on wire / virtual-asset…
Rule packs: kye:rule-pack:travel-rule-fatf-r16, kye:rule-pack:aml-financial-crimes · Sector packs: kye:sector-pack:travel-rule-fatf-r16 · Constitution: 54 sector pack foundry
-
r20-suspicious-transaction-reporting · enforced
Suspicious transaction reporting (R.20): SAR/STR filing is the killer consequential action requiring…
Rule packs: kye:rule-pack:aml-financial-crimes · Constitution: 36 governedui
How this widget is built
- Demonstrates
- KYE™ Compliance Mapping Rail™
- Components
- Framework requirement (clause)
- Coverage status
- KYE™ enforcement artefact (event, decision-record field, Evidence Pack™ entry)
- Flow
- Clause → status → the KYE™ artefact that enforces it, enforced requirements first. Architecture diagram
- Used on
- /compliance/fatf-40-recommendations/: On every framework page, after its opening.
Source: The Financial Action Task Force (FATF) 40 Recommendations are the global authority anchor for anti-money-laundering and counter-terrorist-financing (AML/CFT). They require a risk-based approach (R.1), customer due diligence and beneficial-ownership identification (R.10), record-keeping (R.11), the FATF Travel Rule for wire transfers and virtual-asset transfers (R.16), and suspicious-transaction reporting to the financial intelligence unit (R.20). KYE Protocol™(TM) governs WHETHER an AI agent's AML action may proceed at the action boundary - alert triage, sanctions screening, SAR/STR drafting, KYC/CDD - under a named compliance officer's authority, with due diligence recorded before the action and replay-provable provenance, and section-36 two-person sign-off on consequential filings (SAR/STR). KYE™ does not run transaction-monitoring models, does not decide whether a transaction is truly money-laundering, and does not replace the institution's AML program. · License: The FATF Recommendations are published by the Financial Action Task Force; KYE™ registry cites their recommendation numbers for mapping purposes.
By category
| Category | Reqs | Enforced | Designed | Advisory | Deferred | Coverage |
|---|---|---|---|---|---|---|
| Risk-based approach | 1 | 1 | 0 | 0 | 0 | 100% |
| Customer due diligence & beneficial ownership | 1 | 1 | 0 | 0 | 0 | 100% |
| Record-keeping | 1 | 1 | 0 | 0 | 0 | 100% |
| Travel Rule (wire / virtual-asset transfers) | 1 | 1 | 0 | 0 | 0 | 100% |
| Suspicious transaction reporting | 1 | 1 | 0 | 0 | 0 | 100% |
Every requirement → the KYE™ artefact that enforces it
| ID | Title | Status | KYE™ enforcement |
|---|---|---|---|
fatf-40-recommendations.r1-risk-based-approach | Risk-based approach (R.1): an AI AML action proceeds under a named-authority decision proportionate to assessed ML/TF risk | enforced | rule_packs: kye:rule-pack:aml-financial-crimesdictionaries: internalconstitution_refs: constitution/12-PURPOSE-PERMISSION.md |
fatf-40-recommendations.r10-customer-due-diligence | Customer due diligence & beneficial ownership (R.10): CDD/KYC result recorded before an AI KYC/CDD action proceeds | enforced | rule_packs: kye:rule-pack:aml-financial-crimesdictionaries: internalconstitution_refs: constitution/12-PURPOSE-PERMISSION.md |
fatf-40-recommendations.r11-record-keeping | Record-keeping (R.11): a replay-provable provenance pin preserves the AI AML decision lineage | enforced | rule_packs: kye:rule-pack:aml-financial-crimesdictionaries: internalconstitution_refs: constitution/13-RESILIENCE-LOOP.md |
fatf-40-recommendations.r16-travel-rule | Travel Rule (R.16): originator/beneficiary data and counterparty VASP due diligence on wire / virtual-asset transfers | enforced | rule_packs: kye:rule-pack:travel-rule-fatf-r16, kye:rule-pack:aml-financial-crimessector_packs: kye:sector-pack:travel-rule-fatf-r16dictionaries: internalconstitution_refs: constitution/54-SECTOR-PACK-FOUNDRY.md |
fatf-40-recommendations.r20-suspicious-transaction-reporting | Suspicious transaction reporting (R.20): SAR/STR filing is the killer consequential action requiring section-36 two-person sign-off | enforced | rule_packs: kye:rule-pack:aml-financial-crimesconstitution_refs: constitution/36-GOVERNEDUI.md |
Canonical KYE™ surfaces referenced on this page: KYE Protocol™.