Analyst and senior analyst
What analysts and senior analysts do in FlowSentry, where they work, and what needs a second person.
ForAnalystSenior analyst
tocOn this page
Analysts are the investigators of FlowSentry. They work the alert queue, build cases, review screening hits and record suspicion for the MLRO to decide. Senior analysts do all of that and also act as the team's first checker: they supervise the queue, review a sample of closures, confirm screening matches and close alerts in bulk where policy allows.
What you can do
As an analyst
- Claim, investigate and close alerts with an outcome, a reason code and a rationale.
- Group related alerts into a case and work it through Triage, Investigation, Review and Closed.
- Record suspicion on a case and draft the STR narrative for the MLRO.
- Ask a relationship manager a factual question from a case's Requests (RFI) tab.
- Review screening hits: clear a false positive, propose a true match or escalate to a case.
- Look names up in Name search and screen a CSV file in Batch screening.
- Designate a PEP or request a PEP declassification for a checker to decide.
- Author monitoring rules in the guided rule builder and backtest them.
- Analyse a statement or transaction file in File analysis and promote findings to alerts.
- Read customers, accounts, risk ratings and the live transaction feed.
- Upload evidence documents and use the AI assistants, which draft but never decide.
As a senior analyst, in addition
- Supervise the queue: assign alerts to colleagues and act on alerts or cases owned by others, including handing a case over.
- Bulk close alerts for scenarios the alert-work policy allows.
- Review sampled closures in QA review: Pass or Return for rework.
- Confirm a proposed true match or approve a proposed clear as the screening checker.
- Propose or approve a change to the alert-work policy (SLA windows, QA sampling, bulk-close scenarios).
- Propose a KYC change on a live customer.
- Change metric definitions in the Metric designer.
Where you work
| Page | Route | What for |
|---|---|---|
| Dashboard | / |
Your KPIs and items waiting for you |
| Alerts & cases | /alerts |
The work queue: My work, Team, Unassigned, Claim next |
| Case | /cases/{id} |
Evidence, notes, suspicion and STR draft |
| My approvals | /approvals/inbox |
Four-eyes items you can approve |
| QA review | /qa |
Sampled closures (senior analysts) |
| Screening hits | /screening |
Screening workbench |
| Name search and Batch screening | /screening/search, /screening/batch |
Ad-hoc look-ups |
| Rule library and Create rule | /monitoring/rules, /monitoring/rules/new |
Read and author rules |
| Backtest and Rule performance | /monitoring/backtest, /monitoring/performance |
Test rules and see their outcomes |
| Live transactions | /monitoring/live-feed |
The feed as it lands |
| File analysis | /analysis/files |
Check a statement without loading it |
| Link analysis | /cases/link-analysis |
Map a party's transaction network |
| Customers and Accounts | /customers, /accounts |
Customer profiles and accounts |
| Dashboards | /dashboards |
Monitoring, operations, screening, customer risk and your own |
What needs a second person
| Your action | Who checks it | Step-up for the checker |
|---|---|---|
| Record suspicion | MLRO or Deputy MLRO decides | Yes, to file |
| Close an alert | A sample goes to QA review | No |
| Propose a true match, or clear a hit above the policy threshold or on a statutory list | Senior analyst, MLRO, Deputy MLRO or Screening checker | Yes |
| Submit a rule for approval | MLRO, Deputy MLRO or Administrator | Yes |
| Request a PEP declassification | Senior analyst, MLRO, Deputy MLRO or Screening checker (not the requester) | Yes |
| Propose a KYC change (senior analysts) | MLRO, Deputy MLRO or Senior approver | Yes |
| Propose an alert-work policy change (senior analysts) | Another senior analyst, MLRO or Deputy MLRO | Yes |
When you are the checker, you need a fresh second factor for screening confirmations and policy approvals. You never check your own work: you cannot QA your own closure, confirm your own proposed match or approve a policy change you proposed.
What you cannot do
- Decide whether an STR is filed. That is the MLRO's or deputy's decision.
- Approve or activate a rule. You can author and submit; someone else approves.
- Approve a KYC change, an exclusion or a list change.
- Analysts cannot bulk close, run QA review, confirm screening matches or propose KYC changes.
- See the STR register, the audit trail page or tenant settings.
- Let the AI close, decide or submit anything. Every draft needs you to act.
Warning: When you ask a relationship manager a question, ask only for facts. Never mention suspicion, an alert, an investigation or a report.
A typical day
- Open the Dashboard and check SLA at risk and anything under "Waiting for you".
- Go to Alerts & cases and press Claim next.
- Read the alert drawer, use Summarise with AI if it helps, and check the trigger transactions.
- Close the alert with an outcome, a reason code and a rationale of at least 20 characters, or select it and open a case.
- In a case, gather evidence, then record suspicion on the Suspicion & STR tab if the grounds are there.
- Work any screening hits assigned to you on
/screening, statutory hits first. - Senior analysts: clear the QA review sample and anything in My approvals.