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
Lantern Lending (simulated)
Subject
entity enti_sim_lant_866sn4vcjd
Transfer
acht_sim_lant_c34meeg3eaa · $998.11 · ach outgoing
Skoor at alert
15 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. An alert fired on entity enti_sim_lant_866sn4vcjd, a person named "Potential Pep 3", due to a potential PEP screening match. The alert is tied to one settled outgoing ACH credit transfer of $998.11 dated 2026-09-08. What the evidence shows. The alert score is 15, banded clear, driven by a single signal entity.pep_potential (+15). Hard signal is false. The entity is VERIFIED, high_risk is false, review reasons are none, and last screened 2026-09-01. The transfer itself carries the same skoor of 15, band clear, with no other risk signals, and it settled with no return code. Program-level KRIs show pep_flagged_entities at 1 of 33 (watch, but consistent with a single flagged entity), high_risk_entity_share and verification_denial_rate both low (0.03), stale_screening_share at 0, and ach return rates near zero. Two KRIs are outside normal range: hold_aging_hours (watch) and manual_review_aging_hours (breach), but neither is specific to this entity or transfer and no prior dispositions exist to suggest a pattern. What was checked. Alert evidence and score, transfer status and return code, entity verification and risk flags, screening recency, program KRIs for PEP and screening health, and prior disposition history for this entity. What is recommended. Close the alert. The PEP match is potential only, the entity is verified with no high-risk flag and no review reasons, screening is current (2026-09-01), the transfer settled cleanly with no return, and the score bands clear with no hard signal. The manual_review_aging_hours breach is a program-level metric unrelated to this specific entity or transfer and does not present evidence requiring a hold on these funds. A person should note the aging breach separately if it recurs across other alerts.
Recommendation
close
Confidence
0.72
Model
claude-sonnet-5
Drafted
2026-09-17 19:32Z
Rationale
  • Skoor 15, band clear, hard_signal false at both alert and transfer level
  • Entity is VERIFIED, high_risk false, review reasons none, last screened 2026-09-01, nine days before transfer
  • Transfer settled, no return code, no additional signals beyond the single PEP-potential flag
  • Program KRIs for PEP share, verification denial, stale screening, and returns all within normal range
  • No prior dispositions exist for this entity to indicate a repeat or escalating pattern
  • manual_review_aging_hours is in breach at program level but is not tied to this entity or transfer and does not itself justify holding these settled funds

Evidence

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

Skoor signals

SignalWeightHardDetail
entity.pep_potential+15potential PEP match

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.