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

What happened. Alert fd2e4ed7 fired on entity enti_sim_meri_28dfpclz9pj under the sanctions_or_pep detector due to a potential PEP match. The associated activity is one completed outgoing ACH debit of $348.84 to counterparty cpty_sim_meri_76hym53h9pv, dated 2026-07-12. What the evidence shows. The entity record shows verification status VERIFIED, high_risk flag false, PEP status listed as 'potential' (not confirmed), and review reasons listed as none. Last screening occurred 2026-08-22, after the transfer date, with no stale_screening flag raised. The transfer-level skoor is 25, band 'clear', with hard_signal false. The only contributing signals are entity.pep_potential (+15) and counterparty.first_time (+10), both low-weight. The transfer itself completed normally with no return code. Program-level KRIs show several breaches (reserve_coverage_ratio, ach_unauthorized_return_rate, manual_review_aging_hours, sanctioned_country_transfers) but these are program-wide metrics not tied to this entity or transfer; the counterparty country is unknown, not flagged sanctioned, and this entity's country is US. What was checked. Reviewed the alert evidence block, transfer record, entity screening record, program KRIs, and prior dispositions. Confirmed the route reason is procedural ('detector always reviewed') rather than driven by an elevated score. No prior dispositions exist for this entity or alert. What is recommended. No sanctions or confirmed PEP hit is present; the entity is verified, screened after the transfer date, and carries no open review reasons. The transfer already completed and is not held, so no hold or release action applies. Given the low skoor, clear band, and absence of adverse entity findings, this alert does not require further person-level review. A person should independently confirm the PEP-potential match against the underlying screening vendor result if not already done as part of the 2026-08-22 screening, but the evidence here does not indicate elevated risk requiring escalation.

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