OFAC's General License No. 2, issued on July 10, 2026, under the Democratic Republic of the Congo Sanctions Regulations, presents a unique challenge for sanctions analysts. It allows specific agricultural and medical transactions with the DRC and Rwanda, even if they involve SDNs designated under the DRCSR. This isn't just a policy update; it's a workflow challenge that demands new screening logic, enhanced documentation, and a clear escalation path for borderline cases.
The Problem: Navigating Humanitarian Exceptions with SDN Involvement
GL 2 authorizes transactions "ordinarily incident and necessary" for exporting agricultural commodities, medicine, and medical devices to the DRC or Rwanda. It also covers medical care delivery, clinical trials, and medical research in these countries. Unlike the personal-use carve-out in section 547.513 of the DRCSR, GL 2 has no quantity limits or expiration date.
The challenge lies in transactions involving SDNs designated under the DRCSR, but only if they aren't designated under any other sanctions program. For example, the Rwanda Defense Force was designated as an SDN on March 2, 2026, for supporting the M23 armed group. If your screening system flags any of these parties in a transaction that fits GL 2's scope, you can't just clear the alert. You need a documented compliance assessment.
Preparing for Implementation
Before implementing GL 2 in your workflows, ensure you have:
- Current DRCSR SDN list. Cross-reference this list with your sanctions screening database to ensure all DRCSR SDNs are correctly tagged.
- Transaction type taxonomy. Define which transactions qualify as "agricultural commodities," "medicine," "medical devices," or "ordinarily incident" to medical care. Include payment descriptions, product codes, and beneficiary industry classifications.
- Dual-designation check capability. Your screening platform must identify if a flagged SDN appears on multiple sanctions lists. If the Rwanda Defense Force is also on a UN or EU sanctions list, GL 2 doesn't apply.
- Export control coordination. GL 2 doesn't authorize exports controlled under the Export Administration Regulations. Coordinate with your export compliance team or the Bureau of Industry and Security.
Step-by-Step Implementation
Step 1: Update Screening Rules
Don't configure GL 2 as an auto-pass. Instead, create a screening rule that:
- Identifies transactions involving DRCSR SDNs
- Flags them for manual review with a "GL 2 Eligibility Assessment Required" tag
- Routes them to a designated analyst queue
Example rule:
IF (SDN_Program = "DRCSR")
AND (Transaction_Destination = "DRC" OR "Rwanda" OR Beneficiary_Country = "DRC" OR "Rwanda")
THEN Flag_For_Review = TRUE, Review_Type = "GL2_Assessment"
Step 2: Build a GL 2 Assessment Checklist
For each flagged transaction, document:
- Transaction purpose. Does the payment description or documentation reference agricultural commodities, medicine, medical devices, medical care, clinical trials, or medical research?
- SDN involvement scope. Determine the SDN's role: direct beneficiary, intermediary bank, supplier, or related party.
- Dual-designation check. Verify if the flagged SDN appears under any other OFAC program.
- Export control applicability. Check if the transaction requires a BIS export license.
- Risk indicators. Identify any red flags that warrant escalation or a Suspicious Activity Report.
Step 3: Document Your Determination
Use a standardized memo template to capture:
- Transaction ID and date
- Parties involved
- GL 2 eligibility rationale
- Dual-designation check result
- Export control coordination
- Final decision: Approved, Rejected, or Escalated
Store this memo in your transaction monitoring system for audit purposes.
Step 4: Configure Exception Reporting
Set up a monthly report showing:
- Total GL 2 assessments
- Approval vs. rejection ratio
- Most common SDNs encountered
- Average assessment time
- Escalations to legal or senior management
This report demonstrates active management of GL 2 risk and helps identify patterns for policy adjustments.
Validation: Testing Your Implementation
Test with these scenarios:
- Scenario 1: A medical device supplier in Germany sends a payment to a Rwandan hospital. The hospital's parent entity is the Rwanda Defense Force. Flag for GL 2 assessment.
- Scenario 2: A pharmaceutical company conducts a clinical trial in the DRC involving a logistics provider designated under the DRCSR and narcotics trafficking sanctions. Reject due to dual designation.
- Scenario 3: A US agricultural exporter ships grain to a DRC distributor whose beneficial owner is designated under the DRCSR. Flag for assessment and require documentation.
Run these scenarios in your test environment to confirm correct alert routing and checklist completion.
Maintenance and Ongoing Tasks
GL 2 has no expiration date, but your implementation requires regular updates:
- Weekly: Review OFAC's SDN list updates. Update systems and train analysts on new designations.
- Monthly: Audit GL 2 assessments for consistency and defensibility.
- Quarterly: Review transaction type taxonomy for new descriptions or codes.
- Annually: Reassess dual-designation check logic to ensure accuracy.
Stay informed of changes by subscribing to OFAC's email alerts and monitoring the DRCSR regulations page directly.
GL 2 is a compliance tool, not a blanket authorization. Ensure every transaction approved under it can withstand an OFAC audit.
