The Saudi Extradition Legal Team’s Toolkit: Instruments and Channels
This is a technical inventory, not a narrative. Its purpose is to catalogue the specific legal instruments, databases, and communication channels that a Saudi extradition and sanctions defense team actually uses when a client seeks removal from the SDN list or resists a cross-border transfer request. The list below is ordered by function, beginning with the bilateral treaty framework that governs the entire process, then moving through multilateral conventions, administrative databases, diplomatic channels, and procedural filings. Each instrument is described in terms of what it does, who controls it, and how it interacts with the others.
1. The Bilateral Extradition Treaty Framework
The foundational instrument is the bilateral extradition treaty between the Kingdom of Saudi Arabia and the requesting state. Saudi Arabia maintains extradition relationships through a patchwork of bilateral agreements, most of which predate the modern sanctions era and were drafted with traditional criminal offenses in mind. A sanctions matter rarely fits neatly into a bilateral treaty’s schedule of extraditable offenses, which is precisely why the treaty text must be parsed line by line before any other instrument is invoked.
The team’s first task is to determine whether the alleged conduct is listed as an extraditable offense, whether dual criminality is satisfied, and whether any treaty exception applies. Many bilateral treaties contain nationality exceptions, political offense exceptions, and fiscal offense carve-outs. A sanctions violation is frequently characterized by the requesting state as fraud or money laundering rather than a sanctions offense, so the team must examine how the conduct is framed in the request and whether that framing survives the treaty’s dual criminality test. The treaty also dictates the procedural timeline, the role of the central authority, and the evidentiary standard the requesting state must meet.
2. The Riyadh Arab Convention and Regional Instruments
The Riyadh Arab Convention on Judicial Cooperation, adopted in 1983 under the auspices of the Arab League, is the primary multilateral instrument governing judicial cooperation among Arab states. It covers extradition, mutual legal assistance, and the recognition of judgments. For a Saudi-based client, the Riyadh Convention often supplements or overrides a bilateral treaty, particularly when the requesting state is another Arab League member.
The Convention establishes general principles that the team can invoke: the requirement that the offense be punishable in both states, the prohibition on extradition for political offenses, and the rule of specialty, which limits prosecution to the offense for which extradition was granted. It also creates a channel for mutual legal assistance requests that bypasses slower diplomatic routes. The team uses the Riyadh Convention as a procedural lever when the bilateral treaty is silent or ambiguous, and as a shield when the requesting state attempts to expand the scope of its request beyond what the Convention permits.
3. Mutual Legal Assistance Requests and Letters Rogatory
Mutual legal assistance requests (MLATs) and letters rogatory are the formal channels through which evidence is obtained from a foreign jurisdiction. In the Saudi context, an MLAT is typically transmitted through the Ministry of Foreign Affairs to the Ministry of Interior or the Bureau of Investigation and Public Prosecution, depending on the nature of the request. Letters rogatory, by contrast, travel through the judiciary and are executed by the competent court.
The team monitors both channels for several reasons. First, an MLAT can reveal what evidence the requesting state already possesses, which informs the defense strategy. Second, an improperly executed MLAT can be challenged on grounds of sovereignty, proportionality, or dual criminality. Third, the timing of an MLAT often signals the requesting state’s priorities and the strength of its case. The team maintains a working knowledge of the Saudi central authority’s internal routing so that responses are not delayed by misdirected filings.
4. INTERPOL Channels and the Commission for the Control of INTERPOL’s Files
INTERPOL notices, particularly Red Notices, are frequently the practical mechanism by which a client is detained or flagged at a border. The Commission for the Control of INTERPOL’s Files (CCF) is the independent oversight body that reviews requests to access, correct, or delete data held in INTERPOL’s files. The team’s toolkit includes a CCF application when a Red Notice or diffusion is based on a sanctions-related request that does not meet INTERPOL’s own rules.
INTERPOL’s constitution prohibits notices for offenses of a predominantly political, military, religious, or racial character. A sanctions matter can be characterized as political if the underlying request is motivated by geopolitical friction rather than ordinary criminal enforcement. The team also uses INTERPOL’s pre-removal and post-removal procedures, which allow a member state to request that a notice be reviewed before publication or removed after the fact. The CCF process is slow but it operates independently of the requesting state, which makes it a valuable parallel track while treaty-based arguments are being developed.
5. OFAC Databases, the SDN List, and the 50 Percent Rule
On the sanctions side, the core instrument is the Office of Foreign Assets Control’s Specially Designated Nationals and Blocked Persons List, commonly known as the SDN List. The SDN List is maintained in OFAC’s Sanctions List Search tool and is updated through Federal Register notices and OFAC’s own publication channels. The team monitors these updates because a designation can be triggered by a single transaction, a corporate relationship, or an ownership chain.
The 50 Percent Rule is a critical interpretive instrument: it provides that any entity owned 50 percent or more, directly or indirectly, by one or more blocked persons is itself blocked, even if not separately named. This rule often catches clients who are not on the list by name but are entangled through corporate ownership. The team’s review therefore maps the client’s ownership structure against the SDN List and against OFAC’s consolidated non-SDN lists, including the Sectoral Sanctions Identifications List and the Foreign Sanctions Evaders List. The goal is to identify every possible basis for a blocking or rejection before a formal petition is drafted.
6. OFAC Licensing, Petitions, and Voluntary Self-Disclosure
Once a designation or blocking is identified, the team’s toolkit turns to OFAC’s administrative procedures. A specific license application is the standard instrument for obtaining authorization to engage in otherwise prohibited transactions. A request for removal from the SDN list is a separate administrative petition governed by OFAC’s delisting procedures, which require the petitioner to demonstrate that the circumstances underlying the designation have changed or that the designation was based on incorrect information.
Voluntary self-disclosure is a third instrument, used when a client has inadvertently violated a sanctions program and seeks to mitigate potential penalties. Each of these filings has its own evidentiary standard, its own timeline, and its own internal review path within OFAC. The team typically prepares a delisting petition alongside a licensing request when the client needs immediate relief while the petition is pending. The petition must be supported by documentary evidence, legal argument, and often a showing of changed circumstances, such as divestment from a sanctioned entity or the cessation of the conduct that led to designation.
7. Glossary of Instruments and Their Functions
The table below consolidates the instruments described above and identifies the primary actor responsible for each. It is intended as a quick-reference inventory for paralegals, researchers, and clients who need to understand which instrument applies at which stage.
| Instrument | Primary Function | Controlling Actor |
|---|---|---|
| Bilateral extradition treaty | Governs transfer requests between two states; defines extraditable offenses and exceptions | Both states’ central authorities |
| Riyadh Arab Convention | Multilateral judicial cooperation among Arab League states | Arab League member states |
| MLAT / letters rogatory | Formal evidence-gathering across borders | Ministry of Foreign Affairs; judiciary |
| INTERPOL Red Notice / CCF application | International alert; independent review and removal of data | INTERPOL; CCF |
| SDN List / Sanctions List Search | Identifies blocked persons and entities | OFAC |
| 50 Percent Rule | Extends blocking to majority-owned entities of designated persons | OFAC |
| Specific license | Authorizes otherwise prohibited transactions | OFAC |
| Delisting petition | Requests removal from the SDN List | OFAC |
| Voluntary self-disclosure | Mitigates penalties for inadvertent violations | OFAC |
The inventory above is not exhaustive, but it covers the instruments that appear most frequently in Saudi-linked extradition and sanctions matters. The team’s effectiveness depends less on any single instrument than on sequencing them correctly: treaty analysis before MLATs, INTERPOL challenges in parallel with OFAC petitions, and licensing requests filed early enough to preserve the client’s commercial position. A delisting petition that is filed without a prior ownership mapping, for example, will often be rejected or returned for additional information, wasting months of the client’s time. Conversely, a CCF application that is filed before the underlying criminal request is fully understood may fail because the political offense argument was not properly documented.
Because the instruments interact, the team maintains a single master chronology for each matter. The chronology tracks treaty deadlines, MLAT transmission dates, INTERPOL notice status, OFAC acknowledgment letters, and any Federal Register publications that affect the client’s designation. This chronology becomes the backbone of every filing and every communication with the client. It also allows the team to detect inconsistencies between what the requesting state asserts in its extradition request and what it asserts in its sanctions-related submissions, which is often the most productive source of challenge.
For clients and in-house counsel who need to coordinate with the team, the practical takeaway is that each instrument has its own custodian and its own evidentiary logic. The bilateral treaty belongs to the central authorities. The Riyadh Convention belongs to the Arab League framework. MLATs belong to the foreign ministry and the judiciary. INTERPOL notices belong to the CCF once a challenge is filed. The SDN List and its associated licensing and delisting procedures belong to OFAC. Knowing which custodian controls which instrument is the first step in building a coherent defense, and it is the reason this inventory is organized as a reference rather than a narrative.
