Activity on an entity flagged by screening (PEP status potential).

What happened. Alert e6060667-e27d-4fc9-9e4f-f6a6d1b500a8 was opened on 2026-09-17 by the sanctions_or_pep detector for entity enti_sim_meri_28dfpclz9pj (Meridian Remit program), flagging a potential PEP match. The route reason states this detector is always reviewed. The linked transfer is an outgoing ACH debit of $1,001.24 (acht_sim_meri_ays4c4bgc9a), settled on 2026-09-14, with no return code. What the evidence shows. The transfer skoor is 30, band review, hard_signal false, driven by two 15-point signals: entity.pep_potential and returns.counterparty_prior_any. The entity record shows status VERIFIED, high_risk false, review reasons none, and last screened 2026-08-22, less than a month before this transfer. The counterparty's country is unknown and the prior-return signal indicates a past return history, but this transfer's own return code is none and status is SETTLED. Program KRIs show several breaches (reserve_coverage_ratio, manual_review_aging_hours, ach_unauthorized_return_rate, sanctioned_country_transfers) but none of these fields are tied to this specific entity or transfer in the evidence provided. What was checked. Reviewed the alert evidence, transfer details, entity screening record, program KRIs, and prior dispositions. No prior dispositions exist for this entity or transfer. The entity has no open review reasons and is verified. The transfer has settled with no return. The only elevated signals are the PEP-potential flag (not confirmed) and a counterparty prior-return history unrelated to this specific transaction's outcome. What is recommended. Close the alert. The entity is verified, carries no open review reasons, and was screened recently with no confirmed PEP match. The transfer settled cleanly with no return code. The counterparty prior-return signal and program-level KRI breaches (sanctioned_country_transfers, ach_unauthorized_return_rate) do not trace to this specific transfer or entity in the evidence and should be tracked separately at the program level rather than held against this alert.

{
  "n": 1035,
  "band": "review",
  "skoor": 30,
  "signals": [
    {
      "code": "entity.pep_potential",
      "detail": "potential PEP match",
      "weight": 15
    }
  ],
  "routeReason": "detector always reviewed"
}