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_48ka0x66btc · $456.50 · 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 084c347e-3483-46b8-adb2-7a24ba2874b1 was generated by the sanctions_or_pep detector on entity enti_sim_meri_28dfpclz9pj ("Potential Pep 2") after a single ACH outgoing credit transfer (acht_sim_meri_48ka0x66btc) of $456.50 USD settled on 2026-09-02. The detector fired on a potential PEP match; severity is marked high but the alert route is 'reviewed' because this detector is always reviewed regardless of score.
What the evidence shows. The transfer-level skoor is 15, band clear, hard_signal false, driven solely by the entity.pep_potential signal (weight 15). The transfer settled with no return code. The entity record shows verification status VERIFIED, high_risk false, review reasons none, and a screening date of 2026-08-22, less than a month before the transfer. Counterparty country is unknown but there is no sanctioned-country or high-risk-country signal attached. Program-level KRIs show pep_flagged_entities at 1 of 30 (watch) and stale_screening_share at 0 (ok), consistent with this being an isolated, already-screened PEP-potential match rather than a new or unresolved hit.
What was checked. Reviewed the alert signal composition, transfer status and return code, entity verification and screening history, and program KRI panel for related patterns (pep_flagged_entities, stale_screening_share, high_risk_entity_share, verification_denial_rate). No prior dispositions exist for this alert. Other KRI breaches in the panel (reserve_coverage_ratio, manual_review_aging_hours, ach_unauthorized_return_rate) are program-wide metrics not tied to this entity or transfer and show no direct linkage in the evidence provided.
What is recommended. Close this alert. The transfer has already settled, the entity is verified with no open review reasons, the screening is current, and the score sits in the clear band with no hard signal. No fund movement is pending, so no hold is applicable. A person should independently confirm the entity's PEP determination outside this alert, but nothing in this record requires stopping funds or escalating beyond the single alert.
- Recommendation
- close
- Confidence
- 0.72
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:31Z
- Rationale
- skoor 15 in clear band with hard_signal false
- entity verification VERIFIED, high_risk false, review reasons none
- screening dated 2026-08-22, recent relative to the 2026-09-02 transfer, and stale_screening_share is 0 across the program
- transfer already SETTLED with no return code; nothing pending to hold or release
- pep_flagged_entities KRI shows 1 of 30 (watch), not indicative of a broader pattern tied to this alert
- other program KRI breaches (reserve_coverage_ratio, manual_review_aging_hours, ach_unauthorized_return_rate) are not linked to this entity or transfer in the evidence given
Evidence
{
"n": 832,
"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.