Regulations

Illustrative: obliged entities are expected to keep CDD controls and beneficial ownership information current and to cooperate with their supervisor. Confirm specific duties with counsel.

In this sample, the fixed example cases are tagged with AMLA-related CDD obligations and an illustrative readiness figure. It shows the concept only; it is not an evidence package or a supervisory assessment.

All obliged entities must apply unified CDD standards, PEP screening, 5-year record retention, and STR reporting procedures directly under the AMLR without national variation.

In this sample, example alerts carry a CDD reference so you can see how a signal is linked to an obligation. The links are fixed sample mappings, reviewed by a person — not an automatic reporting determination.

Obliged entities must reflect AMLD6 predicate offence categories in their AML monitoring logic and ensure that corporate compliance policies cover criminal liability for legal persons.

In this sample, some example cases cite a predicate-offence category as illustrative context. It is not a legal classification.

Transactions involving high-risk patterns, jurisdictions, or customer anomalies should trigger enhanced monitoring and due diligence logic.

In this sample, these fields from the example records feed a deterministic score. KYC status is a value the example data asserts; nothing here verifies identity.

Suspicious activity should be documented in a form that can be escalated, reviewed, and eventually turned into official reporting packages.

In this sample, each case shows a summary, a narrative and legal-basis references. Reports in the showcase are samples; any filing is prepared and submitted by authorized people.

CASPs must obtain authorisation from national competent authorities, publish compliant whitepapers for asset-referenced and e-money tokens, maintain sufficient reserves, and implement market abuse monitoring.

In this sample, the crypto example case shows reserve and custody signals mapped to MiCA topics. It is an illustrative mapping, not reserve monitoring and not a MiCA compliance status.

Crypto transfers should be assessed with sender/receiver identity controls, route visibility, and operational integrity expectations.

In this sample, Travel Rule references appear on the crypto example case. This is an illustrative mapping on fixed data; nothing is monitored.

Originator and beneficiary data must accompany transfers, VASP counterparty due diligence must be conducted, and unhosted wallet transfers must be screened for ML/TF risk.

In this sample, Travel Rule gaps on the example data appear as illustrative alerts. Nothing here tracks real transfers.

Users and regulators should be able to understand why an AI-supported compliance classification was produced and which factors materially influenced the result.

In this sample, the dashboard shows a summary, a narrative, deterministic reasoning and legal-basis references for each example case.

High-risk AI systems must preserve meaningful human control over consequential decisions.

In this sample, critical example cases show recommended actions and a human-review expectation; nothing is closed automatically.

A high-risk AI system should be technically robust, sufficiently accurate for its use case, and capable of post-event traceability.

In this sample, the audit trail and the case, evidence and report pages show the traceability chain on fixed example data.

Entities must maintain a documented ICT risk management policy (Article 5), classify and report major incidents to competent authorities, and ensure third-party ICT contracts include DORA-required resilience clauses.

In this sample, DORA topics appear as illustrative mappings on the example data. ICT incident management is not currently available in the customer workspace.