Publication-bound re-screening
Saved names are evaluated against supported registry publications so monitoring is tied to a recorded data change rather than an unsupported real-time promise.
Continuous Counterparty Monitoring
Know when the evidence behind a counterparty changes.
Embargo re-screens saved counterparties after supported registry publications, records the resulting outcome, and sends configured notifications after a relevant change has been processed.
- 5 saved counterparties on Free
- Up to 250 on Professional
- Up to 2,000 on Business
Reviewable changes
A new match or status change retains the source and screening context needed for a compliance practitioner to assess what changed.
Recorded delivery
Configured email or Slack delivery follows processed monitoring events, with delivery outcomes retained for operational review.
How it works
From saved name to reviewable change
- 01
Save the legal name
Add a screened counterparty to an organisation watchlist and verify the available identity details.
- 02
Process a supported registry publication
Embargo ingests and publishes supported source changes through its integrity-controlled registry process.
- 03
Re-screen the saved population
Affected watchlist entries are evaluated using the current published registry evidence.
- 04
Notify and preserve
Relevant processed changes are delivered through configured channels and retained with their evidence trail.
Important boundary
Continuous monitoring is not a real-time delivery guarantee.
Source publication, collection, registry processing, re-screening, and notification are separate stages. Embargo reports source-specific freshness and degraded states; a polling interval is not an alert-delivery SLA.