Your sanctions screening flags nothing. Your supplier is clean. Your beneficiary bank passes every check. Then your payment stops processing because a correspondent bank three hops away just lost its dollar-clearing privileges.
The Office of Foreign Assets Control (OFAC) warned on October 5 that foreign financial institutions transacting with sanctioned entities can be targeted "at any time without advance notification." Recent actions against Banque Misr UAE, Golden Global Bank, and Russia's VTB Bank highlight this risk. When Treasury restricts correspondent access, it doesn't just freeze assets; it makes payment routes commercially unusable.
This isn't just about risk management. It's a structural shift in how sanctions enforcement affects liquidity. You need visibility into the entire payment route, not just the recipient.
Essential Preparations
Before mapping intermediary risk, gather these components:
Access to payment messaging infrastructure. You need visibility into the full payment instruction, not just your internal treasury record. This means access to SWIFT messages, correspondent bank identifiers (BICs), and routing details for cross-border transactions.
Real-time watchlist screening capability. Static monthly checks won't catch a correspondent bank that loses access mid-month. Your screening system must run against current OFAC lists, Specially Designated Nationals (SDN) lists, and correspondent banking restrictions.
ISO 20022 message parsing. If your payment infrastructure has migrated to ISO 20022, you have access to richer structured data about intermediary institutions. If you're still on legacy formats, you'll need translation layers to extract correspondent details from unstructured fields.
Treasury management system integration. Your mapping effort needs to feed into liquidity planning. This isn't a compliance-only project. Finance needs to know which cash positions depend on at-risk corridors.
A baseline inventory of your payment corridors. Document which currency pairs you use, which beneficiary countries you pay into, and which originating banks you use. Start with your top 20 payment routes by volume and value.
Step-by-Step Implementation
Step 1: Extract correspondent bank data from payment messages.
Pull the last 90 days of cross-border payment instructions. For SWIFT MT103 messages, examine Field 56 (Intermediary Institution) and Field 57 (Account With Institution). For ISO 20022 pain.001 messages, parse the <IntrmyAgt1> and <IntrmyAgt2> elements.
Build a table with these columns: originating bank, beneficiary bank, intermediary bank 1, intermediary bank 2, currency, destination country, payment volume, payment value.
You're looking for patterns. Which correspondent banks appear most frequently? Which routes depend on a single intermediary? Which currencies route through institutions you didn't select?
Step 2: Map correspondent relationships your treasury didn't choose.
Your company picks the beneficiary bank. You don't pick the correspondent banks that your originating bank uses to settle that payment. Request correspondent banking relationship documentation from your primary banking partners. Ask specifically:
- Which correspondent banks do you use for USD clearing?
- Which institutions handle EUR, GBP, and other major currencies?
- Do you maintain backup correspondents for critical corridors?
- How quickly can you reroute if a correspondent loses access?
Document the answers. If your bank can't provide this information, that's a red flag about their operational resilience.
Step 3: Implement real-time screening of intermediary institutions.
Configure your transaction monitoring system to screen every BIC that appears in Fields 56 and 57, not just the beneficiary. Use OFAC's SDN list, the Consolidated Sanctions List, and any correspondent banking restrictions published by Treasury.
Set alerts for:
- Any intermediary appearing on a watchlist
- Any intermediary headquartered in a high-risk jurisdiction
- Any intermediary that appears in your payment flow but wasn't in your baseline inventory
Run this screening before payment release, not after settlement. A payment that's already in flight is harder to recall than one held for 15 minutes of additional review.
Step 4: Build alternative corridors for high-risk routes.
Identify payment routes that depend on a single correspondent or that route through jurisdictions with elevated sanctions risk. For each critical route, establish a backup:
- Open accounts at a second originating bank with different correspondent relationships
- Negotiate direct beneficiary bank relationships in markets where you have high payment volume
- Evaluate whether regional payment systems (SEPA, SWIFT gpi, local real-time payment rails) reduce correspondent dependency
Test these alternatives quarterly. A backup corridor you've never used isn't a backup.
Step 5: Integrate correspondent risk into liquidity forecasting.
Add a field to your cash position reporting: "Corridor Status." Mark each position as "Primary route available," "Backup route required," or "Route at risk."
When you report $50 million available in a particular subsidiary, note whether you can actually move that cash. Liquidity you can't deploy isn't liquidity.
Validation: How to Verify It Works
Run a test payment through each of your top 20 corridors. Before releasing the payment, your system should:
- Display all intermediary banks involved in the route
- Confirm that each intermediary passed real-time watchlist screening
- Show the date of the last successful payment through this route
- Flag if the corridor has changed since your last transaction
Conduct a tabletop exercise: OFAC announces restrictions on a major correspondent bank. Can your treasury team identify which payment routes are affected within 30 minutes? Can you reroute critical supplier payments within four hours?
If the answer is no, your mapping isn't operationalized yet.
Maintenance and Ongoing Tasks
Monthly: Re-screen all correspondent banks in your baseline inventory against updated watchlists. Correspondent banking restrictions can appear without advance notice.
Quarterly: Review payment message logs for new intermediary banks that weren't in your baseline. Investigate why the route changed. Was it a deliberate bank decision or a temporary reroute?
When OFAC issues new sanctions: Don't just screen your counterparties. Screen every correspondent bank in your active payment corridors. Check whether any institutions in your payment chain are headquartered in newly sanctioned jurisdictions or have relationships with newly designated entities.
After any payment failure: Document which correspondent was involved. Payment failures aren't always sanctions-related, but a pattern of failures through a specific intermediary is an early warning signal.
The practical distinction between "this payment is illegal" and "our banks won't process it" becomes very small when a critical supplier payment is due. Mapping your payment chain isn't about perfect visibility into every institution. It's about knowing which routes matter, which intermediaries sit in those routes, and how quickly you can reroute when a correspondent becomes commercially toxic.
