EU AML and KYC testing requirements
EU anti-money laundering rules require banks, payment institutions, and crypto-asset service providers to verify customers, screen them against sanctions lists, and monitor transactions. Regulation (EU) 2024/1624 and Directive (EU) 2024/1640 replace Directive (EU) 2015/849 from 10 July 2027. AML testing verifies onboarding, screening, monitoring, and travel rule logic. FintechAssuranceLabs produces screening test data sets and monitoring rule test matrices.
- Jurisdiction
- EU (Directive (EU) 2015/849 until 10 July 2027, then Regulation (EU) 2024/1624 and Directive (EU) 2024/1640; Regulation (EU) 2023/1113 for transfers); FATF Recommendations and US BSA rules as reference
- Primary source
- eur-lex.europa.eu
Engineering interpretation of testing requirements, not compliance advice.
What EU AML and KYC rules require
Directive (EU) 2015/849 sets EU customer due diligence (CDD) rules through national law until Directive (EU) 2024/1640 repeals it with effect from 10 July 2027 (Article 77). From that date, Regulation (EU) 2024/1624 (AMLR, published 19 June 2024, checked on 2026-09-16) applies directly (Article 90) to obliged entities, which include credit institutions and financial institutions such as payment institutions and crypto-asset service providers (Articles 2(1)(6) and 3). The EU Anti-Money Laundering Authority (AMLA, Regulation (EU) 2024/1620) in Frankfurt selects 40 obliged entities during 2027 and supervises them directly from 2028 (AMLA, checked on 2026-09-16). The AMLR rules that change test scope:
- When CDD applies (Article 19). CDD applies to new business relationships and to occasional transactions of EUR 10,000 or more, including linked transactions. Crypto-asset service providers apply CDD to occasional transactions from EUR 1,000 and identify and verify the customer below that value.
- CDD measures (Article 20(1)). Point (d) extends the targeted financial sanctions check to persons who control a legal entity or hold more than 50% of it, individually or collectively.
- Identity data and verification (Articles 22 and 23). Article 22(1) lists the minimum data, including place and full date of birth and nationalities. Verification uses an identity document or eIDAS identification at assurance level substantial or high (22(6)). An account may open early, but no transactions run until the customer and beneficial owners are verified (23(3)).
- Ongoing monitoring (Article 26). Customer information is updated at intervals of no more than 1 year for higher-risk customers and 5 years for others (26(2)). Credit and financial institutions repeat the sanctions check on every new designation (26(4)).
- Enhanced due diligence and PEPs (Articles 34, 42, 45). Complex, unusually large, or unusual-pattern transactions are examined (34(2)). A politically exposed person relationship needs senior management approval (42(1)), and the measures continue for at least 12 months after the person leaves office (45(2)).
- Automated decisions (Article 76(5)). An automated decision to refuse or end a relationship is subject to meaningful human intervention.
- Reporting and records (Articles 69 and 77). Suspicious transactions, including attempted ones, are reported to the FIU, and FIU requests get an answer within 5 working days (69(1)). Records are kept for 5 years after the relationship ends (77(3)).
Regulation (EU) 2023/1113, the travel rule, applies from 30 December 2024. Transfers of funds carry payer and payee information (Article 4), and the payee's provider verifies payee information above EUR 1,000 (Article 7(3)). Crypto-asset transfers carry originator and beneficiary information at any amount (Article 14), with an ownership assessment for self-hosted addresses above EUR 1,000 (14(5), 16(2)). Since 9 January 2025, Regulation (EU) 260/2012 Article 5d, inserted by Regulation (EU) 2024/886, requires instant credit transfer providers to screen all users against EU targeted sanctions at least daily and on every list change, instead of during execution.
The global baseline is the FATF Recommendations (updated June 2026, checked on 2026-09-16): Recommendation 10 on CDD, Recommendation 15 on new technologies including virtual asset service providers, and Recommendation 16 on payment transparency, revised in June 2025 with effect by the end of 2030. In the US, the FinCEN CDD rule (31 CFR 1010.230) requires identification of each individual owning 25% or more of a legal entity customer and one control person. FinCEN order FIN-2026-R001 of 13 February 2026 allows institutions to limit repeat identification to the first account opening and risk-based triggers. The US funds travel rule (31 CFR 1010.410(f)) applies from $3,000. Canada is on the FINTRAC testing requirements page.
What AML and KYC testing verifies
| Requirement | What we test | Evidence produced |
|---|---|---|
| AMLR Article 22(1): minimum identity data per customer | Onboarding submissions with place of birth or nationality missing on web, app, and API | Field validation result per onboarding channel |
| AMLR Article 23(3): no transactions before customer and beneficial owner verification | Card payments, transfers, and top-ups on an account with verification still pending | Blocked transaction log per payment type |
| AMLR Article 20(1)(d): sanctions check covers owners above 50%, individually or collectively | Synthetic legal entities with one sanctioned owner at 51% and two sanctioned owners at 30% each | Ownership screening decision per synthetic entity |
| AMLR Article 26(4): sanctions check repeated on each new designation | A synthetic list update that designates an existing customer and an existing beneficial owner | Rescreening log with list version and time from list update to alert |
| AMLR Articles 42(1) and 45(2): PEP approval and 12-month continuation | Customers who left office 11 months and 13 months ago, and an API call that skips the approval step | PEP decision table with approval record per customer |
| AMLR Articles 26(1) and 34(2): unusual transactions are detected | Synthetic transactions below, at, and above each monitoring rule threshold, including amounts split across days | Transaction monitoring rule test matrix with expected and actual alerts |
| AMLR Article 76(5): human intervention in automated refusals | Onboarding refusals and account closures that an automated rule triggers | Decision trail showing the reviewer action before each final refusal |
| Regulation (EU) 2023/1113 Articles 7(2) and 7(3): missing information detection and payee verification above EUR 1,000 | Inbound transfers from a non-EU provider with the payer address missing, and payee verification at EUR 1,000.00 and EUR 1,000.01 | Missing information detection log per payment message |
| Regulation (EU) 2023/1113 Articles 14 and 17: crypto travel rule data and handling of missing data | Withdrawals of EUR 10 and EUR 1,000.01 to hosted and self-hosted addresses, and an inbound transfer with no originator name | Travel rule message capture with the execute, reject, or return decision per transfer |
| Regulation (EU) 260/2012 Article 5d: daily user screening for instant credit transfers | A list update during the day and an instant transfer to a user designated in that update | Screening run timestamps per calendar day with the instant transfer outcome |
Artifacts supervisors and auditors request
- Written CDD, sanctions, and reporting procedures, and the results of the independent audit function or external expert that tests them (Article 9(2)).
- CDD records with decisions, supporting documents, and justifications, including refused and terminated customers (Article 21(3)).
- Records of each Article 69(2) assessment, whether or not a suspicious transaction report followed (Article 77(1)(b)).
- Sanctions list update history with the time of each rescreening run (Article 26(4); Regulation (EU) 260/2012 Article 5d(1)).
- Travel rule records per transfer and reports on providers that repeatedly omit required information (Regulation (EU) 2023/1113 Article 17(2)).
- For US covered financial institutions: beneficial owner certifications and verification records, retained for 5 years (31 CFR 1010.230(i)).
Common AML and KYC findings
- Account usable during pending verification. A card top-up and an outbound transfer succeed while identity verification is still in progress. The defect breaks AMLR Article 23(3).
- Sanctions screening only at onboarding. A designation published after onboarding never reaches existing customers until the next periodic batch. The defect breaks AMLR Article 26(4).
- Ownership checked per shareholder only. Two sanctioned persons with 30% each pass because no single holding exceeds 50%. The defect breaks the "collectively" condition in AMLR Article 20(1)(d).
- PEP flag removed on the last day in office. Enhanced monitoring stops on the end date in the PEP data feed. The defect breaks AMLR Article 45(2).
- Automatic account closure. A risk score above the threshold closes the account with no reviewer step. The defect breaks AMLR Article 76(5)(b).
- Funds threshold copied to crypto withdrawals. Originator data is sent only for crypto transfers above EUR 1,000. The defect breaks Regulation (EU) 2023/1113 Article 14(1), which sets no threshold.
- Instant transfer screened at execution. The instant payment flow screens payee names against EU targeted sanctions during each transfer and rejects valid payments on near matches. The defect breaks Regulation (EU) 260/2012 Article 5d(2).
- Control person missing. The US onboarding form collects 25% owners but no single control person. The defect breaks 31 CFR 1010.230(d)(2).
How we cover AML and KYC testing
KYC, AML and fraud testing delivers the "Onboarding and verification scenario suite" for Articles 22 and 23, the "Sanctions and PEP screening test data set and results" for Articles 20(1)(d), 26(4), and 45, and the "Transaction monitoring rule test matrix" for Article 34(2). The "False positive and false negative rate report" shows where screening misses a true match or blocks legitimate customers; the sanctions screening false positive testing guide covers the method. The same test evidence supports the independent test of controls under Article 9(2)(b).
Crypto exchange and wallet testing covers travel rule data in the "Deposit and withdrawal test suite per supported chain", including self-hosted address checks under Article 14(5). Crypto-asset service provider rules are on the MiCA page, and personal data limits on the GDPR page.
We test AML and KYC flows for KYC and AML vendors, neobanks, crypto exchanges, remittance, trading, lending, BNPL, business banking, and BaaS programmes. All test identities and sanctions list entries are synthetic.
Related
Segments
- KYC/AML and anti-fraud
- Neobanks and digital banking
- Crypto exchanges and wallets
- International transfers
- Investing and trading apps
- Consumer lending and credit marketplaces
- Buy now pay later
- Robo-advisors and wealthtech
- Business banking
- Spend management and corporate cards
- Banking-as-a-Service and card issuing
- Payment acquiring
- AP/AR automation and treasury
- Family and youth banking
Adjacent standards
Questions
What are KYC regulations?
What is KYC compliance?
Who must comply with KYC regulations?
What are the penalties for KYC non-compliance?
Scope your testing
Send FintechAssuranceLabs your product, segment, money flows, and the standards that need evidence, and get a proposed test scope with its deliverables.
Scope your testing