SKOOR Risk Money movement. Skoored by AI.

Alert · reviewed · open

Activity on an entity flagged by screening (PEP status no, high risk).

Detector
sanctions_or_pep
Severity
high
Program
Harbor Marketplace Payouts (simulated)
Subject
entity enti_sim_harb_skonrvy3x6
Transfer
acht_sim_harb_af8pf8z57xy · $378.08 · ach outgoing
Skoor at alert
20 clear
Hard signal
no
Policy
policy-v1
Opened
2026-09-17 19:31Z
Closed
Decision clock
none · due — no clock
Escalated

Draft narrative

What happened. Alert 63d9fc0a-c772-4bd3-a704-503c809bd463 was opened by the sanctions_or_pep detector for entity enti_sim_harb_skonrvy3x6, which screening has flagged as high risk (not PEP). The detector routes to review on every hit regardless of score; the route reason confirms this ('detector always reviewed'). The associated activity is a single settled ACH outgoing credit of $378.08 USD (acht_sim_harb_af8pf8z57xy), created 2026-08-28. What the evidence shows. The alert score is 20, banded 'clear,' with hard_signal false. The only contributing signal is entity.high_risk (+20); there is no PEP flag, no adverse review reasons, and the entity's verification status is VERIFIED. Last screening was 2026-08-27, one day before the transfer. The transfer itself settled with no return code and no counterparty country data flagged as sanctioned. Program KRIs show most metrics in 'ok' or 'watch' range; two items are in 'breach' (manual_review_aging_hours=1438.0 hours, ach_unauthorized_return_rate=0.0102), but these are program-wide metrics not specific to this entity or transfer, and nothing in the evidence links them to this alert's subject. What was checked. Detector output and score band, hard-signal flag, entity screening record (PEP status, verification, review reasons, last screened date), transfer status and return code, counterparty record, program KRI panel, and prior dispositions (none on file). What is recommended. No evidence here indicates a person needs to intervene on this specific transfer: the transfer already settled with no return, the entity is verified, PEP is no, and the score sits in the clear band with no hard signal. The elevated program-level KRIs (manual_review_aging_hours, ach_unauthorized_return_rate) are not tied to this entity or transfer in the evidence provided and should be tracked at the program level separately, not through this alert.
Recommendation
close
Confidence
0.72
Model
claude-sonnet-5
Drafted
2026-09-17 19:31Z
Rationale
  • Score 20 in band 'clear' with hard_signal false and only one contributing signal (entity.high_risk).
  • Entity is VERIFIED, PEP no, review reasons none, last screened one day before the transfer.
  • Transfer status is SETTLED with return code none; funds already moved and there is no pending hold to release.
  • Route reason is a standing detector policy ('always reviewed'), not evidence of elevated risk on this specific activity.
  • Program KRI breaches (manual_review_aging_hours, ach_unauthorized_return_rate) are aggregate figures with no direct link shown to this entity or transfer, so they do not by themselves support escalation of this alert.
  • No prior dispositions exist to indicate a recurring pattern for this entity.

Evidence

{
  "n": 1585,
  "band": "clear",
  "skoor": 20,
  "signals": [
    {
      "code": "entity.high_risk",
      "detail": "entity marked high risk by screening",
      "weight": 20
    }
  ],
  "routeReason": "detector always reviewed"
}

Skoor signals

SignalWeightHardDetail
entity.high_risk+20entity marked high risk by screening

Decision

Sign in as an operator to decide. Operator sign-in →

Dispositions

No disposition yet.

Actions

Freeze, request to program, and suspend need a second, distinct approver. Clear hold, cancel, and pause execute on the requester's approval. Executed through the bank's own API with the tenant's sandbox key; a dry run when there is none.

No actions requested.