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

What happened. Alert f37eed74-abcf-49c6-9e95-496686c04718 fired on entity enti_sim_meri_28dfpclz9pj under the sanctions_or_pep detector because screening flagged a potential PEP match. The alert is routed to review by policy (routeReason: 'detector always reviewed'), not because of an elevated score. The linked activity is a single outgoing ACH credit of $301.13 USD (acht_sim_meri_cozesqcj9z3), already SETTLED, with no return code. What the evidence shows. Transfer-level skoor is 15, band clear, with hard_signal false; the only contributing signal is entity.pep_potential at weight 15 (n=72, confidence 0.395). The entity record shows PERSON 'Potential Pep 2', verification VERIFIED, high_risk false, review reasons none, country US, last screened 2026-06-25T12:01:30.000Z (about seven weeks before the transfer). No sanctioned-country nexus is indicated; counterparty country is listed unknown but the transfer settled without a return. Program-level KRIs show pep_flagged_entities at a 'watch' level (1 of 30 entities, 3.3%), but most other KRIs are unmeasured (n=0) and the two that are measured (stale_screening_share, verification_denial_rate) sit at ok levels (3.3%). There are no prior dispositions on this entity or alert. What was checked. Detector and score fields, hard_signal flag, route reason, transfer status and return code, entity verification and risk flags, entity screening recency, program KRI panel, and prior disposition history. No sanctions hit, adverse media, or high-risk flag is present in the evidence provided. What is recommended. The entity is verified, not flagged high risk, has no open review reasons, and was screened within the last two months. The associated transfer already settled with no return code, so there is no pending movement to hold. The single supporting signal (potential PEP match) is the reason the detector always routes to review, not an indication of elevated risk on its own. Nothing in the evidence points to a need for further action by a person at this time; the program-level PEP watch metric is based on a small population (n=30) and does not itself implicate this entity beyond what is already reflected. Recommend closing the alert. If screening cadence or entity risk classification changes, or if a review reason is later populated, the alert should be reopened.

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