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
Meridian Remit (simulated)
Subject
entity enti_sim_meri_5if3mzfr9pn
Transfer
acht_sim_meri_53fc9djfc50 · $916.24 · ach outgoing
Skoor at alert
20 clear
Hard signal
no
Policy
policy-v1
Opened
2026-09-17 19:32Z
Closed
Decision clock
none · due — no clock
Escalated

Draft narrative

What happened. Screening flagged entity enti_sim_meri_5if3mzfr9pn (High Risk Trading 2) for the sanctions_or_pep detector due to a high-risk designation. A single outgoing ACH credit of $916.24 USD (acht_sim_meri_53fc9djfc50) tied to this entity is under review; the transfer settled on 2026-09-10 with no return code. What the evidence shows. The alert score is 20, placing it in the clear band, and hard_signal is false. The only contributing signal is entity.high_risk (weight 20); PEP status is no and review reasons are none. The entity is VERIFIED, based in the US, and was last screened 2026-08-27, within a normal screening window. The transfer itself scored 20/clear with the same single signal, settled without a return code, and the counterparty's country is unknown but not flagged as sanctioned. Program-level KRIs show breaches in reserve_coverage_ratio, manual_review_aging_hours, ach_unauthorized_return_rate, and sanctioned_country_transfers, but none of these are linked in the evidence to this specific entity or transfer. What was checked. Alert scoring and signal detail, transfer status and return code, entity verification status, PEP flag, review reasons, and screening recency. Program KRI panel was reviewed for context but shows no entity-specific or transfer-specific tie to the breaches listed. What is recommended. Close this alert. The transfer has already settled with no return, the entity is verified with no PEP flag and no review reasons, and the score sits in the clear band with no hard signal. The program-level KRI breaches (reserve coverage, unauthorized returns, sanctioned-country transfers) are not connected to this entity or transfer in the evidence provided and should be tracked separately at the program level rather than driving disposition of this single alert.
Recommendation
close
Confidence
0.72
Model
claude-sonnet-5
Drafted
2026-09-17 19:32Z
Rationale
  • Score 20/clear, hard_signal false, single low-weight signal (entity.high_risk +20).
  • Entity is VERIFIED, PEP no, review reasons none, last screened 2026-08-27 (recent).
  • Transfer already SETTLED with no return code; nothing to hold or release.
  • Program KRI breaches (reserve_coverage_ratio, manual_review_aging_hours, ach_unauthorized_return_rate, sanctioned_country_transfers) are not tied to this entity/transfer in the evidence, so they do not support escalation of this specific alert.
  • No prior dispositions on this entity to indicate a repeat pattern.

Evidence

{
  "n": 964,
  "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.