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
Northwind Payroll (simulated)
Subject
entity enti_sim_nort_91eod4q93y
Transfer
acht_sim_nort_6bv8f9q5ae · $1,122.68 · ach outgoing
Skoor at alert
20 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 6e56dfb2-c4a5-4fe3-b493-c115413e8511 was generated by the sanctions_or_pep detector for entity enti_sim_nort_91eod4q93y, which screening marked high risk. The alert was opened 2026-09-17T19:30:10.688Z and routed to review because this detector is always reviewed regardless of score. What the evidence shows. The entity screening record shows PEP status no, review reasons none, verification status VERIFIED, and last screened 2026-06-26T12:01:30.000Z. The only signal driving the score is entity.high_risk (+20), giving a skoor of 20 in the clear band with hard_signal false. The associated transfer, acht_sim_nort_6bv8f9q5ae, is a $1122.68 USD outgoing ACH debit under the Northwind Payroll program, already SETTLED with no return code. Counterparty country is unknown but no other signal or review reason attaches to this counterparty or transaction. What was checked. I checked the screening result (PEP no, verification status, review reasons), the transfer status and amount against the declared program volume ($2,500,000.00/month, ACH, US), the skoor and band for both the alert and the transfer, and prior dispositions, of which there are none. Model confidence on the transfer skoor is 0.355 with n=44, which is a thin sample for confidence in the score itself, though the underlying entity attributes (PEP no, no review reasons, verified) are directly stated fields, not scored inferences. What is recommended. No signal beyond the single high-risk flag is present, the entity is verified, PEP status is no, and there are no review reasons. The transfer has already settled, so holding funds is not an option and release does not apply since nothing was held. Recommend closing the alert. A person should still note that this is a first alert on this entity and no prior dispositions exist, so if the high-risk flag recurs on future activity it should be reviewed again.
Recommendation
close
Confidence
0.62
Model
claude-sonnet-5
Drafted
2026-09-17 19:30Z
Rationale
  • Skoor 20 sits in the clear band with hard_signal false.
  • Entity is VERIFIED, PEP no, and review reasons are none.
  • Only signal present is entity.high_risk(+20); no additional signals corroborate elevated concern.
  • Transfer is already SETTLED with no return code, so hold/release are not applicable.
  • Transfer skoor confidence is low (0.355, n=44), which limits certainty in the score but does not contradict the directly stated entity fields.
  • No prior dispositions exist for this entity, so there is no pattern of repeated alerts to escalate.

Evidence

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