Activity on an entity flagged by screening (PEP status no, high risk).

What happened. An alert fired on entity enti_sim_harb_skonrvy3x6 under the sanctions_or_pep detector because the entity is flagged high risk by screening. The alert reviews a single settled ACH outgoing credit of $240.07 (transfer acht_sim_harb_9kxiel4z4gk) dated 2026-07-15. What the evidence shows. The alert score is 20, band clear, with hard_signal false. The only contributing signal is entity.high_risk (+20); there is no PEP flag (pep no) and no listed review reasons. The entity is BUSINESS type, VERIFIED, US-domiciled, last screened 2026-06-26. The transfer itself is SETTLED with no return code and the counterparty country is unknown but no other flags attach to it. Transfer-level scoring matches the alert: skoor 20, band clear, confidence 0.625 on n=152. Program KRIs show pep_flagged_entities and high_risk_entity_share at 'watch' (1/30 and 6.7%), but these are population-level counts, not specific to this entity's activity, and several related KRIs (sanctioned_country_transfers, ach return rates, reserve coverage) are unmeasured (n=0). No prior dispositions exist for this alert or entity. What was checked. Reviewed the alert signal set, the entity's screening status and verification, the single transfer's settlement and return status, the program's declared volume and KRI panel, and prior disposition history. No additional evidence (e.g., sanctions list match detail, transaction pattern history) is present in the record beyond what is summarized here. What is recommended. Close the alert. The score sits in the clear band, there is no hard signal, the entity is verified with no PEP status and no stated review reasons, and the referenced transfer is already settled with no return code issue. Program-level KRIs are at watch but reflect population counts, not this entity's specific activity, and do not on their own indicate a pattern tied to this alert. Since the transfer has already settled, there are no funds to hold, and no basis is shown here to escalate to a broader pattern.

{
  "n": 152,
  "band": "clear",
  "skoor": 20,
  "signals": [
    {
      "code": "entity.high_risk",
      "detail": "entity marked high risk by screening",
      "weight": 20
    }
  ],
  "routeReason": "detector always reviewed"
}