Updating Sanctions Screening for Cuba Designations: 30-Day Playbook

The Problem / Why This Matters Now

On July 23, 2026, OFAC designated 11 new Cuba-related entities and individuals under Executive Order 14404, focusing on energy sector operations, sanctions evasion networks, and Cuba's labor-export program. Alongside, OFAC issued three time-sensitive general licenses authorizing specific wind-down and divestment activities until August 22, 2026.

You have 30 days to implement screening controls that catch these designations while allowing compliant transactions under the new general licenses. Missing a blocked party in a wire transfer could lead to voluntary self-disclosure and potential enforcement action. Rejecting a legitimate transaction under Cuba General License 3 creates unnecessary business friction.

This is a real challenge. The designations include CEIBA Investments Limited, a Guernsey-based real estate firm, and entities with 50 percent or greater CEIBA ownership. Your screening logic must differentiate between prohibited transactions and those authorized under the temporary licenses.

What You Need Before Starting

Access and permissions:

• Write access to your sanctions screening platform's configuration module
• Authority to update screening rules and match thresholds
• Ability to create temporary authorization flags in your transaction monitoring system

Data sources:

• OFAC's Specially Designated Nationals and Blocked Persons List (SDN List) updated July 23, 2026, or later
• Full text of Cuba General Licenses 2, 3, and 4 from OFAC's website
• Your institution's current Cuba sanctions policy document

Technical requirements:

• Screening system capable of fuzzy matching on entity names and addresses
• Transaction monitoring platform that supports date-range filters
• Case management system for documenting general license determinations

Team coordination:

• Sanctions analyst availability to review initial match results
• Operations team lead to brief customer service on the general licenses
• Legal or compliance officer authorized to make general license applicability calls

Step-by-Step Implementation

Day 1-2: Update screening lists and test match logic

Download the updated SDN List from OFAC's website. Import it into your screening platform according to your vendor's process. If using a commercial service, confirm the vendor has ingested the July 23, 2026 updates.

Run a historical screen against your active customer base and pending transactions from the past 90 days. Look for any existing relationships or queued payments that now hit on CEIBA Investments Limited or the other newly designated entities.

Test these match scenarios in your sandbox environment:

• Direct name match on "CEIBA Investments Limited"
• Fuzzy match on common misspellings (CIEBA, CEBIA)
• Address match on Guernsey-based entities
• Ownership screening: entities where CEIBA holds 50 percent or greater interest

Adjust your fuzzy matching threshold if you're getting too many false positives, but don't drop below 85 percent similarity for Cuban entity names.

Day 3-5: Create general license workflow rules

Configure your transaction monitoring system to flag Cuba-related transactions that may qualify for general license treatment. Set up three distinct queues:

Cuba GL2 Queue: Transactions involving CEIBA or majority-owned entities, dated between July 23 and August 22, 2026, that appear to be wind-down activities. Wind-down means closing accounts, terminating contracts, or completing obligations from pre-existing agreements.

Cuba GL3 Queue: Transactions involving divestment or transfer of CEIBA debt or equity to non-US persons, trades placed before 4:00 p.m. EDT on July 23, 2026, or derivative contract wind-downs entered before that timestamp.

Cuba GL4 Queue: Payments to or from third-country diplomatic or consular missions in Cuba for official business.

Document the specific data fields your system will check: transaction date, counterparty type, transaction description keywords (divestment, transfer, wind-down, derivative, diplomatic mission), and US person involvement.

Day 6-10: Build escalation and documentation procedures

Draft a decision tree for your sanctions analysts. When a transaction hits on a newly designated Cuba entity, the analyst must determine:

1. Does the transaction involve CEIBA or a CEIBA majority-owned entity?
2. Is the transaction date between July 23 and August 22, 2026?
3. Does the transaction description match general license criteria?
4. If GL3: Is the transferee a non-US person?
5. If GL3: Was the trade placed or derivative entered before 4:00 p.m. EDT on July 23, 2026?

If yes to questions 1-3 and the relevant sub-questions, the transaction may proceed under general license authority. If no, the transaction must be blocked and assets frozen.

Create a case documentation template that captures:

• Which general license applies
• Specific authorization language from the general license
• Evidence supporting general license applicability (trade timestamp, non-US person status, wind-down justification)
• Analyst name and approval timestamp

Any payments to blocked persons made under general license authority must be deposited into a blocked, interest-bearing account. Configure your payment system to route these to a designated blocked account rather than the intended recipient's account.

Day 11-15: Train your team and test end-to-end

Schedule a 90-minute training session for sanctions analysts, operations staff, and customer service. Walk through:

• The 11 new designations and why they matter
• The three general licenses and their expiration date
• The decision tree and documentation requirements
• Examples of compliant vs. prohibited transactions

Run end-to-end tests with mock transactions:

• A wire transfer from a US bank to CEIBA for a pre-existing real estate contract, dated July 30, 2026 (should route to GL2 queue)
• A securities trade involving CEIBA equity placed on July 22, 2026, settling July 25, 2026 (should route to GL3 queue)
• A payment from a German embassy in Havana for consular services (should route to GL4 queue)
• A new loan application from an entity 60 percent owned by CEIBA (should be blocked, no general license applies)

Confirm each transaction hits the correct queue and your analysts can access the decision tree and documentation template.

Day 16-30: Monitor, refine, and prepare for expiration

Review all general license determinations daily for the first week, then weekly. Track:

• Number of transactions routed to each general license queue
• False positive rate (transactions flagged but not actually eligible)
• Average decision time per case
• Any rejected transactions that should have qualified

Adjust your screening rules if you're seeing patterns in false positives. For example, if legitimate transactions with Cuban diplomatic missions are getting blocked because your system isn't correctly identifying GL4 eligibility, refine your counterparty type logic.

Set calendar reminders for August 15, 2026 (one week before general license expiration) and August 22, 2026 (expiration date). On August 15, notify your operations team that no new wind-down or divestment transactions will be authorized after August 22. On August 23, disable the general license queues and revert to standard Cuba sanctions blocking procedures.

Validation: How to Verify It Works

Run these validation checks weekly:

Screening accuracy test: Pull a random sample of 50 transactions from the past week that passed through Cuba-related screening. Manually verify that none involve the 11 newly designated entities. If you find a miss, investigate whether it's a screening configuration error or a data quality issue (misspelled entity name, missing address field).

General license compliance test: Review all transactions approved under general license authority. Confirm each has complete documentation per your template and meets the specific criteria in the applicable general license. If you find a transaction approved without sufficient evidence, escalate to your MLRO immediately.

Blocked account verification: Check that any payments to blocked persons under general license authority are in blocked, interest-bearing accounts, not regular operating accounts.

Team competency check: Give your analysts a quiz with five transaction scenarios and ask them to identify which general license applies or whether the transaction should be blocked. Aim for 100 percent accuracy.

Maintenance / Ongoing Tasks

Weekly through August 22:

• Review general license queue volumes and decision times
• Update your Cuba sanctions policy document with lessons learned
• Monitor OFAC's website for any amendments to the general licenses or additional Cuba designations

August 22, 2026:

• Disable general license queues at 11:59 p.m. EDT
• Send notification to operations and customer service that wind-down period has ended
• Block any pending transactions that were authorized under the now-expired general licenses

Post-August 22:

• Maintain standard Cuba sanctions screening without general license exceptions
• Archive all general license documentation for the required recordkeeping period (five years under 31 CFR 501.604)
• Conduct a post-implementation review: what worked, what didn't, and what you'll do differently for the next Cuba sanctions expansion

Ongoing:

• Subscribe to OFAC's email updates for Cuba-related sanctions changes
• Review your screening system's performance monthly: false positive rate, average match review time, and any missed designations
• Update your sanctions screening procedures document to reflect lessons learned from this implementation

If OFAC issues additional Cuba designations or extends the general licenses beyond August 22, you'll repeat this playbook with the new parameters. The infrastructure you've built, the queues, decision trees, and documentation templates, can be adapted quickly for future Cuba sanctions actions.