Regulatory Coverage

EU compliance, mapped to the regulation.

Every obligation under MiCAR, AMLD6, DORA, NIS2, and AMLA — and exactly which Arkē pillar handles it. No vague claims, no marketing-speak. Sourced references link directly to the Official Journal and EUR-Lex.

MiCAR

Markets in Crypto-Assets Regulation

In force Full application from 30 December 2024 EUR-Lex ↗

MiCAR (Regulation EU 2023/1114) establishes the first comprehensive EU-wide framework for crypto-asset service providers (CASPs). It applies to anyone issuing crypto-assets or providing crypto-asset services — exchanges, custodians, stablecoin issuers — operating in the EU, regardless of where they are headquartered. Full application began 30 December 2024, with stablecoin provisions (Titles III and IV) applying from 30 June 2024.

Key obligations
  • AML/CFT controls: CASPs must implement know-your-customer (KYC), customer due diligence, and ongoing monitoring equivalent to traditional financial institutions under AMLD6
  • Travel Rule compliance: CASPs must collect, hold, and transmit originator and beneficiary information for crypto transfers (mirroring FATF Recommendation 16)
  • Sanctions screening: Transfers to or from sanctioned individuals, entities, or jurisdictions must be blocked and reported
  • Suspicious transaction reporting: CASPs must file SARs with the national FIU for transactions exhibiting AML typologies — structuring, layering, or sanctions evasion
  • Ongoing transaction monitoring: Automated detection of unusual or high-risk transfer patterns, especially cross-border and crypto-to-fiat movements
  • Third-country CASP assessment: Enhanced due diligence for counterparties in high-risk or non-cooperative jurisdictions
How Arkē handles it
Obligation Arkē pillar What it does
KYC / counterparty due diligence Screening ↗ Screens CASPs and their customers against OFAC SDN, EU consolidated, UN, PEP lists, and adverse media. Risk score 0–100 in under 5 seconds.
Sanctions screening (transfers) Screening ↗ Each named counterparty checked against live sanctions lists before clearing. Matched lists returned with evidence breakdown.
Travel Rule — ongoing monitoring Monitoring ↗ Batch transaction analysis detects structuring, corridor risk, velocity patterns, and crypto-to-fiat layering in a single API call.
SAR filing for suspicious transactions Reporting ↗ Generates AMLD6/MiCAR-compliant SAR drafts in FIU narrative format — all four mandatory sections, missing-field checklist, suggested filing jurisdiction.
Third-country enhanced due diligence Screening ↗ Adverse media and jurisdiction-level risk factors surfaced automatically — UAE, BVI, and other high-risk corridors flagged without manual configuration.

AMLD6

6th Anti-Money Laundering Directive

In force Transposed by EU member states from 3 June 2021 EUR-Lex ↗

AMLD6 (Directive EU 2018/1673) is the foundational AML framework for the EU financial sector. It harmonises the list of predicate offences for money laundering across all member states — expanding to 22 offences including cybercrime and environmental crime — and introduces corporate criminal liability. Obliged entities include credit institutions, payment service providers, cryptocurrency service providers, lawyers, accountants, and real estate professionals. Member states were required to transpose by 3 June 2021.

Key obligations
  • Customer due diligence (CDD): Verify identity of customers, beneficial owners, and counterparties before establishing a business relationship or executing transactions above applicable thresholds
  • Enhanced due diligence (EDD): Apply strengthened measures for high-risk third countries, PEPs, and complex ownership structures — including source-of-funds verification
  • Ongoing transaction monitoring: Continuously scrutinise transactions for consistency with the customer's risk profile and reported business activity
  • Suspicious activity reporting (SAR): File a SAR with the national FIU whenever there is suspicion of money laundering or terrorist financing — without tipping off the subject
  • Record-keeping: Retain CDD documentation and transaction records for a minimum of five years
  • Risk assessment: Maintain a firm-wide AML risk assessment, updated regularly, covering customers, products, geographies, and delivery channels
  • Corporate liability: Senior management and legal persons (entities) can be held criminally liable for AML failures — no longer just individuals
How Arkē handles it
Obligation Arkē pillar What it does
Customer due diligence Screening ↗ Instant KYC screening against OFAC, EU consolidated, UN, PEP lists, and open-source adverse media. Covers both persons and legal entities.
Enhanced due diligence (PEPs, high-risk countries) Screening ↗ PEP status and high-risk jurisdiction flags surfaced automatically. Adverse media covers regulatory enforcement actions and court filings.
Ongoing transaction monitoring Monitoring ↗ Batch analysis of transaction streams for structuring, velocity spikes, round-number clustering, and high-risk corridor flows.
Suspicious activity reporting Reporting ↗ AMLD6 FIU-format SAR drafts with all four mandatory sections. Suggested filing jurisdiction based on transaction corridors. Missing-field checklist included.
Risk-based customer profiling Screening ↗ + Monitoring ↗ Risk score 0–100 per counterparty; transaction risk scores per row. Both feed the compliance officer's risk-based decision workflow.

DORA

Digital Operational Resilience Act

In force Application from 17 January 2025 EUR-Lex ↗

DORA (Regulation EU 2022/2554) mandates that financial entities — banks, investment firms, insurance companies, payment institutions, CASPs — achieve a high common level of digital operational resilience. It has applied since 17 January 2025. The regulation covers five pillars: ICT risk management, ICT-related incident classification and reporting, digital operational resilience testing, third-party ICT risk management, and information sharing. For Arkē users, the most operationally relevant obligations concern ICT third-party risk and incident reporting.

Key obligations
  • ICT third-party risk management: Conduct pre-contract due diligence on all ICT service providers — including cloud, SaaS, and compliance tooling — before onboarding them
  • Contractual requirements for ICT providers: Ensure contracts with critical third-party ICT providers include defined SLAs, audit rights, data portability, and exit strategies
  • ICT-related incident reporting: Classify and report major ICT incidents to the competent authority within prescribed timelines (initial notification, intermediate, and final reports)
  • Operational resilience testing: Conduct regular resilience tests — including threat-led penetration testing (TLPT) for significant entities
  • Concentration risk monitoring: Identify and monitor concentration risk arising from reliance on a single third-party ICT provider across critical functions
  • Information and intelligence sharing: Participate in threat intelligence sharing arrangements as applicable
How Arkē handles it
Obligation Arkē pillar What it does
ICT third-party due diligence Screening ↗ Screen ICT vendors and critical third-party providers against sanctions, PEP, and adverse media before onboarding. Regulatory enforcement history surfaced from open-source intelligence.
Third-party concentration risk assessment Screening ↗ Batch-screen your full vendor register to surface overlapping risk exposures — same jurisdiction, same corporate group, or shared adverse media history.
ICT incident classification and reporting Reporting ↗ SAR and incident report drafts structured around FIU narrative format — adaptable for DORA incident notification to national competent authorities. Missing-field checklist highlights gaps before submission.
Ongoing vendor risk monitoring Monitoring ↗ Monitor transaction flows to and from third-party ICT providers for anomalies — financial behaviour inconsistent with contract terms is an early DORA red flag.

NIS2

Network and Information Security Directive 2

In force Transposition deadline: 17 October 2024 EUR-Lex ↗

NIS2 (Directive EU 2022/2555) significantly expands the original NIS Directive's scope, now covering a broad range of sectors — financial services, digital infrastructure, cloud providers, managed security services, and more. EU member states were required to transpose NIS2 by 17 October 2024. For financial entities subject to both NIS2 and DORA, DORA is lex specialis and takes precedence; NIS2 applies to the broader supply chain and digital service providers that are not themselves financial entities.

Key obligations
  • Cybersecurity risk management: Implement risk-proportionate technical and organisational measures — including access controls, incident detection, cryptography, and supply chain security
  • Incident notification: Report significant cybersecurity incidents to the national CSIRT or competent authority within 24 hours (early warning), 72 hours (notification), and 30 days (final report)
  • Supply chain security: Assess and manage cybersecurity risks in supply chains, including ICT product and service providers
  • Business continuity: Maintain backup management, disaster recovery, and crisis management procedures
  • Senior management accountability: Management bodies of essential and important entities are personally responsible for NIS2 compliance
  • Vulnerability disclosure and information sharing: Cooperate with national authorities and participate in information sharing frameworks
How Arkē handles it
Obligation Arkē pillar What it does
Supply chain risk assessment Screening ↗ Screen third-party digital service providers, software vendors, and managed service providers against sanctions, adverse media, and regulatory enforcement databases before onboarding.
Incident notification (structured reporting) Reporting ↗ SAR-format draft generation adaptable for NIS2 incident notifications — structured narrative sections, missing-field checklist, suggested authority by jurisdiction.
Ongoing supplier monitoring Monitoring ↗ Monitor financial transactions with digital supply chain partners for unusual patterns — velocity changes or corridor anomalies can indicate supplier compromise or fraud.
Third-party PEP and sanctions exposure Screening ↗ Identify if key personnel or beneficial owners of supply chain entities are politically exposed or appear on EU/UN/OFAC sanctions lists — a NIS2 governance risk factor.

AMLA

Anti-Money Laundering Authority

Phased 2025–2027 Authority established July 2025; direct supervision from 2027 EUR-Lex ↗

AMLA (Regulation EU 2024/1620) creates a new EU-level supervisory authority headquartered in Frankfurt that will directly supervise the highest-risk obliged entities across the Union — approximately 40 cross-border financial institutions — and coordinate national supervisors for all other obliged entities. The authority was formally established in July 2025. Direct supervisory powers over selected entities begin in 2027. AMLA will maintain the EU AML rulebook (the new AML Regulation, adopted alongside AMLA), consolidating and replacing AMLD4, AMLD5, and AMLD6 into a single directly applicable regulation.

Key obligations (transitional and prospective)
  • Direct supervision readiness: Obliged entities identified by AMLA for direct supervision must demonstrate full compliance with the EU AML rulebook — gap assessments and documentation are required now
  • Harmonised CDD and EDD standards: AMLA will issue binding technical standards (BTS) to harmonise CDD processes across member states — obliged entities should track AMLA publications and align processes proactively
  • Centralised beneficial ownership data: AMLA will coordinate cross-border beneficial ownership register access — entities must ensure their beneficial ownership documentation is current and consistent
  • Cross-border SAR coordination: AMLA coordinates FIU cooperation for cross-border suspicious transaction analysis — SAR quality and consistency become more important as reports feed centrally
  • Crypto-asset provider integration: CASPs under MiCAR will fall within AMLA's supervision perimeter — compliance with both MiCAR and AMLA is required for crypto obliged entities
  • Supervisory convergence: National supervisors will be required to follow AMLA peer review outcomes — regulatory expectations will converge upwards across all EU member states
How Arkē handles it
Obligation Arkē pillar What it does
CDD / EDD documentation readiness Screening ↗ Every screening run produces a structured evidence record — matched lists, adverse media findings, risk score, and timestamp — audit-ready for AMLA supervisory review.
Beneficial ownership screening Screening ↗ Screen ultimate beneficial owners (UBOs) against PEP lists and sanctions — the most frequent gap in AMLA gap assessments for SMEs and fintechs.
Cross-border SAR quality Reporting ↗ AMLD6/AMLA-compliant SAR drafts with narrative sections aligned to FIU format. Missing-field alerts ensure completeness before filing — critical as AMLA centralises cross-border SAR review.
Ongoing monitoring for supervisory readiness Monitoring ↗ Continuous transaction monitoring demonstrates the "ongoing monitoring" requirement central to AMLA's risk-based supervisory expectations. Batch analysis covers AML typologies relevant to AMLA's enforcement priorities.
MiCAR + AMLA dual compliance (CASPs) Screening ↗ + Monitoring ↗ + Reporting ↗ CASPs subject to both MiCAR and AMLA supervision can use all three Arkē pillars from a single integration — no need to stitch together separate vendors for screening, monitoring, and SAR reporting.
Regulation Tracker — Live

Regulations change. Arkē updates within 24 hours of publication in the Official Journal of the European Union. New EBA guidelines, ESA technical standards, and AMLA binding instruments are applied to the obligation mapping as they come into force.

Most recent update applied:  EBA AML/CFT Guidelines — Amendment No. 2026/03 (13 May 2026) ·  EUR-Lex ↗

Need a regulation we haven't mapped yet?

DORA RTS on ICT risk, SFDR, PSD3, AML Regulation 2024? Tell us and we'll map it within 24 hours of the next Official Journal publication.