Fraud and financial crime
FRAML: why fraud and AML teams should share one platform
FRAML means running fraud detection and anti-money laundering on shared data, features and case management. Fraud and laundering use the same accounts, devices and counterparties, so separate systems miss links and duplicate work. A sovereign lakehouse gives both teams one governed copy of data, while keeping separate models, thresholds and regulatory reporting.
Published . Last updated
On this page
What is FRAML?
FRAML combines fraud (FR) and anti-money laundering (AML). Fraud teams stop money being stolen. AML teams find money being laundered. Often it is the same money: stolen funds move through mule accounts, which is laundering.
Why do separate systems fall short?
- The fraud team sees a mule account receive stolen funds. The AML team sees the same account move money out. Neither sees the whole story.
- Both teams build their own customer, device and counterparty data, so the same work is done twice.
- Investigators re-enter the same evidence in two case tools.
What should be shared, and what should stay separate?
| Shared | Separate |
|---|---|
| Customer, account and device data | Models and thresholds |
| Counterparty and network graph | Alert queues and teams |
| Feature pipelines | Regulatory reports (for example SARs or STRs) |
| Case evidence and outcomes | Access rights to sensitive cases |
How does it work on DataNature?
- One set of StreamHouse pipelines builds features for both teams.
- A shared network graph links accounts, devices and beneficiaries.
- Fraud models run in real time; AML models run on batches or rolling windows.
- Atlas applies access rules, so AML investigation details are visible only to authorised staff.
- Voir agents help investigators summarise an account’s history and draft narratives, with every source cited.
Does FRAML help with regulators?
Regulators expect institutions to report suspicious activity and explain their models. One platform with lineage from report to source event makes that easier. Examples include FINTRAC in Canada, FinCEN in the United States and FIU-Nepal under Nepal Rastra Bank.
Related
Which parts of FRAML run on the hot path?
Fraud decisions are real time; most AML monitoring is near real time or batch. On DataNature both read the same Iceberg tables:
- StreamHouse captures transactions as they happen and feeds fraud scoring and real-time sanctions or threshold alerts.
- Batch AML scenarios (structuring, rapid movement of funds, unusual cross-border flows) run as dbt and Spark jobs over Gold, on the same transactions StreamHouse landed.
- Shared entity data: customer, account and counterparty tables are modelled once in Gold and used by both teams.
- One case trail: fraud and AML alerts are written back to Iceberg with lineage, so an investigator sees the full history of a customer across both.
How does DataNature Atlas keep this secure and compliant?
Investigators see what they need; analysts see masked identifiers; every score and decision is auditable. DataNature Atlas is the platform's governance module:
- Knows your data: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
- Controls access: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
- Governs AI: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
- Proves it: lineage from source to metric to decision, and an audit log of who or what accessed which data.
- Stays local: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.
These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read DataNature Atlas in depth or see security and compliance.
Platform components in this article
Learn more about each DataNature product and module mentioned here.
See it on your own data.
Book a demoDemos and quotes are handled by Dlytica, the company behind DataNature.