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

What happened. The alert fired on entity enti_sim_meri_28dfpclz9pj because screening returned a potential PEP match. The detector routes all such matches to review regardless of score. The linked transfer is a single settled ACH debit of $366.69 with no return code. What the evidence shows. The alert's own score is 15, banded clear, with hard_signal false. The only contributing signal is entity.pep_potential (+15). The entity record shows verification status VERIFIED, high_risk false, review reasons none, and a screening date of 2026-06-25, which is recent relative to the alert open date of 2026-09-17. The transfer skoor is also 15, band clear, confidence 0.6375 on n=151. The transfer is already SETTLED with no return code, so there is no pending movement to hold. Program-level KRIs show pep_flagged_entities at 1 of 30 entities (watch status) but all other KRIs tied to this entity or transfer type (verification_denial_rate, sanctioned_country_transfers, ach return rates, high_risk_entity_share) are within ok range at low percentages. What was checked. Reviewed the alert score and signal composition, the entity's verification and screening status, the transfer's settlement status and return code, and the program KRI panel for corroborating patterns. No prior dispositions exist for this alert. What is recommended. No evidence in this alert indicates unresolved risk requiring a person to act before funds move, since the transfer already settled. The entity has been screened recently, is verified, and carries no open review reasons. The single watch-level KRI (pep_flagged_entities) reflects one entity out of thirty and does not on its own indicate a broader pattern. Recommend closing this alert.

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