Filing a Suspicious Transaction Report (STR)
When a tenant's compliance staff form a suspicion, Ustawi helps them record and progress a Suspicious Transaction Report (STR) as a case — tracking the 24-hour STR reporting clock and producing a goAML-compatible export. The platform does not file for you: submission stays with the institution's own MLRO.
When an STR is required
An STR is warranted once the institution's compliance staff form a suspicion about a transaction — whether that suspicion arises from a screening alert, a pattern in a borrower's activity, or a field observation. Forming the suspicion is a human compliance judgement; the platform's role is to help capture and progress it, not to decide it.
The STR case flow
- 1Open the caseThe MLRO opens the STR case once the suspicion is formed. That is the moment the 24-hour STR reporting clock starts running.
- 2Draft the reportThe case captures the details the report needs, drawing on the client and transaction records already held in the platform.
- 3Export in goAMLThe report is exported in goAML-compatible format — the FIU's standard electronic structure — so it does not have to be re-keyed into a separate tool.
- 4Submit and recordThe MLRO submits the export to the FIU through the regulator's own channel, and the case history records that it was filed.
What the platform does and does not do
- It does track the 24-hour clock from detection so the window is visible the whole way.
- It does produce the goAML-compatible export, reducing a manual re-entry step.
- It does not submit the filing automatically — the MLRO lodges it with the FIU.
- It does not make the filing decision on the institution's behalf; Ustawi is not a reporting entity in its own right.
The tenant institution, as the licensed lender, designates its MLRO, makes the final determination on suspicious activity, and submits statutory filings. Ustawi provides the tooling — see the AML/KYC Compliance Statement.