Screening data quality
Customer names, dates of birth and addresses are standardised and transliterated so sanctions and PEP screening matches reliably without excess alerts.
GRA · Financial Crime and Fraud Risk
Spatial financeWhere capital meets hazard, exposure and transition
Data engineering, interoperability and stewardship for financial crime and fraud risk
Data engineering builds the pipelines, records and quality controls that financial crime systems depend on. On this platform it covers customer and transaction data quality, list management, lineage and retention, because poor data defeats every detection method.
01Register
Data engineering, interoperability and stewardship for financial crime and fraud risk on the record.
Method recordSTEM method
- MethodData engineering, interoperability and stewardship
- StewardData and Compute
- Applied inFinancial Crime and Fraud Risk
- Data3 inputs
- Checks3 validation steps
- Canonical pageSTEM Commons
02Application
What data engineering, interoperability and stewardship does here.
Data engineering, interoperability and stewardship cover the pipelines, standards and governance that make data usable and trustworthy. They determine whether information from different sectors can be combined for joint risk assessment. In financial stability, cyber and digital resilience and governance and institutions, sound data engineering allows hazard, exposure and financial data to be linked consistently. It supports transparent and repeatable analysis of interconnected risk. The canonical description is on the STEM Commons.
Monitoring coverage checks
Pipelines are reconciled to confirm every relevant transaction reaches monitoring, since gaps in feeds have caused major control failures.
Retention and minimisation
Data retention for AML purposes is set against legal minimums and data protection limits, with deletion recorded and checked.
03Exposure, loss and capital
What it means for exposure, loss and capital.
The exposure, loss, scenario and capital views a risk officer, supervisor or ministry of finance would ask for, with the frameworks they report against. Structures follow supervisory and actuarial practice. Values are illustrative: never prices, ratings or advice.
Transmission channels
How a shock in data engineering, interoperability and stewardship for financial crime and fraud risk reaches credit, market, underwriting, liquidity and operational risk, and feeds back.
NGFS climate scenarios · Network for Greening the Financial SystemIFRS S2 Climate-related Disclosures · ISSBTCFD recommendations · Financial Stability Board TCFDPrinciples for the effective management of climate-related financial risks · Basel Committee on Banking Supervision
04Data
What the method consumes.
Datasets and records used by data engineering, interoperability and stewardship on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
| Data | Role | Label |
|---|---|---|
| Customer master data | Screening input | DECLARED |
| Transaction feeds | Monitoring input | OBSERVED |
| Sanctions lists | Reference data | Published statistics |
05Process
How the process runs.
Process explorer · Process
Data engineering, interoperability and stewardship for financial crime and fraud risk: Build, sign and accept
10 steps·4 stages·2 gates
Process
Data engineering, interoperability and stewardship for financial crime and fraud risk: Build, sign and accept
An admitted mission becomes a cycle project; the build is pinned, verified and signed, and the Global Risks Forum (GRF) records acceptance for exercise, not permission to deploy.
01 Request and sources
- 01Admitted mission becomes a cycle projectRecord · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
- 02Qualify data sources and resourcesStep · the Global Centre for Risk and Innovation (GCRI)GCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.
02 Build and verify
- 03Source snapshotRecord · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
- 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
- 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
- 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.
03 Sign and admit
- 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
- 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.
04 Accept
- 09Core Build ReportRecord · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
- 10G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.
The programme year · NXS-FAC · UniverseDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The record order follows the Builds and Releases room lists of NXS-FAC.
06Validation
How results are checked.
Pipelines are tested with automated quality checks, schema validation and lineage audits. Reconciliation against source systems confirms completeness.
| Check | How it is done |
|---|---|
| Completeness reconciliation | Feeds are reconciled to source systems |
| Data lineage | Each control's inputs are traceable |
| List update timeliness | List changes reach screening within set times |
Incompatible standards, missing metadata and restrictive licences block integration. Legacy systems and undocumented transformations introduce silent errors.
07Connections
Topics that rely on this method.
08Stewardship
Who maintains the method.
Data and Compute stewards data engineering, interoperability and stewardship for the Consortium and reviews how it is applied across platforms.
09Connected
Where this page leads across the Consortium.
10Questions
Questions and answers.
What are the limits of data engineering, interoperability and stewardship in this field?
Incompatible standards, missing metadata and restrictive licences block integration. Legacy systems and undocumented transformations introduce silent errors.
How are results checked?
Pipelines are tested with automated quality checks, schema validation and lineage audits. Reconciliation against source systems confirms completeness.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method's use, not a run; no result is reported here.
Where else is this method applied?
The canonical method page lists every platform that applies it.
ReportsContribute
Contribute evidence from this page.
Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
Global Risks AllianceFinancial Crime and Fraud RiskEvidence Brief
- EmailGateway GW-GRASend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGlobal Risks AllianceSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Financial Crime and Fraud Risk
Bring an exposure or capital question to the Alliance.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.