SKOOR Risk Money movement. Skoored by AI.

Alert · reviewed · open

Activity on an entity flagged by screening (PEP status potential).

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

Draft narrative

What happened. Alert 76988042-067c-45cb-9e81-3080cc4181de fired on entity enti_sim_harb_azbiyidj3x2 under the sanctions_or_pep detector due to a potential PEP match. It is tied to one settled outgoing ACH debit of $607.34 to counterparty cpty_sim_harb_2zcowbj75cy. What the evidence shows. The entity is a PERSON with verification status VERIFIED, high_risk false, no open review reasons, last screened 2026-06-25T12:01:30.000Z (before the alert opened). The transfer scored 25 (band clear, n=483, confidence 1) with hard_signal false. Contributing signals were entity.pep_potential(+15) and counterparty.first_time(+10), neither of which alone or combined moved the score out of the clear band. The transfer is SETTLED with no return code. Program-level KRIs show sanctioned_country_transfers=0, ach_overall_return_rate=0, and ach_unauthorized_return_rate=0, none of which support an active sanctions or PEP concern tied to this transfer. What was checked. Entity screening status and last screened date, transfer score and band, hard signal flag, transfer settlement and return status, counterparty history flag, and program KRIs including pep_flagged_entities (1 of 30, watch), high_risk_entity_share (0.067, watch), and manual_review_aging_hours (1438 hours, breach). The aging breach reflects a program-level review backlog across all alerts, not evidence specific to this entity or transfer. What is recommended. Close this alert. The entity is verified with no open review reasons, the transfer scored in the clear band with no hard signal, and the transfer has already settled with no return. Separately, flag the manual_review_aging_hours breach (1438 hours, n=2) to the program owner as an operational backlog item unrelated to this specific alert's disposition.
Recommendation
close
Confidence
0.74
Model
claude-sonnet-5
Drafted
2026-09-17 19:30Z
Rationale
  • Skoor 25, band clear, hard_signal false
  • Entity verification VERIFIED, high_risk false, review reasons none
  • Transfer already SETTLED with return code none, no funds to hold
  • Program KRIs show no sanctioned-country or unauthorized-return activity
  • Manual_review_aging_hours breach is a program-level KRI, not alert-specific evidence, so it does not change this alert's disposition but is worth separate follow-up

Evidence

{
  "n": 483,
  "band": "clear",
  "skoor": 25,
  "signals": [
    {
      "code": "entity.pep_potential",
      "detail": "potential PEP match",
      "weight": 15
    }
  ],
  "routeReason": "detector always reviewed"
}

Skoor signals

SignalWeightHardDetail
entity.pep_potential+15potential PEP match
counterparty.first_time+10first transfer with this counterparty

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.