Purpose of This Template
Reactive sanctions programs wait for a hit, then scramble. A proactive program defines in advance who gets screened, when, against what, and who decides. This template is a sanctions screening and escalation policy for AML/KYC teams that want that structure on paper before an examiner or enforcement attorney asks for it.
The urgency is clear. In 2023, OFAC assessed over $1.5 billion in penalties across 17 resolutions, the highest volume it has ever assessed in a single calendar year. Record settlements with Binance Holdings, Ltd. and British American Tobacco (BAT) drove much of that total. Four of the actions were parallel resolutions with the Department of Justice and/or other regulators, so a screening failure can now become a criminal exposure question, not just a civil one. Seven different sanctions programs were involved, with most actions tied to Russia or Iran. A policy that only covers one program or one customer type won't hold up.
Prerequisites
Before you adopt the template, confirm you have:
- A documented risk assessment covering customers, products, geographies, delivery channels, and third parties. The policy's thresholds depend on it.
- Access to current OFAC lists, including the Specially Designated Nationals (SDN) list, delivered through a vendor feed or direct download.
- A screening system (automated or manual) that can match names against list entries and log results.
- A named owner, typically the BSA/AML or sanctions compliance officer, with authority to block or reject activity.
- Legal counsel access for ambiguous matches. Ignorance of a designation is not a defense.
The Template
Copy the text below into your policy library and replace bracketed fields.
[Company Name] OFAC Sanctions Screening and Escalation Policy
1. Purpose and Scope. This policy establishes controls to prevent [Company Name] from conducting prohibited transactions with sanctioned persons, entities, or jurisdictions. It applies to all employees, contractors, and business lines, including [list products/channels].
2. Governance. The [Sanctions Compliance Officer] owns this policy and reports [quarterly] to [Board/Risk Committee]. The owner has authority to block, reject, or freeze activity without business-line approval.
3. Screening Subjects. The following are screened against the SDN list and other applicable sanctions lists using Watchlist Screening:
- (a) Customers and beneficial owners at onboarding
- (b) Counterparties, beneficiaries, and originators on every [wire/payment/transaction type]
- (c) Third parties, vendors, and intermediaries before contract execution
- (d) [Add: shipping parties, agents, merchants, as relevant]
4. Screening Frequency.
- Onboarding: before account opening or first transaction.
- Transactions: in real time, prior to release.
- Existing relationships: [daily/on every list update] rescreening of the full customer base.
5. Geographic and Indirect-Exposure Review. Activity with a nexus to [comprehensively sanctioned jurisdictions] is rejected or escalated. Staff must also review for U.S.-person involvement, U.S.-origin goods, services, or technology, and U.S. dollar clearing, since these can create jurisdiction for non-U.S. entities.
6. Alert Handling.
- Tier 1 analyst reviews each alert within [X hours] and documents the match rationale.
- Confirmed or unresolvable potential matches escalate to the Sanctions Compliance Officer immediately.
- Pending resolution, the transaction is held. No one may release a held item without written Compliance approval.
7. Blocking and Reporting. The Sanctions Compliance Officer determines whether to block or reject and files required reports with OFAC within the applicable deadlines, in consultation with counsel.
8. Training. All relevant staff complete training at hire and [annually]. Training covers prohibited activities, red flags, escalation paths, and the consequences of non-compliance.
9. Testing and Audit. Independent testing of screening logic occurs [annually]. Results and remediation are reported to [Board/Risk Committee].
10. Recordkeeping. Screening results, alert dispositions, and escalation decisions are retained for [period set with counsel].
11. Policy Review. This policy is reviewed [annually] and upon any significant sanctions program change, new product launch, or enforcement development.
How to Customize It
Section 3 (Subjects): Expand to match your risk assessment. A payments company should add merchants and acquirers; a trade-adjacent business should add vessels, agents, and freight parties. If a population isn't screened, document why.
Section 4 (Frequency): Rescreening on list updates, not on a calendar, closes the gap between a new designation and your next batch run. If your volume makes that impractical, document the compensating control.
Section 5 (Indirect Exposure): The enforcement pattern includes non-U.S. firms whose conduct touched U.S. persons or the U.S. financial system. Tailor this section to your actual flows: where you clear dollars, which U.S. vendors sit in your stack, and what goods or technology you handle.
Section 6 (Alerts): Set time limits that match your transaction speed. Real-time payments need minutes, not days. Define what "unresolvable" means so analysts don't release items on a hunch.
Technology Placement: Automated screening tools improve speed and consistency, but the policy should state their limits. Specify fuzzy-matching thresholds, how name transliteration is handled, and who approves tuning changes. Untuned thresholds are a common source of both missed matches and alert floods.
Cross-Agency Exposure: Because enforcement increasingly involves multiple agencies, align this policy with your Bank Secrecy Act program so a single event triggers coordinated review, not siloed responses.
Validation Steps
A policy that isn't tested is just a document. Before you call it adopted:
- Run a List-Match Test. Submit known SDN entries, including name variants and misspellings, through each screening point. Confirm alerts fire at onboarding, in transaction flow, and in batch rescreening.
- Test the Hold. Trigger a test alert and verify the transaction actually stops, and that only Compliance can release it.
- Trace a Sample End to End. Pick several closed alerts and confirm the file shows the match rationale, reviewer, timestamp, and approval.
- Check List Freshness. Verify the timestamp of your loaded list against the latest published update, and confirm your rescreening ran after it.
- Walk the Escalation Path. Run a tabletop exercise with Compliance, legal, and operations. Time how long a true-positive takes to reach a blocking decision.
- Review Coverage Gaps. Compare Section 3 against your actual onboarding, payment, and vendor workflows. Any population that bypasses screening is a finding.
- Document and Date Everything. Examiners and enforcement counsel evaluate whether a program works in practice and whether you can prove it.
Revisit the template after each test cycle. The goal is a policy that your team follows, your systems enforce, and your records can defend.





