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_6iybrai53mo · $1,027.78 · ach outgoing
- Skoor at alert
- 15 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 00be7b06-95fe-4287-8591-b268d601781d fired on entity enti_sim_nort_sr7cv2o3u under the sanctions_or_pep detector after a $1,027.78 outgoing ACH debit (acht_sim_nort_6iybrai53mo) settled on 2026-09-15. The alert was routed to review because the detector always routes to review, not because of a scoring threshold.
What the evidence shows. The transfer-level skoor is 15, band clear, hard_signal false, driven solely by one signal: entity.pep_potential (+15). The entity record shows verification VERIFIED, high_risk false, pep potential noted but review reasons listed as none, and last screened 2026-09-01. The transfer itself settled with no return code, on a program (Northwind Payroll) with declared monthly volume of $2,500,000.00 and US-rail ACH activity. Counterparty country is unknown but the transfer already settled without incident.
What was checked. Reviewed the alert evidence, transfer detail, entity screening record, program KRIs, and prior dispositions. No prior dispositions exist for this alert. Program KRIs are mostly ok or watch (pep_flagged_entities=1 of 33, watch; high_risk_entity_share=0.061, watch); one KRI, manual_review_aging_hours, is in breach at 1,434.7 hours on n=13, but this is a program-wide aging metric, not specific evidence tied to this entity or transfer. No sanctioned-country transfers, no unauthorized returns, and reserve_coverage_ratio is above 1.0.
What is recommended. Close the alert. The score is in the clear band, hard_signal is false, the entity is verified with no open review reasons, and the underlying transfer has already settled with no return. The only elevated program-level signal (manual_review_aging_hours breach) is not specific to this entity or transfer and does not present grounds to hold or escalate this alert on its own. If the manual_review_aging_hours breach is not already being tracked separately, it should be addressed as a program-level item outside this alert.
- Recommendation
- close
- Confidence
- 0.78
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:32Z
- Rationale
- Transfer skoor is 15 in the clear band with hard_signal false, based on a single low-weight PEP-potential signal.
- Entity is VERIFIED, high_risk false, and has no listed review reasons despite the PEP-potential flag.
- The associated ACH transfer settled with no return code; there is no indication funds are at risk or need to be held.
- Program KRIs relevant to this alert type (pep_flagged_entities, high_risk_entity_share) are at watch, not breach, and stale_screening_share is 0, indicating screening currency is not an issue.
- The manual_review_aging_hours breach is a program-wide metric unrelated to this specific entity or transfer and does not itself justify escalation of this alert.
- No prior dispositions exist to indicate a recurring or worsening pattern for this entity.
Evidence
{
"n": 1431,
"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.