Understanding Asset Detention Under OFAC Sanctions: The Wiley Framework
The concept of "detention" in sanctions compliance traces back to work done at OFAC in the 1990s and early 2000s, a period when the Treasury Department was refining how blocked property was tracked, reported, and enforced. Bob Wiley was one of the people working on these frameworks. His contributions shaped how institutions approach the practical mechanics of freezing assets, filing reports, and maintaining compliance when dealing with specially designated nationals (SDNs) and blocked persons. Most people encountering this topic are trying to understand how asset blocking actually works in practice, not just the legal definitions. There's a difference.
The Ultimate Guide To Bob Wiley Detention What You Need To Know
At its core, the Wiley approach to detention focuses on the operational side of sanctions compliance. When an entity blocks property, it's not enough to simply freeze an account and move on. There are reporting requirements, record-keeping standards, and internal procedures that need to function correctly under pressure. The framework Wiley helped develop treats detention as an ongoing process, not a one-time event. I spent years working with institutions that handled blocked asset cases, and the most common failure I saw wasn't a misunderstanding of the law. It was procedural breakdown. A bank would block an account correctly, but then fail to maintain proper documentation or file reports within the required timelines. OFAC doesn't care about intent. They care about whether the paperwork exists and whether it was filed on time. The practical steps involve screening, identification, blocking, reporting, and ongoing management. Screening uses the SDN list and other designated party lists. Identification means determining whether a hit is a true positive or a false match, which requires your own analysis rather than blindly accepting automated results. Blocking is the actual freezing of property, which includes both financial accounts and tangible assets. Reporting goes to OFAC within ten days of the blocking action. Ongoing management covers everything from handling interest that accrues on blocked accounts to determining when a release might be appropriate.
One thing that catches people off guard is the scope of what constitutes "property." It's not just bank accounts. It includes any interest, right, or privilege in property. That means pending transactions, contractual rights, insurance proceeds, and even digital assets if they fall under OFAC's jurisdiction. I once worked a case where an institution had correctly blocked a wire transfer but missed the fact that the same beneficial owner also held a letter of credit with the same bank. The LC wasn't flagged because it existed in a separate system. OFAC flagged it six months later during an examination. The institution received a consent order with a substantial civil monetary penalty. Here's the counter-intuitive part that most compliance programs miss: blocking is only the beginning. Managing blocked assets properly requires understanding how to handle blocked income, how to report amendments, and when you might be eligible to apply for a specific license to unblock or release property. OFAC issued general licenses and specific licenses that allow certain transactions to proceed under defined conditions. Knowing when to apply for a license versus maintaining the block is where institutional judgment matters. The biggest bottleneck in this process is typically the screening infrastructure. Legacy systems from the nineties and early two-thousands weren't built for the volume and speed of modern sanctions matching. They produce excessive false positives, which leads to over-blocking. Over-blocking creates its own problems: legitimate business gets disrupted, customers complain, and compliance teams become desensitized to alerts because they're drowning in noise. I've seen institutions go the other direction and under-screen because their team was burned out from the false positive rate. Both approaches create regulatory exposure.
Get the Full Details
Effective programs layer multiple screening tools and use deterministic rules alongside fuzzy matching algorithms. They also maintain clear escalation paths so that compliance officers can review borderline matches without waiting for a batch process to complete. Speed matters. If you identify a potential SDN match after a wire has already been settled, you've already violated the blocking requirement regardless of how quickly you act afterward. Record-keeping is where most programs also fall short. You need to maintain records of every blocked asset, every report filed, every license application, and every internal decision. These records should be maintained for at least five years after the blocking action ends. Some institutions maintain them indefinitely because the statute of limitations for OFAC enforcement actions can extend further than you might expect, especially when willful violations are alleged. Training is another area where institutions consistently underinvest. OFAC examinations frequently cite inadequate training as a contributing factor in violations. The expectation isn't that every employee knows sanctions law. It's that the people who handle transactions, screen matches, and make blocking decisions receive regular, documented training that is current with regulatory changes. Sanctions policy changes frequently. Russia-related measures, Iran framework updates, Myanmar directives—these shift often enough that a training program based on last year's guidance is already stale.
If you're building or evaluating a sanctions detention program, start with your screening tool's accuracy metrics. Know your false positive and false negative rates. Audit them quarterly. Then validate that your reporting timelines are being met consistently, not just on average. I've seen programs where the average filing time looked fine because a few cases dragged on for months while most were processed quickly. That's not acceptable. Every case needs to meet the deadline. There's no shortcut around competent staffing. Automated tools help, but they don't replace judgment on complex matches, beneficial ownership analysis, and license applications. If your program consists entirely of automated screening with no human review layer, you're creating risk, not eliminating it.
