Alert · reviewed · open
Activity on an entity flagged by screening (PEP status potential).
- Detector
- sanctions_or_pep
- Severity
- high
- Program
- Meridian Remit (simulated)
- Subject
- entity enti_sim_meri_28dfpclz9pj
- Transfer
- acht_sim_meri_4y1ht4k1a92 · $1,359.56 · ach outgoing
- Skoor at alert
- 15 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. Alert b84a59f0-da7a-492f-8bb3-a8f6575a5caa fired on entity enti_sim_meri_28dfpclz9pj under the sanctions_or_pep detector due to a potential PEP match. The entity is linked to one settled ACH outgoing debit transfer of $1,359.56 dated 2026-07-20, which has already settled.
What the evidence shows. The alert score is 15, banded clear, with hard_signal false, driven by a single signal: entity.pep_potential (weight 15). The entity record shows verification VERIFIED, high_risk false, review reasons none, and last screened 2026-06-25. The transfer itself carries the same clear-band score (15, n=163, confidence 0.6825) with no additional adverse signals, and its return code is none, indicating no ACH failure. The associated transfer already settled, so there is no held transfer to release. Program-level KRIs show pep_flagged_entities at watch status (1 of 30, n=30) but all other KRIs are ok or unmeasured, and no sanctioned_country_transfers or elevated return rates are present. Counterparty country is unknown, but no other signal ties this counterparty to elevated risk.
What was checked. Reviewed alert signal detail, transfer-level skoor and band, entity screening status and review reasons, program KRI snapshot, and prior dispositions (none on file). No evidence of hard signal, high-risk flag, or open review reason on the entity.
What is recommended. Given clear band scoring, verified entity status, no review reasons, and a settled transfer with no adverse signals, no manual hold or fund action is warranted. Close the alert. The program-level pep_flagged_entities watch metric (1/30) is noted but does not on its own indicate a pattern requiring escalation; it should be monitored at the program level rather than acted on via this single alert.
- Recommendation
- close
- Confidence
- 0.70
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:30Z
- Rationale
- Skoor 15, band clear, hard_signal false at both alert and transfer level.
- Entity verification is VERIFIED with high_risk false and review reasons none.
- Transfer already SETTLED with return code none; nothing to hold or release.
- Only one signal present (entity.pep_potential, weight 15); no corroborating adverse signals.
- Program KRIs mostly ok; pep_flagged_entities is at watch (1/30) but this is a program-level metric, not alert-specific evidence of a broader pattern.
- No prior dispositions exist for this entity or alert to suggest recurring concern.
Evidence
{
"n": 163,
"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.