Skip to content
Book a demo
Use cases · Transaction monitoring & AML

Monitoring an examiner can follow.

Sieve explains every alert in plain English. Your FRC or NFIU reporting deadline stays in view.

Book a demoSanctions & PEP screening

For commercial and microfinance banks, deposit-taking SACCOs and MFIs.

How it hits

Four ways the money goes missing.

Each looks like ordinary activity. Sieve scores every event in context, before the money moves.

  1. 01

    Structuring

    Cash deposits kept just under the reporting line (KES 1M in Kenya, NGN 5M in Nigeria), day after day.

    Caught by Structuring rule and pattern, cash transaction

  2. 02

    Mule accounts

    Money from dozens of senders, passed straight through to one account.

    Caught by Pass-through, fan-in, payout account shared by several customers

  3. 03

    Dormant-account abuse

    An account silent for most of a year receives KES 2.4M and wires it abroad that afternoon.

    Caught by Dormant account wakes up, dormant takeover pattern

  4. 04

    Sanctions & PEPs

    A customer on the UN, OFAC or Nigeria Sanctions List, or a politically exposed person.

    Caught by Continuous screening against UN, OFAC, EU, Kenya FRC, Nigeria Sanctions List and PEP lists

A catch, step by step

Minutes of activity. One decision.

A story from the Banks, SACCOs & MFIs demo, run through the same engine as your events. Each reason is written for the analyst who acts on it.

A dormant account wakes upreplayed through the engine
  1. Last activityKES 4,000 salary credit, ten months ago
  2. Day 0, 09:10KES 2,400,000 from a company never seen beforeDormant account wakes up
  3. Day 0, 14:05KES 2,350,000 wired to the UAEMoney in, straight back out
  4. DecisionReview
    • Dormant for 317 days, now moving KES 2.35M
    • 98% of what came in today is leaving again
    • Above the KES 1M monitoring line

Opened as a case for a human, not blocked. If your analyst marks it suspicious, the STR clock starts and the goAML narrative is drafted.

What Sieve does

Choose “Banks, SACCOs & MFIs” and these start enforcing.

Plain-English rules you can adjust, joined into fraud patterns. Everything else runs in Watch, scoring without acting, until you trust it.

Rules
  • Structuring
  • Regulatory threshold
  • Dormant account wakes up
  • Money in, straight back out
  • Payout account shared by several customers
  • Cash transaction
Patterns
  • Structuring
  • Money mule
  • Dormant-account abuse
Integrate

Send these events. One endpoint.

  • customer.createdName, date of birth and nationality, for screening from day one.
  • transactionEvery credit and debit, with method (cash, bank, agency) and counterparty.
  • customer.updatedIdentity changes trigger a rescreen.
POST /v1/events
await sieve.events.create({
  type: 'transaction',
  customer_id: '1002017',
  direction: 'in',
  amount: 985000,
  method: 'cash',
  status: 'success',
  counterparty: { id: 'branch_westlands' },
})
Compliance

What your regulator will ask, answered.

Sieve supports your obligations. It doesn’t replace your compliance team.

goAML reporting to the FRC (Kenya) and NFIU (Nigeria)
STR deadlines tracked per country: two days to the FRC (POCAMLA), 24 hours to the NFIU (MLPPA 2022). Sieve drafts the goAML narrative from the evidence.
CBK and SASRA (Kenya), CBN (Nigeria) supervision
Every rule is versioned and backtested. Show its precision, recall and change history.
Sanctions screening
When a list changes, customers are rescreened within the hour. Scheduled rescreens follow each customer’s risk tier.

Deploying in a bank? See Sieve for banks: on-premise deployment, model risk management and procurement.

Other use cases
Book a demo

See it on a workspace built for you.

A private Banks, SACCOs & MFIs workspace for Kenya or Nigeria, with a month of traffic and the fraud above. We walk your team through a live catch.

Book a demoTalk to our team