Leela

Model policy · version 1

Sanctions / OFAC

Screen every customer, owner, and transaction against the OFAC lists, hold anything that looks like a match, and get the sponsor bank the facts it needs to block and report within the hour. Sanctions liability is strict, so the clocks in this policy are the control.

What’s in this policy8 sections · Sanctions / OFAC · Read the full policy
9Obligations · things you must do
24Evidence · records that prove it
3Monitoring · checks and deadlines
0Reporting · reports you must send

Does this apply to you?

Answer a few questions and each obligation is marked applies, likely, or needs more information.

Tell Leela about your company

Hand over the whole policy

Every obligation in this policy, in one request.

What the policy requires

Automate

Leela can perform the work through your connected systems.

Monitor

Leela can watch for the trigger, keep the clock, and flag what is late.

Prepare for review

Leela can prepare the artifact and hand it to a person for review.

Human required

A person must do the work; Leela can track it and file the evidence.

Policy reference§3.1
Leela can
Monitor
TriggerEvent-driven · Each new customer, before account activation; again at each periodic review
EvidenceScreening result, Activation gate record
Policy reference§3.2
Leela can
Monitor
TriggerContinuous · Every digital-asset transaction as it is initiated; alerts the same business day
EvidenceAlert record, Hold and notification log, Configuration sign-off
Policy reference§3.3
Leela can
Monitor
TriggerEvent-driven · Each wire at or above the threshold, before transmission; weekly flag export until the routing protocol is live
EvidencePre-transmission screening record, Fiat screening protocol, Weekly flag export
Policy reference§4.1, §4.2
Leela can
Monitor
TriggerEvent-driven · Each potential match on any screening surface, immediately on the alert
EvidenceHold log, Sponsor bank potential-match notice, Match workpaper
Policy reference§4.3, §4.4
Leela can
Human required
TriggerEvent-driven · Each confirmed match, on confirmation
EvidenceBlock action record, Sponsor bank confirmed-match notice, Division of steps log
Policy reference§4.3
Leela can
Prepare for review
TriggerEvent-driven · Each false-positive outcome, within 24 hours; each unresolved match, within four business hours and one business day
EvidenceFalse-positive workpaper, Escalation record, Suppression log entry
Policy reference§3.1, §5.1
Leela can
Automate
TriggerDaily · Daily list check; delta re-screen promptly on each publication
EvidenceDaily monitoring log entry, Delta re-screening run record
Policy reference§5.2, §5.3
Leela can
Human required
TriggerAnnual · Each year with the compliance program review; operating report each quarter
EvidenceAnnual review record, Training completion roster, Quarterly sanctions operating report
Policy reference§6
Leela can
Monitor
TriggerContinuous · Five years from each record; from the transaction date for blocking records
EvidenceRetention schedule entry, Suppression log