Screening five GCC and MENA national designation lists

Ask a screening vendor which sanctions lists they cover and you will hear OFAC, the UN, the EU and the UK, usually followed by a long tail of “and 200 more”. Ask which national terrorist lists in the Middle East and North Africa they parse from the official source, daily, with Arabic name handling, and the answer gets shorter. This post covers the five lists AdverseMe treats as first-class sources, how their source formats differ, and what “parsed daily” actually involves.

Which GCC and MENA national lists does AdverseMe integrate?

AdverseMe integrates national designation lists from the United Arab Emirates, Lebanon, Tunisia, Morocco and Algeria. Each has a separate ingestion path and a daily refresh schedule. The coverage directory identifies the publishers; the screening trace records the source outcomes for a particular run.

Key takeaways

• The UAE, Lebanon, Tunisia, Morocco and Algeria each publish a national designation list under their own counter-terrorism or UN-implementation framework.
• National lists can overlap with international lists, but their coverage should be checked independently.
• Most of them are published as PDFs, spreadsheets or gazette notices in Arabic or French, which requires source-specific ingestion and validation.
• AdverseMe parses all five from the official files every day, applies Arabic transliteration handling and screens them alongside 13 international sanctions feeds.

Why national lists exist

The UN Security Council requires member states to freeze the assets of persons designated under its counter-terrorism resolutions. Many states go further and maintain their own list of designated individuals and organisations under domestic law, sometimes to implement UN designations locally, sometimes to add domestic designations that the UN has not made. For a firm regulated in that country, the national list is binding in the same way as the UN list. For a firm elsewhere that does business with counterparties in the region, it is a material risk indicator that an international feed will not show.

The five lists below are the ones AdverseMe parses directly. Each has its own coverage page with the issuer, format and cadence.

United Arab Emirates: the Local Terrorist List

The UAE Local Terrorist List is issued by Cabinet decision and administered by the Executive Office for Control and Non-Proliferation (EOCN). Under UAE AML rules, financial institutions and DNFBPs must screen against it and act on updates without delay, as covered in our post on Cabinet Decision 74 of 2020. The list is published as an official file that the EOCN updates when the Cabinet adds or removes names. AdverseMe parses that file daily; details are on the UAE coverage page.

Lebanon: the Internal Security Forces list

Lebanon’s designation list is published by the Internal Security Forces. It is a separate national source; a provider’s international-list coverage alone does not confirm this integration. For firms dealing with Lebanese counterparties, or with GCC-based businesses that have Lebanese shareholders, it is a source that a UN-plus-OFAC screen will not reach. AdverseMe parses it from the official file and re-checks daily; see the Lebanon coverage page.

Tunisia: the CNLCT list

Tunisia’s list is maintained by the Commission Nationale de Lutte Contre le Terrorisme, the national counter-terrorism commission, and is published as an official workbook that the commission updates. The configured workbook contains French and Latin-script fields, and the parser normalises identifying details. AdverseMe parses the latest workbook daily; see the Tunisia coverage page.

Morocco: the CNASNU list

Morocco’s national commission responsible for applying UN Security Council sanctions, the CNASNU, publishes the Moroccan list applying UN designations as an official PDF. The value here is partly the format: a PDF list needs entity-level extraction and validation, otherwise a page break or a merged cell produces a missing or corrupted entry. AdverseMe extracts the list from the official PDF with entity-level validation and re-checks daily; see the Morocco coverage page.

Algeria: the CTRF list

Algeria’s list is published through the Cellule de Traitement du Renseignement Financier, the financial intelligence unit, in the official gazette. Gazette PDFs require extraction and validation before their entries can be used for matching. AdverseMe extracts it from the gazette PDF with entity-level validation and re-checks daily; see the Algeria coverage page.

What makes national lists harder to integrate?

Source formats, language and update cadence all require attention.

The first is format. OFAC, the UN, the EU and the UK publish machine-readable XML or CSV that any aggregator can ingest. The five lists above are published as PDFs, spreadsheets and gazette notices. Ingesting them means writing a parser per list, validating the output entity by entity and re-running that parser whenever the issuer changes the layout.

The second is language. The source entries are in Arabic, sometimes with French transliteration, sometimes with none. Matching a Latin-script customer name against an Arabic entry requires transliteration handling that accounts for the many valid spellings of the same name. A tool that matches on exact strings will miss; a tool that matches on loose phonetics will bury the analyst in noise.

The third is cadence. A quarterly refresh of a national list is worse than useless, because it creates the impression of coverage. A firm regulated in the UAE is expected to act on a list change without delay. A daily software refresh is an operational schedule, not a guarantee of meeting every regulatory deadline.

What “parsed daily” means at AdverseMe

Each of the five lists has its own parser that reads the official file, extracts entries with entity-level validation and writes them into the screening index. The parsers run every day, and the coverage page lists each list with its issuer and format.

Names are indexed with Arabic transliteration handling, so that variant Latin spellings of the same Arabic name are matched. Every candidate match is then scored by four independent judges at temperature zero, so a transliteration match on a common name does not become a hit on spelling alone.

The five national lists are screened in the same run as the 13 international feeds and the rest of the 110+ sources, and every source searched appears in the Engine Trace, including the ones that returned nothing. That matters for the file: a regulator asking whether the Tunisia list was checked gets a dated answer, not an assumption.

Who this is for

Firms regulated in the UAE and the wider Gulf are the obvious audience; our GCC coverage page covers the regulators alongside the lists. But the lists matter well beyond the region. Correspondent banks, payment providers onboarding merchants with MENA shareholders, law firms taking on clients with regional structures and trade finance desks all deal with counterparties for whom a domestic designation in Beirut, Tunis, Rabat or Algiers is the single most relevant fact, and the one an international-only screen will not surface.

All five lists are part of the standard 110+ source screening, not a regional add-on you have to ask for. Plans are on the pricing page. To screen a name against the five lists and the 13 international feeds in one run, get started.

Source references

The EOCN sanctions page publishes the UAE list and related guidance. The Lebanon ISF workbook is the configured Lebanese source. Our coverage directory documents all five integrations and their status; the methodology explains availability and refresh limits.