Objective

Ensure every in-scope crypto transfer receives the approved monitoring workflow.

Evidence

  • Expected evidence: transaction ID, screening result, severity, disposition, reviewer and timestamp.
  • Evidence location: Odoo chatter/helpdesk and Crystal.
  • Retention: according to AML record-retention requirements.
  • Testing method: reconcile in-scope transfers to monitoring records.
  • Testing frequency: monthly.

Assurance

Runtime effectiveness results are maintained in Odoo and assessed through the Hermes workflow tracked in ISS-HERMES-001. This note defines design, ownership, evidence expectations and testing method; it does not contain a manually maintained operation, evidence or overall effectiveness rating.

  • Design status: implemented design; runtime effectiveness pending system-derived assessment

Relationships

History

  • 2026-07-26: Normalized evidence metadata and separated design status from runtime effectiveness.