09 Nov 2026 By CISO Consulting team 39 views 4 min read

Wolfsberg Questionnaire: Sanctions Screening Gaps

Correspondent banks now challenge vague answers on screening technology, false positives and escalation. This article explains which three Wolfsberg sections expose architecture gaps and which four evidence artifacts answer them.

A compliance officer reviewing screening match-disposition reports on a monitor in a modern Riyadh office.
In this article
  1. Why these sections expose architecture, not policy
  2. Section 5.2: screening technology
  3. Section 5.4: false-positive rates
  4. Section 5.6: escalation thresholds
  5. The four evidence artifacts
  6. 1. Anonymized screening-rule logic
  7. 2. Monthly match-disposition statistics
  8. 3. Escalation decision trees
  9. 4. Sample investigation logs
  10. Signs it is time to review your program
  11. What a good outcome looks like
  12. How we run it
  13. Next step

A Wolfsberg correspondent banking questionnaire sanctions screening section is often the point where a routine renewal becomes a long exchange of follow-up questions. Correspondent banks have learned that a well-written policy says little about how screening actually works. They now press on the technology, the results and the escalation path. For Saudi banks, this guide explains which sections do that and what evidence answers them.

The section numbers below follow the questionnaire layout referenced in this brief. Confirm them against the version your correspondent sends, since the Wolfsberg Group updates the document and numbering can change.

Why these sections expose architecture, not policy

A policy gap is fixed by rewriting a document. An architecture gap is different: the screening design does not cover what the policy says it covers. Three areas reveal this most clearly because they cannot be answered truthfully with a general statement.

Section 5.2: screening technology

This section asks what you screen, against which lists, and with what tooling. Vague answers such as "we use an industry-leading solution" invite follow-up. The real gaps tend to sit in coverage:

  • Payment message fields that are not screened, such as free-text fields or intermediary and beneficiary bank details.
  • Customer data and payment data screened against different list versions.
  • Lists applied unevenly across products, for example trade finance handled outside the main engine.
  • No documented logic for fuzzy matching, transliteration of Arabic names, or list-update timing.

Section 5.4: false-positive rates

Questions about alert volumes and match outcomes test whether you tune and measure your screening. A bank that cannot show match-disposition data usually has no systematic feedback loop between investigators and rule design. Two opposite weaknesses appear here: thresholds so loose that analysts clear alerts in bulk, or thresholds so tight that true matches may be missed and nobody can show otherwise.

Section 5.6: escalation thresholds

This section asks who decides when a potential match is real, at what level, and how fast. Architecture gaps show up as unclear authority, no defined path from front-line analyst to sanctions officer, and no link between a confirmed match and regulator reporting. A policy sentence stating that matches are "escalated appropriately" does not answer it.

The four evidence artifacts

Correspondent banks generally want proof of design and operation, not vendor identity. These four formats provide that. Each can be prepared without naming a product or supplier.

1. Anonymized screening-rule logic

Document the logic, not the brand. Describe which data elements are screened, the matching approach, the threshold bands and the treatment of name variants. Replace tool names with functional descriptions such as "name-screening engine" and "payment-message filter". Show list sources and update frequency. This is the core answer to Section 5.2.

2. Monthly match-disposition statistics

Present, per month, the number of alerts generated, the number closed as false positives, the number escalated and the number confirmed. Keep the data internal in format and share only what your sharing policy allows. Add a short note on any threshold change made that month and why. Stable, explained figures answer Section 5.4 better than any target rate.

3. Escalation decision trees

Provide a one-page diagram showing the path from alert to disposition: first-level review, second-level review, sanctions officer decision, senior approval, account action and regulatory reporting. State the role at each step and the expected time frame. This answers Section 5.6 directly.

4. Sample investigation logs

Provide redacted examples of closed alerts: the alert trigger, the evidence reviewed, the reasoning, the decision and the approver. Include at least one false positive and one escalated case. Remove names, account numbers and counterparties. These logs show that the decision tree is followed in practice.

Signs it is time to review your program

You likely need more than a better questionnaire response if any of these apply:

  • Answers to the questionnaire differ between teams, or each renewal needs a fresh drafting effort.
  • Nobody can state with confidence which message fields and products are inside screening scope.
  • Match-disposition data is not produced routinely.
  • Escalation authority is documented in policy but not tested.
  • A correspondent has issued repeated follow-up questions on screening.

What a good outcome looks like

A good outcome is a screening program whose answers can be demonstrated. Coverage is mapped across customers, payments, trade finance and correspondent activity. The four artifacts exist as maintained documents rather than one-off responses. Escalation is understood by front-line staff and decision-makers. The questionnaire becomes a summary of evidence you already hold.

How we run it

Our Sanctions Compliance Program covers the design or review of a sanctions program across UN, local, OFAC and EU regimes, including screening, trade and payment controls, escalation and reporting. It is delivered as a project of 6–12 weeks in four stages:

  1. Assess: sanctions risk across products and geographies.
  2. Design: policy, screening coverage and escalation.
  3. Test: screening quality and control testing.
  4. Train: front-line and decision-maker training.

The deliverables are sanctions policy and procedures, a screening coverage assessment, control testing results and training for front-line staff. The work includes trade-finance and correspondent banking controls, and it is framed by SAMA AML/CTF requirements and the Wolfsberg standards.

Where you need independent proof that name-screening tools and thresholds perform as intended, our AML Monitoring and Screening Model Validation service examines data quality, thresholds, fuzzy-matching performance and coverage against your risk assessment. For a wider view of your AML/CTF program against the SAMA rules and the FATF Recommendations, the AML Assessment provides an independent review.

Next step

If your next correspondent renewal is approaching, or recent questions on Sections 5.2, 5.4 or 5.6 exposed uncertainty, begin with a scoping conversation about our Sanctions Compliance Program. We will help you establish what your screening architecture covers and build the evidence your correspondents expect.

Tags: Wolfsberg Sanctions screening Correspondent banking SAMA Sanctions compliance Due diligence
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment