Alert · reviewed · open
Activity on an entity flagged by screening (PEP status no, high risk).
- Detector
- sanctions_or_pep
- Severity
- high
- Program
- Lantern Lending (simulated)
- Subject
- entity enti_sim_lant_6uvwvng8cjh
- Transfer
- acht_sim_lant_194f5clvegz · $1,160.60 · ach outgoing
- Skoor at alert
- 20 clear
- Hard signal
- no
- Policy
- policy-v1
- Opened
- 2026-09-17 19:32Z
- Closed
- —
- Decision clock
- none · due — no clock
- Escalated
- —
Draft narrative
What happened. Alert 78653e49-9d9c-4b83-b77a-b1271689ad62 was generated by the sanctions_or_pep detector on entity enti_sim_lant_6uvwvng8cjh, a US-based business named 'High Risk Trading 3' under the Lantern Lending program. The detector always routes to review by rule, and the trigger was a single screening signal: the entity is marked high risk.
What the evidence shows. The alert score is 20, band clear, with hard_signal false. The only contributing signal is entity.high_risk (weight 20). The entity record shows PEP status no, verification VERIFIED, no review reasons listed, and last screened 2026-08-29. The associated transfer (acht_sim_lant_194f5clvegz) is a $1,160.60 ACH outgoing credit, status SETTLED, with return code none, and its own transfer-level skoor is 20/clear. No prior dispositions exist for this alert.
What was checked. Reviewed the alert evidence payload, the entity screening record, the transfer detail and its independent skoor, and program-level KRIs. Program KRIs show manual_review_aging_hours in breach (1433.57 hrs, n=8) and hold_aging_hours and pep_flagged_entities in watch status, but these are program-wide metrics not specific to this entity or transfer, and no signal in this alert ties them to this subject.
What is recommended. No single-entity evidence here indicates activity beyond the standard high-risk screening flag: the entity is verified, not PEP, has no review reasons, and the linked transfer settled cleanly with no return. This does not require a person to intervene on funds movement, but the program-level breach in manual_review_aging_hours is worth separate tracking outside this alert. Recommend closing this alert.
- Recommendation
- close
- Confidence
- 0.78
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:32Z
- Rationale
- Score 20 falls in the clear band and hard_signal is false.
- Single signal is entity.high_risk; no sanctions match, no PEP flag, no adverse review reasons.
- Entity is VERIFIED and screened within the last three weeks (2026-08-29).
- Transfer is SETTLED with return code none; transfer-level skoor is also clear (20).
- Program KRI breaches (manual_review_aging_hours, hold_aging_hours) are portfolio-level and not linked to this entity or transfer by any signal in the evidence.
- No prior dispositions exist to suggest a repeat pattern for this subject.
Evidence
{
"n": 794,
"band": "clear",
"skoor": 20,
"signals": [
{
"code": "entity.high_risk",
"detail": "entity marked high risk by screening",
"weight": 20
}
],
"routeReason": "detector always reviewed"
}
Skoor signals
| Signal | Weight | Hard | Detail |
|---|---|---|---|
| entity.high_risk | +20 | entity marked high risk by screening |
Decision
Sign in as an operator to decide. Operator sign-in →
Dispositions
No disposition yet.
Actions
Freeze, request to program, and suspend need a second, distinct approver. Clear hold, cancel, and pause execute on the requester's approval. Executed through the bank's own API with the tenant's sandbox key; a dry run when there is none.
No actions requested.