Evally
Finance & compliance

Transaction risk screen

Prioritize AML alerts: unusual for the customer, structuring, high-risk places, vague purpose.

Turns a transaction narrative and a customer profile into risk indicators investigators can sort by. It doesn't file anything; it decides which alerts a person looks at first and which can wait.

Decision support for trained investigators. It doesn't determine whether activity is suspicious or replace your filing obligations.

Try it live

Real calls to Jev. Pick an example or paste your own.

Examples
173
63
No verdict yet

Pick an example or paste your own input, then run it.

Under the hood

Every question and rule, in the open. Fork it to change any of them.

What it asks

Reads transaction and profile, then asks 6 questions in one call.

  1. Q1Unusual for the customerYes / no

    Is the transaction unusual for the profile (in amount, frequency, geography or counterparty)?

  2. Q2StructuringYes / no

    Does the transaction look split up to stay under reporting thresholds?

  3. Q3High-risk jurisdictionYes / no

    Does the transaction involve a high-risk or sanctioned jurisdiction?

  4. Q4Vague purposeYes / no

    Is the stated purpose of the transaction vague, inconsistent or missing?

  5. Q5Pass-throughYes / no

    Does money move through third parties with no clear business reason (shell companies, or funds passed straight through)?

  6. Q6Overall riskScore

    How risky is the transaction overall?

    1. 0Low
    2. 1Medium
    3. 2High
    4. 3Critical

How it decides

Rules run in code, top to bottom. The first one that matches gives the verdict.

  1. 1
    If Overall risk ≥ 2.5 of 3Escalatereview
  2. 2
    If High-risk jurisdiction ≥ 0.8Escalatereview
  3. 3
    If Unusual for the customer ≥ 0.6Investigatereview
  4. 4
    If Structuring ≥ 0.6Investigatereview
  5. 5
    If Vague purpose ≥ 0.6Investigatereview
  6. 6
    If Pass-through ≥ 0.6Investigatereview
  7. 7
    If Overall risk ≥ 1.5 of 3Investigatereview
  8. ·
    DefaultClear

Call it from your code

Every template runs as-is with an API key, no setup: POST /api/v1/judges/transaction-risk-screen/run.

curl -X POST https://tryevally.com/api/v1/judges/transaction-risk-screen/run \  -H "Authorization: Bearer $EVALLY_API_KEY" \  -H "Content-Type: application/json" \  -d '{  "input": {    "transaction": "Four cash deposits of $9,500, $9,800, $9,700 and $9,900 on consecutive days, followed by a wire of $38,000 to a newly opened account at an offshore bank. Memo: '\''consulting'\''.",    "profile": "Retail customer, schoolteacher, average monthly balance $3,200."  }}'

More in Finance & compliance