Securities settlement messaging in the GCC and Egypt, market by market
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
Global custodians reach Gulf markets over Swift ISO 15022, but the depositories behind them do not all work the same way. The Saudi depository, Edaa, introduced straight-through processing of ISO 15022 messaging in 2022; Dubai CSD described its participant messaging as proprietary in January 2024; Muscat Clearing and Depository announced in March 2026 that it was introducing Swift; for several markets the public sources checked name no message standard. This page sets out what the public record says for each market, with the source for every statement and a note where a source could not be confirmed.
In short
| Market | Depository and clearing | Messaging with participants | Cash leg |
|---|---|---|---|
| Saudi Arabia | Edaa (Securities Depository Center); Muqassa (Securities Clearing Center) | ISO 15022 straight-through processing introduced at Edaa with the April 2022 post-trade programme. ISO 20022 support was reported for the November 2024 phase; the detail could not be confirmed when this page was checked. | SARIE (SAMA). The SAMA sources checked made no statement on ISO 20022 for the RTGS. |
| UAE: ADX | AD Clear; AD CSD | In September 2026 ADX announced that it had joined Swift with BIC ADSEAEADXXX to message custodians, CSDs and ICSDs. The announcement did not name the message standard. | UAEFTS. The official sources checked made no ISO 20022 statement. |
| UAE: DFM | Dubai CSD; Dubai Clear | Proprietary messaging formats, with a technology refresh then under way (Dubai CSD PFMI disclosure, January 2024). | As above. |
| UAE: Nasdaq Dubai | Nasdaq Dubai CSD | Swift MT599 for transfers to the US registrar and depositary receipt movements; MT535 statements from depositary receipt issuing banks (procedures, December 2021). | As above. |
| Kuwait | Kuwait Clearing Company (Maqasa): CSD, clearing and CCP | The public rule book describes sequenced exchange-to-KCC trade feeds and does not mention Swift or ISO messaging with custodians. | KASSIP (Central Bank of Kuwait): moved to ISO 20022 in 2021; KCC joined KASSIP in 2023. |
| Qatar | Edaa Qatar (QCSD) | Members and custodians take clearing reports from the CSD system; the settlement summary goes to Qatar Central Bank by Swift (undated procedure guide). | QA-RTGS: launched on ISO 20022 in December 2024. |
| Oman | Muscat Clearing and Depository (MCD) | In March 2026 Oman’s Ministry of Finance announced that MCD was introducing Swift in two phases: user to application first, then application to application. The announcement did not name the message standard; check MCD’s own announcements for the status of each phase. | The CBO RTGS operating rules (May 2023) cover MT and ISO 20022, with the cash leg of securities operations settling on pacs.009. |
| Bahrain | Bahrain Clear | Bahrain Clear publishes a T+2 delivery versus payment cycle. The public sources checked name no messaging standard. | CBB RTGS: the sources checked made no ISO 20022 statement. |
| Egypt | MCDR | The public sources checked include no recent statement. A 2010 rating report recorded plans for ISO 15022 messaging into MCDR systems. | CBE RTGS and interbank Swift: ISO 20022 from 21 June 2026. |
Saudi Arabia: Edaa and Muqassa
The Saudi post-trade technology programme went live in April 2022. Its first phase listed straight-through processing of ISO 15022 messaging at Edaa, the securities depository, together with daily and ad hoc reconciliation and reporting for participants, and extended Muqassa’s clearing to equities, sukuk, bonds and funds. The second phase went live on 25 November 2024 and improved messaging and reporting. Tadawul Group’s 2024 annual report is indexed as saying that Edaa adopted the ISO 20022 messaging standard, but the report could not be opened, so the message set and the scope (custodian link, issuer reporting or both) are not confirmed here.
Saudi listed securities moved to T+2 in April 2017; check the Saudi Exchange for the cycle in force. For a custodian or broker, the working messages are the ISO 15022 settlement set: MT540 to MT543 instructions, MT548 status advices, MT544 to MT547 confirmations, MT535 holdings statements and MT564 corporate action notifications.
International investors usually reach the market through a local custodian. Clearstream, for example, publishes how its clients instruct Saudi securities movements with MT540 and MT542, which it routes through its local link. That describes the client side of the chain, not the depository’s own interface.
United Arab Emirates: three venues, three pictures
Abu Dhabi. ADX announced in September 2026 that it had set up its Swift BIC, ADSEAEADXXX, to message custodians, central securities depositories and international CSDs as part of its post-trade programme. The announcement did not say whether the flows would use ISO 15022 or ISO 20022, or when each flow would go live. The AD CSD operational rules booklet checked for this page does not mention Swift or ISO. Ask ADX which message standard and release apply, and check its current announcements.
Dubai. Dubai CSD’s PFMI disclosure of January 2024 said its systems used proprietary messaging formats with participants and that a technology refresh was under way. Dubai Clear became the central counterparty in April 2020.
Nasdaq Dubai. The Nasdaq Dubai CSD runs on DFM’s CSD system. Its operating procedures (December 2021) use Swift MT599 free-format messages, with a published layout, for transfers to the US registrar and for depositary receipt movements, and MT535 statements from depositary receipt issuing banks.
Kuwait, Qatar, Oman, Bahrain and Egypt
- Kuwait. The Kuwait Clearing Company (Maqasa) is the CSD and the clearing house, and became the central counterparty with the post-trade reforms of 2025. Its public rule book, an older edition, describes sequenced trade feeds from the exchange and does not mention Swift or ISO. The public sources checked include no Swift user guide.
- Qatar. The Edaa Qatar procedure guide says members and custodians print their clearing report from the CSD system, and that the summary of the financial settlement is sent to Qatar Central Bank by Swift, or by fax or e-mail if Swift is unavailable. The guide is undated and some settlement-day references may be out of date.
- Oman. The Ministry of Finance reported in March 2026 that Muscat Clearing and Depository was introducing Swift as a single channel for trade settlement and clearing, settlement notifications, cash and securities confirmations, reconciliation, corporate actions and voting, and securities lending. The announcement set out two phases, user to application and then application to application with straight-through processing, did not name the message standard, and said a separate project would replace the CSD system. Check MCD’s own announcements for the status of each phase.
- Bahrain. Bahrain Clear publishes a T+2 delivery versus payment settlement cycle. The public sources checked name no messaging standard.
- Egypt. The public sources checked include no recent statement of MCDR’s messaging with custodians. A 2010 rating report recorded plans for ISO 15022 messaging into MCDR systems and a national market practice group.
The cash leg moved to ISO 20022 first
Across the region, the payment systems that settle the cash leg adopted ISO 20022 sooner than the depositories. Kuwait’s KASSIP moved to ISO 20022 payment messages in 2021, and the Kuwait Clearing Company joined it in 2023. Qatar’s QA-RTGS launched on ISO 20022 in December 2024. Oman’s RTGS operating rules (May 2023) cover MT and ISO 20022, with the cash part of securities operations settling on pacs.009. Egypt’s central bank adopted ISO 20022 for interbank Swift messaging and its RTGS from 21 June 2026.
Globally, Swift retired MT for cross-border payment instructions on 22 November 2025. Securities messages were not part of that change: Swift and each market infrastructure set the timeline for ISO 15022 MT5xx messages, and ISO 20022 for securities has been adopted market by market. A broker or custodian in the region can therefore receive pacs and camt messages for cash while its securities flows use MT5xx, and needs to read both. Check Swift’s published roadmap for the dates that apply. See ISO 15022 and ISO 20022 for securities.
What this means in practice
- Keep one table per market: depository, clearing house, message standard, channel (Swift, a depository gateway or files), settlement cycle and cash system. Review it when an infrastructure announces a change.
- Expect ISO 15022 with custodians across the region, and check each depository’s own interface separately: it may be Swift, a gateway or proprietary files.
- Model each business object once (instruction, status, holding, event) and map every format into it, so a market can move from files to MT, or from MT to ISO 20022, without changing operations.
- Ask Oman’s MCD and ADX which message standard and release they use; at the time of their 2026 announcements neither had named one.
- Test failing and unmatched paths per market, not only the happy path. See settlement fails triage.
Where ZagTrader fits
In Saudi Arabia, ZagTrader exchanges ISO 15022 messages with Edaa over the depository’s gateway: investor and account registration, settlement status, holdings statements and corporate action notifications. It also links Muqassa trade and settlement-instruction feeds to every order, so operations see trade by trade how far settlement has gone.
For Kuwait, ZagTrader reconciles each customer’s holdings with the Kuwait Clearing Company statement, physical and depository legs side by side, and keeps trades the depository has not yet registered out of the break list.
For DFM, QSE and EGX brokers, ZagTrader imports exchange trade files and sends ISO 15022 settlement instructions to custodians through the Swift Engine. ADX joined Swift in September 2026. The Swift Engine adds a new counterparty such as ADX the way it adds any custodian: register the partner BIC and the message templates, with no code change. As depositories such as Muscat Clearing and Depository connect to Swift, the template-driven Swift Engine adds new counterparties and message sets through configuration reviewed under maker-checker.
The trading side of the same trades runs over FIX. For orders, executions, allocations and FIX post-trade messages, see the free ZagTrader FIX Parser and its guide to FIX connectivity in GCC and MENA markets.
Questions
- Does Edaa use ISO 15022 or ISO 20022?
- ISO 15022 straight-through processing was part of the April 2022 phase of the Saudi post-trade programme. ISO 20022 support was reported for the November 2024 phase, but the message set and scope could not be confirmed from the public documents checked.
- Do UAE depositories use Swift?
- It differs by venue. ADX set up a Swift BIC in September 2026 without naming the message standard. Dubai CSD described its participant messaging as proprietary in January 2024. Nasdaq Dubai CSD’s December 2021 procedures use Swift MT599 and MT535 for specific transfer and depositary receipt flows.
- Is MT5xx being retired in the Gulf?
- When this page was checked, no retirement date had been announced and Swift had set no end date for ISO 15022 securities messages; check Swift’s published roadmap and each depository’s announcements. The cash leg moved to ISO 20022 in Kuwait, Qatar and Egypt, and Oman’s RTGS operating rules cover both MT and ISO 20022.
- Is there a market practice for each Gulf market?
- The sources checked for this page include no country-specific market practice document for these seven markets. Rely on each depository’s and custodian’s own documents and confirm details with them.
Messages in this guide
- MT540Receive Free
- MT541Receive Against Payment
- MT542Deliver Free
- MT543Deliver Against Payment
- MT544Receive Free Confirmation
- MT548Settlement Status and Processing Advice
- MT535Statement of Holdings
- MT564Corporate Action Notification
- sese.023Securities Settlement Transaction Instruction
- sese.024Securities Settlement Transaction Status Advice
- pacs.009Financial Institution Credit Transfer
Sources
- Argaam, 3 April 2022: Tadawul Group post-trade programme Phase 1, including ISO 15022 straight-through processing at Edaa (reproduces the group’s release)
- Argaam, 7 April 2022: Phase 1 completed
- Arab News, 25 November 2024: Phase 2 of the post-trade programme
- Tadawul Group 2024 annual report, Edaa section (indexed; could not be opened on 21 October 2026)
- RBC Investor Services, Saudi Arabia market profile (secondary source)
- Clearstream, instruction specifications for Saudi Arabia
- ADX release on Zawya, September 2026: ADX joins the Swift network
- AD CSD operational rules booklet
- Dubai CSD PFMI disclosure, January 2024
- Nasdaq Dubai operating procedures: clearing, settlement and risk management for securities, v1.8, December 2021
- Kuwait Clearing Company rule book
- Central Bank of Kuwait: development of payment systems (KASSIP on ISO 20022; KCC joined in 2023)
- Edaa Qatar procedure guide (undated)
- Qatar Central Bank: QA-RTGS
- Oman Ministry of Finance, 16 March 2026: Muscat Clearing and Depository launches Swift
- Central Bank of Oman: RTGS operating rules v3.2.0, May 2023
- Bahrain Bourse: Bahrain Clear clearing and settlement
- Public CSD rating report on MCDR, 2010 (secondary copy)
- Daily News Egypt, 21 June 2026: banks in Egypt adopt ISO 20022
- Swift press release, 25 November 2025: the switch to ISO 20022 for cross-border payments (indexed; direct access blocked)
- Swift ISO 20022 FAQ for securities markets (indexed; direct access blocked)
- Swift: ISO 20022 programme timeline (the dates in force)
Sources were checked on the review date shown at the top of the page. Market infrastructures change their rules and messaging; confirm a detail with the depository or your custodian before you rely on it.