Alert · reviewed · open
Activity on an entity flagged by screening (PEP status potential).
- Detector
- sanctions_or_pep
- Severity
- high
- Program
- Northwind Payroll (simulated)
- Subject
- entity enti_sim_nort_sr7cv2o3u
- Transfer
- acht_sim_nort_mwuum2g358 · $2,088.43 · 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. Alert 047de7c9-9d37-48c9-99be-261c6c762845 fired on entity enti_sim_nort_sr7cv2o3u under the sanctions_or_pep detector after screening flagged a potential PEP match. The alert is tied to one settled ACH outgoing debit of $2,088.43 (acht_sim_nort_mwuum2g358) dated 2026-09-05, under the Northwind Payroll program.
What the evidence shows. The composite score at both alert and transfer level is 15, which falls in the 'clear' band, and hard_signal is false. The only contributing signal is entity.pep_potential (+15). The entity record shows verification status VERIFIED, high_risk false, pep potential noted, and review reasons listed as none, with a last screening date of 2026-09-01, sixteen days before the alert opened. The transfer settled normally with no return code. Counterparty country is unknown, but there is no sanctioned-country or return-code signal attached to this transfer.
What was checked. I reviewed the alert evidence block, the linked transfer's own score and signal list, the entity's verification and risk fields, the program's declared volume and rails, and the program KRI panel. Program KRIs show pep_flagged_entities at 1 of 33 entities (watch band, not breach), stale_screening_share at 0 (ok), verification_denial_rate at 3.0% (ok), and sanctioned_country_transfers at 0 (ok). manual_review_aging_hours shows a breach (1434.7 hours, n=10), but this is a program-wide backlog metric unrelated to this specific entity's screening or transfer, and no prior dispositions exist for this alert.
What is recommended. Close this alert. The evidence is limited to a single low-weight potential PEP flag on a verified, non-high-risk entity, the composite score sits in the clear band, the transfer has already settled with no return, and no review reasons or additional signals are present. The transfer is not on hold, so no release action applies. The program-level manual_review_aging_hours breach is noted for separate operational follow-up but does not by itself indicate a pattern tied to this entity or alert.
- Recommendation
- close
- Confidence
- 0.78
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:32Z
- Rationale
- skoor 15 falls in the 'clear' band with hard_signal false
- only one contributing signal, entity.pep_potential, weight 15
- entity is VERIFIED, high_risk false, and review reasons are none
- transfer already SETTLED with no return code, so hold/release is not applicable
- program KRIs relevant to PEP/sanctions (pep_flagged_entities, stale_screening_share, sanctioned_country_transfers) are at ok/watch, not breach
- manual_review_aging_hours breach is a separate program-wide metric, not specific evidence against this entity or transfer
Evidence
{
"n": 1188,
"band": "clear",
"skoor": 15,
"signals": [
{
"code": "entity.pep_potential",
"detail": "potential PEP match",
"weight": 15
}
],
"routeReason": "detector always reviewed"
}
Skoor signals
| Signal | Weight | Hard | Detail |
|---|---|---|---|
| entity.pep_potential | +15 | potential 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.