Skip to main content
FinCrimes

AML compliance from first alert to filed report

FinCrimes gives a bank’s financial crime team one system from first alert to filed report: transaction monitoring, sanctions and PEP screening, queues with SLA clocks, case management with an escalation ladder, and regulator-format filings. Separation of duties is part of the permission model, so the analyst who proposes a SAR cannot approve it. Every step leaves an attributable record an examiner can verify.

See how it works
Transaction monitoringCustomer due diligencesupportSTR and SAR filingSanctions, PEP andwatchlist screeningAlert queues and casemanagementAudit trail and modelgovernanceAML compliancePART OF DARK POOLS FINCRIMES
Capabilities

What aml compliance gives your team

Transaction monitoring

Accounts, cards, mobile money and remittances are monitored against AML and fraud typologies in real time and in batch, with activity measured against each account’s own baseline.

  • Structuring, mule rings, round-tripping, dormant reactivation and corridor structuring
  • Thresholds and windows set to your jurisdiction’s reporting limits
  • Alerts that share an account, party or transaction collapse into one cluster with one narrative

Sanctions, PEP and watchlist screening

Parties, counterparties and providers are screened at ingest, on demand and inline at decision time against sanctions, PEP and internal lists.

  • Names in Cyrillic, Arabic and common Chinese characters are transliterated and matched, not discarded
  • Phonetic and edit-distance matching, corroborated by date of birth, ID number and country
  • Versioned, effective-dated lists that show what was designated on the day you screened
  • Scheduled refresh of UN, US, UK and EU lists, with each decision stamped with the list version
  • Precision, recall and threshold-sweep benchmarks for the matcher

Customer due diligence support

FinCrimes works alongside your onboarding system and supports KYC and CDD reviews by bringing identity, screening and behavior into one customer view.

  • Application-fraud detection when several applicants submit from one device in a short window
  • Synthetic-identity clusters built from shared phones, emails, devices, ID numbers and addresses
  • A customer 360 with transactions, alerts, cases and the customer’s own network
  • Screening of new and existing customers against PEP and sanctions lists

Alert queues and case management

Alerts route into work queues by severity, typology and product line. Each SLA runs in business hours against your own calendar and public holidays.

  • Claim-lock and pull-next work distribution, with keyboard triage and bulk actions
  • A configurable case lifecycle with a second approver on closure and escalation
  • An escalation ladder from investigator to Compliance or MLRO, with its own authority and SLA at each tier
  • Dispositions such as confirmed fraud, false positive, SAR filed and recovered feed back into tuning

STR and SAR filing

Filings are drafted from case evidence and serialized as goAML-format XML for STR, SAR and CTR reports, or as a FinCEN SAR. Each draft is checked for required fields, code-list values, date and currency formats and narrative quality before it can advance.

  • Your FIU’s reporting-entity ID, transaction-mode, funds and indicator codes, and MLRO details held per jurisdiction
  • A grounded narrative draft that lists its basis, for the analyst to edit
  • A deadline register, and a second approver before anything is filed
  • Branded investigation reports in DOCX and PDF

Audit trail and model governance

Every routing, assignment, status change, automated action and security event is attributed to a person or a named automation. Case actions are written to a hash-chained custody ledger that can be verified at any time.

  • An examination pack per case: criteria met, lineage, actors, ruleset version and ledger verification
  • Versioned rulesets, backtests and approvals behind every threshold change
  • Model promotion from challenger to champion only with a second approver
  • One audit console across every source, with CSV export
How it works

From data to decision

  1. 01MonitorTransactions are scored in real time and in batch, and parties are screened at ingest and at decision time.
  2. 02TriageAlerts route to severity queues with business-hour SLAs, and approved suppressions keep known false positives out.
  3. 03InvestigateAnalysts work the case with the evidence trail, link chart, money flow and similar past cases.
  4. 04EscalateCases move up the ladder to senior investigator, team lead or MLRO, each tier with its own SLA.
  5. 05DecideOne person proposes the disposition and another approves it.
  6. 06FileThe STR or SAR is drafted from the case, checked against the format and filed after a second approval.
In the field

Where it is used

BankingMule network cashing outStolen funds hop through dozens of freshly opened accounts and exit through ATMs and remittance corridors before the bank's overnight batch review even runs.Ring frozen before the cash-outBankingSIM-swap account takeoverFraudsters hijack a customer's phone number, intercept one-time passcodes and drain accounts in minutes, long before the victim's first call to the contact center.Takeover stopped mid-session
FAQ

Questions buyers ask

Get started

Take the next step

See aml compliance working on your own data, deployed on infrastructure you control.

Explore FinCrimes