Alert · reviewed · open
Activity on an entity flagged by screening (PEP status potential).
- Detector
- sanctions_or_pep
- Severity
- high
- Program
- Harbor Marketplace Payouts (simulated)
- Subject
- entity enti_sim_harb_azbiyidj3x2
- Transfer
- acht_sim_harb_7ijhdzz56nz · $624.18 · 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 3f62c4d2-efd5-47ff-9a0c-e945f6088021 was opened on 2026-09-17 by the sanctions_or_pep detector on entity enti_sim_harb_azbiyidj3x2, a person flagged with potential PEP status. The route reason states this detector is always reviewed regardless of score. The linked transfer is an outgoing ACH credit of $624.18 (acht_sim_harb_7ijhdzz56nz), settled on 2026-08-12, with no return code.
What the evidence shows. The alert score is 15, placing it in the 'clear' band, with hard_signal false. The only contributing signal is entity.pep_potential (weight 15). The entity record shows verification status VERIFIED, high_risk false, review reasons none, and a last screening date of 2026-06-25, prior to the transfer date. The transfer itself settled normally with no return code, indicating no rail-level failure or reversal. Program-level KRIs show pep_flagged_entities at 1 of 30 (watch) and high_risk_entity_share at 6.7% (watch), but these are aggregate program metrics not specific to this entity's conduct. Two KRIs show breach status (manual_review_aging_hours, ach_unauthorized_return_rate), but neither is tied in the evidence to this entity or this transfer.
What was checked. Reviewed the alert score and band, the hard_signal flag, the entity's verification and review-reason fields, the transfer's settlement status and return code, and the program KRI panel for any entity- or transfer-specific breach. No prior dispositions exist for this alert.
What is recommended. Close the alert. The score is clear, hard_signal is false, the entity is verified with no open review reasons, and the transfer settled without incident. The PEP potential flag triggered a mandatory review per the detector's always-review routing, but nothing in the evidence indicates unresolved risk requiring a person to intervene before further action. The program-level KRI watch/breach items are not linked to this specific entity or transfer and should be tracked separately at the program level, not through this alert.
- Recommendation
- close
- Confidence
- 0.74
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:31Z
- Rationale
- Alert score 15 falls in the 'clear' band with hard_signal false.
- Entity is VERIFIED, high_risk false, and has no open review reasons.
- Transfer settled with no return code, indicating no failed or reversed payment.
- Route reason indicates this alert type is always reviewed regardless of risk level, consistent with a routine low-risk review rather than a specific finding.
- Program KRI breaches (manual_review_aging_hours, ach_unauthorized_return_rate) are not evidenced as connected to this entity or transfer.
- No prior dispositions exist to suggest a repeat pattern for this entity.
Evidence
{
"n": 1056,
"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 | |
| returns.entity_rate_gt_threshold | +15 | entity unauthorized return rate 1/25 originated ACH debits in 60d |
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.