AML compliance software for Tanzania's reporting institutions.
Sanctions and PEP screening, transaction monitoring, customer risk rating, case management and reporting to the Financial Intelligence Unit through goAML, in one analyst workspace for reporting persons under Tanzania's Anti-Money Laundering Act.
Built for the Anti-Money Laundering Act and the Financial Intelligence Unit.
Tanzania's Anti-Money Laundering Act (Cap. 423, Revised Edition 2023), its regulations and FIU guidance set out what a reporting person has to do. Each duty maps to a module, so the evidence sits where an examiner will look for it.
Identify customers and rate their risk
Six-factor customer risk rating across country, industry, product, channel, behaviour and PEP/sanctions exposure, with four-eyes overrides, plus a beneficial-owner graph for legal-entity customers.
Apply enhanced due diligence to PEPs and higher-risk customers
An EDD workflow inside case management, with periodic reviews scheduled automatically by risk band so a high-risk file does not go stale.
Screen customers against sanctions lists and PEP data
Multi-script, locale-aware matching against lists synced from providers such as Dow Jones and World-Check, plus manual upload for lists you maintain yourself, with versioned lists and freshness dashboards.
Monitor transactions for suspicious activity
A rule engine running in batch and streaming, with typology-aligned starter rules, back-testing and versioned promotion, fed by REST, SFTP, Kafka, CDC or ISO 20022 connectors.
Report suspicious and cash transactions to the FIU
A draft, review, approve and submit lifecycle with acknowledgement handling. The goAML XML is generated and validated by the Creodata goAML Reporting Platform, with a manual download if the portal is down.
Keep records and show supervisors the evidence
An append-only audit log behind every decision, evidence packs for inspections, a read-only regulator portal, and an obligation registry that turns new guidance and amendments into tracked tasks.
This maps software capability to obligations; it is not legal advice. For registration and filing mechanics, see the Tanzania FIU goAML reporting guide.
For Tanzania's reporting institutions, whichever regulator supervises them.
The Act names the regulators, and section 26 makes the regulator or the FIU responsible for enforcing compliance.
The Bank of Tanzania, which also licenses Tier 2 microfinance service providers.
The Bank of Tanzania has delegated Tier 3 SACCOS to the Tanzania Cooperative Development Commission and Tier 4 to local government authorities; the Act names the Registrar of Cooperatives.
The Tanzania Insurance Regulatory Authority and the Capital Markets and Securities Authority.
The Gaming Board of Tanzania, the Tanganyika Law Society, the National Board of Accountants and Auditors and the other regulators named in the Act; otherwise the FIU.
- FIU goAML Registration in Tanzania: Who Registers, the Portal's Steps and What to Prepare (2026)
- Suspicious Transaction Reports in Tanzania: The 24-Hour Rule, the STR Form and Tipping-Off (2026)
- Cash Transaction Reports in Tanzania: USD 10,000 CTRs, USD 1,000 EFT Reports and the Five-Working-Day Deadline (2026)
- Tanzania's Anti-Money Laundering Act, Cap. 423, and the Anti-Money Laundering Regulations, 2022 Explained
- AML Compliance Software in Tanzania: A Buyer's Guide for Banks, SACCOS and Fintechs (2026)
- goAML reporting software for Tanzania
- Loan origination software in Tanzania
- Expense management software in Tanzania
- AML compliance software in Kenya
- AML software in Uganda
- AML software in Zambia
- AML software in Rwanda
- AML software in Nigeria
- AML software in Ghana
- AML software in South Africa
- AML software in the UAE
Frequently asked questions.
Does the software report to the FIU?
Yes, through goAML. Suspicious and threshold transaction reports move through a draft, review, approve and submit lifecycle in the AML software, with retry, reconciliation and acknowledgement handling. The Creodata goAML Reporting Platform then generates and validates the goAML file for the FIU's portal, and a manual download is available if the portal is down.
How quickly must a Tanzanian reporting person file a suspicious transaction report?
Within 24 hours after forming the suspicion, and where possible before the transaction, under section 18(1) of the Anti-Money Laundering Act, Cap. 423 (R.E. 2023). The 2022 Regulations refer to 24 working hours, but the Act's stricter clock should govern.
What are Tanzania's cash and electronic transfer reporting thresholds?
Currency transactions of USD 10,000 or more, or the equivalent, and electronic funds transfers of USD 1,000 or more, converted at the Bank of Tanzania rate at the time of the transaction. Related transactions within 24 hours that together reach USD 10,000 count as one. Reports are due within 5 working days under the 2019 Electronic Funds Transfer and Cash Transaction Reporting Regulations. Whether domestic transfers are covered is unclear: the regulations define electronic funds transfers to include domestic ones, but their reporting form and sanctions provision refer to international transfers, so confirm with the FIU.
Can we run the software on-premises in Tanzania?
Yes. The on-premises edition runs on your own Kubernetes cluster with Postgres 16, RabbitMQ, MinIO, OpenSearch and Keycloak, and has the same features as the Microsoft Azure edition, so an institution that must keep data in its own data centre is not running a lesser product.
How much does AML software cost in Tanzania?
There is no public price list. Each capability is licensed separately and grouped into Starter, Growth and Enterprise tiers, so a quote depends on the modules you switch on and whether you deploy on Azure or on-premises. A demo is the quickest route to a quote scoped to your institution.
Can a smaller institution start small?
Yes. The Starter tier covers screening, customer risk rating and case basics in the cloud. Growth adds transaction monitoring, STR/CTR reporting and ingestion connectors, which a deposit-taking institution will need for its monitoring and reporting duties. Modules switch on per tenant, so moving up a tier adds capability without starting again.
How long does implementation take?
It depends on how many modules you start with and how your data arrives. Screening and risk rating need customer data; transaction monitoring also needs transaction feeds, which connect over REST, SFTP, Kafka, change data capture or ISO 20022 with replay and a dead-letter queue, so a failed load is visible rather than silent. After scoping, we propose a phased path to your first production go-live.
See the AML software run on a Tanzania reporting profile.
Screening, monitoring, cases and FIU reporting on a realistic alert queue, in a live demo.