Welcome to FlowSentry
What FlowSentry does, the modules it brings together and the principles that shape every screen.
tocOn this page
FlowSentry is an anti-money-laundering (AML) and transaction-monitoring platform for regulated financial institutions: banks, SACCOs, microfinance institutions, digital lenders, payment service providers and fintechs. It watches every transaction, screens every customer, rates customer risk and gives your compliance team one place to investigate, decide and report — with AI assistants that draft the paperwork and people who make every decision.
This article explains what each part of the product does and how the parts fit together. If you are signing in for the first time, continue with Sign in, set up MFA and understand step-up.
What FlowSentry does
| Module | What it does for you | Where to find it |
|---|---|---|
| Monitoring | Runs your monitoring rules and scenarios against every transaction as it arrives and raises alerts. Includes a rule library, a guided rule builder, backtesting and rule performance. | Monitoring in the rail, /monitoring/rules |
| Work | Your alert queue, cases and investigations, the MLRO's decision workbench, QA review of closures and the approvals inbox. | Work, /alerts |
| Customers | The customer and account registers, governed KYC changes, customer risk ratings, risk models, enhanced due diligence (EDD), the enterprise-wide risk assessment (EWRA) and, where switched on, client onboarding. | Customers, /customers |
| Screening | Screens customers, directors and beneficial owners against sanctions, PEP and internal lists; hit review with explanations; name search; batch screening; exclusions; the PEP register. | Screening, /screening |
| Reporting | Suspicious transaction reports (STR/SAR) and cash transaction reports (CTR) in goAML format, the filing registers, regulator reviews and the audit trail. | Reporting, /reporting |
| Insight | Dashboards for executives, monitoring, operations, screening, customer risk and AI usage; a personal dashboard; pivot analytics and a metric designer. | Insight, /dashboards |
| Data | Connects your core banking, mobile-money or brokerage systems; maps their fields; loads files; tracks every run. | Data, /integration/sources |
| Admin | Institution settings, kill switches, webhooks, reason codes, FX rates and platform health. | Admin, /admin |
You only see the modules and pages your role allows. An analyst will not see the Admin module; an executive sees dashboards but not cases. See User roles at a glance.
How the parts fit together
A typical flow through FlowSentry looks like this:
- Data arrives. Your systems send customers, accounts and transactions to FlowSentry through a signed API or file uploads. Every record traces back to the run that brought it in.
- Customers are screened and rated. New and changed customers are screened against your lists and given a risk rating with a full, explainable breakdown.
- Rules raise alerts. Each transaction is evaluated against your active rules. When a pattern matches — structuring, a mule fan-in, a rapid pass-through — an alert lands in the queue with the evidence that triggered it.
- Analysts investigate. Analysts claim alerts, close the ones that are explained with a coded reason, and group the rest into cases. AI assistants summarise, draft memos and suggest narratives.
- The MLRO decides. When an analyst records suspicion, the case goes to the MLRO, who files an STR, returns the case for more work, or decides not to file with grounds.
- Reports go to the FIU. FlowSentry builds and validates the goAML report, and the MLRO hands it off to the FIU portal and records the reference.
- Everything is evidenced. Every decision is attributed to a named person in a tamper-evident audit trail, and dashboards show how the programme is performing.
Principles you will notice
- Human accountable, AI accelerated. AI assistants draft summaries, memos and narratives. They never close an alert, decide a screening hit, file a report, approve a change or edit a list. See Meet Ask Sentry.
- Four eyes on every regulated outcome. Rule activation, STR filing, true-match confirmation, KYC changes, settings and onboarding approvals all need a second person. You can never approve your own work.
- A fresh second factor for sensitive actions. Step-up asks for your authenticator code or passkey before a regulated action, even if you signed in minutes ago.
- Configuration, not code. Thresholds, lists, reason codes, calendars and risk models are your institution's settings. Nothing is hard-wired for one bank.
- Evidence or it didn't happen. Alerts show the thresholds against the actual values, risk scores show every factor, screening hits show why they matched.
- Your data stays yours. Each institution's data is isolated from every other institution's, identifiers are masked by default, and AI features can run entirely on a self-hosted model.
Tip: Press Ctrl+K (or ⌘K on a Mac) anywhere to jump to a page, a customer, an account or a case. It is the fastest way around FlowSentry.
Where to go next
- New to the product: Sign in, set up MFA and understand step-up, then Find your way around.
- Want a quick path for your job: Your first day, by role.
- Unfamiliar with a term: Key concepts and the Glossary.