aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- aml-kyc-basics
- description
- Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
03 SKILL.md 正文
AML / KYC Basics
Overview
Anti-money laundering (AML) and know-your-customer (KYC) programs prevent the financial system from being used for illicit finance. They combine identification, risk rating, ongoing monitoring, and reporting duties.
When to Use
- Customer onboarding and CDD/EDD design
- Periodic KYC refresh programs
- Transaction monitoring alert concepts
- SAR/STR escalation awareness
- AML training and culture support
Core Practices
- Identify and verify customers (and beneficial owners where required)
- Risk-rate customers and apply proportionate due diligence
- Monitor transactions and behavior for unusual patterns
- Escalate and report suspicious activity through defined channels
- Screen against sanctions and prohibited parties as required
- Retain records for mandated periods
Principles
- Risk-based approach — not identical effort for every customer
- Tip-offs and tipping-off prohibitions matter operationally
- Quality of KYC data drives monitoring effectiveness
- Compliance and business share responsibility for outcomes
Verification
- [ ] CDD/EDD requirements are defined by risk tier
- [ ] Escalation path for suspicious activity is clear
- [ ] Sanctions screening coverage is defined and owned
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.
data-governance
Establish data governance — ownership, policies, decision rights, and accountability — so data is trusted, compliant, and usable across the organization. Use when designing governance operating models, assigning data owners, or fixing chronic trust and access problems.