The Portfolio Monitoring service is an optional component of AML Compliance Solutions. It is designed to track entity records for modifications in attributes such as names, status, and risk profile. Upon detecting a record update, the system sends automated event notifications to a customer through a webhook and then exposes the updated data through a secure API endpoint.
The monitoring service operates through three primary layers:
-
Portfolio Storage Layer: Contains historical screening requests and entity profiles, maintaining the operational baseline for all ongoing evaluations.
-
Active Watchlist Ingestion: Continuous ingestion pipelines tracking global watchlist updates, including Office of Foreign Assets Control (OFAC), Politically Exposed Person (PEP), Adverse Media, and Enforcement data sources.
-
Automated Rerunning Engine: Event-driven evaluation infrastructure that automatically re-screens stored portfolio records against watchlist updates using full match-engine logic.
All lists are checked and re-screened whenever list updates are published. Re-evaluations execute silently in the background, surfacing downstream alerts only when a potential match or risk state change is verified.
Contact your Customer Success Manager or contact us at support.kount.com for specific information about update cadence for each data source.
You must set up the metadata.monitoring.processingAction property during request submissions to control entity monitoring.
Caution
In any request where records are stored, updated, or removed, a unique monitoringId must be sent in the request body to maintain identity mapping within the database.
|
processingAction |
System behavior |
|
|
Performs initial screening and automatically loads/UPSERTs the record into the customer portfolio for continuous monitoring. Because it adds the record to the portfolio, a unique |
|
|
Adds/updates the record in the portfolio for monitoring without running an initial screen or returning match results.
|
When an auto-evaluation identifies a match, the system follows a structured human-in-the-loop and event notification workflow:
-
Soft-Hit Generation: The evaluation engine generates a potential match and assigns a status of
machine_soft_hit. -
Alert Queue Routing: Soft hits are routed into the Kount 360 Screening Alerts Queue for review.
-
Analyst Adjudication: Analysts investigate potential matches against playbooks (standard operating procedures for a customer), resolving the item as
analyst_confirm(true positive) oranalyst_false_positive. -
Customer Webhook Notification (URES): Upon resolution, the Screening API dispatches an automated webhook containing the
inquiryId. The client system then fetches full match details by querying GET/v1/inquiries/{id}. -
Monitoring Response: Property values change based on the use case.
The context.origination attribute specifies the original submission channel or event source that generated the screening inquiry.
|
Origination property |
Description |
|
|
Automated re-screening event generated in the background by Monitoring when a connected watchlist updates. |
|
|
High-volume file processing request submitted via Managed File Transfer (MFT) or direct portal upload. |
|
|
Manual, on-demand compliance check initiated directly through the user interface (UI). |
Configuration is determined by the customer's portfolio parameters, such as active data sources, scoring thresholds, and features. Equifax engineers complete the configurations for each tenant.
A customer can override their default portfolio rules, such as subscribed data sources, on individual API requests. For example, opting out of monitoring for specific high-volume or single-use queries.
These examples demonstrate how to use an override across different screening endpoints.
Comments
0 comments
Article is closed for comments.