Alert · reviewed · open
Activity on an entity flagged by screening (PEP status no, high risk).
- Detector
- sanctions_or_pep
- Severity
- high
- Program
- Meridian Remit (simulated)
- Subject
- entity enti_sim_meri_5if3mzfr9pn
- Transfer
- acht_sim_meri_aiqkia8j9q7 · $1,104.13 · ach outgoing
- Skoor at alert
- null unscored
- Hard signal
- no
- Policy
- policy-v1
- Opened
- 2026-09-17 19:30Z
- Closed
- —
- Decision clock
- none · due — no clock
- Escalated
- —
Draft narrative
What happened. Alert d9176923-0b18-4049-914b-7f71e91a80eb fired on entity enti_sim_meri_5if3mzfr9pn under the sanctions_or_pep detector, routed for review because that detector is always reviewed. The entity is flagged high risk by screening; PEP status is no. The associated transfer is an outgoing ACH credit of $1,104.13 USD (acht_sim_meri_aiqkia8j9q7), status SETTLED, to a first-time counterparty with unknown country.
What the evidence shows. The entity record shows verification VERIFIED, pep no, high risk true, and review reasons none, last screened 2026-06-26. The alert carries no hard signal and is unscored (band unscored, n=0, skoor null). The two contributing signals are entity.high_risk (+20) and counterparty.first_time (+10), with no sanctions list hit, no adverse media reason, and no PEP match documented anywhere in the evidence. The transfer has already settled and carries no return code. There are no prior dispositions on this entity.
What was checked. Reviewed the alert evidence block, the program declaration (Meridian Remit, $1,200,000.00 monthly, rails ACH/wire/SWIFT, countries US/MX/PH), the transfer record, the entity screening record, and prior disposition history. No sanctions list match, no PEP match, and no specific review reason are present in the entity record beyond the generic high-risk marker. The transfer is settled, not held, so no funds are in a position to be released or blocked.
What is recommended. Close the alert. The entity is verified, not PEP, and carries no documented review reason beyond a generic high-risk flag; the transfer has already settled with no return. Nothing in the evidence indicates a sanctions or PEP match requiring further action, and there is no pattern across dispositions to warrant escalation. A person should confirm the underlying reason for the entity's high-risk marking is on file with screening, since that detail is not present in this evidence.
- Recommendation
- close
- Confidence
- 0.62
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:30Z
- Rationale
- Entity verification status is VERIFIED and pep is no; review reasons field is none.
- Alert is unscored (skoor null, band unscored, n=0) and hard_signal is false.
- Only contributing signals are entity.high_risk (+20) and counterparty.first_time (+10); no sanctions or PEP match signal is present.
- Transfer acht_sim_meri_aiqkia8j9q7 is already SETTLED with no return code, so hold/release actions do not apply.
- No prior dispositions exist for this entity, so no pattern across alerts supports escalation.
- Evidence does not state the specific basis for the entity's high-risk classification, which limits confidence and should be confirmed by a reviewer.
Evidence
{
"n": 0,
"band": "unscored",
"skoor": null,
"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 | |
| counterparty.first_time | +10 | first transfer with this counterparty | |
| counterparty.first_time_and_large | +15 | amount above the program p95 (109935) |
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.