Before the designation: the public procurement trail of a sanctions-listed group

AqlData — procurement insights · 52M awarded public contracts (OCDS) · 30,962 risk entities (OFAC / UK-OFSI / EU / UN) · aggregate, entity-level only

The same day Russia invaded Ukraine, a European subsidiary of a Russian energy group — its parent later named on the OFAC and UK OFSI sanctions lists — signed a public supply contract with Vienna's airport authority. The subsidiary was not itself on any designation list that day; the contract was not illegal. It is part of a larger pre-designation procurement trail: 100 unique public contracts (101 records) awarded to Lukoil group affiliates across five EU/EEA jurisdictions between February 2022 and October 2024 — before the parent entity's formal designation dates (OFAC: 2025-10-22; UK OFSI: 2025-10-15). These records are public, yet surfaced by no conventional sanctions-screening tool.

This is the gap: standard sanctions screening checks entity names against lists. It does not map whether those entities built an active government contracting footprint in the years preceding designation — exposure that may still be generating downstream obligations when sanctions land.

The signal

AqlData cross-references 30,962 designated entities across four sanctions regimes — OFAC (19,050), UK-OFSI (9,451), EU (1,586), and UN (875) — against 52 million public procurement records from 68 countries.

The initial finding: Lukoil group affiliates accumulated a documented public procurement footprint — 100 unique contracts (101 records) across five jurisdictions — in the period preceding the parent entity's designation. This retrospective exposure map is what standard sanctions screening does not surface.

One verified entity group with high-confidence, public-record matches:

Source: OCDS public procurement registries (TED EU, Romanian e-licitatie, Netherlands TenderNed, Croatian eTrg, Macedonian ESPP), cross-referenced against OFAC SDN List / UK OFSI Consolidated List / EU Sanctions Map / UN Consolidated List. Award dates verified against published_at with date_valid=1 flag. NL Gorinchem record identified as mirror-duplicate; excluded, yielding 100 unique contracts (101 raw records). Value in USD is FX-approximate (single current exchange rate applied; directional, not precise). All figures represent procurement contract values, not asset values. Methodology and reproducible source queries available on request.

EU designation note: The EU has not listed the Lukoil parent entity — Hungary exercised its veto in EU Council deliberations. The EU 19th sanctions package (October 2025) added specific Lukoil subsidiaries under the Ukraine-related programme only. Parent-entity designation: OFAC and UK OFSI only.

A third entity group (an EU-designated financial-institution affiliate) was identified but is withheld pending subsidiary-identity verification — a corporate-registry trace confirming whether the contracting entity falls within the EU ownership-extension scope. It will be published upon completion. Its exclusion does not materially affect the aggregate signal.

One illustrative record (public-registry sourced)

Record 1 — Lukoil Lubricants Europe GmbH / Austria, 24 February 2022 OCDS record ocds-70d2nz-c9d1ad9f-4cdc-3534-981b-0de71df7ec3e (source: TED EU / Tenders Electronic Daily, procurement notice AT-2022-02-24; retrievable via TED reference or national Bundesvergabeamt registry): Flughafen Wien AG (Vienna International Airport, a public entity) awarded a lubricants supply contract, value €85,000, to Lukoil Lubricants Europe GmbH on the date of Russia's full-scale invasion. The parent entity, PJSC Oil Company Lukoil, was later designated by OFAC (2025-10-22) and UK OFSI (2025-10-15). The Austrian subsidiary itself was not on any designation list on this date — the contract was not illegal — but this record is one data point in the pre-designation procurement trail: the gap between documented government-contract activity and eventual designation is precisely what standard screening tools do not map.

This example is drawn from a public contracting registry. It is presented as a procurement data point, not a legal adjudication. A gap in the procurement trail is not a breach — compliance conclusions require legal review of designation scope, subsidiary coverage, and applicable jurisdiction.

Why conventional tools miss this

Most sanctions-screening workflows operate at the counterparty onboarding layer: when a bank, insurer or buyer initiates a transaction, it checks the entity against a list. This works for direct designations. It has three structural gaps:

1. Subsidiaries below the designation threshold. Parent entities are listed; operating subsidiaries in third countries may not be. The parent–subsidiary linkage is not in standard list formats.
2. Historical contracts. A contract signed before designation may continue to generate payments after. Procurement registry records show both the award date and, in some cases, the contract period.
3. Third-party / indirect exposure. A compliance team screening its own counterparties does not see that its counterparty's government clients are buying from designated groups in another market.

AqlData surfaces the procurement layer — the pre-designation contracting trail of sanctioned-entity affiliates, across jurisdictions, over time.

Data sources & freshness

Sources: Open Contracting Data Standard (OCDS) public procurement records ingested from TED EU, Romanian e-licitatie, Netherlands TenderNed, Croatian eTrg, and Macedonian ESPP. Sanctions lists: OFAC Specially Designated Nationals (SDN), UK OFSI Consolidated List, EU Financial Sanctions Map, UN Security Council Consolidated List. All four regimes ingested; ingestion tracked via ingested_at timestamp per record.

Designation status (as of data ingestion): Lukoil parent (PJSC OIL COMPANY LUKOIL / LUKOIL OAO) is designated by OFAC (effective 2025-10-22) and UK OFSI (effective 2025-10-15). The EU has not designated the Lukoil parent entity — the Hungarian veto blocked this in EU Council. The EU 19th sanctions package (October 2025) added specific Lukoil subsidiaries to the Ukraine-related programme; the parent entity remains off the EU list. UN: not listed. All procurement records in this analysis predate the OFAC and UK OFSI designation dates.

Freshness: Procurement records are periodically re-ingested; ingested_at timestamps are tracked per record. This is not a live-streaming feed. Sanctions list state reflects the most recent ingestion cycle.

Coverage and honest limits

What this data covers: 52M public procurement records from 68 countries, OCDS-standard or normalized. High-confidence entity matching has been validated for the Lukoil affiliate group using multi-field resolution: parent canonical entity → group key → known subsidiaries, cross-referenced against award date and designation date (temporal validation). A third affiliate group is identified but withheld pending subsidiary-identity verification (see note above). Broader systematic screening across all 30,962 risk entities is in development; the infrastructure (entity resolution layer, canonical supplier map, sanctions overlay) is in place.

What it does not cover: - Private-sector contracts (by definition, not in public procurement registries) - Jurisdictions outside the 71-country corpus (most of MENA, Southeast Asia, Central Africa) - Sanctions regimes beyond OFAC / UK-OFSI / EU / UN (e.g. Swiss SECO, Australian DFAT, Japan METI) - Real-time alerting (current data is updated periodically, not live-streaming)

False-positive risk: Sanctions list names frequently share tokens with unrelated entities. "New Energy," "Iris," "Titan" appear on OFAC lists and also as legitimate EU procurement suppliers — these are different entities. The matches shown in this preview use multi-level entity resolution (parent entity → group canonical key → known subsidiaries) and temporal validation (award date versus designation date). Single-token name matching without resolution produces false positives at high rate; this analysis does not rely on it.

This is an indicator signal, not an adjudication. Identification of a procurement record linked to a sanctions-affiliated entity does not establish legal liability. A documented procurement trail is not evidence of a breach — compliance action requires legal review of designation specifics, subsidiary scope, applicable jurisdiction, and contract terms.

The compliance value proposition

For an AML or sanctions-compliance function, the relevant question is not only "is this counterparty listed?" but "where else is this entity group transacting, and are those transactions creating downstream exposure for our clients or portfolio?"

A government-contract win by a sanctioned-entity affiliate creates a documented public record: buyer name, contract value, date, jurisdiction. That record is: - Traceable — OCDS records carry persistent identifiers - Cross-jurisdictional — the same group may appear in Romania, the Netherlands, and Croatia in the same year - Temporal — award date is verifiable against designation date

This is third-party and supply-chain risk analysis that does not currently exist in standard sanctions-data products, which are built around direct-counterparty screening, not procurement-trail analysis.

For full entity-level breakdown, historical award trail, and subsidiary linkage mapping: desk@data.heyvaql.com

Source: Open Contracting Data Standard (OCDS) public records, 68 countries, 52M records. Sanctions lists: OFAC Specially Designated Nationals (SDN), UK OFSI Consolidated List, EU Financial Sanctions Map, UN Security Council Consolidated List. All entity matches are corporate/institutional; no natural persons are named or profiled in this preview. AqlData is an independent data compilation; not affiliated with any government, regulator, or sanctions authority. This document does not constitute legal advice.