FX & Treasury Payments

The GCC Cross-Border Payments Context

Cross-border payment flows out of the GCC are among the largest in the world relative to GDP. Five of the six GCC currencies are pegged to the US dollar; the Kuwaiti dinar is pegged to an undisclosed currency basket. The pegs simplify FX management between most GCC currencies, but many cross-border payments, and most payments to non-GCC currencies, still run through US dollar correspondent accounts, often cleared in New York. That creates operational dependence on a small number of correspondent banks and sanctions compliance obligations for every bank and payment institution in the region. Regional alternatives exist: Buna, the Arab Monetary Fund's regional payment system, settles in several Arab currencies as well as dollars and euros.

For corporate treasurers in the GCC, the practical problems are familiar: SWIFT payments that are slow and hard to track through the correspondent chain, FX costs hidden in transfer fees, sanctions screening at each correspondent that makes delivery times unpredictable, and growing AML/CFT documentation for larger transfers.

Payment institutions and fintechs offering cross-border services face the same problems, and more: correspondent accounts are harder to obtain, regulation at both ends of each corridor has to be managed at once, and margins are under steady pressure from digital competitors offering transparent, low-cost transfers on the main corridors.

SWIFT gpi and ISO 20022 Migration

SWIFT gpi is now the norm for cross-border payments between correspondent banks. It tracks each payment end to end, confirms when the beneficiary is credited and shows the fees taken at each step. For banks and payment institutions sending high-value payments from the GCC, corporate clients now expect gpi as standard.

ISO 20022: Status and Obligations

The SWIFT coexistence period for cross-border payment instructions ended in November 2025, and ISO 20022 (MX) messages are now the required format on the network. Institutions that have not finished migrating rely on translation, which keeps payments moving but drops structured data such as the LEI, purpose code and structured address that make ISO 20022 payments machine-readable and easier to screen.

When a payment passes from a fully MX-capable bank to one still working in MT formats, its structured data is lost at the translation point. The receiving bank then screens unstructured text, which produces more false positives, slower processing and higher cost.

• ISO 20022 readiness assessment: gap analysis against MX message requirements
• Structured data completion: LEI, purpose code and structured address
• Sanctions screening calibration for structured data: fewer false positives without losing coverage
• gpi review: tracking integration, fee transparency reporting and service level management

Multi-Currency Settlement Strategy

For payment firms that accept funds in one currency and pay out in another, the settlement set-up drives both profit and operational risk. The main decisions are: which currency pairs to hold balances in and which to convert through a bridge currency; whether to act as principal (carrying FX risk on the firm's own balance sheet) or as agent (passing conversion to a partner and earning a margin); and how to manage the exposure between the moment a customer locks a rate and the moment settlement completes.

FX Risk Management for Payment Firms

A firm that quotes a rate when a payment starts and settles later carries FX risk in between. On a single small remittance the risk is negligible, but across thousands of open transactions it can become significant when currencies move sharply. In corporate and B2B flows, where one payment can run to hundreds of thousands of dollars, the exposure on a single transaction can matter commercially.

• Exposure measurement: portfolio-level value at risk by currency pair and settlement lag
• Hedging strategy: forwards, options and natural hedging through currency matching
• Treasury counterparties: bank FX desks or specialist FX providers (such as Corpay, Convera, Equals or Moneycorp)
• Multi-currency account infrastructure: pooling, virtual accounts and nostro management

GCC-Specific FX Considerations

The Saudi riyal has been fixed at 3.75 per dollar since 1986, the UAE dirham at 3.6725 since 1997 (in practice since 1980) and the Qatari riyal at 3.64, formalised in 2001. These pegs are well backed by reserves, but payment firms in the region still need to manage dollar liquidity in local banking systems and the conversion costs on payments to floating currencies such as the Indian rupee, Pakistani rupee, Philippine peso and Egyptian pound, which are the main remittance corridors.

Treasury Payments for Corporates

Large GCC companies, particularly in energy, construction and government-related sectors, send large cross-border payments for procurement, project finance and payroll. The infrastructure behind these payments is often fragmented: many banks in many countries, inconsistent payment formats, manual reconciliation against ERP systems and little visibility between initiation and credit.

We help treasuries reduce the number of banking relationships, standardise payment formats across the group, adopt ISO 20022 data structures that allow automated reconciliation, and set up payment factories that centralise cross-border payments while meeting local compliance and reporting rules.

Payment Factory and In-House Banking

A payment factory routes all of a group's cross-border payments through one central entity, usually the group treasury centre, which holds the external bank relationships and pays on behalf of the subsidiaries. The benefits are a stronger negotiating position with banks, lower bank fees, better FX pricing through netting, and a single point of control for sanctions and AML screening.

• Feasibility: volumes, legal entity structure and requirements in each GCC market
• In-house bank design: intercompany lending, notional pooling and cross-currency netting
• Banking panel review: RFP design, relationship bank selection and account structure
• ERP integration: SAP, Oracle and Microsoft Dynamics payment modules producing ISO 20022 output
• Sanctions screening in the payment workflow: UN, OFAC, EU and national lists in each GCC market