Table of Contents
Sanctions screening for correspondent banking is how a bank checks the payments and partners that flow through its accounts against government watchlists. A correspondent bank moves money for other banks, often across borders. That means it can process a payment for a customer it has never met, at a bank it does not fully control.
This makes screening harder than in normal retail banking. You see fragments of each transaction. You depend on the respondent bank to do its own checks. When screening fails, the money can reach a sanctioned party, and the correspondent bank pays the fine. This guide covers the risk, the controls, the message fields, and the mistakes that cause enforcement cases.
What correspondent banking is, in plain terms
A correspondent bank holds accounts for other banks. The bank that provides the account is the correspondent. The bank that uses it is the respondent. A small bank in one country may not have a branch in the United States. So it opens an account with a US bank to send and receive dollar payments. The US bank is the correspondent.
The problem is distance. The correspondent bank often does not know the respondent’s underlying customer. It may not know the true purpose of the payment. It relies on the respondent to screen first. Sanctions rules do not accept that as an excuse. If a blocked party is in the payment chain, the correspondent must catch it.
Why correspondent banking carries higher sanctions risk
Several features of this business raise the risk level. You should know each one before you set thresholds or write procedures.
- Limited visibility. You screen the data in the message. You often cannot see the respondent’s customer files.
- Cross-border flows. Payments touch multiple countries and multiple sanctions regimes at once.
- Nested relationships. The respondent may quietly let other banks use its account with you. You never onboarded those banks.
- Speed and volume. Large correspondents screen millions of messages a day. Every alert competes with a settlement deadline.
- Data gaps. Incoming messages arrive with missing or messy party names.
Nested banking is the risk many teams underestimate. A respondent in a low-risk country may process payments for a bank in a sanctioned jurisdiction. From your side it all looks like one relationship. This is why due diligence and screening have to work together. For the account-opening side, see our guide to sanctions screening in customer onboarding.
The lists you screen against
A dollar-clearing bank screens mainly against US lists. A bank with global reach screens against several regimes. Match your list coverage to where your payments go and which currencies you clear.
| List | Issued by | Why it matters |
|---|---|---|
| OFAC SDN List | US Treasury (OFAC) | Blocked persons and entities. Core list for dollar payments. |
| OFAC sectoral and non-SDN lists | US Treasury (OFAC) | Partial restrictions that still limit certain dealings. |
| EU Consolidated List | European Union | Needed for euro clearing and EU-linked payments. |
| UK OFSI List | UK Treasury (OFSI) | Applies to sterling and UK-touching activity. |
| UN Consolidated List | UN Security Council | Baseline targets adopted by most member states. |
Start with the primary source. OFAC publishes and updates the SDN list at the OFAC website. Do not rely on a vendor feed alone without knowing when it refreshes. Names get added between your daily loads. For a closer look at the SDN list itself, read our page on denied party screening and the OFAC SDN list.
The 50 percent rule and hidden ownership
A name match is not the only way a party is blocked. OFAC’s 50 percent rule says an entity is blocked if one or more blocked persons own it 50 percent or more, directly or together. That company may not appear on any list by name. You still cannot process its payment.
This matters in correspondent banking because ownership hides behind layers of companies. A respondent’s customer can be owned by a sanctioned oligarch through three shell firms. Name screening alone will miss it. You need beneficial ownership data and a way to flag entities linked to blocked owners. Our explainer on the 50 percent rule in sanctions screening walks through the math.
Which message fields you screen
Payment screening reads the parties inside each message and compares them to your lists. In a wire, that means more than the sender and receiver.
- Originator. The person or firm sending the money.
- Beneficiary. The person or firm receiving it.
- Ordering and beneficiary institutions. The banks at each end.
- Intermediary banks. Any bank in the middle of the chain.
- Payment reference and remarks. Free-text fields that can name a country, port, or vessel.
Cover payments and the MT202COV
Cover payments are a known blind spot. In a cover arrangement, one message moves the funds between banks and a separate message carries the customer details. Older bank-to-bank formats hid the true originator and beneficiary. The MT202COV message was created so the underlying customer data travels with the cover payment. Screen the COV fields, not just the bank names. If your system only reads the interbank leg, you can clear a payment for a blocked party without seeing it.
Wire stripping is a red flag
Wire stripping is when a bank removes or alters names, countries, or references so a payment slips past screening. It is deliberate evasion, and past enforcement cases have centered on it. If you see edited fields, missing originator data, or a respondent that keeps sending vague references, treat it as a warning sign. See more patterns in our list of red flags of sanctions evasion.
Due diligence on the respondent bank
Screening is only half the job. You also have to know the bank you serve. Correspondent due diligence uses the Wolfsberg Correspondent Banking Due Diligence Questionnaire as a common standard. It asks about ownership, licensing, the respondent’s own sanctions program, and whether it allows nested access.
- Identify ownership and control. Know who owns the respondent and where it is licensed.
- Assess its sanctions program. Confirm it screens its own customers and updates its lists.
- Ask about nesting. Find out if downstream banks use the account.
- Apply enhanced due diligence for banks in high-risk countries or with weak controls.
- Refresh the review on a schedule and after any trigger event.
Set the review cycle by risk. High-risk respondents get reviewed more often. For a general rhythm, see our note on how often to screen.
Handling alerts and false positives
Correspondent screening produces a flood of alerts. Common names, transliterated names, and city names all trigger hits. Most are false positives. The goal is to clear the real matches fast without missing the true one hidden in the pile.
- Freeze the payment when a strong match appears. Do not let it settle during review.
- Compare full identifiers. Check date of birth, address, and country, not just the name.
- Escalate real or unclear matches to a senior analyst or legal.
- Document the decision with the data you relied on.
- Report and block when a true match is confirmed, following your regime’s rules.
Tune thresholds with care. Loosen them and you miss matches. Tighten them and analysts drown. A good false positive process protects both. Read how to resolve a false positive for the step-by-step. Deciding how much to automate is its own question, covered in automated vs manual screening.
Records, audit trail, and penalties
Regulators expect proof, not promises. Keep a record of every alert, decision, and reviewer. Keep the list version you screened against. If you clear a payment, you should be able to show why. A clean audit trail is what turns a good decision into a defensible one. Our guide to what an audit trail is explains the basics.
The stakes are high. OFAC sanctions are strict liability, so a violation can stand even without intent. Banks have paid large settlements for stripping and screening failures in correspondent channels. Our page on OFAC penalties covers how the fines are calculated. This whole discipline sits inside broader denied party screening, which every regulated firm should understand.
A practical control checklist
| Control | What good looks like |
|---|---|
| List coverage | All relevant regimes loaded and refreshed daily or faster. |
| Field scope | Originator, beneficiary, all banks, and free-text screened. |
| Cover payments | MT202COV underlying parties read, not just the interbank leg. |
| Ownership | 50 percent rule applied with beneficial ownership data. |
| Respondent DD | Wolfsberg questionnaire completed and risk-rated. |
| Alert handling | Real-time freeze, tuned thresholds, documented clears. |
| Records | Full audit trail with list versions retained. |
Frequently Asked Questions
Who is responsible when a sanctioned payment gets through?
The correspondent bank that processed the payment carries the liability, even if the respondent should have caught it first. You cannot outsource the duty to screen. This is why you screen every message yourself rather than trusting the respondent’s word.
What is nested correspondent banking?
Nesting is when a respondent lets other banks use its correspondent account without your knowledge. Those downstream banks were never onboarded by you. They can bring hidden sanctions exposure into your account, so you ask respondents directly whether they permit it.
Do I screen the banks or the underlying customers?
Both. Screen the ordering and beneficiary institutions and the intermediary banks. Also screen the originator and beneficiary customers named in the message. In cover payments, that customer data sits in the MT202COV fields, so read those too.
How often should sanctions lists be updated?
As close to real time as you can manage. OFAC and other bodies add names without notice. Many banks load updates daily, and some run intraday refreshes for high-volume clearing. Screen against the current list, not last week’s copy.
Key Takeaways
Sanctions screening for correspondent banking is hard because you act on partial information at high speed. The correspondent bank still owns the risk. Cover the right lists, read every party field including MT202COV data, apply the 50 percent rule, and know your respondent through solid due diligence. Freeze strong matches, document your clears, and keep a full audit trail. Do those things and you catch the blocked party before the money moves. If you want help building or reviewing a screening program, contact our team.