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

What happened. An alert fired because entity enti_sim_meri_5if3mzfr9pn, a US-based business named "High Risk Trading 2," was flagged by screening as high risk. The alert is tied to one ACH outgoing credit transfer of $534.26 (acht_sim_meri_75gruliga5p), settled, to a first-time counterparty whose country is unknown. What the evidence shows. The entity is VERIFIED, marked pep: no, and lists no specific review reasons. Last screened 2026-06-26, which is within the program's normal cadence (stale_screening_share is 0.033, flagged 'ok'). The alert score is 30, banded 'review,' with hard_signal false, driven only by the generic entity.high_risk signal (+20) plus a transfer-level counterparty.first_time signal (+10). There is no sanctions list match detail, no adverse-media or PEP finding, and no return code or dispute on the transfer, which is already SETTLED. Program KRIs show high_risk_entity_share at 3.3% (ok) and pep_flagged_entities at watch (1 of 30, small sample). No prior dispositions exist for this entity or alert. What was checked. Reviewed the alert evidence payload, the entity's screening fields (verification, pep, high_risk, review reasons, last screened date), the transfer's status and counterparty details, the program's declared volume and rails, and the program KRI panel for corroborating patterns (frozen accounts, verification denial rate, stale screening share, sanctioned country transfers). What is recommended. Close the alert. The entity carries a high-risk category label from screening but has no specific sanctions or PEP match, is verified, has no open review reasons, and was screened within a normal window. The associated transfer has already settled with no return or dispute. Nothing in the evidence requires further transaction hold or escalation. If the counterparty's unknown country or the first-time relationship becomes a repeated pattern, a person should revisit at that time.

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