Conformity Check
Automatic AML Screening Check company, officers and beneficial owners against Sanctions & Watchlists, PEP, and Adverse Media database. In partnership with Complycube.
| Field | Type | Description |
|---|---|---|
| id | uuid | Unique identifier of the result. |
| first_name | string | User's first name. |
| last_name | string | User's last name. |
| birth_date | date | User's date of birth (format: YYYY-MM-DD). |
| name | string | Name of the company. |
| registration_number | string | SIREN number. |
| company_profile_id | uuid | Company profile id. |
| officer_id | uuid | Company officer id. |
| beneficial_owner_id | uuid | Beneficial owner id. |
| node_id | string | Background check node the screened entity was taken from, when it was taken from one. |
| outcome | string | Compliance check result. See Details |
| file_id | uuid | Associated file identifier. |
| issues | array<object> | What the screening raised, one entry per matched entity and per category. See Details |
| tags | array<object> | List of details associated with the issues. See Details |
| source_created_at | datetime | Date on which the check was created. |
| source_updated_at | datetime | Date on which the check was updated. |
Outcome
| TYPE | DESCRIPTION |
|---|---|
| CLEAR | Verification OK |
| ATTENTION | Verification NOK |
Issues
An issue is one category raised by one entity the screening matched. A check on a common name can match several entities, so expect several issues, and read each one against the entity it names rather than against the company or person you asked about.
| Field | Type | Description |
|---|---|---|
| section | string | Family the category belongs to. See Details |
| type | string | Category raised. See Details |
| entity_name | string | Name of the entity that was matched. It is often not the one you asked about: a namesake, a foreign subsidiary, or the parent of the matched company. |
| score | integer | How closely the matched name resembles the one submitted, from 0 to 100. Null when the issue comes from an associated company, which was never compared to anything. |
| validation_outcome | string | What the screening did with the match. See Details |
| origin | string | match when the entity named is the one that matched, association when it is a company the match belongs to. |
| label | string | Wording the source puts on the category, such as Corruption Issues, Fraud Issues. Null when the source gives none. |
| source_links | array<string> | Links to the sources behind the record of the entity named, one per article or official page. See Details |
Source links
source_links lists the sources the screening holds on the entity the issue names, as
URLs. Most point at a press archive that requires a subscription to open; the URL still
identifies the article for whoever has one. Some point at official pages, such as a
regulator's sanction decisions or a police notice, and open freely.
The links belong to the entity, not to the category. Every issue raised by one match
carries the same list, that of the matched entity's record, whatever the category; an
issue whose origin is association carries the associated company's own links, never
those of the subsidiary that matched. Null when the source lists none.
Validation outcome
An issue is not an alert on its own. It says a category was raised by a match, and the
match still has to hold. Weigh validation_outcome before acting on one, and note that
the check's own outcome already ignores the matches that were rejected: that is why a
check can come back CLEAR and still carry issues.
| VALUE | DESCRIPTION |
|---|---|
| rejected | The match was discarded, for being too weak or after review. The category is reported for completeness, not as a finding. |
| pending | The match is strong enough to keep and awaits a decision. |
| confirmed | The match was accepted after review. |
Example
A check on a company whose name resembles that of a foreign subsidiary. The verdict is
CLEAR because the only match was rejected, and the two issues say which entity raised
what: one the subsidiary that matched, one the group it belongs to.
{
"name": "EXAMPLE HOLDING",
"registration_number": "123456789",
"outcome": "CLEAR",
"issues": [
{
"section": "ADVERSE_MEDIA",
"type": "social_labour",
"entity_name": "Example Holding Philippines",
"score": 88,
"validation_outcome": "rejected",
"origin": "match",
"label": null,
"source_links": [
"https://archive.example.com/article?id=20140510-example-holding-ph",
"https://archive.example.com/article?id=20180726-example-holding-ph"
]
},
{
"section": "ADVERSE_MEDIA",
"type": "regulatory",
"entity_name": "Example Holding",
"score": null,
"validation_outcome": "rejected",
"origin": "association",
"label": "Regulatory Issues, Corruption Issues",
"source_links": null
}
],
"tags": []
}
Sections and types
| SECTION | TYPE |
|---|---|
| WATCHLIST (Sanctions & Watchlist) | sanctions_list |
| terror | |
| war_crimes | |
| other_official_lists | |
| other_exclusion_lists | |
| sanctions_control_and_ownership | |
| PEP (PEP - Politically Exposed Person) | level_1 |
| level_2 | |
| level_3 | |
| level_4 | |
| ADVERSE_MEDIA (Adverse media) | competitive_financial |
| regulatory | |
| environment_production | |
| social_labour | |
| OTHER_LISTS (Other prudent lists) | tax_crime |
| corruption | |
| trafficking | |
| financial_crime | |
| organised_crime | |
| associated_entity |
Tags
| Field | Description |
|---|---|
| type | Type of tag (see the table of tag types). See Details |
| url | URL associated with the tag. |
| title | Title of the tag. |
| description | Description of the tag. |
| entity_name | Name of the matched entity the tag was read from, so an occupation or an identity document is attributed to the right person when several matched. |
Types and Descriptions of Tags
| Value | Description |
|---|---|
| occupation | Information on the user's occupation |
| reference | Reference associated with the user |
| identification | Identification information of the user |
Pep levels explained
| Level | PEP Coverage |
|---|---|
| 1 |
|
| 2 |
|
| 3 |
|
| 4 |
|
Endpoints
/api/v6/users/{userId}/conformity-checksReturns the AML screening results for the user's company, officers, and beneficial owners.