Every list your screening depends on, in one governed place: imported from source, reconciled, quality-checked, versioned and distributed. Plus the intelligence layer no list tool offers: know the impact before a list lands, and see the network risk behind the names, down to sanctioned vessels.
Screening engines are only as good as the lists that feed them. Vendor files arrive on the vendor's schedule, not the regulator's. Nobody can prove the vendor file matches what the source published. Internal lists live in spreadsheets with no approval trail. When a designation wave hits, the first warning is the alert spike, and when an auditor asks for the list as it stood on a given date, the lookback becomes a project. Every one of those gaps is a control gap with a regulator's name on it.
Direct from source, in near real time. FabriK monitors regulatory sources directly including EU, OFAC, HMT and UN publications, and ingests updates within minutes of publication rather than waiting on data-provider lead times.
Reconciliation you can show an auditor. Vendor lists are reconciled against sanctions lists at source, so you can evidence that what you screen against is what the regulator published: no silent gaps, no silent duplicates.
Data quality before it becomes alert noise. Comprehensive profiling and quality checks on every list, with transformations applied before ingestion, so bad entries are fixed before they generate a week of false positives.
Internal lists, properly governed. Global and local internal lists with full data segregation, validation at entry, and multi-level approval workflow with four-eye checks. No more spreadsheet lists with no owner.
Versioning and point-in-time retrieval. Record-level history on every list. Retrieve the exact list as it stood on any date, with field-level changes, which turns lookback projects into a query.
List landscape governance. One view of every list in use, with rationale and approvals recorded. The governance trail exists because the system creates it.
Simulate what a list change will do to your alert volumes before it goes live: forecast spikes from designation waves, surface the likely top-hitting entries, and flag data quality issues while they are still upstream of your screening engines. One consistent methodology, one comparable view across all engines, captured and auditable.
The first warning of a designation wave should not be the alert spike. It should be a forecast that gives your operations team time to prepare.
Screening a name tells you whether it is listed. It does not tell you that a counterparty in your book is two ownership hops from a sanctioned entity, or that a vessel connected to your customer's trade finance exposure has just gone dark in a high-risk zone.
FabriK fuses licensed maritime and ownership data with your own customers, lists and transactions to produce customer-anchored alerts: not "this vessel entered a high-risk zone" but "this vessel matters to you, here is the customer, the exposure and the linkage, with the evidence attached." A lookup tells you about the vessel. This tells you about your risk.
The data providers answer "tell me about this vessel." The Watch List Management module answers "which of my customers is exposed, and why."
Watch List Management sits upstream of your screening engines and is engine-agnostic: it imports from any source and exports to any filter, in whatever format your engines expect. It does not require any other FabriK module. Integration is via the Integration Hub's standard connectors and APIs; typical deployments are live in weeks, configured self-service by your own team.
List changes flow straight into screening with zero handoff, and impact assessment reads your real matching context rather than a sample.
A list change that touches one of your customers can trigger a risk rating reassessment automatically.
Every list decision and every network-intelligence alert lands in the same case record and audit trail as the rest of your financial crime operation.
Agents handle the routine of list operations under your SOPs: triaging delta alerts, drafting impact summaries, preparing the evidence pack for the human approver.
Take it alone today. Everything above is configuration later, not a new project.
Every import, transformation, approval and export is logged.
Approval workflows enforce four-eye checks on internal list changes.
Versioned exports give you point-in-time evidence for auditors and lookbacks.
Documents why every list is in use and who approved it. When the regulator asks, the answer is a report, not a reconstruction.
Designation-wave spikes, vendor-file doubts, spreadsheet internal lists, lookback dread: pick one and we will show you how a leading European bank runs it instead.