Settings — AML / Sanctions Screening
The Settings ▸ AML page configures the platform’s automated anti-money-laundering screening pipeline. When enabled, every verification subject is screened against the configured sanctions and risk lists, and any matches surface on the verification detail page for reviewer triage.
The platform’s design principle: findings are informational, decisions are human. AML hits never auto-reject a verification; the reporting entity retains the compliance decision and the audit trail captures both the hit and the human decision.
Anatomy of the page
Section titled “Anatomy of the page”1. Page header
Section titled “1. Page header”Standard PageHeader with the title AML / Sanctions Screening and a multi-line description summarizing the lists screened.
2. Settings panel
Section titled “2. Settings panel”A bordered card with four field rows:
| Field | Control | Saved on |
|---|---|---|
| Enable AML screening | Switch | Toggle change |
| Match threshold | Range slider (70–99) | Mouse-up / touch-end |
| Retention years | Number input (5–10) | Blur |
| Screening list sources | Per-list toggles + timestamps | Toggle change |
3. Sources section
Section titled “3. Sources section”A nested section header (Screening list sources) followed by one row per list. Each row carries a description, an on/off toggle, a “last refreshed” timestamp, and a Refresh now button.
Lists screened
Section titled “Lists screened”| List | Authority | Coverage |
|---|---|---|
| OSFI | Canada Office of the Superintendent of Financial Institutions | Canadian consolidated list |
| OFAC SDN | US Treasury | Specially Designated Nationals |
| OFAC sectoral | US Treasury | Sector-specific sanctions |
| UN | United Nations | Consolidated sanctions |
| EU | European Union | Consolidated list |
| UK OFSI | HM Treasury | UK financial sanctions |
| FATF | Financial Action Task Force | Jurisdiction risk |
The platform pulls from upstream sources nightly at 02:00 UTC and indexes the results into a fast in-memory matcher. The matcher uses fuzzy name matching with the configured threshold.
Match threshold mechanics
Section titled “Match threshold mechanics”The threshold is a percentage: a match score below it is suppressed, above it surfaces as a hit on the verification detail page.
- 70–80% — wide net, more false positives, useful for high transliteration risk
- 85% — calibrated default; balances signal and noise
- 90–99% — tight net, fewer false positives, may miss near-matches
The score is computed from a name-similarity algorithm tuned for multi-script inputs (Latin, Cyrillic, Arabic, CJK).
Retention
Section titled “Retention”PCMLTFR (Canada) and most other regulators require AML records to be retained for at least 5 years. The platform defaults to 7 years for buffer. Values outside 5–10 are rejected server-side.
The retention clock starts at the verification’s completion timestamp. After expiry, AML hits are purged from the verification record but the verification itself remains.
List sources
Section titled “List sources”Each list source has a toggle and a last-refresh timestamp. Disabling a list:
- Suppresses new hits from that list immediately
- Does not purge existing hits — those remain in audit history
Manual refresh:
- Triggers an out-of-band pull from the upstream regulator
- Useful when an emergency designation is published mid-day
- Idempotent — safe to spam; the worker dedupes
Permissions and scope
Section titled “Permissions and scope”| Role | View | Edit |
|---|---|---|
| Owner / Admin | ✓ | ✓ |
| Member | Indirect (sees hits on verification detail) | ✗ |
| Viewer | ✗ | ✗ |
AML configuration is tenant-wide. No per-matter override exists.
Audit logging
Section titled “Audit logging”| Action | Event |
|---|---|
| Toggle AML | org.aml_settings_updated (diff includes enabled) |
| Threshold change | org.aml_settings_updated (diff includes match_threshold) |
| Retention change | org.aml_settings_updated (diff includes retention_years) |
| Source toggle | org.aml_settings_updated (diff includes sources) |
| Manual refresh | org.aml_refresh_triggered (with source ID) |
Troubleshooting
Section titled “Troubleshooting”| Symptom | Most likely cause | Fix |
|---|---|---|
| AML toggle stuck off | Plan tier excludes AML | Upgrade under Settings ▸ Billing |
| Threshold won’t save | Released outside 70–99 | Drag back in range |
| Last-refreshed timestamp old | Auto-refresh hasn’t run yet today | Click Refresh now |
| Excessive false positives | Threshold too low | Raise to 90 and observe |
| Missed obvious hit | Threshold too high or list disabled | Lower threshold or re-enable list |
Related pages
Section titled “Related pages”- Verifications — surface where AML hits appear on the detail page
- Settings ▸ Compliance — broader compliance dashboard
- Settings ▸ Audit Log —
org.aml_*events - Settings ▸ Billing — tier gates AML availability