Sanctions Screening Validation UAE | AML Screening Testing

An AML screening system is easy to switch on and hard to trust. The system runs quietly in the background, returns a result and moves on. If it misses a designated name because of a spelling variation, an outdated list or a threshold set too high, nobody notices until the customer turns out to be sanctioned and the funds should have been frozen months ago.

goAML Registration's sanctions screening validation service independently tests whether your AML screening software actually does its job. We check that the right lists are loaded and current, that every relevant person is screened, that the matching logic catches realistic name variations and that every decision is properly recorded. You receive clear evidence of how your system performs and practical steps to fix any weaknesses.

What Is Sanctions Screening Validation?

Sanctions screening validation is an independent test of whether a sanctions screening system finds the names it is supposed to find. The test runs records with known correct answers through the system, compares the results with the expected outcome and measures detection rates, false-positive rates and how quickly list updates take effect. Sanctions screening validation also reviews the human side of screening, including how alerts are cleared, who approves whitelists and whether each decision is recorded. The result is documented evidence that your screening control works with your own data, settings and lists, not an assumption based on a vendor's assurance.

Can you prove your screening tool would catch a newly designated name?

Let us test it.

Contact Us Now

Key Points at a Glance

The key points about sanctions screening validation in the UAE are:

  • Cabinet Resolution No. 74 of 2020 (CR 74/2020) requires ongoing screening and, on a confirmed match, freezing or rejection, as applicable.
  • Cabinet Resolution No. 134 of 2025 (CR 134/2025) requires the effectiveness of controls to be monitored and independently tested.
  • Sanctions screening failures can be silent, so only testing reveals them.
  • We use known-positive test packs to measure detection and false positives.
  • Sanctions screening validation covers lists, population coverage, data, matching, thresholds, whitelists, alerts and audit trails.
  • Missed matches mean missed Confirmed Name Match Reports (CNMRs) and Partial Name Match Reports (PNMRs) on goAML.
  • Sanctions screening validation fees range from AED 20,000 to AED 50,000, depending on the scope of work.
  • The timeline is mutually agreed for each defined scope.
  • 12+ sanctions screening validation projects completed across 3+ sectors, with an average reduction of 32%+ in false positives across projects.

Why Must Sanctions Screening Be Tested?

Sanctions screening must be tested because the screening and freezing duties are strict, and a system that misses a match breaks them silently. UAE targeted financial sanctions (TFS) rules require ongoing screening against the UAE Local Terrorist List and the UN Security Council Consolidated List. Screen immediately when either list changes. A confirmed match requires freezing or rejection, as applicable. An unresolved partial match follows a separate suspension or rejection process. When freezing is required, act without prior notice, immediately and in any event within 24 hours of the designation decision. Cabinet Resolution No. 74 of 2020 sets out these duties, and Article 36(3) of Cabinet Resolution No. 134 of 2025 extends the applicable targeted financial sanctions obligations to virtual asset service providers (VASPs).

Cabinet Resolution No. 134 of 2025 (CR 134/2025), Article 5(2)(b) requires businesses to monitor the implementation of their controls, assess their effectiveness and enhance them where needed. CR 134/2025, Article 21(6) requires an independent audit function to test the effectiveness and adequacy of policies, controls and procedures.

If your sanctions screening relies on a system, testing that system is part of assessing whether your controls are effective. Responsibility stays with your business even when a vendor supplies and hosts the tool. A vendor's assurance that the product works is not the same as evidence that it works with your data, your settings and your lists.

The Problem of Silent Screening Failure

Sanctions screening failures rarely announce themselves, because a system that misses a match produces no alert and no error message. The alert count simply falls, which can look like an improvement. Common causes of silent screening failure include:

  • List updates that stop loading after a vendor change or expired subscription
  • New customer data fields that are not passed to the screening engine
  • Beneficial owners and signatories that are captured in know your customer (KYC) checks but never screened
  • Thresholds raised to reduce false positives, which can also hide real matches
  • Whitelists that permanently suppress matches without periodic review
  • Arabic names or transliterations that the matching logic cannot handle

In each of these silent failures, the alert count drops and the screening system looks healthy. Only testing reveals whether fewer alerts mean fewer risks or a broken control.

What Our Sanctions Screening Validation Covers

Sanctions screening validation covers every stage of the screening control, from the lists loaded into the system to the record of each decision. A weakness at any one stage can let a designated name through, even when the rest of the system works well. Our sanctions screening validation tests nine areas:

List coverage and currency

List coverage testing confirms which sanctions lists are loaded into your screening system, including the UAE Local Terrorist List and the UN Security Council Consolidated List, and tests how quickly new designations appear in the system after publication. A list that loads a day late can leave a newly designated person free to move funds during that gap. We compare the list version in your system with the published list on the test date.

Population coverage

Population coverage testing checks that all required parties are screened: customers, beneficial owners, directors, authorised signatories, transaction counterparties, prospective clients and, where relevant, suppliers and business partners. We trace a sample of files from onboarding through to the screening log to confirm each party actually reached the screening engine. A beneficial owner recorded in KYC files but never screened is a gap that only this kind of file tracing reveals.

Data quality

Data quality review examines the customer data sent to the screening engine, including names, dates of birth, nationalities and identification numbers, and checks for missing or truncated fields. Good matching logic cannot compensate for a name that is cut short or a date of birth that never arrives, so data quality is tested before matching. We also check that both Arabic and English name fields reach the engine where your onboarding captures them.

Matching logic

Matching logic testing shows how the screening engine handles spelling variations, transliterations, missing name parts, reversed name order, initials, honorifics and Arabic script. Fuzzy-matching settings decide how close a name must be to raise an alert. Testing each type of variation shows exactly where the engine stops recognising a listed name.

Thresholds and settings

Threshold and settings review checks whether match thresholds and filters strike a reasonable balance between catching true matches and avoiding excessive false positives. A threshold raised to cut alert volumes can quietly reduce detection if the effect is not measured. Our test packs show what each threshold setting catches and what it misses.

Re-screening triggers

Re-screening trigger testing checks that your system screens again at every point the rules and your policy require. We test whether screening runs immediately after a sanctions list update, before onboarding a new customer or processing a counterparty transaction, and during periodic KYC reviews or after a material change in the customer's nature or ownership. We check system logs to confirm that each trigger screened the relevant records.

Whitelisting and suppression

Whitelisting and suppression review examines how cleared matches are suppressed, who approves them and whether they are periodically re-reviewed. A whitelist entry with no expiry can hide a customer who is later designated under a similar name. We test whether new list entries still alert against whitelisted customers.

Alert handling

Alert handling review samples real screening alerts to check that decisions are reasonable, documented and made by authorised staff, and that partial and confirmed matches led to the right actions. The right actions include freezing, suspending or rejecting a transaction and filing the correct goAML report on time. We trace sampled alerts from the system log to the recorded decision using authorised, appropriately redacted evidence. Any access to filed reports or identifiable case data is subject to applicable confidentiality and data protection rules.

Audit trail

Audit trail testing checks that every screening result and decision can be evidenced later. We check that your records show which list version was used, what the system returned and why the reviewer closed or escalated the alert. The Executive Office for Control and Non-Proliferation (EOCN) guidance requires reporting entities to keep all screening results, including confirmed matches, partial matches and false positives, for at least five years.

Get independent evidence on how your screening system performs.

Talk to our team.

Contact Us Now

How We Test: Known-Positive Test Packs

A known-positive test pack is the core of sanctions screening validation: a set of test records with known correct answers. Each record is designed either to match a listed name or to stay clear of one. Our test packs include:

  • Exact matches to names on the relevant lists
  • Realistic variations of those names, such as different spellings, missing middle names or reversed order
  • Transliterated and Arabic-script versions
  • Names with matching dates of birth or nationalities to test secondary filters
  • Clearly different names that should not match, to measure false positives

The test records are run through your screening system, and the results are compared with the expected outcome. Comparing actual and expected results shows how many true matches were caught, how many were missed and how many false alerts were generated. Where possible, we use synthetic data and public list entries rather than live customer records, to protect personal data.

Our Sanctions Screening Validation Process

Our sanctions screening validation process runs in seven steps, from scoping your setup to optional re-testing after fixes. Each step produces evidence that goes into the final report:

Step 1: Scope and system review

The scope and system review documents your screening setup: the system, lists, data feeds, settings, workflows and the parties screened. We review your AML policy and screening procedures alongside the system configuration. Gaps between what the policy says and what the system does are recorded at this stage.

Step 2: Test design

Test design prepares known-positive and known-negative test packs suited to your customer base, languages and risks. A real estate broker serving many nationalities needs different name variations from an exchange house focused on regional corridors. Each test record has a documented expected outcome before testing begins.

Step 3: Test execution

Test execution runs the test packs through your screening system, in a test environment or under controlled conditions in production, with your team's support. Results are exported directly from the system so nothing is re-keyed. Batch screening, real-time screening and re-screening are tested separately where your system uses them.

Step 4: Alert and file sampling

Alert and file sampling reviews a sample of real alerts and decisions to test how the human side of the screening process performs. We check who closed each alert, the reason recorded and whether the decision was escalated where needed. A well-tuned system still leaves the screening control weak if alerts are closed without proper review.

Step 5: Analysis

The analysis step measures detection rates, false-positive rates, list update speed and coverage gaps, and identifies their root causes. A missed match may come from data, matching logic, thresholds or a whitelist, and each needs a different fix. Root-cause analysis stops you from fixing the symptom and missing the cause.

Step 6: Report and recommendations

The validation report sets out results, evidence, findings rated by severity and recommended configuration or process changes. Each finding links to the test records that exposed it, so your team and vendor can reproduce the issue. The report is written for your audit file and for review by senior management and your supervisor.

Step 7: Re-test

Re-testing confirms that the fixes work after configuration or process changes are made. We re-run the relevant test records and compare the results with the original findings. Re-test results are added to the report so the audit trail shows each issue from discovery to closure. Re-testing is an optional step and is quoted separately from the validation fee.

When Should You Validate Your Sanctions Screening System?

Sanctions screening validation is most valuable at moments when the screening system, its data or its settings have changed, or when there is a reason to doubt its results. Validate your screening system at these points:

  • Before go-live of a new screening tool
  • After major configuration changes or threshold tuning
  • After a vendor change, system upgrade or data migration
  • When alert volumes change suddenly without a clear reason
  • After a missed match or near-miss
  • Before a supervisory inspection
  • Periodically, as part of your independent audit cycle

Who Needs Sanctions Screening Validation?

If your business relies on screening software or a vendor database, validation can show how well the tool performs with your data, settings and workflows. We scope testing around your risks and the requirements of your supervisory authority. The service is most relevant to:

  • Financial institutions and exchange houses screening customers and payments
  • Virtual asset service providers (VASPs) screening customers, counterparties and wallets
  • Dealers in precious metals and stones using point-of-sale screening
  • Real estate brokers screening buyers, sellers and payers
  • Trust and company service providers screening complex ownership structures
  • Any business that relies on a screening system or a vendor database for sanctions and politically exposed person (PEP) screening

How Can You Test Your Own Sanctions Screening System?

You can test your own sanctions screening system with five quick checks before commissioning a full validation. The checks take little time and need no specialist tools. They will not measure detection rates, but they will show whether a full test is urgent:

  • Pick a recent designation and confirm the name appears in your system's list.
  • Screen a test record using a slight spelling variation of a listed name and see whether it alerts.
  • Check that beneficial owners in a few corporate files were actually screened.
  • Confirm the date of the last full re-screen of your customer base.
  • Review a few closed alerts and check that the reason for closure is recorded.

If any of these quick checks fails, a full sanctions screening validation is strongly recommended.

Why Sanctions Screening Validation Matters for goAML Reporting

Sanctions screening results drive goAML reporting, so a missed or mishandled match becomes a missed or late report. File a Confirmed Name Match Report (CNMR) within five business days of freezing assets or, where the transaction or service is rejected, within five business days of rejection. If a partial match involving an existing customer remains unresolved after reviewing their identification documents, suspend the transaction without delay and file a Partial Name Match Report (PNMR) within five business days of suspension. Keep the suspension in place pending EOCN instructions. For a prospective customer or counterparty, seek identification documents. If you cannot obtain them within 10 business days of identifying the partial match, reject the transaction or service and file a PNMR within five business days of rejection. Record any match you resolve as a false positive.

The EOCN guidance also covers relevant former business relationships, transactions and accounts in the five years before designation. This includes closed accounts and cases where you no longer hold any funds or other assets. The historical reporting procedure applies to CNMRs and PNMRs. We test whether your system and records can support that look-back.

Sanctions Screening Validation by Sector

Sanctions screening validation is tailored to each sector, because each one screens different parties at different points in the customer journey. The test areas below reflect where screening is most exposed in each sector:

Financial institutions and exchange houses

Sanctions screening validation for financial institutions and exchange houses typically covers payment screening, wire transfer data, real-time response times and high alert volumes. Payment messages can carry incomplete or free-text names, so data quality and matching logic are tested closely. Real-time screening must also respond fast enough that transactions are not released before an alert is reviewed.

Virtual asset service providers (VASPs)

Sanctions screening validation for VASPs typically covers customer, counterparty and wallet screening, including data quality in fast onboarding flows. Wallet screening depends on accurate blockchain analytics data as well as name matching. Fast digital onboarding can skip fields that the screening engine needs, so data capture is tested end to end.

Dealers in precious metals and stones

Sanctions screening validation for dealers in precious metals and stones typically covers point-of-sale screening speed, walk-in customer data and screening of suppliers and refiners. Walk-in sales leave little time to capture full customer details before the sale completes. Supplier and refiner screening is tested because sanctions exposure in this sector can sit in the supply chain.

Real estate brokers

Sanctions screening validation for real estate brokers typically covers screening of buyers, sellers, payers and corporate beneficial owners before transactions complete. Third-party payers and corporate buyers can be missed, because they may never be entered as customers. Timing is also tested, since screening must happen before the transaction completes, not after.

Trust and company service providers

Sanctions screening validation for trust and company service providers focuses on layered ownership and control. We test whether the system screens relevant parties, including beneficial owners, transaction parties and directors or agents acting on behalf of customers. We check whether the process can identify ownership or control by a designated person and whether material changes to a structure trigger fresh screening.

Common Sanctions Screening Failures Found in Testing

Sanctions screening validation can uncover the same types of weakness across different sectors and systems. The findings below are weaknesses identified in our own screening tests:

  • Lists updated days after publication rather than within hours
  • Beneficial owners excluded from batch screening
  • Date-of-birth filters set so tightly that true matches with missing data are suppressed
  • Arabic names not matched against transliterated list entries
  • Whitelists with no expiry or review
  • Alert decisions with no recorded reason or reviewer
  • No evidence of re-screening the customer base after list updates

Each of these screening weaknesses can be fixed once it is identified, and sanctions screening validation is how you find them.

What You Receive from Sanctions Screening Validation

Every sanctions screening validation engagement ends with documented evidence you can place in your audit file. The deliverables are:

  • A documented description of your screening setup
  • Tailored test packs and results
  • Detection and false-positive measurements
  • Findings rated by severity, with root causes
  • Recommended configuration, data and process changes
  • Re-test results after remediation, where re-testing is commissioned separately
  • A summary for senior management and your audit file

Replace assumptions with evidence.

Book sanctions screening validation today.

Contact Us Now

Engagement, Timeline and Fees for Sanctions Screening Validation

Sanctions screening validation is priced and planned around the scope of work agreed with you. The scope sets which systems, lists and parties are tested, and that in turn drives the fee and the timeline:

Sanctions screening validation fees

Sanctions screening validation fees range from AED 20,000 to AED 50,000, depending on the scope of work. The final fee is confirmed once the scope has been defined with your team. You know the full fee before any testing begins. Re-testing after fixes is not included in the validation fee and is quoted separately.

Sanctions screening validation timeline

The timeline for sanctions screening validation is mutually agreed for each defined scope. There is no fixed turnaround, because each engagement covers a different combination of systems, lists and parties screened. The agreed timeline is set alongside the scope before testing begins.

Our Sanctions Screening Validation Track Record

goAML Registration has delivered sanctions screening validation projects for UAE businesses across several sectors. Our track record includes:

12+

sanctions screening validation projects completed

3+

sectors served

32%+

average reduction in false positives across projects

Each sanctions screening validation engagement uses test packs built for the client's own customer base, lists and systems, not reused templates.

Why Choose goAML Registration for Sanctions Screening Validation

Sanctions compliance, CNMR reporting and PNMR reporting are core parts of goAML Registration's work, so we understand exactly what is at stake when screening fails. Our sanctions screening validation is independent of screening vendors, uses structured test packs with known answers and produces evidence you can place in your audit file and show your supervisor. We test the system and the people who clear its alerts together, so findings cover configuration, data and decision-making in one report.

How to Get Started with Sanctions Screening Validation

Getting started with sanctions screening validation takes a short conversation about your screening setup. The engagement then follows five steps:

  1. Contact our team through the contact page to discuss your screening system and your concerns.
  2. We hold a scoping discussion covering your systems, lists, data feeds and the parties you screen.
  3. You receive a quote within the AED 20,000 to AED 50,000 range, with the agreed scope and timeline.
  4. We design and run the test packs and sample real alerts, with your team's support.
  5. You receive the validation report with findings and recommendations, and re-testing after fixes can be quoted separately.

FAQs About Sanctions Screening Validation and AML Screening Testing

How much does sanctions screening validation cost?

Sanctions screening validation costs AED 20,000 to AED 50,000, depending on the scope of work. The fee is confirmed once the systems, lists and parties to be tested have been agreed. You know the full fee before testing begins.

How long does sanctions screening validation take?

The timeline is mutually agreed for each defined scope. There is no fixed turnaround, because each engagement tests a different combination of systems, lists and parties. The agreed timeline is set before testing begins.

What is included in sanctions screening validation?

Sanctions screening validation includes scoping, tailored test packs, test execution, alert and file sampling, analysis and a written report. Re-testing after fixes is not included and is quoted separately. The report covers detection and false-positive measurements, findings rated by severity and recommended changes. A summary for senior management and your audit file is also included.

Is sanctions screening validation required by UAE law?

Not as a named requirement. UAE rules require effective sanctions screening, ongoing assessment of controls and an independent audit function. A software validation engagement can help demonstrate that your screening works with your data, settings and workflows. The testing scope and frequency should reflect your risks and any specific requirements or guidance from your supervisor.

Isn't the screening software vendor responsible for the system working?

No. The vendor supplies the screening tool, but your business remains responsible for sanctions compliance. Sanctions screening validation confirms the tool works with your own data, settings and lists.

Will sanctions screening testing disrupt our operations?

Rarely. Sanctions screening tests are planned with your team and can usually be run in a test environment or in controlled batches. Live screening continues as normal while testing takes place.

Do you use real customer data for sanctions screening testing?

Not by default. We prefer synthetic test records and public list entries to protect personal data. Where real data is needed, it is handled under agreed data protection controls.

How often should sanctions screening be validated?

Sanctions screening should be validated after any significant change and periodically as part of your independent audit cycle. Significant changes include a new system, a vendor change, threshold tuning or a data migration. The right periodic frequency depends on your risk profile and how often your system changes.

Can sanctions screening validation help reduce false positives?

Yes. goAML Registration's sanctions screening validation projects have achieved an average reduction of 32%+ in false positives. Our recommendations aim to reduce unnecessary alerts without lowering detection of genuine matches. Because every change is measured against the test pack, you can see the effect on detection before you adopt it.

Does sanctions screening validation include PEP and adverse media screening?

Yes. While sanctions screening is the priority because of freezing obligations, we can also test PEP and adverse media screening coverage and matching. The same known-positive approach applies, using publicly available PEP and media information.

Can you test sanctions screening built into a third-party platform?

Yes. We test screening whether it runs in a standalone tool, a core system, an onboarding platform or a vendor-hosted service. Where the vendor controls the settings, we work with your team to obtain the configuration details the test needs.

What evidence do we receive from sanctions screening validation?

You receive a written sanctions screening validation report with test packs, results, detection and false-positive measurements, findings and recommendations. The report is suitable for your audit file and supervisory review. If you commission re-testing separately, re-test results are added once fixes are made.