The Transaction Screening Challenge Every AML Operations Lead Knows

A payment is waiting. The screening engine has returned a potential match. The analyst can see the name that triggered it, but still needs to establish whose name it is, where it appeared in the message, and whether the available information supports the match. Meanwhile, another alert arrives.

For an AML operations lead, the difficult question is how often this work has to be repeated. When analysts routinely reconstruct the same context, each increase in transaction volume brings more manual effort. Keeping the queue under control can become a daily achievement that conceals a deeper weakness in the screening process.

How much of your team’s capacity is spent investigating risk, and how much is spent assembling the information needed to begin?

Transaction Growth Exposes The Cost of Unresolved Friction

The scale of the challenge is visible in the region’s payment trajectory. ACI Worldwide and GlobalData’s 2024 Prime Time for Real-Time report recorded 855 million real-time payment transactions in the Middle East in 2023 and projected 3.0 billion by 2028, a compound annual growth rate of 28.8%. The 2028 figure is a forecast, but it makes the capacity question difficult to ignore.

Research conducted by Forrester Consulting, with findings published in 2024, found that 78% of surveyed financial institutions across Europe, the Middle East and Africa reported increasing screening alerts as payment volumes grew.

If the share of transactions generating alerts and the effort required per alert stay unchanged, growing volumes translate directly into more work. An unchanged alert rate can still mask a worsening operational burden. Management sees a familiar percentage; the operations lead sees a queue that takes longer to clear.

Adding reviewers can provide necessary capacity. Yet recurring manual work deserves its own investigation. Which alerts need expert judgment? Which take longer because the relevant field, party role or matching rationale is difficult to find? Those questions reveal where improvements could release capacity without weakening detection.

Richer Messages Need to Produce Better Decisions

ISO 20022 offers an opportunity to address part of that problem. Swift describes how richer, structured data can improve transaction processing and how more complete and accurate party information supports screening and compliance. The operational benefit depends on what happens to that information after the message enters the institution.

Consider this example:  USD 48,200 supplier payment from Saudi Arabia to Qata. The message identifies the debtor, an ultimate debtor, the beneficiary, the banks involved and remittance information. Each element contributes something different to understanding the transaction.

A potential match on the ultimate debtor should carry that role into the investigation. A bank identifier requires a different comparison from a party name. A location mentioned in an address needs to remain distinguishable from a name in the remittance narrative. For names represented in Arabic and Latin scripts, testing also needs to account for transliteration and spelling variation.

If these distinctions disappear during extraction, matching or alert presentation, the analyst has to recover them manually. The institution receives a richer message while retaining much of the old investigation burden.

A useful test of ISO 20022 readiness is to follow one transaction through the process. Can the team see which field triggered the match, the relevant reference record and the surrounding payment context? Does the same information remain available when the case moves to another reviewer? Receiving structured data is only the beginning of using it effectively.

The Decision Window is Part Of The Control

Timing makes these design choices consequential. Saudi Central Bank’s (SAMA) Rules for the Implementation of Targeted Financial Sanctions require outgoing transactions to be screened before execution and incoming transactions as soon as they are received. The rules also require ongoing effectiveness testing and documented, tested changes to screening procedures.

For operations leaders, this places attention on the entire path from message receipt to an actionable decision. A fast matching response provides limited operational value if the resulting alert lacks enough information for review, or if an unresolved result cannot reliably prevent release where required.

Regional supervisory evidence also shows why having screening in place deserves closer examination. In its May 2026 thematic review, the Central Bank of the UAE reported that 65% of the reviewed stored value facility and retail payment service providers had comprehensive sanctions screening policies, procedures and processes covering transaction parties. The review drew on earlier self-assessments, with responses from 26 of 35 providers. This is a finding about those provider sectors, rather than a measure of UAE banks or the wider MENA market.

For any institution, it raises a practical question: can the screening process demonstrate consistent coverage and decision handling across the transaction types the business actually supports?

That question matters for proliferation financing as well. FATF’s report published on 20 June 2025 describes evasion through intermediaries and concealed beneficial ownership. A screening result must therefore be understood within its limits. The absence of a direct listed-name match cannot establish that a transaction is free of proliferation financing risk. Customer due diligence, ownership information and wider financial crime controls remain essential.

Consistent Screening Requires Deliberate Configuration

Instant retail transfers and corporate payments through correspondent banks place different demands on the same screening system. Their message structures, parties and decision windows differ. Applying one configuration across both can create unnecessary alerts or leave relevant information poorly handled.

A better approach is to make these choices explicit. Screening templates can define how transaction contexts are handled, supported by documented field mappings, matching settings and review routes. Each configuration needs a clear rationale, testing and approval, while any process change must preserve applicable screening obligations.

Evidence of improvement should go beyond a smaller queue. Teams need to know whether known matches remain detectable, decisions arrive within the required window, and reviewers spend less time reconstructing payment context. Fewer alerts matter only when the institution can explain what changed and demonstrate that required detection remains effective.

At the next screening performance review, ask what would happen if transaction volumes increased while staffing stayed the same. Which parts of the process would absorb the growth, and which would pass it directly to analysts? The answer can reveal more about screening readiness than today’s cleared queue.

Explore The Challenge With MOZN

Join MOZN’s webinar, Getting Transaction Screening Right: Managing Sanctions & Proliferation Financing Risk in MENA, to explore these questions with Basheer Abualasal, Senior Business Development Expert, and Sameh AlQadi, Principal Product Manager, moderated by Anup Gunjan, Senior Product Marketing Lead.

The discussion will examine regional evidence, richer payment messages and configurable screening controls, followed by a practical demonstration of MOZN Real-Time Transaction Screening.