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

What happened. Alert 67b80529-4132-4960-b0e5-bd14a8926af1 was generated by the sanctions_or_pep detector on entity enti_sim_meri_28dfpclz9pj, flagged for potential PEP status. The alert is tied to a single outgoing ACH credit transfer (acht_sim_meri_hkyifdiboe) of $1,069.68 USD, which settled on 2026-08-29 with no return code. What the evidence shows. The alert-level skoor is 15, banded 'clear,' with hard_signal false. The only contributing signal is entity.pep_potential (+15), the same signal driving the transfer-level skoor, which is also 15/clear (n=772, confidence 1). The entity record shows verification status VERIFIED, high_risk false, review reasons none, and a screening date of 2026-08-22, roughly three weeks before the alert opened. The transfer itself settled normally with no return code and no counterparty country recorded. Program-level KRIs show three breaches (reserve_coverage_ratio, manual_review_aging_hours, ach_unauthorized_return_rate) and two watch-level metrics (hold_aging_hours, pep_flagged_entities=1 of 30 entities), but none of these are linked in the evidence to this specific entity or transfer. What was checked. Reviewed the alert signal composition, transfer status and return code, entity verification and screening recency, and program KRI panel for any entity- or transfer-specific linkage. No prior dispositions exist for this alert. No sanctioned-country or high-risk flags are present on the entity or transfer. What is recommended. Close the alert. The PEP-potential signal is the sole driver of a clear-banded score, the entity is verified with no open review reasons, screening is recent, and the associated transfer settled without incident. The program-level KRI breaches (reserve coverage, manual review aging, ACH unauthorized returns) are not shown in the evidence to relate to this entity or transfer and should be tracked separately rather than used to hold this alert.

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