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_9f0s1ojqc59 · $1,298.86 · 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. An entity associated with Meridian Remit was flagged by sanctions/PEP screening for a potential PEP match. The alert attached to a single settled outgoing ACH credit of $1298.86 dated 2026-09-10.
What the evidence shows. The entity-level screening produced a potential PEP hit with weight 15, resulting in a transfer skoor of 15, which falls in the 'clear' band (n=960, confidence=1). Hard signal is false. The entity is a verified PERSON, not marked high risk, with no review reasons listed, last screened 2026-08-22. The transfer already settled and carries no return code, so there is no held transfer to act on. Program KRIs show pep_flagged_entities at 1 of 30 (watch, consistent with this single case) and high_risk_entity_share at 3.3% (ok). Other KRI breaches present in the program (reserve_coverage_ratio, manual_review_aging_hours, ach_unauthorized_return_rate, sanctioned_country_transfers) are program-wide metrics not tied to this entity or this transfer by any evidence field.
What was checked. Detector and severity, skoor and band, hard signal flag, entity verification status and risk flags, review reasons, last screening date, transfer status and return code, and program KRI panel for related PEP metrics.
What is recommended. No prior dispositions exist for this entity or alert. The screening hit is a potential match only, the entity is verified with no review reasons, the score bands as clear, and the associated transfer already settled with no return. Nothing in the evidence indicates a need for a person to intervene on this specific alert before closing. The unrelated program KRI breaches (reserve coverage, manual review aging, unauthorized returns, sanctioned country transfers) are not evidenced as connected to this entity and should be tracked separately at the program level, not through this alert.
- Recommendation
- close
- Confidence
- 0.72
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:32Z
- Rationale
- Skoor 15 bands as 'clear' with hard_signal false and high confidence (n=960).
- Entity is VERIFIED, high_risk=false, and review reasons is 'none', indicating screening did not escalate this as a confirmed match.
- The associated transfer is already SETTLED with no return code, so there is no fund movement to hold or release.
- pep_flagged_entities KRI is at 'watch' not 'breach', consistent with a single low-severity potential match rather than a pattern.
- Other program KRI breaches (reserve_coverage_ratio, sanctioned_country_transfers, etc.) are program-wide figures with no field linking them to this entity or transfer, so they do not support escalation on this alert.
- No prior dispositions exist to indicate repeat flagging on this entity.
Evidence
{
"n": 960,
"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.