When an entity is added to monitoring, the platform rescreens it automatically whenever the watchlists change. A monitoring hit raises an alert and, when that alert is closed, triggers a webhook with the same illustrative ENS envelope and AML Compliance Solutions payload as an online screening webhook, plus payload.monitoringId and a payload.origination value of monitoring.
|
Property |
Online screening |
Portfolio Monitoring |
|
|
|
|
|
Envelope |
|
Same |
|
|
Screening inquiry UUID and hit group |
Monitoring-hit inquiry UUID and hit group |
|
|
Not applicable |
Present (the monitored entity key) |
Because the original online request's correlationId and inquiryId are not the identifiers of a later monitoring hit, that hit carries its own inquiry UUID. The customer routes the illustrative webhook by payload.origination and reconciles it to the customer record by payload.monitoringId.
For example, the entity 8b6f41e0-57a2-4b89-9c31-000000000001 was onboarded earlier with load_only or the monitored default. Weeks later a watchlist update adds a matching global-sanctions record, and an analyst reviews and confirms it. The monitoring webhook is:
{
"id": "d5fde5cd-44fc-430f-a65e-4acc1aaa9001",
"eventType": "Compliance.Notification",
"apiVersion": "v1",
"clientId": "335246718073365",
"eventDate": "2026-10-06T10:49:51.878081573Z",
"payload": {
"review": "analyst_confirm",
"origination": "monitoring",
"inquiryId": "9f2a1c40-0000-4000-8000-000000009001",
"monitoringId": "8b6f41e0-57a2-4b89-9c31-000000000001",
"groupId": "global-sanctions"
}
}
Retrieval uses the same GET endpoint, with payload.inquiryId as the path UUID and its payload.groupId as the query filter. payload.monitoringId and the envelope Id are not required for this GET:
GET https://api.kount.com/api/compliance/v1/inquiries/9f2a1c40-0000-4000-8000-000000009001?groupId=global-sanctions Authorization: Bearer <access-token>
The proposed group-filtered response has the same illustrative alert view as online retrieval (including remarks and events), with origination: "monitoring" and the monitoringId echoed back:
{
"inquiryId": "9f2a1c40-0000-4000-8000-000000009001",
"groupId": "global-sanctions",
"monitoringId": "8b6f41e0-57a2-4b89-9c31-000000000001",
"origination": "monitoring",
"entityType": "person",
"riskLevel": "critical",
"alertStatus": "closed",
"assignee": "jdoe@bank.example",
"decision": "analyst_confirm",
"decisionReason": "watchlist update matched the monitored individual on name and program",
"createdAt": "2026-10-02T06:15:00Z",
"closedAt": "2026-10-02T13:40:00Z",
"remarks": [
{
"note": "Monitoring hit from the 2026-10-02 OFAC update; confirmed against the entity's passport and DOB on file.",
"author": "jdoe@bank.example",
"createdAt": "2026-10-02T13:35:00Z"
}
],
"events": [
{"description": "monitoring alert created from watchlist delta", "user": "system", "timestamp": "2026-10-02T06:15:00Z"},
{"description": "match hit a7553630-bbc6-474b-a79d-000000009001 decided hit", "user": "jdoe@bank.example", "timestamp": "2026-10-02T13:30:00Z"},
{"description": "alert closed as analyst_confirm", "user": "jdoe@bank.example", "timestamp": "2026-10-02T13:40:00Z"}
],
"matches": [
{
"screeningId": "a7553630-bbc6-474b-a79d-000000009001",
"groupId": "global-sanctions",
"source": {
"dataSet": "OFAC",
"dataSubset": "SDN",
"subcategory": "individual",
"riskType": "critical",
"compositeScore": {"min": 0.97, "avg": 0.97, "max": 0.97}
},
"determination": "machine_soft_hit",
"decision": "analyst_confirm",
"score": 0.97,
"sourceId": "38644",
"riskLevel": "critical",
"reason": [
{"attribute": "name", "score": 0.97}
],
"note": {
"note": "Confirmed against monitored entity's passport and DOB.",
"author": "jdoe@bank.example",
"createdAt": "2026-10-02T13:30:00Z"
},
"details": {
"matchedName": "John DOE",
"sanctionsOrPrograms": [
{"type": "program", "value": "RUSSIA-EO14024"}
]
}
}
]
}
Monitoring webhooks follow the same group-consolidation rule (one webhook per payload.groupId), the same close-only timing (sent when the alert is closed, not when the monitoring hit first opens), and the same at-least-once delivery with ENS envelope Id deduplication as online screening callbacks (pending contract confirmation).
Analysts receive notifications when an automated preliminary match (machine_soft_hit) is investigated and finalized by a compliance analyst in Kount 360.
The analyst update process is as follows:
-
The analyst evaluates the soft hit against customer playbooks and adjudicates the record (for example, marking one or more OFAC or PEP hits as
analyst_confirmoranalyst_false_positive) and then closes the alert. -
The alert closure triggers an outbound webhook sent to the customer's system.
-
The client retrieves the inquiry by using the
GET /v1/inquiries/{id}endpoint, and the response contains review:analyst_confirm(oranalyst_false_positive), along with analyst notes, timestamps, and confirmed hit details.
When external watchlists—such as Office of Foreign Asset Control (OFAC)—publish change updates, Portfolio Monitoring provides the customer with a webhook notification.
The process in which a customer receives a monitoring notification is:
-
Watchlists, such as OFAC, are ingested and checked as frequently as every 30 minutes (and other watchlists daily).
Note
For more specific information about data source update frequency, contact your Customer Success Manager or support@kount.com.
-
Auto-evaluation runs the screening match engine in the background against all active entities stored in the customer's portfolio. No manual resubmission is required.
-
If the match engine detects a delta match or risk-state change for an existing entity, it flags the record and triggers a notification.
-
The system checks the customer notification configuration. If the configuration allows for it, a JSON webhook is delivered to the customer.
-
The customer receives a webhook, and then fetches the complete alert information with the
GET /v1/inquiries/{id}endpoint. The context reflects that the event was generated by background monitoring, such as"origination": "monitoring"and"monitoringChange": true. -
The final step of the flow depends on whether the customer subscribes to our analyst review:
-
If enabled, an analyst review is conducted. Once the analysis is complete, the webhook is triggered to notify the end user about the updated alert.
-
If analyst review is not enabled, the webhook is triggered to notify the end user about the updated alert.
-
Comments
0 comments
Article is closed for comments.