Continuous Monitoring
Monitor sanctions risk after onboarding.
Re-screen customers and counterparties when sanctions lists change, receive risk-change alerts, and preserve evidence for compliance review.
Why monitoring matters
Risk changes after onboarding.
A customer cleared today may be sanctioned tomorrow. Continuous monitoring closes the gap between onboarding screening and ongoing compliance obligations.
Sanctions lists update
OFAC, UN, UK, and other authorities publish updates regularly. Entities can be added, modified, or removed.
Aliases change
New aliases, alternative spellings, and transliterations are discovered and published over time.
Entities get newly listed
A previously unknown individual or company may be designated months or years after your first screen.
Counterparties need review
Regulators expect ongoing diligence, not just onboarding checks. Monitoring demonstrates continuous oversight.
How it works
From watchlist to alert.
Add entity
Add a person or company to your watchlist
Monitor lists
Verifex records updates across configured sources
Re-screen
Affected watches are re-screened after source updates
Alert
Configured webhooks receive decision or coverage events
Review
Compliance dashboard queues hits for review
Preserve
Evidence capsule captures the full context
Capabilities
What monitoring delivers.
Scheduled re-screening
Entities on your watchlist are re-screened automatically when configured sanctions lists are updated.
List change monitoring
Configured source updates drive monitoring work. The result records the execution and coverage state rather than assuming every source completed.
Webhook alerts
Growth and above can configure signed, retried webhook delivery for match-change and coverage-degradation events. No public delivery-latency SLO is claimed.
Portfolio monitoring
Monitor hundreds or thousands of entities in a single watchlist. Filter by risk level, source, and review status.
Delta review
Review changed candidates and decisions with their source, coverage and prior-state context. Coverage degradation is a separate operational event, not a clean result.
Evidence export
Export monitoring history and evidence capsules in JSON or CSV for regulatory reporting and audit review.
Audit log
Every re-screening event is logged with timestamps, list versions, and the delta that triggered the alert.
Alert example
Webhook alerts when risk changes.
When a monitoring decision changes after a source update, a configured webhook can receive the same verdict, action, review and coverage facts served for that screen. Coverage degradation is delivered as a separate event and is never represented as clear.
- Illustrative payload fields match the current match-change contract
- Previous and new risk state with the served verdict
- Trigger source and rescreen mode
- Coverage status and review requirement
- Decision identifier for cross-reference
Illustrative screening.match_changed payload
{
"watch_id": "vfx_watch_9a2b4c...",
"name": "Acme Global Ltd",
"previous_risk_level": "clear",
"new_risk_level": "review",
"screening_decision_id": "decision_9f2a4c7e...",
"trigger_source": "OFAC",
"rescreen_mode": "differential",
"verdict": "possible_match",
"recommended_action": "review",
"human_review_required": true,
"coverage_status": "complete"
}Expectations
Timing depends on source and delivery state.
Verifex records source updates and re-screens affected watches. Timing depends on source publication, ingestion, queue work and your webhook endpoint. It is not a public latency commitment. Review the result's coverage state before treating a re-screen as complete.
Get started
Start monitoring your portfolio.
Available on all plans. Watched entities are re-screened when lists update; each rescreen consumes quota. Growth and above. Delivery is signed and retried.