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_3gjbb7kq7af · $357.70 · ach outgoing
- Skoor at alert
- 20 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. Alert 6f56550e-4023-4d5b-bfce-713216c6c196 fired on entity enti_sim_harb_skonrvy3x6 under the sanctions_or_pep detector because the entity is marked high risk by screening. The alert scored 20 (band clear, hard_signal false) and was routed to review only because this detector always routes high-risk entities regardless of score. The transfer in scope is an outgoing ACH credit of $357.70 USD (acht_sim_harb_3gjbb7kq7af), status SETTLED, no return code.
What the evidence shows. The entity is a VERIFIED business, PEP status is no, review reasons are none, and it was last screened 2026-06-26. The only signal present is entity.high_risk (+20), which alone keeps the alert in the clear band. The transfer itself settled with no return code and no counterparty country data flagged as high risk. Transfer-level skoor is also 20/clear with n=1320 and confidence=1. No prior dispositions exist for this entity.
What was checked. Reviewed the alert signals, entity verification status, PEP flag, review reasons, and screening date. Reviewed the transfer status and return code. Reviewed program KRIs for related context: high_risk_entity_share is at 0.067 (watch), pep_flagged_entities at 1/30 (watch), manual_review_aging_hours is in breach (1438 hours), and ach_unauthorized_return_rate is in breach (0.0104). None of these KRIs are specific to this entity or this transfer; they reflect program-wide conditions and are not tied by the evidence to this alert.
What is recommended. Close this alert. The entity is verified, not PEP, has no open review reasons, and the only signal is the high-risk flag that already keeps it in the clear band. The associated transfer settled without incident. The transfer is not held, so no release action applies. The program-level KRI breaches (manual_review_aging_hours, ach_unauthorized_return_rate) are noted for separate operational review but do not provide entity-specific evidence to escalate this particular alert.
- Recommendation
- close
- Confidence
- 0.78
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:31Z
- Rationale
- Skoor 20, band clear, hard_signal false; only signal is entity.high_risk (+20).
- Entity is VERIFIED, PEP no, review reasons none, last screened 2026-06-26.
- Transfer status is SETTLED with no return code; transfer skoor also 20/clear with confidence 1.
- Route to review was automatic (detector always reviewed), not driven by elevated score.
- No prior dispositions exist for this entity to suggest a pattern.
- Program KRI breaches (manual_review_aging_hours, ach_unauthorized_return_rate) are program-wide and not linked in the evidence to this specific entity or transfer, so they do not support escalation of this alert.
Evidence
{
"n": 1320,
"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.