Step 1 of 2
Run a Free Risk Check
Tell us who you want to research. We’ll ask for your details in the next step.
Vendor onboarding is where most compliance failures begin. Here's a structured process for what to check, when to check it, and what triggers a deeper review.
Vendor onboarding is not a single gate—it is a four-stage risk management continuum that begins with pre-engagement screening and extends through continuous monitoring. Each stage corresponds to specific data points, decision thresholds, and escalation triggers that compliance officers must apply consistently to protect the organization from sanctions exposure, ownership obscurity, litigation risk, and adverse media signals.
This is the first risk checkpoint: a new vendor intake triggers automated screening across sanctions lists, beneficial ownership registries, PEP databases, adverse media feeds, and litigation records. The compliance officer receives a risk score and a binary decision: approve, escalate, or reject.
Purpose: Identify immediate red flags that disqualify a vendor or trigger enhanced due diligence before any contractual commitment is made.
Data inputs: Entity identity and registration, Ultimate Beneficial Owner (UBO) verification, sanctions screening (OFAC, EU Sanctions, UK HM Treasury), PEP status, adverse media (12-month window), litigation history.
Decision output: Risk score (0–100); risk tier assignment (Low/Medium/High); approval, escalation, or rejection.
When initial screening detects a red flag—UBO gaps, sanctions hits, high-risk PEPs, credible adverse media, or active litigation—the compliance officer initiates enhanced due diligence. This stage requires manual investigation: requesting vendor documentation, cross-verifying data via alternate registries, assessing materiality of litigation, and classifying PEP risk by jurisdiction.
Purpose: Resolve ambiguities, validate red flags, and determine whether conditional approval or rejection is warranted.
Escalation triggers: UBO obscured by shell entities; sanctions hit confidence >70%; PEP ties to sanctioning regimes; credible adverse media from Tier-1 sources; active criminal or high-value civil litigation; missing or conflicting beneficial ownership documentation.
Decision output: Approve with conditions, conditional approval (with escalated monitoring), or reject and disengage.
Once the risk verdict is reached, the compliance officer locks in the approval decision, assigns a risk tier, and codifies the recertification schedule. This stage generates audit-ready artifacts: screening reports with source citations, UBO verification records, sanctions match certificates, risk ratings, vendor acknowledgment of compliance obligations, and subprocessor pre-approval registers.
Purpose: Create a defensible audit trail that demonstrates regulatory compliance and supports internal reviews.
Artifacts required: Signed screening report; UBO verification chain; sanctions match certificate; risk tier assignment; vendor acknowledgment; recertification schedule; subprocessor register (if applicable).
Approval gate: Compliance officer signature on screening report; CFO/CEO sign-off for High-Risk vendors; legal review of contract risk controls; vendor acknowledgment received.
Vendor risk is not static. Ownership structures change, sanctions lists update weekly, adverse media can surface overnight, and litigation filings occur without notice. Ongoing monitoring detects these changes and triggers re-evaluation based on risk tier: monthly sanctions re-screening for High-Risk vendors, quarterly adverse media reviews for Medium-Risk, and annual recertification for Low-Risk.
Purpose: Maintain visibility into vendor risk posture; trigger escalation when material changes occur; ensure recertification compliance.
Monitoring activities: Sanctions re-screening (cadence per tier); UBO verification updates; adverse media monitoring; litigation tracking; recertification reviews; transactional anomaly detection; subprocessor change notifications.
Recertification cadence by tier:
Outcome options: Continue (no material changes); conditional continuation (escalated monitoring); remediation hold (pause transactions pending investigation); disengagement (terminate relationship; document rationale).
The four stages form a closed loop. Initial screening feeds risk tier assignment; risk tier dictates monitoring cadence; monitoring alerts trigger re-evaluation (which may loop back to enhanced due diligence); recertification outcomes adjust tier assignments and monitoring frequency. This lifecycle structure ensures that vendor risk management is not a one-time check but a continuous, data-driven discipline.
Regulatory alignment: The lifecycle model aligns with FATF risk-based approaches, NIST SP 800-161 Rev. 1 supply chain risk management practices, and ISO 37301:2021 compliance management system requirements—all of which mandate documented risk assessment, escalation thresholds, and ongoing monitoring.
Diligard’s role in the lifecycle: Automates data gathering at every stage—initial screening runs in under 4 minutes; enhanced due diligence receives pre-pulled investigative data (registry extracts, alias matches, litigation summaries); ongoing monitoring delivers scheduled re-screening alerts and real-time adverse event notifications. Compliance officers focus on judgment: interpreting red flags, assessing materiality, determining business justification, and making escalation or disengagement decisions. The platform handles data normalization, source attribution, confidence scoring, and audit trail generation.
For vendor risk management at scale, explore vendor & partner due diligence and legal & compliance intelligence use cases.
Every vendor onboarding stage generates specific risk signals that demand immediate compliance action. The following red flags map directly to decision thresholds: ignore them, and your organization inherits sanctions exposure, litigation risk, or concealed beneficial ownership.
Ownership structure unclear, beneficial owner hidden behind shell entities, or jurisdictional mismatch between registration and operational headquarters. Shell companies layered across tax havens (e.g., BVI → Cyprus → Malta) are designed to obscure control. If you cannot confirm a natural person with ≥25% ownership within three tiers, escalate immediately.
Escalation trigger: UBO remains unknown after registry query; ownership chain exceeds three layers without reaching a natural person; beneficial owner resides in a non-cooperative jurisdiction (FATF grey/blacklist).
Data sources: UK PSC Register, EU beneficial ownership databases, national corporate registries, OpenCorporates.
Name-match hits on OFAC, EU Sanctions, or UK HM Treasury lists indicate direct or indirect exposure to sanctioned individuals, entities, or regimes. Alias variants (transliterations, nicknames, maiden names) complicate matching; a single false negative can trigger regulatory enforcement.
Escalation trigger: Any match with confidence score >70%; multiple low-confidence matches (<50%) that share jurisdiction + entity type; beneficial owner or director flagged on any sanctioned list.
Data sources: OFAC SDN List, EU Consolidated Financial Sanctions List, UK HM Treasury Sanctions List, INTERPOL Red Notices.
Politically exposed persons tied to the vendor entity elevate corruption, sanctions, and reputational risk. High-risk PEPs (heads of state, senior officials in sanctioning regimes, family members of designated persons) require enhanced due diligence under FATF Recommendation 12.
Escalation trigger: High-risk PEP identified (head of state, cabinet minister, or equivalent); PEP jurisdiction matches a sanctioning regime (Iran, North Korea, Russia, Syria); family or close associate of a sanctioned individual.
Data sources: World-Check, Dow Jones Risk & Compliance, ComplyAdvantage PEP databases, national PEP registries.
Credible negative coverage within a 12-month window indicates regulatory action, litigation, fraud allegations, or reputational damage. Media must be validated for credibility; rumors and unsubstantiated blog posts do not constitute red flags.
Escalation trigger: Tier-1 media source (Reuters, Bloomberg, Financial Times) reports regulatory enforcement, criminal investigation, or civil fraud allegation; multiple credible sources corroborate the same incident; regulatory body issues public notice or enforcement order.
Data sources: LexisNexis, Factiva, regulatory enforcement databases (SEC, FCA, DOJ), court docket alerts.
Active civil or criminal cases, regulatory enforcement actions, or repeated litigation patterns signal operational, financial, or compliance risk. Materiality depends on case type, jurisdiction, and outcome.
Escalation trigger: Active criminal case filed against vendor or beneficial owner; civil fraud findings exceeding $1M in damages; regulatory fine >$5M; repeated litigation (≥3 cases in 24 months) indicating systemic issues.
Data sources: PACER (US federal courts), national court registries, SEC enforcement actions, FCA Final Notices, DOJ press releases.
UBO shifts within a 6-month pre-onboarding window suggest undisclosed control transfers, asset restructuring to avoid detection, or distressed entity sales. Sudden ownership changes correlate with sanctions evasion and fraud.
Escalation trigger: Beneficial owner changed within 6 months without disclosed rationale; ownership transferred to a newly registered entity with no operating history; ownership structure modified concurrent with adverse media or litigation event.
Data sources: Corporate registry filings, beneficial ownership change logs, M&A databases (PitchBook, Crunchbase).
Vendor or related entity newly listed post-initial screening. OFAC, EU, and UK sanctions lists update weekly; a clean screening result can become a sanctions hit within days.
Escalation trigger: Vendor, beneficial owner, or director added to any sanctions list after initial screening; entity flagged for indirect exposure (e.g., 50%+ owned by newly sanctioned parent).
Data sources: OFAC SDN updates (weekly), EU Official Journal (sanctions amendments), UK OFSI updates.
Missing beneficial ownership documentation, inconsistent registry data, or conflicting entity identifiers prevent confident risk assessment. Incomplete data equals unverified risk.
Escalation trigger: Vendor fails to provide UBO certification after request; beneficial ownership registry returns “no data” or “under investigation”; entity registration number mismatches across databases; vendor operates in a jurisdiction with no public beneficial ownership registry.
Data sources: National corporate registries, beneficial ownership databases, vendor-provided documentation.
Unusual vendor activity post-engagement: payment spikes, geographic shifts, or invoice irregularities suggest fraud, sanctions evasion, or control transfer.
Escalation trigger: Payment volume increases >50% without contract amendment; vendor invoices from previously undisclosed jurisdiction; payment routed through intermediary entity not disclosed during onboarding.
Data sources: Transaction monitoring systems, vendor invoice records, bank transaction metadata.
New litigation, regulatory actions, or media coverage post-onboarding indicate deteriorating compliance posture or emerging risk.
Escalation trigger: New criminal case filed; regulatory enforcement action announced; credible adverse media published by Tier-1 source; vendor files for bankruptcy or restructuring.
Data sources: Court docket alerts, regulatory RSS feeds, LexisNexis alerts, bankruptcy filings.
Failed recertification, missing documentation updates, or control gaps signal vendor neglect of compliance obligations.
Escalation trigger: Vendor misses recertification deadline; updated UBO documentation not provided within 15 days of request; vendor fails annual compliance questionnaire; insurance or financial health documentation lapses.
Data sources: Vendor compliance calendar, recertification tracking system, insurance certificate repository.
Undisclosed third-party processors or service changes propagate risk through the supply chain. Vendors must notify and obtain pre-approval for subprocessor additions.
Escalation trigger: Vendor adds subprocessor without pre-approval; subprocessor fails ongoing monitoring (sanctions hit, adverse media, litigation); vendor changes data processing jurisdiction without notification.
Data sources: Vendor subprocessor register, contract amendments, supply chain risk monitoring.
Low-Risk vendors: Zero red flags; UBO verified; no sanctions/PEP exposure; no adverse media. Annual recertification; annual sanctions re-screen; quarterly adverse media review.
Medium-Risk vendors: Minor red flags resolved via Enhanced Due Diligence; low-risk PEP; immaterial litigation history. Semi-annual recertification; quarterly sanctions re-screen; monthly adverse media monitoring.
High-Risk vendors: Material red flags mitigated with conditions; high-risk PEP; active litigation; ownership complexity. Quarterly recertification; monthly sanctions re-screen; real-time (daily) adverse media monitoring; transactional anomaly detection enabled.
Diligard automates the data-gathering layer across all red flag categories: UBO verification via entity-graph mapping, sanctions screening with alias normalization, PEP classification by jurisdiction tier, adverse media aggregation with credibility scoring, and litigation tracking via court docket feeds. The platform delivers a consolidated risk verdict in under 4 minutes, complete with source citations and confidence scores.
Compliance officers retain all escalation decisions, risk tier assignments, and business justification authority. Diligard eliminates manual data collection, normalizes conflicting registry entries, and flags material changes in real time—enabling judgment on high-stakes risks, not data entry.
For organizations managing complex vendor partner due diligence or legal compliance intelligence programs, automated red flag detection is the difference between proactive risk management and reactive crisis response.
Vendor onboarding is a continuous risk management process, not a one-time gate. Compliance officers must structure screening, escalation, and monitoring across four distinct stages: Initial Screening (pre-engagement), Enhanced Due Diligence (risk-triggered escalations), Onboarding Approval & Documentation, and Ongoing Monitoring & Recertification.
First contact to risk verdict. Screen every vendor intake for entity identity, beneficial ownership, sanctions exposure, PEP status, and adverse media before engagement begins.
Triggered by red flags from Initial Screening. Deeper investigation into UBO incongruities, litigation history, PEP nexus, or data quality gaps requiring vendor documentation and third-party verification.
Risk verdict reached; approval gate locked. Generate audit-ready artifacts, assign risk tier, define monitoring cadence, and secure vendor acknowledgment of compliance obligations.
Post-engagement surveillance tied to risk tier. Monthly to annual re-screening for sanctions, adverse media, litigation, and ownership changes; recertification cycles enforce control drift detection.
Regulatory requirements translate into actionable red flags at each stage. Compliance officers must know which data points trigger intervention, escalation thresholds, and when to reject outright.
Ownership structure unclear, beneficial owner hidden behind shell entities, or jurisdictional mismatch between registered address and UBO domicile. If ownership chain exceeds three tiers without clear natural-person identification, escalate immediately.
Name-match hits on OFAC, EU Sanctions, or UK HM Treasury lists; alias variants flagged with confidence score above 50%. Zero tolerance for confirmed matches; any hit above 70% confidence triggers rejection unless vendor produces credible counter-evidence.
Politically exposed persons tied to entity; risk tier assessed by jurisdiction and role. High-risk PEPs (head of state, family of sanctioned individuals, associates in sanctioning regimes) require Enhanced Due Diligence and CFO/CEO approval.
Credible negative coverage within 12-month window; severity classification assigned (allegation vs. regulatory action vs. criminal conviction). Tier-1 media sources with corroborating court filings or regulatory notices trigger escalation.
Active civil or criminal cases; regulatory enforcement actions filed within 24 months. Material threshold: regulatory fine exceeding $5M, repeated civil fraud findings, or active criminal proceedings related to vendor capability.
UBO shifts within 6-month pre-onboarding window or during Enhanced Due Diligence investigation. Ownership structure change greater than 10% requires updated beneficial ownership certification and registry re-verification.
Vendor or related entity newly listed post-Initial Screening. Weekly sanctions feed checks during Enhanced Due Diligence window; any new hit triggers immediate escalation to legal review and potential disengagement.
Missing beneficial ownership documentation; inconsistent registry data across jurisdictions; UBO certification older than 90 days. After 15 calendar days, vendor failure to provide required documentation triggers rejection.
Unusual vendor activity post-engagement: geographic payment spikes, volume increases exceeding 200% of baseline, or payments routed through previously undisclosed jurisdictions. Manual investigation required within 48 hours.
New litigation, regulatory actions, or credible adverse media coverage detected during monitoring cycle. Real-time alerts (daily for High-Risk vendors) trigger escalation if event is material to vendor capability or compliance posture.
Failed recertification; missing documentation updates; vendor non-response to recertification questionnaire within 30 days. Conditional continuation with escalated monitoring or remediation hold pending resolution.
Undisclosed third-party processors or service changes detected post-onboarding. Vendor adds subprocessor without pre-approval; subprocessor fails Initial Screening checklist. Pause affected transactions pending subprocessor clearance.
Compliance officers must screen specific data points immediately and apply decision thresholds that differentiate approval, escalation, and rejection. Every vendor intake passes through this gate before engagement discussions proceed.
| Data Point | Source | Decision Threshold | Escalation Trigger |
|---|---|---|---|
| Entity Identity & Registration | Corporate registries (national + international) | Valid registration + matching legal name | Missing or fraudulent registration |
| Ultimate Beneficial Owner (UBO) | Public registries, beneficial ownership DB, corporate filings | UBO identified & verified; ownership chain ≤3 tiers | UBO obscured; shell entities detected; ownership unclear |
| Sanctions Screening | OFAC, EU Sanctions, UK HM Treasury lists | Zero hits on primary + alias name variants | Any hit; confidence score >70% |
| PEP Status | PEP databases (jurisdictional tiers) | No PEP association OR low-risk PEP (non-sanctioning jurisdiction) | High-risk PEP; PEP in sanctioning regime; family ties to HVT |
| Adverse Media (12-month window) | News feeds, regulatory databases, litigation records | Zero credible negative coverage | Credible allegations; regulatory action; litigation pending |
| Data Freshness | Source metadata (last update timestamp) | Data <90 days old (UBO), <30 days old (Sanctions) | Stale data; incomplete verification trail |
Enhanced Due Diligence defines deeper investigative steps triggered by red flags. Compliance officers conduct targeted investigations, request vendor documentation, and determine resolution thresholds that separate conditional approval from rejection.
| Red Flag Category | Enhanced Check | Evidence Required | Resolution Threshold | Rejection Trigger |
|---|---|---|---|---|
| UBO Incongruity | Request UBO certification letter; verify via beneficial ownership registry | Signed UBO declaration + registry match (name, ID, %) | UBO confirmed within 2 tiers; explanation for shell entities documented | UBO remains unknown after registry + client query; shell entity used to obscure ownership |
| PEP Presence (High-Risk) | Classify PEP type (head of state, family, associate); assess sanctioning regime nexus | PEP status confirmation from authoritative source; sanction list cross-check | PEP status accepted with mitigation (e.g., no sanctioning regime ties); business justification documented | PEP tied to OFAC/EU/UK sanctioning regime; family relation to HVT (High-Value Target) |
| Litigation History | Obtain case summaries, outcome, and recency; assess materiality to vendor capability | Court filings, docket records, settlement docs | Litigation concluded >2 years ago; resolved favorably or immaterial to vendor capability | Active criminal case; repeated civil fraud findings; regulatory fine >$5M or capability-critical outcome |
| Adverse Media (Credible) | Validate media source credibility; assess severity (allegation vs. conviction vs. rumor) | Primary source (court filing, regulatory notice) vs. secondary (news aggregation) | Allegation without conviction; media coverage credible but unsubstantiated; documented rebuttal accepted | Regulatory conviction; repeated substantiated allegations; media coverage from Tier-1 sources with corroborating evidence |
| Data Quality Gaps | Request missing documentation; cross-verify via alternate registries | Notarized corporate filings; beneficial ownership registry extracts | Documentation gaps resolved; alternate source confirms data | After 15 calendar days, vendor fails to provide required documentation; alternate registry sources conflict materially |
| Sanctioning Regime Change | Re-screen against updated sanctions lists (weekly feed check) | Sanctions list version date; updated screening report | No new hits post-update | New sanctions hit post-initial screening |
Approval decisions must be codified with audit-ready documentation and locked-in recertification schedules. Every artifact serves a regulatory audit or internal control review.
| Artifact | Owner | Requirement | Storage |
|---|---|---|---|
| Screening Report | Compliance Officer | Signed off; includes data sources, decision rationale, risk score | Vendor master file (audit trail) |
| UBO Verification Record | Compliance Officer | Beneficial ownership chain + registry extract + update frequency | Vendor master file |
| Sanctions Match Certificate | Compliance Officer | List version, date screened, name variants checked, zero-hit confirmation | Vendor master file |
| Risk Rating & Tier Assignment | Compliance Officer | Assigned tier (Low/Medium/High); monitoring cadence linked | Vendor master file + monitoring schedule |
| Vendor Acknowledgment | Vendor Legal/Compliance | Signed attestation of compliance obligations + ongoing disclosure duty | Contract amendment or standalone letter |
| Recertification Schedule | Compliance Officer | Recertification date (baseline 12–24 months per tier); monitoring trigger list | Compliance calendar + alert system |
| Subprocessor Pre-Approval (if applicable) | Compliance Officer | Vendor’s list of third-party processors; each pre-screened per Initial Screening checklist | Vendor master file; subprocessor register |
Ongoing monitoring defines when to escalate post-engagement changes and ensures recertification cycles detect control drift. Risk tier determines monitoring frequency and alert thresholds.
| Monitoring Activity | Cadence | Data Source | Escalation Trigger | Action |
|---|---|---|---|---|
| Sanctions Re-screening | Monthly (High-Risk) / Quarterly (Medium) / Annually (Low) | OFAC, EU, UK lists (automated feed) | New sanctions hit; alias match with confidence >50% | Escalate to Enhanced Due Diligence; consider vendor disengagement |
| UBO Verification Update | Quarterly (High-Risk) / Annually (Medium/Low) | Public registries; beneficial ownership databases | UBO change; ownership structure shift >10% | Request updated UBO certification; assess materiality |
| Adverse Media Monitoring | Monthly (High-Risk) / Quarterly (Medium) | News feeds, court docket alerts, regulatory databases | Credible adverse media within recency window (12 months); regulatory action filed | Escalate; assess materiality; request vendor response |
| Litigation Tracking | Quarterly (High-Risk) / Annually (Medium/Low) | Court dockets, regulatory databases, litigation alerts | New civil/criminal case filed against vendor; regulatory enforcement action | Escalate; request case summary; assess impact on vendor capability |
| Recertification Review | 12–24 months (per tier assignment) | Vendor re-questionnaire; updated documentation | Failed recertification; missing documentation; control gaps | Conditional approval with monitoring; escalate for legal review |
| Transactional Anomaly Detection | Monthly | Transaction analytics (if integrated) | Unusual payment patterns; geographic or volume spikes | Manual investigation; escalate if correlated with adverse event |
| Subprocessor Changes | Ongoing (notification-triggered) | Vendor disclosure + pre-approval gate | Vendor adds subprocessor without pre-approval; subprocessor fails ongoing monitoring | Escalate; pause affected transactions pending subprocessor clearance |
Diligard automates data gathering so compliance officers focus on judgment calls. The platform delivers audit-ready artifacts with source attribution and version control in under 4 minutes.
Explore how Diligard accelerates vendor partner due diligence and strengthens legal compliance intelligence across onboarding workflows.
VENDOR ONBOARDING SCREENING REPORT Vendor Name: [Legal Entity Name] Screening Date: [ISO Date] Screening ID: [Unique Report ID] Screened By: [Compliance Officer Name] 1. ENTITY REGISTRATION - Registered Jurisdiction: [Country/State] - Registration Number: [ID] - Legal Name Match: ✓ PASS / ✗ FAIL - Source: [Registry Name, Last Updated: Date] 2. ULTIMATE BENEFICIAL OWNER (UBO) - UBO Identified: ✓ YES / ✗ NO - UBO Name(s): [Name(s)] - Ownership Tier(s): [Tier 1 → Tier 2 → ... → UBO] - Ownership %: [Cumulative %] - Verification Source: [Registry, Last Updated: Date] - Shell Entity Detected: ✓ YES / ✗ NO - Verification Status: COMPLETE / INCOMPLETE / ESCALATE 3. SANCTIONS SCREENING - OFAC Screening: 0 Hits / [# Hits] - EU Sanctions Screening: 0 Hits / [# Hits] - UK HM Treasury Screening: 0 Hits / [# Hits] - Alias Variants Checked: [Count] - Highest Confidence Score: [Score] - Sanctions Status: CLEAR / ESCALATE / REJECT 4. PEP STATUS - PEP Classification: NOT PEP / LOW-RISK PEP / HIGH-RISK PEP - PEP Jurisdiction(s): [If applicable] - Sanctioning Regime Nexus: NO / YES [Regime name] - Source: [PEP Database, Last Updated: Date] 5. ADVERSE MEDIA (12-Month Window) - Adverse Media Detected: NO / YES - Media Items: [Count & Summary] - Credibility Assessment: Low / Medium / High - Severity: Allegation / Regulatory Action / Criminal Conviction - Recency: [Most recent date] - Adverse Media Status: CLEAR / ESCALATE 6. DATA QUALITY ASSESSMENT - UBO Data Freshness: [Days old] - Sanctions List Version: [Date] - Data Provenance: [Source breakdown] - Gaps Identified: [List or NONE] 7. RISK SCORE & DECISION - Risk Score: [0–100] - Risk Tier: LOW / MEDIUM / HIGH - Initial Screening Decision: APPROVE / ESCALATE / REJECT - Rationale: [50–100 words] - Escalation Triggers (if applicable): [List] 8. DOCUMENTATION & AUDIT TRAIL - Report Generated: [Timestamp, System] - Data Sources: [List with versions] - Next Review Date: [Date for recertification] - Compliance Officer Sign-Off: [Signature & Date]
ENHANCED DUE DILIGENCE SUMMARY Vendor Name: [Legal Entity Name] Initial Screening ID: [Reference] EDD Initiation Date: [ISO Date] EDD Completion Date: [ISO Date] 1. ESCALATION TRIGGERS (From Initial Screening) - Trigger 1: [Red Flag Category & Description] - Trigger 2: [Red Flag Category & Description] 2. INVESTIGATIVE FINDINGS [For each trigger:] Trigger: [Red Flag] Investigation: [Description of steps taken] Evidence: [Documents reviewed, sources consulted] Finding: [Outcome: RESOLVED / UNRESOLVED] Mitigation: [If applicable] Source: [Document IDs, links, or references] 3. RISK REASSESSMENT - Updated Risk Score: [0–100] - Updated Risk Tier: LOW / MEDIUM / HIGH - Material Change from Initial Screening: YES / NO 4. FINAL DECISION - EDD Outcome: APPROVE / CONDITIONAL APPROVAL / REJECT - Business Justification: [50–150 words] - Conditions (if applicable): [Specific requirements or monitoring triggers] - Compliance Officer Recommendation: [Signature & Date] - CFO/CEO Approval (if High-Risk): [Signature & Date] 5. AUDIT TRAIL - All investigative files linked and dated - Source citations - Decision rationale documented
ONGOING MONITORING ALERT & ACTION LOG Vendor Name: [Legal Entity Name] Monitoring Period: [Month/Quarter, Year] Report Generated: [Timestamp] 1. MONITORING ACTIVITIES COMPLETED - Sanctions Re-screening: ✓ COMPLETED [Date] - Adverse Media Review: ✓ COMPLETED [Date] - Litigation Tracking Update: ✓ COMPLETED [Date] - [Other activities as per tier] 2. ALERTS & FINDINGS [If no alerts:] No material changes detected. Vendor remains in compliance. [If alerts triggered:] Alert ID | Alert Type | Date Detected | Severity | Status | Action Required [Rows for each alert] 3. ACTION ITEMS Action ID | Vendor | Action | Owner | Due Date | Status [Rows for each action] 4. RECERTIFICATION TRACKING - Last Recertification: [Date] - Next Recertification Due: [Date] - Recertification Status: ON TRACK / AT RISK / OVERDUE 5. MONITORING ADJUSTMENT (if any) - Frequency Change: [If applicable, new cadence & rationale] - New Monitoring Triggers: [If added] - Subprocessor Changes: [If applicable] 6. Compliance Officer Sign-Off: [Signature & Date]
Knowledge Nugget: UBO verification in multi-tier structures requires tracing ownership chains through beneficial ownership registries (e.g., UK PSC Register, EU beneficial ownership databases) and corporate filings. Start by identifying the immediate parent entity; then iterate upward until you reach an individual (natural person) with ≥25% ownership. For complex international structures, cross-reference corporate registries in each jurisdiction and request notarized beneficial ownership declarations from the vendor. Resolution threshold: UBO confirmed within 3 ownership tiers with matching documentation. Escalation trigger: UBO remains unknown after registry query + vendor query, or shell entities are used explicitly to obscure ownership. Diligard role: Automates entity-graph linkage mapping (ownership chains) and cross-registry verification, surfacing missing layers or conflicting data in minutes.
Knowledge Nugget: A sanctions hit occurs when a vendor’s name (or a beneficial owner’s name) matches a name on OFAC, EU Sanctions, or UK HM Treasury lists. False positives are matches that result from name similarity (e.g., “John Smith”) rather than identity confirmation. Confidence scoring mitigates this: Diligard uses multi-field matching (name + date of birth + jurisdiction + entity type) and assigns a confidence score (0–100). Decision logic: Hits with confidence >80% and name + DOB + country match = escalate to Enhanced Due Diligence (request vendor denial & counter-evidence). Hits with confidence <50% (e.g., common name match only) = investigate alias variants and entity type; if no secondary match, likely false positive = CLEAR. Critical rule: Zero tolerance for confirmed sanctions hits; any hit >70% confidence triggers rejection unless vendor produces credible counter-evidence (court ruling, sanctions delisting, or official government denial). Diligard role: Normalizes name variants (transliterations, nicknames) and applies multi-field confidence weighting to reduce false positives while flagging all credible matches.
Knowledge Nugget: Ongoing monitoring cadence is risk-tier dependent. Low-Risk vendors: annual sanctions re-screen, annual adverse media review, no PEP re-check (unless jurisdiction changes). Medium-Risk vendors: quarterly sanctions re-screen, monthly adverse media review, semi-annual PEP verification. High-Risk vendors: monthly sanctions re-screen, real-time (daily) adverse media monitoring, quarterly PEP re-check. Why the cadence varies: Sanctions lists update weekly (OFAC, EU, UK); adverse media can surface suddenly (triggering rapid escalation); PEP status is typically static but changes if individual assumes new political role. Practical triggers: Set monitoring alerts based on tier; automate sanctions re-screening via API feeds; subscribe to court docket alerts for litigation changes. Documentation: Maintain a monitoring calendar with due dates; escalate any alert within 48 hours of detection. Diligard role: Automates scheduled re-screening runs; flags new sanctions matches, adverse media items, and litigation filings in a single consolidated alert; enables real-time monitoring for High-Risk vendors.
Knowledge Nugget: First step: Assess materiality. Pull the court docket (if public); determine case type (civil contract dispute vs. fraud vs. criminal) and stage (filed vs. ongoing vs. concluded). Escalation trigger: Active criminal case OR civil fraud allegation OR regulatory enforcement action = escalate immediately. Routine civil contract dispute (unrelated to compliance/data handling) = continue monitoring; escalate only if litigation outcome is adverse or reaches settlement >$1M. Action: Request vendor’s litigation summary and response; add litigation case ID to monitoring watchlist (auto-alert if judgment rendered or settlement announced). Documentation: Log incident in ongoing monitoring alert; update vendor’s risk profile if case is material; assess whether insurance or financial health is impaired (if applicable to vendor capability). Recertification impact: If active litigation is material and unresolved at recertification, elevate recertification frequency (e.g., from annual to semi-annual). Diligard role: Streams court filings via docket alerts; classifies case type and party roles (vendor as plaintiff vs. defendant); flags material outcomes (judgment, settlement, sanctions) triggering escalation thresholds.
Knowledge Nugget: Audit-ready documentation requires three artifacts per vendor: (1) Initial Screening Report: signed-off screening results, risk score, decision (APPROVE/ESCALATE/REJECT), data sources, and decision rationale. (2) Escalation File (if applicable): investigative steps taken, evidence reviewed, findings, mitigation, and final decision with CFO/CEO sign-off (for High-Risk). (3) Ongoing Monitoring Log: recertification attestations, alert summaries, remediation actions, and recertification outcomes. Storage & accessibility: Centralize all artifacts in a vendor master file (digital vault with date-stamped entries, searchable by vendor ID and screening ID). Key audit-trail elements: (a) Screening date & screened-by signature, (b) Data sources with version/update dates, (c) Decision thresholds applied (e.g., “sanctions hit >70% confidence = escalate”), (d) Any policy exceptions documented with CFO/CEO approval, (e) Escalation rationale in 50–100 words (clarity for auditors), (f) Timeline of actions (EDD initiated → completed → decision made → vendor notified). Regulator expectations: FATF, AML frameworks, and ISO 37301 all expect documented risk assessment, source attribution, and escalation logic; auditors will ask “Why did you approve this vendor?” or “Why didn’t you flag this risk?” — your documentation must answer conclusively. Diligard role: Auto-generates audit-ready reports with source citations, decision timestamps, and version control; enables one-click export of complete screening file for regulatory review.
Strengthen audit preparedness with Diligard’s legal compliance intelligence and family office risk management capabilities.
| Risk Score | UBO Status | Sanctions Hit | PEP Status | Adverse Media | Decision |
|---|---|---|---|---|---|
| 0–20 | VERIFIED | CLEAR | NOT PEP | CLEAR | APPROVE |
| 21–40 | VERIFIED | CLEAR | LOW-RISK PEP | MINOR | ESCALATE (review PEP/media) |
| 21–40 | INCOMPLETE | CLEAR | NOT PEP | CLEAR | ESCALATE (request UBO docs) |
| 41–70 | ANY | CLEAR | HIGH-RISK PEP | ANY | ESCALATE (Enhanced Due Diligence) |
| 41–70 | ANY | HIT (<70% confidence) | ANY | ANY | ESCALATE (alias verification) |
| >70 | ANY | HIT (>70% confidence) | ANY | ANY | REJECT (unless counter-evidence) |
| ANY | ANY | ANY | ANY | CRIMINAL/FRAUD | REJECT |
| Red Flag Resolved? | Vendor Response Quality | Risk Tier Reassignment | EDD Outcome |
|---|---|---|---|
| YES (credible explanation) | Timely, complete documentation | LOW → LOW / MEDIUM | APPROVE |
| PARTIAL (some gaps remain) | Incomplete; request follow-up | MEDIUM → MEDIUM / HIGH | CONDITIONAL APPROVAL + monitoring |
| NO (unresolved) | No response; insufficient evidence | HIGH | REJECT |
| YES (but materiality high) | Strong evidence, but business risk high | ANY → HIGH | CONDITIONAL APPROVAL + escalated monitoring |
Apply these frameworks across all vendor risk categories, from contractor background screening to supply chain ESG risk assessment.
All vendors must pass baseline identity, ownership, and sanctions checks before engagement. The table below defines minimum requirements and hard escalation triggers.
| Data Point | Source | Decision Threshold | Escalation Trigger |
|---|---|---|---|
| Entity Identity & Registration | Corporate registries (national + international) | Valid registration + matching legal name | Missing or fraudulent registration |
| Ultimate Beneficial Owner (UBO) | Public registries, beneficial ownership DB, corporate filings | UBO identified & verified; ownership chain ≤3 tiers | UBO obscured; shell entities detected; ownership unclear |
| Sanctions Screening | OFAC, EU Sanctions, UK HM Treasury lists | Zero hits on primary + alias name variants | Any hit; confidence score >70% |
| PEP Status | PEP databases (jurisdictional tiers) | No PEP association OR low-risk PEP (non-sanctioning jurisdiction) | High-risk PEP; PEP in sanctioning regime; family ties to HVT |
| Adverse Media (12-month window) | News feeds, regulatory databases, litigation records | Zero credible negative coverage | Credible allegations; regulatory action; litigation pending |
| Data Freshness | Source metadata (last update timestamp) | Data <90 days old (UBO), <30 days old (Sanctions) | Stale data; incomplete verification trail |
Red flags from initial screening demand deeper investigation. This phase determines whether mitigation is viable or rejection is mandatory.
| Red Flag Category | Enhanced Check | Evidence Required | Resolution Threshold | Rejection Trigger |
|---|---|---|---|---|
| UBO Incongruity | Request UBO certification letter; verify via beneficial ownership registry | Signed UBO declaration + registry match (name, ID, %) | UBO confirmed within 2 tiers; explanation for shell entities documented | UBO remains unknown after registry + client query; shell entity used to obscure ownership |
| PEP Presence (High-Risk) | Classify PEP type (head of state, family, associate); assess sanctioning regime nexus | PEP status confirmation from authoritative source; sanction list cross-check | PEP status accepted with mitigation (e.g., no sanctioning regime ties); business justification documented | PEP tied to OFAC/EU/UK sanctioning regime; family relation to HVT (High-Value Target) |
| Litigation History | Obtain case summaries, outcome, and recency; assess materiality to vendor capability | Court filings, docket records, settlement docs | Litigation concluded >2 years ago; resolved favorably or immaterial to vendor capability | Active criminal case; repeated civil fraud findings; regulatory fine >$5M or capability-critical outcome |
| Adverse Media (Credible) | Validate media source credibility; assess severity (allegation vs. conviction vs. rumor) | Primary source (court filing, regulatory notice) vs. secondary (news aggregation) | Allegation without conviction; media coverage credible but unsubstantiated; documented rebuttal accepted | Regulatory conviction; repeated substantiated allegations; media coverage from Tier-1 sources with corroborating evidence |
| Data Quality Gaps | Request missing documentation; cross-verify via alternate registries | Notarized corporate filings; beneficial ownership registry extracts | Documentation gaps resolved; alternate source confirms data | After 15 calendar days, vendor fails to provide required documentation; alternate registry sources conflict materially |
| Sanctioning Regime Change | Re-screen against updated sanctions lists (weekly feed check) | Sanctions list version date; updated screening report | No new hits post-update | New sanctions hit post-initial screening |
Final approval requires audit-ready documentation and locked recertification schedules. The table below defines mandatory artifacts and ownership.
| Artifact | Owner | Requirement | Storage |
|---|---|---|---|
| Screening Report | Compliance Officer | Signed off; includes data sources, decision rationale, risk score | Vendor master file (audit trail) |
| UBO Verification Record | Compliance Officer | Beneficial ownership chain + registry extract + update frequency | Vendor master file |
| Sanctions Match Certificate | Compliance Officer | List version, date screened, name variants checked, zero-hit confirmation | Vendor master file |
| Risk Rating & Tier Assignment | Compliance Officer | Assigned tier (Low/Medium/High); monitoring cadence linked | Vendor master file + monitoring schedule |
| Vendor Acknowledgment | Vendor Legal/Compliance | Signed attestation of compliance obligations + ongoing disclosure duty | Contract amendment or standalone letter |
| Recertification Schedule | Compliance Officer | Recertification date (baseline 12–24 months per tier); monitoring trigger list | Compliance calendar + alert system |
| Subprocessor Pre-Approval (if applicable) | Compliance Officer | Vendor’s list of third-party processors; each pre-screened per Initial Screening checklist | Vendor master file; subprocessor register |
Post-engagement risk shifts demand continuous surveillance. Monitoring frequency scales to vendor risk tier; escalation thresholds are non-negotiable.
| Monitoring Activity | Cadence | Data Source | Escalation Trigger | Action |
|---|---|---|---|---|
| Sanctions Re-screening | Monthly (High-Risk) / Quarterly (Medium) / Annually (Low) | OFAC, EU, UK lists (automated feed) | New sanctions hit; alias match with confidence >50% | Escalate to Enhanced Due Diligence; consider vendor disengagement |
| UBO Verification Update | Quarterly (High-Risk) / Annually (Medium/Low) | Public registries; beneficial ownership databases | UBO change; ownership structure shift >10% | Request updated UBO certification; assess materiality |
| Adverse Media Monitoring | Monthly (High-Risk) / Quarterly (Medium) | News feeds, court docket alerts, regulatory databases | Credible adverse media within recency window (12 months); regulatory action filed | Escalate; assess materiality; request vendor response |
| Litigation Tracking | Quarterly (High-Risk) / Annually (Medium/Low) | Court dockets, regulatory databases, litigation alerts | New civil/criminal case filed against vendor; regulatory enforcement action | Escalate; request case summary; assess impact on vendor capability |
| Recertification Review | 12–24 months (per tier assignment) | Vendor re-questionnaire; updated documentation | Failed recertification; missing documentation; control gaps | Conditional approval with monitoring; escalate for legal review |
| Transactional Anomaly Detection | Monthly | Transaction analytics (if integrated) | Unusual payment patterns; geographic or volume spikes | Manual investigation; escalate if correlated with adverse event |
| Subprocessor Changes | Ongoing (notification-triggered) | Vendor disclosure + pre-approval gate | Vendor adds subprocessor without pre-approval; subprocessor fails ongoing monitoring | Escalate; pause affected transactions pending subprocessor clearance |
Diligard automates the data-gathering layer; compliance officers retain all escalation and mitigation judgment. The division is strict.
See also: Legal Compliance Intelligence | Supply Chain ESG Risk
VENDOR ONBOARDING SCREENING REPORT Vendor Name: [Legal Entity Name] Screening Date: [ISO Date] Screening ID: [Unique Report ID] Screened By: [Compliance Officer Name] 1. ENTITY REGISTRATION - Registered Jurisdiction: [Country/State] - Registration Number: [ID] - Legal Name Match: ✓ PASS / ✗ FAIL - Source: [Registry Name, Last Updated: Date] 2. ULTIMATE BENEFICIAL OWNER (UBO) - UBO Identified: ✓ YES / ✗ NO - UBO Name(s): [Name(s)] - Ownership Tier(s): [Tier 1 → Tier 2 → ... → UBO] - Ownership %: [Cumulative %] - Verification Source: [Registry, Last Updated: Date] - Shell Entity Detected: ✓ YES / ✗ NO - Verification Status: COMPLETE / INCOMPLETE / ESCALATE 3. SANCTIONS SCREENING - OFAC Screening: 0 Hits / [# Hits] - EU Sanctions Screening: 0 Hits / [# Hits] - UK HM Treasury Screening: 0 Hits / [# Hits] - Alias Variants Checked: [Count] - Highest Confidence Score: [Score] - Sanctions Status: CLEAR / ESCALATE / REJECT 4. PEP STATUS - PEP Classification: NOT PEP / LOW-RISK PEP / HIGH-RISK PEP - PEP Jurisdiction(s): [If applicable] - Sanctioning Regime Nexus: NO / YES [Regime name] - Source: [PEP Database, Last Updated: Date] 5. ADVERSE MEDIA (12-Month Window) - Adverse Media Detected: NO / YES - Media Items: [Count & Summary] - Credibility Assessment: Low / Medium / High - Severity: Allegation / Regulatory Action / Criminal Conviction - Recency: [Most recent date] - Adverse Media Status: CLEAR / ESCALATE 6. DATA QUALITY ASSESSMENT - UBO Data Freshness: [Days old] - Sanctions List Version: [Date] - Data Provenance: [Source breakdown] - Gaps Identified: [List or NONE] 7. RISK SCORE & DECISION - Risk Score: [0–100] - Risk Tier: LOW / MEDIUM / HIGH - Initial Screening Decision: APPROVE / ESCALATE / REJECT - Rationale: [50–100 words] - Escalation Triggers (if applicable): [List] 8. DOCUMENTATION & AUDIT TRAIL - Report Generated: [Timestamp, System] - Data Sources: [List with versions] - Next Review Date: [Date for recertification] - Compliance Officer Sign-Off: [Signature & Date]
ENHANCED DUE DILIGENCE SUMMARY Vendor Name: [Legal Entity Name] Initial Screening ID: [Reference] EDD Initiation Date: [ISO Date] EDD Completion Date: [ISO Date] 1. ESCALATION TRIGGERS (From Initial Screening) - Trigger 1: [Red Flag Category & Description] - Trigger 2: [Red Flag Category & Description] 2. INVESTIGATIVE FINDINGS [For each trigger:] Trigger: [Red Flag] Investigation: [Description of steps taken] Evidence: [Documents reviewed, sources consulted] Finding: [Outcome: RESOLVED / UNRESOLVED] Mitigation: [If applicable] Source: [Document IDs, links, or references] 3. RISK REASSESSMENT - Updated Risk Score: [0–100] - Updated Risk Tier: LOW / MEDIUM / HIGH - Material Change from Initial Screening: YES / NO 4. FINAL DECISION - EDD Outcome: APPROVE / CONDITIONAL APPROVAL / REJECT - Business Justification: [50–150 words] - Conditions (if applicable): [Specific requirements or monitoring triggers] - Compliance Officer Recommendation: [Signature & Date] - CFO/CEO Approval (if High-Risk): [Signature & Date] 5. AUDIT TRAIL - All investigative files linked and dated - Source citations - Decision rationale documented
ONGOING MONITORING ALERT & ACTION LOG Vendor Name: [Legal Entity Name] Monitoring Period: [Month/Quarter, Year] Report Generated: [Timestamp] 1. MONITORING ACTIVITIES COMPLETED - Sanctions Re-screening: ✓ COMPLETED [Date] - Adverse Media Review: ✓ COMPLETED [Date] - Litigation Tracking Update: ✓ COMPLETED [Date] - [Other activities as per tier] 2. ALERTS & FINDINGS [If no alerts:] No material changes detected. Vendor remains in compliance. [If alerts triggered:] Alert ID | Alert Type | Date Detected | Severity | Status | Action Required [Rows for each alert] 3. ACTION ITEMS Action ID | Vendor | Action | Owner | Due Date | Status [Rows for each action] 4. RECERTIFICATION TRACKING - Last Recertification: [Date] - Next Recertification Due: [Date] - Recertification Status: ON TRACK / AT RISK / OVERDUE 5. MONITORING ADJUSTMENT (if any) - Frequency Change: [If applicable, new cadence & rationale] - New Monitoring Triggers: [If added] - Subprocessor Changes: [If applicable] 6. Compliance Officer Sign-Off: [Signature & Date]
Knowledge Nugget: UBO verification in multi-tier structures requires tracing ownership chains through beneficial ownership registries (e.g., UK PSC Register, EU beneficial ownership databases) and corporate filings. Start by identifying the immediate parent entity; then iterate upward until you reach an individual (natural person) with ≥25% ownership. For complex international structures, cross-reference corporate registries in each jurisdiction and request notarized beneficial ownership declarations from the vendor. Resolution threshold: UBO confirmed within 3 ownership tiers with matching documentation. Escalation trigger: UBO remains unknown after registry query + vendor query, or shell entities are used explicitly to obscure ownership. Diligard role: Automates entity-graph linkage mapping (ownership chains) and cross-registry verification, surfacing missing layers or conflicting data in minutes.
Knowledge Nugget: A sanctions hit occurs when a vendor’s name (or a beneficial owner’s name) matches a name on OFAC, EU Sanctions, or UK HM Treasury lists. False positives are matches that result from name similarity (e.g., “John Smith”) rather than identity confirmation. Confidence scoring mitigates this: Diligard uses multi-field matching (name + date of birth + jurisdiction + entity type) and assigns a confidence score (0–100). Decision logic: Hits with confidence >80% and name + DOB + country match = escalate to Enhanced Due Diligence (request vendor denial & counter-evidence). Hits with confidence <50% (e.g., common name match only) = investigate alias variants and entity type; if no secondary match, likely false positive = CLEAR. Critical rule: Zero tolerance for confirmed sanctions hits; any hit >70% confidence triggers rejection unless vendor produces credible counter-evidence (court ruling, sanctions delisting, or official government denial). Diligard role: Normalizes name variants (transliterations, nicknames) and applies multi-field confidence weighting to reduce false positives while flagging all credible matches.
Knowledge Nugget: Ongoing monitoring cadence is risk-tier dependent. Low-Risk vendors: annual sanctions re-screen, annual adverse media review, no PEP re-check (unless jurisdiction changes). Medium-Risk vendors: quarterly sanctions re-screen, monthly adverse media review, semi-annual PEP verification. High-Risk vendors: monthly sanctions re-screen, real-time (daily) adverse media monitoring, quarterly PEP re-check. Why the cadence varies: Sanctions lists update weekly (OFAC, EU, UK); adverse media can surface suddenly (triggering rapid escalation); PEP status is typically static but changes if individual assumes new political role. Practical triggers: Set monitoring alerts based on tier; automate sanctions re-screening via API feeds; subscribe to court docket alerts for litigation changes. Documentation: Maintain a monitoring calendar with due dates; escalate any alert within 48 hours of detection. Diligard role: Automates scheduled re-screening runs; flags new sanctions matches, adverse media items, and litigation filings in a single consolidated alert; enables real-time monitoring for High-Risk vendors.
Knowledge Nugget: First step: Assess materiality. Pull the court docket (if public); determine case type (civil contract dispute vs. fraud vs. criminal) and stage (filed vs. ongoing vs. concluded). Escalation trigger: Active criminal case OR civil fraud allegation OR regulatory enforcement action = escalate immediately. Routine civil contract dispute (unrelated to compliance/data handling) = continue monitoring; escalate only if litigation outcome is adverse or reaches settlement >$1M. Action: Request vendor’s litigation summary and response; add litigation case ID to monitoring watchlist (auto-alert if judgment rendered or settlement announced). Documentation: Log incident in ongoing monitoring alert; update vendor’s risk profile if case is material; assess whether insurance or financial health is impaired (if applicable to vendor capability). Recertification impact: If active litigation is material and unresolved at recertification, elevate recertification frequency (e.g., from annual to semi-annual). Diligard role: Streams court filings via docket alerts; classifies case type and party roles (vendor as plaintiff vs. defendant); flags material outcomes (judgment, settlement, sanctions) triggering escalation thresholds.
Knowledge Nugget: Audit-ready documentation requires three artifacts per vendor: (1) Initial Screening Report: signed-off screening results, risk score, decision (APPROVE/ESCALATE/REJECT), data sources, and decision rationale. (2) Escalation File (if applicable): investigative steps taken, evidence reviewed, findings, mitigation, and final decision with CFO/CEO sign-off (for High-Risk). (3) Ongoing Monitoring Log: recertification attestations, alert summaries, remediation actions, and recertification outcomes. Storage & accessibility: Centralize all artifacts in a vendor master file (digital vault with date-stamped entries, searchable by vendor ID and screening ID). Key audit-trail elements: (a) Screening date & screened-by signature, (b) Data sources with version/update dates, (c) Decision thresholds applied (e.g., “sanctions hit >70% confidence = escalate”), (d) Any policy exceptions documented with CFO/CEO approval, (e) Escalation rationale in 50–100 words (clarity for auditors), (f) Timeline of actions (EDD initiated → completed → decision made → vendor notified). Regulator expectations: FATF, AML frameworks, and ISO 37301 all expect documented risk assessment, source attribution, and escalation logic; auditors will ask “Why did you approve this vendor?” or “Why didn’t you flag this risk?” — your documentation must answer conclusively. Diligard role: Auto-generates audit-ready reports with source citations, decision timestamps, and version control; enables one-click export of complete screening file for regulatory review.
| Risk Score | UBO Status | Sanctions Hit | PEP Status | Adverse Media | Decision |
|---|---|---|---|---|---|
| 0–20 | VERIFIED | CLEAR | NOT PEP | CLEAR | APPROVE |
| 21–40 | VERIFIED | CLEAR | LOW-RISK PEP | MINOR | ESCALATE (review PEP/media) |
| 21–40 | INCOMPLETE | CLEAR | NOT PEP | CLEAR | ESCALATE (request UBO docs) |
| 41–70 | ANY | CLEAR | HIGH-RISK PEP | ANY | ESCALATE (Enhanced Due Diligence) |
| 41–70 | ANY | HIT (<70% confidence) | ANY | ANY | ESCALATE (alias verification) |
| >70 | ANY | HIT (>70% confidence) | ANY | ANY | REJECT (unless counter-evidence) |
| ANY | ANY | ANY | ANY | CRIMINAL/FRAUD | REJECT |
| Red Flag Resolved? | Vendor Response Quality | Risk Tier Reassignment | EDD Outcome |
|---|---|---|---|
| YES (credible explanation) | Timely, complete documentation | LOW → LOW / MEDIUM | APPROVE |
| PARTIAL (some gaps remain) | Incomplete; request follow-up | MEDIUM → MEDIUM / HIGH | CONDITIONAL APPROVAL + monitoring |
| NO (unresolved) | No response; insufficient evidence | HIGH | REJECT |
| YES (but materiality high) | Strong evidence, but business risk high | ANY → HIGH | CONDITIONAL APPROVAL + escalated monitoring |
Ongoing monitoring prevents post-engagement risk drift; recertification cadence, escalation triggers, and transactional alerts must align with the vendor’s assigned risk tier. Compliance officers who fail to maintain disciplined monitoring expose their organization to sanctions violations, ownership changes, and adverse events that emerge months or years after initial approval.
| Monitoring Activity | Cadence | Data Source | Escalation Trigger | Action |
|---|---|---|---|---|
| Sanctions Re-screening | Monthly (High-Risk) / Quarterly (Medium) / Annually (Low) | OFAC, EU Sanctions, UK HM Treasury lists (automated feed) | New sanctions hit; alias match with confidence >50% | Escalate to Enhanced Due Diligence; consider vendor disengagement |
| UBO Verification Update | Quarterly (High-Risk) / Annually (Medium/Low) | Public registries; beneficial ownership databases | UBO change; ownership structure shift >10% | Request updated UBO certification; assess materiality |
| Adverse Media Monitoring | Monthly (High-Risk) / Quarterly (Medium) | News feeds, court docket alerts, regulatory databases | Credible adverse media within recency window (12 months); regulatory action filed | Escalate; assess materiality; request vendor response |
| Litigation Tracking | Quarterly (High-Risk) / Annually (Medium/Low) | Court dockets, regulatory databases, litigation alerts | New civil/criminal case filed against vendor; regulatory enforcement action | Escalate; request case summary; assess impact on vendor capability |
| Recertification Review | 12–24 months (per tier assignment) | Vendor re-questionnaire; updated documentation | Failed recertification; missing documentation; control gaps | Conditional approval with monitoring; escalate for legal review |
| Transactional Anomaly Detection | Monthly | Transaction analytics (if integrated) | Unusual payment patterns; geographic or volume spikes | Manual investigation; escalate if correlated with adverse event |
| Subprocessor Changes | Ongoing (notification-triggered) | Vendor disclosure + pre-approval gate | Vendor adds subprocessor without pre-approval; subprocessor fails ongoing monitoring | Escalate; pause affected transactions pending subprocessor clearance |
OFAC, EU, and UK HM Treasury lists update weekly; any vendor name match post-initial screening triggers mandatory escalation. Cross-reference alias variants and entity types; confidence scores >50% require immediate Enhanced Due Diligence. Zero tolerance applies: confirmed sanctions hits mandate vendor disengagement unless the vendor produces official delisting documentation or government denial within 15 calendar days.
Ownership shifts >10% signal potential control changes; shell entity insertion or beneficial owner replacement demands UBO recertification within 30 days. Request notarized beneficial ownership declarations and cross-verify via corporate registries. Escalation threshold: UBO remains unverified after 30 days or new UBO appears on PEP or sanctions lists.
Adverse media alerts require credibility assessment: Tier-1 sources (regulatory filings, court dockets, recognized news outlets) trigger escalation; Tier-2 sources (aggregators, unverified blogs) require corroboration. Escalation logic: credible allegations of fraud, bribery, sanctions violations, or criminal activity = escalate immediately. Routine civil disputes or unsubstantiated rumors = log and monitor; escalate only if corroborated or litigation filed.
New civil or criminal cases demand case-type classification. Criminal cases, regulatory enforcement actions, or civil fraud allegations = immediate escalation. Routine contract disputes unrelated to vendor capability = continue monitoring; escalate if judgment exceeds $1M or impairs vendor operations. Request vendor’s litigation summary, case docket, and legal counsel response; assess whether insurance or financial stability is compromised.
Missed recertification deadlines, incomplete documentation, or vendor refusal to attest compliance obligations = conditional approval hold. Pause new transactions; set 15-day remediation window. If vendor fails to recertify within 30 days, escalate for legal review and consider disengagement. Document recertification failure rationale and remediation actions taken.
Vendors adding third-party processors without pre-approval violate onboarding conditions. Escalate immediately; run Initial Screening Checklist on new subprocessor. If subprocessor fails sanctions screening, PEP checks, or adverse media review, pause transactions routed through that subprocessor pending clearance or vendor substitution. Maintain subprocessor register with screening dates, risk scores, and approval status.
Every monitoring cycle generates a timestamped summary report with screening updates, alert logs, and remediation actions. Archive monitoring artifacts in the vendor master file: recertification attestations (vendor + compliance officer sign-off), escalation incident logs (trigger, investigation, resolution), and ongoing risk score updates. Regulators expect documented evidence that monitoring cadence matched assigned risk tier and that escalation thresholds were applied consistently.
ONGOING MONITORING REPORT Vendor Name: [Legal Entity Name] Monitoring Period: [Month/Quarter, Year] Risk Tier: LOW / MEDIUM / HIGH Report Generated: [Timestamp] 1. SCREENING ACTIVITIES COMPLETED - Sanctions Re-screening: ✓ COMPLETED [Date] | Result: CLEAR / ESCALATE - Adverse Media Review: ✓ COMPLETED [Date] | Items Detected: [Count] | Severity: [Classification] - Litigation Tracking: ✓ COMPLETED [Date] | New Cases: [Count] | Material: YES / NO - UBO Verification: ✓ COMPLETED [Date] | Ownership Change: YES / NO - [Additional activities per tier] 2. ALERTS & ESCALATION TRIGGERS [If no alerts:] No material changes detected. Vendor remains in compliance. [If alerts triggered:] Alert ID | Alert Type | Date Detected | Severity | Status | Action Taken [001] | [Sanctions Hit - Alias Match] | [Date] | [HIGH] | [ESCALATED] | [EDD Initiated; Vendor Response Requested] [002] | [Adverse Media - Regulatory Action] | [Date] | [MEDIUM] | [MONITORING] | [Case Summary Requested; Review Pending] 3. RECERTIFICATION STATUS - Last Recertification: [Date] - Next Recertification Due: [Date] - Recertification Status: ON TRACK / AT RISK / OVERDUE - Documentation Gaps (if any): [List or NONE] 4. RISK SCORE UPDATE - Previous Risk Score: [Score] - Current Risk Score: [Score] - Risk Tier Change: YES [Old → New] / NO - Rationale for Change: [If applicable] 5. MONITORING ADJUSTMENT (if any) - Frequency Change: [New cadence & rationale] - New Monitoring Triggers: [If added] - Subprocessor Changes: [If applicable; pre-approval status] 6. ACTION ITEMS Action ID | Description | Owner | Due Date | Status [A01] | [Request UBO certification letter] | [Compliance Officer] | [Date] | [OPEN] [A02] | [Review litigation outcome] | [Legal] | [Date] | [IN PROGRESS] 7. COMPLIANCE OFFICER SIGN-OFF Reviewed By: [Name] Signature: [Digital/Physical] Date: [ISO Date]
Diligard automates scheduled re-screening runs (sanctions, PEP, adverse media, litigation) and consolidates alerts into a single dashboard. Real-time monitoring for High-Risk vendors streams daily sanctions list updates, court docket filings, and adverse media hits. Compliance officers receive timestamped alerts with source citations, confidence scores, and pre-configured escalation thresholds, enabling judgment calls within hours instead of weeks.
Vendor: Payment processor with PEP-linked UBO; Medium-Risk at onboarding; elevated to High-Risk due to ownership change.
Monitoring Cadence: Monthly sanctions re-screen; real-time adverse media; quarterly UBO verification; monthly transactional anomaly review.
Alert Triggered: Month 3 — Adverse media reports regulatory investigation by financial authority in vendor’s jurisdiction.
Action: Compliance officer requests vendor’s regulatory response and legal counsel summary within 7 days. Vendor provides documentation showing investigation closed with no penalties. Compliance officer logs resolution; continues monthly monitoring. Risk score updated from 68 to 62; remains High-Risk tier.
Vendor: Cloud infrastructure provider; Medium-Risk due to cross-border data processing.
Monitoring Cadence: Quarterly sanctions re-screen; quarterly adverse media review; annual UBO verification.
Alert Triggered: Quarter 2 — UBO verification update detects 12% ownership shift; new beneficial owner identified.
Action: Compliance officer requests notarized UBO certification and beneficial ownership registry extract. New UBO screened via Initial Screening Checklist: no sanctions hits, no PEP status, no adverse media. Ownership change documented; risk score unchanged; recertification scheduled for Quarter 4.
Vendor: Office supply distributor; Low-Risk at onboarding; no adverse signals.
Monitoring Cadence: Annual sanctions re-screen; annual recertification; quarterly adverse media review (automated).
Alert Triggered: Year 1 — No alerts detected. Recertification due.
Action: Compliance officer sends recertification questionnaire; vendor returns signed attestation and updated corporate documentation within 10 days. No material changes; risk score remains 18; recertification approved; next cycle scheduled for Year 2.
Trigger: Vendor misses recertification deadline or returns incomplete documentation.
Day 1: Automated alert to compliance officer; vendor notified of overdue recertification.
Day 7: Second notification; set 15-day hard deadline.
Day 15: If no response, escalate to legal and procurement; pause new transactions.
Day 30: If vendor still non-responsive, initiate disengagement review; document failure rationale; archive vendor file with “FAILED RECERTIFICATION” flag.
Audit Trail: Recertification request timestamps, vendor responses (or lack thereof), escalation notices, and disengagement decision log.
| Alert Type | Severity | Immediate Action | Escalation Threshold | Outcome |
|---|---|---|---|---|
| Sanctions Hit (New) | HIGH | Pause transactions; request vendor denial + counter-evidence within 7 days | Confidence >50%; no credible counter-evidence after 15 days | DISENGAGEMENT |
| UBO Change | MEDIUM | Request updated UBO certification; screen new UBO via Initial Screening Checklist | New UBO fails sanctions/PEP check; ownership structure obscured | ESCALATE to EDD |
| Adverse Media (Credible) | MEDIUM / HIGH | Request vendor response; assess credibility and materiality | Regulatory action filed; criminal allegation; fraud conviction | ESCALATE to EDD or DISENGAGEMENT |
| Litigation Filed | MEDIUM | Pull case docket; request vendor litigation summary | Criminal case; regulatory enforcement; civil fraud; judgment >$1M | ESCALATE to EDD |
| Recertification Missed | MEDIUM | Send overdue notice; set 15-day hard deadline | No response after 30 days; repeated failures | DISENGAGEMENT |
| Subprocessor Added | LOW / MEDIUM | Run Initial Screening on subprocessor; request vendor justification | Subprocessor fails sanctions/PEP screening; unapproved addition | PAUSE transactions until clearance |
| Transactional Anomaly | LOW / MEDIUM | Manual investigation; correlate with adverse events | Anomaly + adverse media/sanctions hit = possible financial crime | ESCALATE to EDD |
MONITORING ALERT LOG ENTRY Alert ID: 2024-Q2-VEN-047-ADV Vendor Name: [Legal Entity Name] Vendor ID: [Unique Vendor ID] Risk Tier: MEDIUM Alert Date: [ISO Date] Alert Type: Adverse Media - Regulatory Investigation Severity: MEDIUM Source: [Financial Regulatory Authority Press Release] Source Date: [ISO Date] Source URL: [Link] ALERT DETAILS: Regulatory authority announced investigation into vendor's data handling practices. Investigation status: ongoing; no penalties assessed. Vendor cooperation confirmed. IMMEDIATE ACTION TAKEN: - Vendor notified [Date]; response requested within 7 days - Legal counsel summary requested - Monitoring escalated to monthly adverse media review (from quarterly) VENDOR RESPONSE RECEIVED: [Date] - Investigation closed [Date] with no penalties - Corrective action plan implemented; certified by external auditor - Documentation archived in vendor master file RESOLUTION: - Risk score updated: 58 → 55 - Risk tier: MEDIUM (unchanged) - Monitoring frequency: Monthly adverse media review maintained until Q4 recertification - No escalation to Enhanced Due Diligence required COMPLIANCE OFFICER SIGN-OFF: Reviewed By: [Name] Date: [ISO Date] Decision: CONTINUE with escalated monitoring Next Review: [Q3 Monitoring Cycle]
For compliance teams managing 50+ vendors, Diligard’s vendor and partner due diligence platform automates this monitoring architecture, consolidating alerts and enabling risk-based escalation decisions in minutes instead of days. Organizations requiring broader risk coverage can extend monitoring to supply chain ESG risk and legal compliance intelligence, ensuring comprehensive third-party oversight across the vendor lifecycle.