· Yair Knijn
Your EU-only screening was twenty days behind OFAC, and the designation landed in the gap
The risk and compliance director at an EU insurer screens every party against the EU consolidated list and signs off. It is the list the regulator names, the list the Council maintains, the list that binds the firm under EU law. The reasoning is clean and the reasoning is wrong. Treating the EU list as the world's sanctions position assumes OFAC, the EU, and the UN move in lockstep. They do not. They run on three different clocks, and the gap between them is an unscreened window you can count in days.
Here is how the assumption fails in practice. A name is designated by OFAC on a Tuesday. Your EU-only program does not flag it, because the EU has not adopted it yet, and may not for weeks. The policy binds, the premium clears, and the party is already sanctioned in another jurisdiction you transact with. You did not miss a match. You screened against a list that had not caught up.
Three lists, three update clocks: OFAC several times weekly, EU after Council decisions, UN slower
OFAC has no fixed publication day. It releases when an action clears interagency review, which means a cluster of designations one afternoon and then silence for a week and a half. The EU moves on a different mechanism entirely: a designation binds when the amending regulation is published in the Official Journal, which the Council publishes within roughly a day or two of adopting the decision, and the searchable consolidated database can trail that publication by further days. The UN is slower still, but its designations bind all 193 member states, so a UN listing eventually propagates into both the OFAC and EU lists on their own timelines.
Three sources, three triggers. OFAC fires on interagency clearance. The EU fires on Council adoption and Official Journal publication. The UN fires on Security Council consensus. None of them waits for the others, and none of them tells your screening engine when the other two have moved.
The 48-hour-to-three-week sync lag between an OFAC designation and its EU mirror
When the EU mirrors an OFAC designation, the delay is not fixed and it is not short. Reported lags run from roughly 48 hours at the fast end to about three weeks at the slow end, and a designation that originates at the UN can take anywhere from same-day to several weeks to surface in both the OFAC and EU lists. The variability is the problem. You cannot plan around a lag you cannot predict, and you cannot screen a party against a designation that has not reached your list yet.
The exposure window is exactly this lag. For the days or weeks that an OFAC name has not yet been mirrored into the EU consolidated list, an EU-only program is structurally blind to it. The party clears, not because they are clean, but because your reference data is behind.
Why a single-list program has a structural blind spot you can measure in days
This is not an operational miss you fix by screening more carefully. A single-list program cannot see a designation that exists only on another list, no matter how good the matching logic is. The blind spot is built into the data source, and it has a measurable width: the number of days between when one authority designates and when your chosen authority mirrors it.
- Trigger mismatch: each authority designates on its own legal mechanism, so the lists are never simultaneously current.
- Mirror delay: the days-to-weeks gap before a designation propagates is your unscreened window.
- Database trail: even within one authority, the binding legal text can precede the searchable list version your tool actually queries.
Screening the consolidated union and re-running on every delta from any source
Closing the window requires screening against the union of OFAC, EU, and UN lists, not any single one of them. If a name is sanctioned anywhere you have exposure, you want it flagged the day that authority designates it, not the week a second authority gets around to mirroring it. That means refreshing reference data at least daily and re-running screening on every delta, whichever source produced it, against parties on policies that are already bound. It also means recording the exact list version used for each screening event, so the case file shows which database, on which date, cleared the name.
Inside an InsureGuardAI workspace, the consolidated union is the default screening target and every list refresh triggers a re-screen of in-force parties against the new delta, with the source list and version stamped onto the match record as evidence. The lag between OFAC and its EU mirror stops being a blind spot when no single list's clock is the one you depend on. See how continuous union screening closes the window.