Financial crime intelligence · built on IONLive demo

ION Financial Crime Suite

One suite for money laundering, trade-based laundering and fraud. Every alert is explained in plain words. People decide.

About ION Financial Crime Suite

The idea

One intelligence suite for anti-money laundering, trade-based money laundering and fraud detection, built on ION. Risk is scored as it happens, explained in plain language, and governed end to end.

Product tour

How ION Financial Crime Suite works

  1. Four modules, one platform

    ION AML, ION TBML, ION Fraud Detection and the Risk Dashboard share one platform, one audit trail and one picture of customers, accounts and devices. The demo runs on synthetic data, clearly labelled.

    Four modules, one platform
  2. Fits beside the systems you have

    Five steps, and none of them changes a system of record: a read-only daily or nightly extract, one linked view of the data, versioned checks, reasons in plain language, and a decision by a named officer.

    Fits beside the systems you have
  3. Work the AML queue, worst first

    Alerts arrive ranked, and each one shows its reasons before the case is opened. Every signed decision is used to measure how precise each pattern is, so noisy patterns are tuned or retired on the record.

  4. Hold the payment, call the customer

    Each payment is scored against the customer's own twelve-month history. A proposed hold goes to the fraud desk with its reason, and the desk calls the customer. The suite never holds a payment on its own.

  5. File on time

    When suspicion is recorded, a clock starts. The case gathers its alerts, its evidence pack and a draft report in the goAML format, and an officer reviews and signs it before anything is filed.

  6. Show the examiner and the board

    The examination pack and the board brief are built from the work as it was done: every alert traced to its source rows, and every decision to a named officer, with a time and a reason.

The film · 0:41

See ION Financial Crime Suite in motion

Sample data · synthetic demo
The problem

What ION Financial Crime Suite catches

Case 01

Structuring

A customer pays cash into several branches over a few days. Each deposit is just under the reporting limit, so no single one looks unusual.

Red flag: Deposits split under the reporting threshold, across branches and days.

Case 02

A mule account

A quiet account suddenly receives money from many unrelated senders. Each payment is small and arrives through an ordinary channel.

Red flag: The money leaves again within hours of arriving.

Case 03

Account takeover

A customer's mobile banking signs in on a new device, adds a new payee and sends a large transfer straight away.

Red flag: Scored against the customer's own twelve-month history, the payment is far out of line.

Case 04

Dormant account raiding

An account has been untouched for over a year. A member of staff looks at it, and soon after it is reactivated.

Red flag: One staff ID viewed the dormant account several times before it woke up.

Stage by stage

How work moves through ION Financial Crime Suite

  1. Extract

    A daily or nightly read-only copy of core banking, the AML and screening systems, the trade platform, the ledger, and access and channel logs. Nothing is written back.

  2. Link

    Rows are tied to customers, accounts, counterparties, staff, branches and devices, each with its own twelve-month history, in one entity graph.

  3. Analyse

    Named, versioned agents run the typologies, screening matches, price bands, document checks and pattern libraries, each under a stated scope and evaluation score.

  4. Explain

    Each finding is written as weighted reasons, with the source rows, the list edition and the model version attached.

  5. Decide

    A named officer clears, holds, escalates, releases or files, with a reason on record. The suite never files and never acts.

Ground rules

Promises it always keeps

  • People decide

    Agents rank, explain and gather evidence. A named officer makes every decision, and nothing is filed automatically.

  • Evidence, not assertion

    Every finding names its reasons and cites the rows, list edition and model version behind it. If it cannot be explained to an examiner, it does not ship.

  • Inside your walls

    It runs on the bank's own infrastructure from read-only extracts. No customer data leaves the bank, and BISTEC keeps none.

  • Nothing cleared by default

    Every sanctions list update rescreens the whole book, and likely matches go to a person. No match is cleared automatically.

  • The machine never promotes its own ideas

    A suggested pattern runs in shadow for four weeks and is measured against the desk's verdicts. Only a named person can add it to the library.

  • Retired, not deleted

    A pattern that keeps raising false alarms is retired on the record. It stays searchable and can be brought back after a back-test.

Under the hood

What's inside ION Financial Crime Suite

ION AML

Transaction monitoring, sanctions and PEP screening, cases and goAML reports: the compliance officer's workbench.

ION TBML

Reads the trade documents behind letters of credit and flags mispriced goods, phantom shipments and mismatched goods descriptions.

ION Fraud Detection

Screens payments as they pass the switch and reads the book overnight for mules, scams, account takeover, suspense misuse and overrides.

Risk Dashboard and Governance

Programme health, examiner readiness and board reporting, with the agent roster, run ledger and audit log that every module shares.

Entity graph

One linked view of customers, accounts, counterparties, devices, staff and branches, shared by all four modules.

Sector view

Gives each member institution its own workspace. An association sees only an anonymised read-out across its members.

By design

What it deliberately won't do

  • It won't: File reports by itself

    It drafts the report in the goAML format; an officer reviews, signs and files it.

  • It won't: Hold a payment on its own

    It proposes a hold with a reason. The fraud desk calls the customer and decides.

  • It won't: Replace your systems

    Core banking, the existing AML system and the trade platform keep running. It reads their data and alerts, and changes none of their rules.

  • It won't: Send customer data out of the bank

    It runs inside the bank. Data is never pooled, and BISTEC keeps none of it.

  • It won't: Promote its own patterns

    New patterns are suggestions until a named person approves them after a shadow run.

Technical details

The suite is an intelligence layer beside the bank's existing systems. It is deployed on the bank's own infrastructure and works from read-only extracts: core banking, the existing AML and screening systems, the trade platform, the general ledger, and access and channel logs. Data arrives first through a watched folder or SFTP drop; APIs follow only once the value is proven. Nothing is written back to core banking, no customer data leaves the bank, and BISTEC keeps none. Payments and card authorisations are read from copies of the payment switch feed, never the live payment rail. The book and staff activity are read overnight, with row counts and control totals checked against the source. Every row is linked into one entity graph of customers, accounts, counterparties, devices, staff and branches, with twelve months of history. Checks run as named, versioned agents, each with a stated scope and an evaluation score. Each has a human gate, and an autonomy switch (off, suggest, or act with approval) sets how far they go; with it off, the product still works on rules and people. Every run is logged in a ledger that can be replayed, and every human and agent action goes into one audit log. A VAPT (security test) certificate is available on request.

Target audience

Heads of compliance, money laundering reporting officers (MLROs) and fraud teams at banks. Trade services teams use the TBML module, and internal audit uses the overnight findings on suspense accounts, overrides and staff access. Risk officers, boards and examiners get the dashboard, the board brief and the examination pack. Banking associations can get an anonymised read-out across their members.

Questions

Does it file reports or block payments by itself?

No. It drafts suspicious transaction reports and proposes holds, but a named officer makes every decision. Nothing is filed automatically, and the suite never holds a payment on its own.

Does our data leave the bank?

No. It is deployed on the bank's own infrastructure and works from read-only extracts. Nothing is written back to core banking, no customer data crosses the bank's boundary, and BISTEC keeps none.

Do we have to replace our current AML system?

No. It works beside the systems you already have. The existing AML system keeps running; the suite reads its alerts and does not edit its rules.

Can I see why something was flagged?

Yes. Every alert lists its reasons in plain language and cites the source rows, the sanctions list edition and the model version behind it.

What does it cover?

Anti-money laundering (structuring, rapid in-and-out movement, mule patterns and screening), trade-based money laundering (mispricing, phantom shipments and mismatched goods) and fraud (account takeover, scams and unusual behaviour), plus a risk dashboard over all three.

How does it connect to our systems?

Through a daily or nightly read-only extract, first by a watched folder or SFTP drop. APIs come later, once the value is proven.

How would we start?

With a two-week discovery on your own book: week one connects a single read-only extract and replays twelve months of history, and week two puts the results beside your current practice. You set the success criteria on day one.

Is there a security test report?

Yes. A VAPT (vulnerability assessment and penetration test) certificate is available on request.

Book a demo

See any of the nine running on your own use case.

A 30-minute walkthrough with the team that built it.

Email us
hello@bistecglobal.com

Offices in Sydney and Colombo.

bistecglobal.com
© 2026 BISTEC Global · Intelligent design. Engineered for adaptability.Demos on this page use sample data.