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_3s73e88g9h1 · $592.80 · 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. Alert generated by the sanctions_or_pep detector on entity enti_sim_harb_skonrvy3x6, a verified US business flagged high risk by screening. The alert was opened because this detector always routes flagged entities to review, not because of an elevated score. The associated transfer is a settled $592.80 outgoing ACH credit with no return code.
What the evidence shows. Screening shows PEP status no, review reasons none, and last screened 2026-08-27T13:10:35.000Z, about three weeks before this alert opened. Entity verification status is VERIFIED. The alert skoor is 20, band clear, hard_signal false, driven solely by the entity.high_risk signal (+20), which reflects the entity's standing classification rather than new adverse activity. The transfer itself carries the same clear-band score and no additional signals. The transfer is already SETTLED, so there is no held transfer to release.
What was checked. Reviewed the entity record (verification, PEP flag, review reasons, last screened date), the transfer record (status, return code, amount), the alert score and signal detail, and program KRIs for related patterns. Program KRIs show high_risk_entity_share at 0.067 (watch, n=30) and pep_flagged_entities at 1 (watch, n=30), both within the program's existing watch thresholds and not specific to this entity. Two KRIs are in breach (manual_review_aging_hours, ach_unauthorized_return_rate) but neither is tied to this entity or transfer in the evidence provided. No prior dispositions exist for this alert.
What is recommended. Close this alert. The entity is verified, not PEP, has no open review reasons, and was screened within the last month with no adverse findings. The transfer has settled with no return code. The only signal present (entity.high_risk) reflects a standing classification already accounted for in the clear-band score, not new activity requiring a person to intervene before funds move. The transfer has already settled, so no hold or release action applies.
- Recommendation
- close
- Confidence
- 0.72
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:32Z
- Rationale
- Skoor 20, band clear, hard_signal false; only signal is entity.high_risk which is a standing classification, not new adverse information.
- Entity is VERIFIED, PEP no, review reasons none, last screened within the past month.
- Transfer is SETTLED with no return code; there is no held transfer to act on, so release does not apply.
- Program KRIs tied to high-risk/PEP entity share are at watch level (not breach) and are program-wide, not specific evidence against this entity.
- Two KRI breaches exist (manual_review_aging_hours, ach_unauthorized_return_rate) but the evidence does not connect them to this entity or transfer, so escalation is not supported on this alert alone.
- No prior dispositions exist to indicate a repeat or worsening pattern for this entity.
Evidence
{
"n": 2195,
"band": "clear",
"skoor": 20,
"signals": [
{
"code": "entity.high_risk",
"detail": "entity marked high risk by screening",
"weight": 20
}
],
"routeReason": "detector always reviewed"
}
Skoor signals
| Signal | Weight | Hard | Detail |
|---|---|---|---|
| entity.high_risk | +20 | entity 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.