KYC360 Screening Features
Explore the capabilities that power sanctions, PEP, adverse media and watchlist screening across the customer lifecycle.
The below provides a detailed overview of the features available within KYC360 Screening. From sanctions, PEP, RCA and adverse media screening to risk-based matching, ongoing monitoring, case management and audit reporting, the matrix below outlines the platform's capabilities for identifying, assessing and managing financial crime risk.
| Category | Feature | Availability | Description |
| Screening coverage | Sanctions screening | Yes | Screens individuals and organisations against sanctions data. |
| Screening coverage | PEP screening | Yes | Screens for Politically Exposed Persons (PEPs). |
| Screening coverage | RCA screening | Yes | Screens for relatives and close associates (RCAs). |
| Screening coverage | Watchlist screening | Yes | Screens against watchlists and special-interest lists. |
| Screening coverage | Special-interest screening | Yes | Supports special-interest/watchlist classifications. |
| Screening coverage | Structured adverse media screening | Yes | Screens against adverse-media records supplied through screening datasets. |
| Screening coverage | Live adverse media screening | Optional module | Searches wider unstructured online sources for adverse information. |
| Screening coverage | Internal watchlist screening | Yes / configuration dependent | Allows internally identified risk subjects to form part of screening. |
| Screening coverage | Individual/person screening | Yes | Screens natural persons. |
| Screening coverage | Company/entity screening | Yes | Screens legal entities and organisations. |
| Screening coverage | Unknown/other classifications | Configurable | Criteria can include additional source classifications where provided. |
| Screening methods | One-off screening | Yes | Performs an individual point-in-time screening check. |
| Screening methods | Immediate screening | Yes | Allows a newly created customer to be screened immediately. |
| Screening methods | Ongoing screening | Yes | Retains customers for recurring AML screening. |
| Screening methods | Batch screening | Yes | Screens customer populations automatically at scale. |
| Screening methods | High-volume screening | Yes | Designed to support screening populations up to millions of records. |
| Screening methods | Web-based screening | Yes | Screening can be accessed through a browser-based interface. |
| Screening methods | Salesforce-native screening | Available | Screening can operate within Salesforce workflows. |
| Screening methods | API screening | Available | Supports integration of screening into other systems using APIs. |
| Matching | Risk-based matching | Yes | Applies screening rules according to risk instead of a single universal threshold. |
| Matching | 3D risk-based matching | Yes | KYC360's risk-based matching approach combines name and other metadata to prioritise relevant results. |
| Matching | Configurable matching sensitivity | Yes | Matching sensitivity can be adjusted through screening criteria. |
| Matching | First-name matching threshold | Yes | First-name match sensitivity can be configured. |
| Matching | Middle-name matching threshold | Yes | Middle-name match sensitivity can be configured. |
| Matching | Last-name matching threshold | Yes | Last-name match sensitivity can be configured. |
| Matching | Fuzzy / similarity name matching | Yes | Detects close rather than only exact name matches. |
| Matching | Advanced alias/name matching | Yes | Supports matching against alternative customer identities and names. |
| Matching | Multi-language name matching | Yes | Advanced multi-language alias and name matching is identified in KYC360 product material. |
| Matching | Reverse-name search | Yes | Repeats the search with first and last names transposed. |
| Matching | Blank middle-name handling | Yes | Controls whether source records without middle-name information can generate potential matches. |
| Matching | Date-of-birth matching | Yes | Uses date of birth as part of person screening. |
| Matching | Incorporation-date matching | Yes | Uses incorporation/registration dates for organisations. |
| Matching | Exact-date filtering | Yes | Can require exact dates to generate relevant match potentials. |
| Matching | Date-range filtering | Yes | Excludes potential matches beyond a configurable date radius. |
| Matching | Partial-date relevance | Yes | Month/year, year-only and day/month correspondence can influence match ranking. |
| Matching | Country matching | Yes | Uses associated countries during screening. |
| Matching | Multiple customer countries | Yes | Up to three associated countries can be supplied for a customer. |
| Matching | Country filtering | Yes | Potential matches can be excluded where source countries do not correspond. |
| Matching | Metadata-based ranking | Yes | Relevant metadata increases a match's ranking using KYC360's Meta Bump logic. |
| Matching | Date match ranking | Yes | Exact and partial date correspondence can increase result priority. |
| Matching | Country match ranking | Yes | Country correspondence can contribute to result relevance. |
| Matching | Batch ID Search | Yes | Batch screening of records against ID numbers associated with the record. These could include ISIN number (for securities), passport number (for individuals), IMO number (for vessels) or many others. |
| Screening criteria | Multiple screening criteria | Yes | Different screening configurations can be created for different customer populations. |
| Screening criteria | Criteria assigned by customer | Yes | Customers can be assigned to the appropriate screening criteria. |
| Screening criteria | Configurable PEP screening | Yes | PEP screening can be enabled or disabled at criteria level. |
| Screening criteria | Configurable RCA screening | Yes | RCA screening can be enabled or disabled. |
| Screening criteria | Configurable sanctions screening | Yes | Sanctions screening can be enabled or disabled. |
| Screening criteria | Configurable watchlist screening | Yes | Watchlist/special-interest screening can be enabled or disabled. |
| Screening criteria | Configurable adverse-media screening | Yes | Adverse-media screening can be controlled by criteria. |
| Screening criteria | Granular Screening | Available module | Allows organisations to curate a smaller subset of lists/categories from source data. |
| Aliases | Customer aliases | Yes | Alternative identities can be attached to a primary customer. |
| Aliases | Alias-specific names | Yes | An alias can have its own name information. |
| Aliases | Alias-specific dates | Yes | Alias records can contain date information. |
| Aliases | Alias-specific countries | Yes | Alias records can contain country information. |
| Aliases | Alias-specific criteria | Yes | Different screening criteria can be associated with alias data. |
| Aliases | Alias-parent linkage | Yes | Alias records remain linked to the main customer. |
| Aliases | Alias identification in reports | Yes | Reports can identify whether a result relates to an alias and its parent record. |
| Sanctions intelligence | Active sanctions identification | Yes | Indicates active sanctions status. |
| Sanctions intelligence | Inactive/expired sanctions identification | Yes | Identifies sanctions records where applicable sanctions are no longer active. |
| Sanctions intelligence | Historical PEP status | Yes | Inactive PEP information and relevant dates can be displayed where available. |
| Sanctions intelligence | Historical RCA status | Yes | Inactive RCA information can be shown. |
| Sanctions intelligence | Related-party information | Yes | Related records and their type can be presented to aid assessment of indirect risk. |
| Live adverse media | Unstructured adverse media search | Optional | Extends screening beyond conventional structured adverse-media data. |
| Live adverse media | Configurable search terms | Yes | Search criteria can use configured adverse-risk terminology. |
| Live adverse media | AND search terms | Yes | Terms can be required in addition to the subject's identity. |
| Live adverse media | OR search terms | Yes | Alternative risk terms can broaden relevant searches. |
| Live adverse media | Excluded terms | Yes | Irrelevant terms can be excluded. |
| Live adverse media | Search-engine selection | Yes | Individual search engines can be included or removed at criteria level. |
| Live adverse media | Number of search results | Yes | Users can configure the number of results returned. |
| Live adverse media | Name/adverse-term proximity | Yes | Controls how close the customer's name and adverse term must appear for more targeted results. |
| Live adverse media | Country-based search controls | Yes | Country information can help refine adverse-media searching. |
| Live adverse media | Date-range controls | Yes | Search results can be constrained by date. |
| Live adverse media | Configurable monitoring frequency | Yes | Adverse-media screening criteria can support differing screening schedules. |
| Live adverse media | AVM-specific reporting | Yes | Dedicated reports show adverse-media potential matches. |
| Monitoring | Recurring customer rescreening | Yes | Active customers can be screened repeatedly against updated data. |
| Monitoring | Source-data change monitoring | Yes | Changes to previously reviewed source records can be surfaced. |
| Monitoring | Data-change notification emails | Yes | Alerts users when relevant source records change. |
| Monitoring | Configurable change notifications | Yes | Administrators can control the kinds of changes for which notifications are generated. |
| Monitoring | Sanctions-change notifications | Yes | Notifications can be limited to relevant sanctions changes. |
| Monitoring | Name-change notifications | Yes | Changes to source-record names can trigger notifications. |
| Monitoring | Date-change notifications | Yes | Changes to DOB/incorporation information can be identified. |
| Monitoring | Country-change notifications | Yes | Relevant country changes can be identified. |
| Monitoring | Classification-change notifications | Yes | Changes to SAN, PEP and other classifications can be identified. |
| Monitoring | Source-record deletion notifications | Yes | Users can be notified if a source record has been deleted. |
| Monitoring | Direct link from notification to case | Yes | Change-notification emails can link to the affected customer record. |
| Evidence | Point-in-time snapshots | Yes | Stores evidence of source information associated with reviewed matches. |
| Evidence | Updated profile snapshots | Yes | Captures later versions of relevant data-source profiles. |
| Evidence | Snapshot difference comparison | Yes | Compares historic and updated records and identifies differences. |
| Evidence | Downloadable snapshot | Yes | Users can retrieve previous snapshots. |
| Evidence | Downloadable difference report | Yes | Differences between source versions can be downloaded/reviewed. |
| Alert management | Potential-match queue | Yes | Presents outstanding screening alerts for investigation. |
| Alert management | Match prioritisation | Yes | Helps higher-priority/risk cases appear appropriately in investigator workflows. |
| Alert management | Match type identification | Yes | Identifies whether a potential match relates to sanctions, PEP, watchlist, adverse media etc. |
| Alert management | Flag relevant match | Yes | Confirms a potential match as relevant. |
| Alert management | Discount false positive | Yes | Rejects a potential match as irrelevant/false positive. |
| Alert management | Acceptable relevant match | Yes | Supports classification of a true match that remains acceptable. |
| Alert management | Unacceptable relevant match | Yes | Supports classification of a true match that is not acceptable. |
| Alert management | Mandatory decision rationale | Configurable | A free-text reason can be made mandatory for specified dispositions. |
| Alert management | Configurable flag categories | Yes | Organisations can create their own flag reasons. |
| Alert management | Configurable discount categories | Yes | Organisations can define their own false-positive/discount reasons. |
| Alert management | Extended decision notes | Yes | The disposition reason field supports up to 25,000 characters. |
| Alert management | Bulk match handling | Yes | Multiple matches can be actioned together. |
| Alert management | Bulk supporting-document upload | Yes | Supporting evidence can be attached during bulk match handling. |
| Alert management | Delete unresolved match potentials | Yes | Appropriate users can remove unresolved potential matches. |
| Workflow | Case/user assignment | Yes | Customers and potential matches can be assigned to specific users. |
| Workflow | User-group assignment | Yes | Screening workloads can be routed to handler groups. |
| Workflow | Supervisor reassignment | Yes | Supervisors can transfer potential matches between authorised users. |
| Workflow | Risk priority | Yes | Customer risk classifications can influence workflow prioritisation. |
| Workflow | Configurable risk classifications | Yes | Risk values can be configured and assigned to customers. |
| Workflow | Outstanding-match summary email | Yes | Users can receive an email summary of outstanding potential matches. |
| Workflow | Scheduled summary emails | Yes | Summary emails can be scheduled daily, weekly or monthly. |
| Workflow | Immediate summary email | Yes | Administrators can send outstanding-match summaries on demand. |
| Data quality | Screening Data Quality Report | Yes | Tests customer data for issues that could negatively affect screening quality. |
| Data quality | Duplicate person detection | Yes | Identifies customer-person duplicates. |
| Data quality | Duplicate entity detection | Yes | Identifies duplicate organisation records. |
| Data quality | Missing first-name detection | Yes | Flags person records where first-name information is absent. |
| Data quality | Multiple-word/name-field checks | Yes | Identifies potentially incorrectly structured names. |
| Data quality | Initial/single-character checks | Yes | Detects potentially incomplete name information. |
| Data quality | Numeric-character person-name checks | Yes | Identifies numbers contained within person-name fields. |
| Data quality | Numeric-character entity-name checks | Yes | Detects numeric information in entity names for review. |
| Data quality | Unusual name-length checks | Yes | Identifies unusually long values that may indicate poor data quality. |
| Data quality | DOB anomaly checks | Yes | Includes age/date-based checks for potentially questionable customer data. |
| Data quality | Data-quality issue volumes | Yes | Reports the number/percentage of records affected by individual quality issues. |
| Data quality | Record-level remediation information | Yes | Identifies the actual customer records affected so they can be corrected. |
| Reporting | Match Potential Report | Yes | Reports outstanding potential matches. |
| Reporting | Match Potential Summary | Yes | Provides summary information on outstanding matches. |
| Reporting | Match Potential Volume | Yes | Provides volume reporting for potential matches. |
| Reporting | Match Potential Statistics | Yes | Reports alert age, risk priority and volumes by screening category. |
| Reporting | Match Flag Report | Yes | Reports confirmed/flagged screening matches. |
| Reporting | Match Discount Report | Yes | Reports discounted/false-positive matches. |
| Reporting | Match Flag by Category | Yes | Analyses flagged matches by configured category. |
| Reporting | Match Discount by Category | Yes | Analyses discounts by configured reason/category. |
| Reporting | Match Data by Day | Yes | Supports date-based screening-volume analysis. |
| Reporting | Processing Run Statistics | Yes | Provides information on screening processing runs. |
| Reporting | Data-change report | Yes | Shows source entities that generated customer change notifications. |
| Reporting | Data Quality Report | Yes | Reports screening-input data-quality issues. |
| Reporting | AVM Match Potentials Report | Yes | Reports adverse-media potential matches for selected periods/business units. |
| Reporting | Customer report | Yes | Consolidates profile, matches, outcomes and screening history for a customer. |
| Reporting | Flagged Entity Report | Yes | Provides detailed information on a flagged data-source entity. |
| Reporting | Data export | Yes | Customer/screening data can be exported for authorised operational purposes. |
| Dashboards | Screening dashboards | Yes | Provides visual management information in addition to detailed reports. |
| Dashboards | Matches Dashboard | Yes | Analyses match volume and type over specified periods. |
| Dashboards | User Performance Dashboard | Yes | Provides insight into team/user handling of screening work. |
| Audit | Screening audit history | Yes | Records historical changes and decisions. |
| Audit | Client Entity Audit | Yes | Shows changes made to customer records. |
| Audit | Discounted-match audit | Yes | Shows changes made to discounted matches. |
| Audit | Flagged-match audit | Yes | Shows changes made to flagged matches. |
| Audit | Historic screening evidence | Yes | Snapshots and audit trails help evidence information available at decision time. |
| Administration | User management | Yes | Administrators can invite, manage and disable users. |
| Administration | User groups | Yes | Users can be organised into groups. |
| Administration | Handler groups | Yes | Supports group-based handling of customer matches. |
| Administration | Admin groups | Yes | Supports administrative groups and permissions. |
| Administration | Group permissions | Yes | View/add/update/delete and other permissions can be managed by group. |
| Administration | Supervisor access | Yes | Supervisors can oversee and reassign work within relevant groups. |
| Administration | Two-factor authentication | Yes | Additional user authentication is available. |
| Administration | Business units | Available module/configuration | Customer records can be separated between business units. |
| Administration | Multi-business-unit import | Yes with relevant module | One import can allocate records to multiple business units. |
| Administration | Business-unit branding | Yes | Individual business units can display their own internal logo. |
| Data management | Manual customer creation | Yes | Individual customers can be created within the platform. |
| Data management | Bulk customer import | Yes | Structured files can add and update customer populations. |
| Data management | Customer export | Yes | Customer data can be exported in supported formats. |
| Data management | Custom customer reference | Yes | Source-system identifiers can be retained as interface references. |
| Data management | Custom text fields | Yes | Additional internal reference/note fields can be stored. |
| Data management | Active/inactive customer status | Yes | Inactive customer records can be excluded from recurring screening. |
| Data management | Controlled data deletion | Yes | Administrative deletion workflows are provided. |
| Data management | Two-admin deletion approval | Yes | Sensitive deletion actions require request and approval by separate administrators. |
| Integrations | Batch API | Available | Supports high-volume integrated screening use cases. |
| Integrations | Real-time API | Available | Supports real-time integration use cases where configured. |
| Integrations | Salesforce integration | Available | KYC360 provides Salesforce screening capabilities. |
| Integrations | Salesforce sandbox/test integration | Available | Test API credentials/environment options are supported. |
| Integrations | Quantios integration | Listed | KYC360 Screening supports Quantios integration |
| Integrations | Internal watchlist integration | Available | Internal risk data can be incorporated into screening. |
| Deployment | SaaS / web deployment | Yes | Browser-based Screening is available. |
| Deployment | API deployment/integration | Yes | Screening can be incorporated into wider technology estates. |
| Deployment | On-premise option | Stated in current product material | Configurable deployment options include on-premise. |
| Deployment | Test environment | Available | Supports testing before production deployment. |
| Deployment | Pre-production environment | Available | Allows releases and integrations to be validated outside production. |
| Data providers | Dow Jones data | Supported | Can use Dow Jones screening data depending on configuration. |
| Data providers | LSEG World-Check data | Supported | World-Check is available for appropriate configurations/products. |
| Data providers | LexisNexis data | Supported | LexisNexis is supported within appropriate Screening configurations. |
| Data providers | Data-provider choice | Yes | Supports a choice of leading screening-data providers. |
| Extended data | Factiva articles | Available | Access to Factiva articles is available for additional adverse-media context. |
| Extended data | Additional specialist sources | Available by module |
Access to extended sources including OpenCorporates, Offshore Leaks and Wikileaks is available in additional modules. |