How to set your AML configurations

Summary

Set the thresholds, deadlines and windows that the built-in monitoring rules read. About 5 minutes · 4 steps. Also called: AML settings, thresholds, reporting limit.

Prerequisites

• A sign-in for Wakandi AML Risk Monitoring with an administrator role.
• Your country's reporting threshold and filing deadline, agreed with your compliance officer.

Step-by-step

1. Open Wakandi AML Risk Monitoring and sign in.
2. In the top menu, click Settings.
3. Click the Configurations tab. You'll see every setting with its value.

1. Change the values you need, then click Save.

What each one does:

• Country code — your AML jurisdiction, as a two-letter code such as UG. Screening uses it as the default country.
• Operating currency — the currency your thresholds are written in, such as UGX.
• LCT threshold — the amount above which a cash transaction has to be reported. Written in whole currency units.
• LCT channels — which channels count towards that threshold, as a list. For example Online, Import, Job, System and Teller.
• Risk scoring — two numbers: the score at which a case is treated as medium, and the score at which it is escalated.
• STR deadline (hours) — how long you have to file a suspicious transaction report. This sets the Report due date on every case.
• Retention (years) — how long AML records are kept.
• Structuring min occurrences — how many smaller transactions it takes before splitting is suspected.
• Structuring window (hours) — the period those transactions have to fall inside.
• Unusual frequency multiplier — raises an alert when today's transaction count is more than the member's average daily count multiplied by this figure.
• Round amount — the unit that counts as round, and how many times it has to repeat.
• Case alert fallback recipients — who is told about an urgent case when no one else is set on the rule.

Warning: These values decide what your institution detects. Raising the LCT threshold means large cash transactions below the new figure stop being reported. Agree every change with your compliance officer first.

Note: The keys shown in grey, such as aml.lct_threshold, are fixed by the application. You change the value beside them, not the key.

Common pitfalls & FAQ

• My change had no effect on old cases. Configurations apply to transactions monitored from now on. Cases already open keep the values that produced them.
• The value went back to what it was. Click Save after editing. Moving to another tab first discards the change.
• What should the LCT threshold be? Your country's regulator sets it. Wakandi does not choose it for you.
• A setting expects JSON. The grey hint under the field shows the exact shape to copy, such as { "unit": 1000000, "minOccurrences": 3 }.