- contact@insightaml.com
InsightAML reads the bank’s transactions with ten monitoring rules that show their evidence, and puts each customer’s alerts in one case. It maps who the money came from and went to, compares what the customer declared with what the account actually did, and drafts the suspicious activity report narrative from the facts, every figure traceable. Then it stops. An investigator closes or escalates, and a lead who didn’t prepare the report files it.
Most of an investigation is preparation: pulling the transactions behind an alert, finding the customer’s declared profile, tracing where the money went, checking whether the same pattern was explained last year, and then retyping all of it into a narrative. The judgement, which only a person can make, gets whatever time is left, and the filing deadline keeps running.
A rule name and a score tell an investigator where to start, not what happened. Every alert sends them into three other systems before they can decide anything.
Structuring, a high-risk wire, credits ten times the profile and an unusual cash share are one story about one customer. Worked as four alerts, they are four half-investigations.
The suspicious activity report is what law enforcement reads. A figure copied wrong, a missing “where”, or a conclusion instead of a fact weakens it, and nobody checks until a lead reads it, close to the deadline.
One case per customer, from the first alert to a filed report or a closure with a reason. Seven agents prepare each step. A person accepts, rejects or asks about what they prepared, and makes every decision that matters.
Ten rules read the last 90 days of transactions. Each alert keeps the transactions behind it and the figures it computed. A rerun doesn’t duplicate an alert.
Alerts land in their customer’s case, ordered by a triage score that lists its points. The triage agent looks for what in the data might explain the activity.
The counterparty network, the transaction timeline, the declared profile against the last 90 days, prior SARs and the legacy system’s alerts, on one page.
Close with a reason or escalate with a reason. Disposition controls refer risky closures to a lead. Escalating opens the SAR and starts the filing clock.
A six-part narrative drafted from the facts, a quality review, and a lead who didn’t prepare it files, returns or declines it, on the decision record.
From Northmere Bank, a fictional bank whose every transaction is generated: Lakepoint Strategic Consulting LLC declared $20,000 a month in credits. Four rules fired on it. InsightAML put them in one case, AML-2026-000026, scored it 100, and traced part of the money to another of the bank’s own customers.
The score orders the queue; it decides nothing. Its weights are illustrative and yours to set.
The submission to a lead waits for the analyst. A lead other than the analyst files it.


Every number on a case is computed by the engines from the bank’s own data. The language model, when one is configured, explains and drafts over those numbers; it never supplies them.
Ten rules over a 90-day review window, parameters in plain sight.
Alerts grouped one case per customer, ordered by an explainable score.
What an investigator would otherwise assemble by hand.
Close or escalate, each with a reason code and a note.
A narrative that can be traced, filed by someone else.
Ask without tipping off; tune on outcomes.
Each agent does one step of the case and stops at a prepared decision: take the case, ask the relationship manager, close or escalate as proposed, use the drafted narrative, submit for a lead’s review. You accept, reject or ask a question. Every answer goes on the record.

Agents draft questions to the relationship manager or the customer, and the request is held until a person sends it. The recipient answers through their own link with no login. A message to a customer that mentions suspicion, an investigation, a SAR or a report to the authorities can’t be sent.

The questions an AML leader is asked are simple. InsightAML keeps the evidence for each answer on the case, as it stood when the decision was made.
A reason code, a note in the analyst’s words, and every disposition control’s outcome at that moment, on the decision record.
The lead who files or declines a SAR can’t be the person who prepared or submitted it. The API refuses otherwise.
Every escalated case carries its filing clock: days left, due soon at seven days, overdue in red, and an overdue filing needs a reason.
Alert-to-SAR rates per rule, for this system and the legacy one, with the close reasons behind the false positives.


A Python API, a React app and PostgreSQL, designed to run in your own cloud account against your own systems. Nothing in a case is a value the model made up.
Rules, scores, the network, the profile comparison and the narrative’s facts are deterministic code. A model answer carrying a name or number not in the facts is thrown away.
InsightAML reads transactions, profiles, invoices and lists from the bank’s systems and keeps its own work in its own schema.
Which closures need a lead and what blocks a filing are controls you can read, test against a real case and publish, not code.
A lead records the filing in InsightAML. The submission to your financial intelligence unit happens through your own channel, outside it.