When the Office of Foreign Assets Control (OFAC) issues a general license, many assume it's a green light to ease restrictions and move on. For a lean fintech compliance team, this seems appealing. However, this approach is incomplete and potentially dangerous.
Misinterpretation of General Licenses
When OFAC issued GL 135 on October 9, 2026, and GL 13S the day before, many compliance teams adopted a simplified view. GL 135 authorizes transactions related to Russian-origin diesel fuel until April 7, 2027. GL 13S allows US persons to pay taxes and obtain permits in Russia until January 9, 2027. The shorthand: these activities are now permitted, so reduce alerts and expedite processes. This is misleading.
Why General Licenses Don't Reduce Risk
A general license doesn't lower risk; it shifts the focus to compliance with specific conditions. The question becomes, "Does this transaction meet the authorization criteria?" This is harder to automate and easier to misjudge.
Narrow Authorizations: GL 13S only covers transactions "ordinarily incident and necessary" to US operations in Russia. This requires judgment, not just data. Payments must be scrutinized to ensure they align with day-to-day operations.
Carve-Outs and Violations: Neither license allows debits to accounts of the Central Bank of the Russian Federation, the National Wealth Fund, or the Ministry of Finance. If your platform interacts with these entities, you must ensure compliance.
Blocked Persons Exclusion: GL 13S doesn't authorize transactions involving blocked persons under the Russian Harmful Foreign Activities Sanctions Regulations unless separately authorized. Even if a transaction seems compliant, involvement of a blocked party can invalidate it.
Evidence of Complexity
Consider the structure of these licenses. GL 135 allows transactions otherwise prohibited by 31 CFR part 587 and 589, related to Russian-origin diesel. Unlike earlier authorizations, it lacks a loading or in-transit cut-off date, complicating compliance checks.
GL 13S supersedes GL 13R from July 8, 2026. This change affects internal procedures and audit trails. Expiry dates differ, April 7, 2027, and January 9, 2027, requiring careful monitoring to avoid compliance lapses.
Recommended Actions
Treat each license as a controlled exception, not a blanket rule change.
Maintain Strict Screening: Don't suppress alerts assuming authorization. Route alerts through a license-eligibility check to identify any blocked parties.
Document Eligibility Tests: For GL 13S, record why payments are necessary for operations in Russia. For GL 135, confirm no blocked persons are involved. Use structured fields, not free-text notes.
Enforce Debit Carve-Outs: Implement a monitoring rule to flag potential debits to restricted accounts.
Version-Control License References: Update procedures to reflect current licenses. Ensure each exception ties to a specific license with effective and expiry dates.
Update Customer Risk Ratings: Reassess risk profiles for clients using time-limited authorizations, as their risk changes when licenses expire.
Escalate Edge Cases: Define escalation protocols for complex authorization questions, involving your sanctions lead or MLRO.
When Simplified Views Are Correct
General licenses do remove prohibitions, impacting operations. If your team has been blocking all transactions related to Russian-origin diesel or routine payments, you might be rejecting lawful activities. Over-rejection can harm customers and increase operational burdens. Legitimate transactions should be facilitated, but with caution.
The key is not to ignore licenses but to implement them as exceptions, backed by evidence and with expiry dates in mind. The risk lies in assuming the authorization handles compliance for you.




