When screening runs
At onboarding, before first payment, and continuously when lists update. Screen legal entities, beneficial owners, banks, and freight forwarders—not only the brand name on the invoice.
Lists and jurisdictions
OFAC SDN for US nexus, EU consolidated lists, UK HMT, and others depending on operations. Export control classifications may add product-specific restrictions.
False positives
Common names trigger hits; analysts clear with documentation. Block payments until resolution—no informal overrides.
Integration with P2P
AP must not pay flagged vendors. PO blocks at master data prevent new spend. Re-screen when suppliers change ownership or banking.
Operational checklist for sanctions screening
Screen at onboarding, before payment, and on list updates—batch overnight is not enough for high-risk geographies. Train AP to stop payments on holds without exception.
Document false positive resolution with identifiers used. Re-screen when ownership, banks, or country of shipment changes.
Review metrics quarterly with procurement, finance, and business owners who feel process pain—adjust rules when data shows a control is cosmetic or a bottleneck is upstream.
Metrics, audits, and rollout for sanctions screening
Internal audit samples sanctions screening by tracing transactions from requisition or contract through payment, looking for missing evidence and override patterns. Findings are usually systemic—stale catalogs, receivers not trained, or tolerances set too wide—rather than one rogue approver. Remediation plans should name a process owner outside AP when the root cause is upstream.
Leading indicators for sanctions screening include open exceptions, unposted receipts, contracts past notice windows, and classification backlog; lagging indicators include paid-after-due volume, duplicate hits, and price variance dollars. Review the same dashboard weekly with procurement during a transformation, not only at quarter close, so fixes land before suppliers escalate.
Pilot changes to sanctions screening on one company code or region with documented before-and-after samples on the same supplier mix. Parallel-run old and new rules until match or classification variances fall below an agreed threshold, then cut over with a rollback plan. Executive sponsors should see cycle time and touch-per-document, not only license go-live dates.
Technology helps sanctions screening only when master data, contracts, and receiving discipline keep pace. Budget for content stewardship—catalog updates, clause playbooks, screening lists—alongside software. Tie savings claims to redirected spend, captured discounts, and avoided overbill with line-level examples auditors can reproduce.
Stakeholder alignment matters: publish a one-page RACI for sanctions screening that names who sets policy, who operates the process, and who approves exceptions. Exception approvals should expire automatically after 90 days unless renewed with business justification, preventing "temporary" tolerances from becoming permanent holes in control.
Training should use live examples from your ERP, not generic slides—walk receivers and buyers through one held document and show which fields they can change to clear sanctions screening issues. Reinforce that fixing upstream data beats overriding match or approval rules downstream, because overrides rarely scale across thousands of transactions per month.
Documentation and retention
Maintain a playbook with ERP screenshots and named examples updated after each release. Retain match packets, award memos, screening results, and approval history for the period your auditors expect so reconstructions do not depend on tribal knowledge.
Quarterly, sample three transactions and ask a new analyst to rebuild the decision trail without administrator access. If they cannot, fix attachments, naming, and workflow history before expanding automation or supplier self-service further.