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_87255z5ue6 · $1,771.39 · 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. An alert fired on entity enti_sim_nort_91eod4q93y under the sanctions_or_pep detector because screening marked the entity high risk. The route is always-review for this detector, so the alert opened regardless of score. The linked transfer is an ACH outgoing credit of $1,771.39 USD (acht_sim_nort_87255z5ue6), already SETTLED, with no return code.
What the evidence shows. The alert score is 20, band clear, with no hard signal. The only contributing signal is entity.high_risk (+20). The entity record shows verification VERIFIED, pep flag no, no review reasons listed, and last screened 2026-06-26. The transfer itself carries the same score and band (20, clear) with n=82 and confidence 0.525. Program KRIs for Northwind Payroll show frozen_accounts, overdraft_events, stale_screening_share, and verification_denial_rate all in the 'ok' range. pep_flagged_entities and high_risk_entity_share are flagged 'watch' but are drawn from a small sample (n=33) and no prior dispositions exist for this entity to indicate a pattern.
What was checked. Reviewed the alert evidence payload, the transfer record and its own score/band, the entity screening record (verification status, PEP flag, review reasons, last screened date), the program's declared volume and rails, the KRI panel for Northwind Payroll, and prior dispositions history.
What is recommended. Because the transfer has already settled, there is no funds-movement decision to make; a hold or release recommendation would not apply. The score is clear, the sole signal is a high-risk flag on an entity that is otherwise verified with no open review reasons and no stale screening, and no prior dispositions or hard signals raise this above routine. Recommend closing the alert. A person should still note the 'watch' status on pep_flagged_entities and high_risk_entity_share KRIs for the program if these trend upward across more alerts, but that is a program-level observation, not a basis to hold this settled transfer.
- Recommendation
- close
- Confidence
- 0.72
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:30Z
- Rationale
- Score 20 falls in the clear band with hard_signal false.
- Sole contributing signal is entity.high_risk; PEP is no and verification is VERIFIED with no listed review reasons.
- Transfer status is SETTLED with no return code, so no funds are pending movement.
- Entity screening is recent (2026-06-26) and stale_screening_share KRI is in the ok range (0.03).
- No prior dispositions exist on this entity to suggest a recurring or escalating pattern.
- Program KRIs pep_flagged_entities and high_risk_entity_share are marked watch but derive from a small sample (n=33) and do not by themselves indicate a pattern tied to this specific transfer.
Evidence
{
"n": 82,
"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.