
AML & FIU
AML controls that follow every customer and transaction.
Screen customers against PEP and sanctions data, monitor activity, work alerts into documented cases, and prepare STR information for goAML export — with AML records restricted by role.
- Customers screened
- 412 · PEP & sanctions checked
- STR reporting clock
- 24h from suspicion formed
- CASE-1042 · Amina Joseph
- Escalated to the MLRO
AML is not just screening — it is the whole chain
A name check on its own answers almost nothing. The value is the chain: who is being screened, what triggered the alert, how it was investigated, what evidence was kept, how the case was decided, and what remains on the record. Each link is a section on this page — follow one case through it below.
Tap a stage to stop on it. Hover pauses the animation.
From scattered files to one documented case
Drag the slider: the same alerts, tracked in a spreadsheet versus worked as cases in Ustawi.
| Amina Joseph | PEP match | ask Halima | STR due? |
| Tanzanite Foods | adverse info | in email | ?? |
| John Michael | unusual txn | case open? | — |
| Kilimo Bora | sanctions | #REF! | — |
Ustawi provides software controls and workflows that help financial institutions operationalize AML/CFT processes. It does not, on its own, guarantee regulatory compliance — the applicable requirements depend on your institution type and framework.
From customer to report
Start with a complete customer profile
Customer due diligence is where AML begins. Identity, customer type, occupation, source of funds and — for a business — beneficial ownership are captured on the customer record, so screening and monitoring run against a real profile rather than a bare name.
Risk-based AML assessment
Not every customer carries the same money-laundering risk. Ustawi records the factors that matter — customer type, PEP exposure, jurisdiction, cash intensity, behaviour and ownership complexity — and rolls them into a classification that drives review frequency, the depth of due diligence, and when a case should be opened.
The factors weighed and the review frequency for each band are configured per institution — the classification shown is not a universal rule.
Risk classification drives what happens next — the depth of due diligence, monitoring frequency, whether enhanced review applies, and when an alert should escalate into a case.
Screen customers before risk becomes exposure
PEP and sanctions screening runs against the customer record and lands in a queue an officer works through. Crucially, a potential match is not proof of anything — it is a prompt to look. The officer decides whether it is a false positive or a genuine concern, and that decision is recorded.
| Customer | Type | Result |
|---|---|---|
| Amina Joseph | PEP | Potential match |
| Tanzanite Foods Ltd | Sanctions | No match |
| John Peter | PEP | Potential match |
| Kilimo Bora Co-op | Adverse info | Review |
- PEP — No match
- Sanctions — No match
- Next review in 12 months
- Name / DOB similarity
- Needs an officer decision
- Confirm or mark false positive
- Match confirmed on review
- Escalated to a case
- Compliance review required
A match is not automatically a case
Every alert goes through adjudication before it can become a case. The officer sees the match detail alongside the customer's own history and the evidence to hand — then either clears it as a false positive or escalates it into a documented case. The page you see is a decision, not a raw match list.
- Customer profile
- Screening result
- Transaction history
- Supporting document1 attached
The decision, and who made it, is recorded on the audit trail.
Monitor activity, not just identities
Screening checks a name; monitoring watches behaviour. Ustawi compares a customer's activity against their own historical profile and surfaces the transactions that don't fit — so an officer can investigate an unusual pattern the same way they work a screening alert.
| Customer | Transaction | Risk | Action |
|---|---|---|---|
| Amina Joseph | TSh 8,400,000 | HIGH | Investigate → |
| Tanzanite Foods Ltd | TSh 12,200,000 | MEDIUM | Investigate → |
| John Peter | TSh 450,000 | LOW | Investigate → |
Transaction differs from the customer's historical profile. Flagged for an officer to review.
Monitoring surfaces patterns for a person to review; it does not, on its own, determine that a transaction is suspicious. Which patterns are watched is configured per institution.
Compliance doesn't stop after onboarding
A customer cleared at onboarding can change. Ustawi re-runs PEP and sanctions screening on a schedule, prompts periodic customer reviews, and keeps monitoring activity — so a new match or a change in behaviour is caught during the relationship, not just at the start of it.
Rescreening frequency and review schedules are configured per institution and per risk band.
Turn alerts into documented investigations
When an alert is escalated, it becomes a case with its own reference, owner and history. Everything the officer needs is in one place — the customer profile, the screening result, the activity history, the documents and the notes — and the decision, with its next action, is recorded.
- Customer profileReviewed
- Screening resultReviewed
- Transaction historyReviewed
- Supporting documents2 attached
- Officer notes3 recorded
- DecisionUnder review
Case states — Open, Under investigation, Escalated, Closed — are configured per institution.
Every compliance decision leaves an evidence trail
A case is only as strong as the evidence behind it. Ustawi keeps the profile, the screening result, the transaction history, the supporting documents and the officer's notes attached to the decision — so the answer to a reviewer's question is one screen, not a hunt through email.
- Customer profileCUS-10482
- Screening resultPEP — 92% name match
- Transaction history42 transactions reviewed
- Supporting documents2 attached
- Officer notes3 recorded
Each item is tied to the exact case and the decision it informed. The record shows not just that a decision was made, but what it was based on.
Retention is configured per institution policy.
From suspicious activity to documented reporting
Where an investigation leads a reporting officer to form the required suspicion, Ustawi carries the case through to a suspicious transaction report — each step recorded, and the reporting deadline tracked from the point the suspicion is formed.
- Alert detected
Screening or monitoring raises a prompt
- Compliance review
An officer adjudicates the alert
- Investigation
Evidence gathered in a case
- Case decision
Suspicion is formed — or the case is cleared
- STR prepared
Report drafted from the case
- Compliance approval
Reviewed by the MLRO / compliance manager
- goAML submission / export
Prepared and exported for reporting
Ustawi tracks the reporting deadline from the point the required suspicion is formed — not from the instant a screening match first appears. Under the Tanzanian AML framework a suspicious transaction report is submitted to the FIU within 24 hours of that suspicion being formed; the workflow surfaces how much of that window remains.
The deadline shown is the applicable reporting requirement; forming the suspicion, and the report itself, remain the reporting officer's responsibility.
Prepare and export STR information for goAML
The STR workspace assembles the customer information, related transactions, the suspicion narrative and the supporting documents into a report a compliance officer reviews before it is prepared for goAML. Ustawi prepares and exports the report — it does not file it for you.
- Customer information
- Transaction details
- Suspicion narrative
- Supporting documents2 attached
- Compliance reviewPending
All your AML work in one place
One control center for your AML workload
Above every customer and loan sits a single view of the AML work that is open, due, or running late — customers to screen, alerts to review, cases under investigation, and STR deadlines. AML stops being a set of disconnected tools and becomes a worklist tied to the customers and loans themselves.
- PEP reviews3
- Sanctions alerts2
- Customer risk reviews4
- Cases awaiting decision2
- STR deadlines1
| Customer | Reason | Risk | Action |
|---|---|---|---|
| Amina Joseph | PEP potential match | HIGH | Review → |
| Tanzanite Foods Ltd | Adverse information | MEDIUM | Investigate → |
| John Michael | Unusual transaction pattern | HIGH | Open case → |
| Kilimo Bora Co-op | Sanctions screening | REVIEW | Review → |
An alert is a prompt to review — not a finding of wrongdoing.
AML tied to the customer and loan lifecycle
Because AML lives on the customer record, a customer's whole compliance history reads as one story — screening, cases, reviews and the loans behind them, in order. AML is not a separate island; it is part of the customer's lifecycle.
- Loan application20 Jun 2026Approved · Loan #2318
- Periodic AML review15 Aug 2026Completed — risk unchanged
- PEP screening18 Sep 2026Potential match detected
- Case opened18 Sep 2026Escalated from alert AML-1042
- Documents reviewed18 Sep 2026Customer documents checked by Halima S.
- Case escalated18 Sep 2026Referred to the MLRO
Confidential, and on the record
Protect sensitive AML investigations
Tipping-off controls matter: staff outside the compliance function should not be able to tell that a customer is under AML review. Ustawi restricts AML cases and STR records by role, so a loan officer sees the customer and the loan, but not that a case is open behind them.
| Role | Customer profile | Loan info | AML case | STR approval |
|---|---|---|---|---|
| Loan officer | ✓ | ✓ | — | — |
| Branch manager | ✓ | ✓ | — | — |
| Compliance officer | ✓ | ✓ | ✓ | — |
| Compliance manager / MLRO | ✓ | ✓ | ✓ | ✓ |
Roles and permissions are configured per institution.
An audit trail that keeps every step
Ustawi doesn't only tell you there was an alert — it records what happened afterwards. Every material action is captured with a timestamp, the user and what they did, so an examiner can see who did what, and when, on one screen.
- 18 Sep · 09:12Screening performed· System
- 18 Sep · 09:13Potential PEP match generated· System
- 18 Sep · 09:20Case assigned· Halima S.
- 18 Sep · 10:02Customer documents reviewed· Halima S.
- 18 Sep · 10:14Investigation note added· Halima S.
- 18 Sep · 11:30Case escalated to MLRO· Halima S.
- 18 Sep · 15:40Suspicion formed · STR draft opened· N. Kweka (MLRO)
Access to the trail is governed by roles — see Staff Admin & Security.
Put AML behind every customer and every transaction.
Connected across the Ustawi platform
AML & FIU is not a separate island. It reads and writes against the same customer and loan record as the apps around it — so screening, cases and reporting stay tied to the lending they protect.
The customer, application and loans AML screening runs against.
Explore app →AML sits inside the wider control and evidence layer.
Explore app →Guarantors and related parties on the same records.
Explore app →Where supported regulatory reports are generated and exported.
Explore app →Role-based access enforces tipping-off controls.
Explore app →Who uses AML & FIU
AML is a team effort. Each role sees the part of the workflow it needs — and only that part.
Investigate alerts, manage cases and prepare reports.
The Money Laundering Reporting Officer reviews cases, forms the reporting decision and is responsible for timely STR filing.
See permitted customer risk information without accessing restricted AML cases.
Monitor AML workload, open cases and reporting status.
Review compliance evidence and the history of actions taken.
AML exists to protect the institution and its customers
Due diligence, screening, an alert reviewed properly, a case decided on evidence — these are not box-ticking. They keep the institution safe from being used to move illicit funds, and they keep honest customers from being caught by a false positive. Ustawi's job is to make the right control the easy one to do at the right moment.

Getting live
How we get you live
A structured rollout, from mapping your applicable framework to running AML controls on live customers.

- 01Discover
Map your institution type, applicable AML/CFT framework and current controls.
- 02Configure
Set risk factors, screening, monitoring rules, review schedules and roles.
- 03Migrate
Bring existing customers and their due-diligence records onto the platform.
- 04Test
Validate screening, monitoring, cases and STR export against known scenarios.
- 05Train
Bring compliance, credit and management staff up to speed on the workflow.
- 06Go live
Run AML controls on live customers, with support on hand.
See AML & FIU in a live demo
Request a DemoFrequently asked questions
Yes — PEP and sanctions screening run against the customer record, landing in an adjudication queue an officer works through.