SAS AML Due Diligence
- Version 3
- Version 2
- Version 1
🎯 Functional documentation
- SAS AML Due Diligence can be used to screen a party. If an external reference is known on the party, the provider will first try to retrieve the screening result based on this external reference. If this is not available, the provider will perform a screening based on the provided party information.
- HIT handling is performed in SAS-AML using Dow Jones as Due Diligence source. Once due diligence is calculated in Harmoney, the handled HIT will be imported in the respective Due Diligence parameter.
- This provider supports the generation of a due diligence pdf to trace which hits are returned by the provider
Input data points
- Individual
- First name
- Last name
- Date of birth
- Place of birth
- Gender
- Address: Country
- Company
- Name
Due Diligence parameters
This provider supports results for the following parameters:
-
Individual
-
PEP -
SANCTION_LIST -
SPECIAL_INTEREST -
PEP_RELATIVES -
ASSETS_FROZEN -
Company
-
SANCTION_LIST -
SPECIAL_INTEREST -
ASSETS_FROZEN -
parameterResultList:
-
NO -
YES -
APPC_ALT -
UNDEFINED
⚙️ Configuration
- Implementation class:
AppcV3DueDiligenceProvider - Resource uri:
https://conformite-appc.com/SASBIWS/rest/storedProcesses/Products/SAS%20Compliance%20Solutions%20FCFBU_${APPC_URI_VAR_1}/Stored%20Processes - Set the "dueDiligenceMetadataSupplier" : "eu.myharmoney.app.providers.duediligence.appc.AppcMetadataSupplier"
key in the RBA module settings JSON.
This configuration also allows the use of the variable
${APPC_URI_VAR_1}, which is automatically sourced from the FSP's external metadata.
Settings
authentication(required):clientId(required)clientSecret(required)DUE_DILIGENCE_DOCUMENT_FETCH(optional, boolean): If true, fetches and stores a due diligence document (default:false).
Example
{
"authentication": {
"clientId": "$vault{SAS_AML_DD_<client>_clientId}",
"clientSecret": "$vault{SAS_AML_DD_<client>_clientSecret}"
},
"DUE_DILIGENCE_DOCUMENT_FETCH": true,
"PROVIDER_DISPLAY_NAME": "Watchlist monitoring"
}
🎯 Functional documentation
- SAS AML Due Diligence can be used to screen a party. If an external reference is known on the party, the provider will first try to retrieve the screening result based on this external reference. If this is not available, the provider will perform a screening based on the provided party information.
- HIT handling is performed in SAS-AML using Dow Jones as Due Diligence source. Once due diligence is calculated in Harmoney, the handled HIT will be imported in the respective Due Diligence parameter.
- This provider supports the generation of a due diligence pdf to trace which hits are returned by the provider (Version 2 provides more details in this PDF).
Input data points
- Individual
- First name
- Last name
- Date of birth
- Place of birth
- Gender
- Address: Country
- Company
- Name
Due Diligence parameters
This provider supports results for the following parameters:
-
Individual
PEPSANCTION_LISTPEP_RELATIVESASSETS_FROZEN
-
Company
SANCTION_LISTASSETS_FROZEN
-
parameterResultList:
NOYESAPPC_ALTUNDEFINED
⚙️ Configuration
- Implementation class:
AppcV2DueDiligenceProvider - Resource uri:
https://conformite-appc.com/SASBIWS/rest/storedProcesses/Products/SAS%20Compliance%20Solutions%20FCFBU_${APPC_URI_VAR_1}/Stored%20Processes - Set the "dueDiligenceMetadataSupplier" : "eu.myharmoney.app.providers.duediligence.appc.AppcMetadataSupplier" key in the RBA module settings JSON.
This configuration also allows the use of the variable
${APPC_URI_VAR_1}, which is automatically sourced from the FSP's external metadata.
Settings
authentication(required):clientId(required)clientSecret(required)
DUE_DILIGENCE_DOCUMENT_FETCH(optional, boolean): If true, fetches and stores a due diligence document (default:false).
Example
{
"authentication": {
"clientId": "$vault{SAS_AML_DD_<client>_clientId}",
"clientSecret": "$vault{SAS_AML_DD_<client>_clientSecret}"
},
"DUE_DILIGENCE_DOCUMENT_FETCH": true,
"PROVIDER_DISPLAY_NAME": "Watchlist monitoring"
}
🎯 Functional documentation
- Version 1 allows HIT handling in SAS AML
- A due diligence pdf is generated in Harmoney to trace on which hits are returned based on the party information provided.
Input data points
- Individual
- First name
- Last name
- Date of birth
- Place of birth
- Gender
- Address: Country
- Company
- Name
Due Diligence parameters
This provider supports results for the following parameters:
- Individual
PEPSANCTION_LISTPEP_RELATIVESASSETS_FROZEN
- Company
SANCTION_LISTASSETS_FROZEN
⚙️ Configuration
- Implementation class:
AppcDueDiligenceProvider - Resource uri:
https://conformite-appc.com/SASBIWS/rest/storedProcesses/Products/SAS%20Compliance%20Solutions%20FCFBU_${APPC_URI_VAR_1}/Stored%20Processes - Set the "dueDiligenceMetadataSupplier" : "eu.myharmoney.app.providers.duediligence.appc.AppcMetadataSupplier" key in the RBA module settings JSON.
This configuration also allows the use of the variable
${APPC_URI_VAR_1}, which is automatically sourced from the FSP's external metadata.
Settings
authentication(required):clientId(required)clientSecret(required)
DUE_DILIGENCE_DOCUMENT_FETCH(optional, boolean): If true, fetches and stores a due diligence document (default:false).
Example
{
"authentication": {
"clientId": "$vault{SAS_AML_DD_<client>_clientId}",
"clientSecret": "$vault{SAS_AML_DD_<client>_clientSecret}"
},
"DUE_DILIGENCE_DOCUMENT_FETCH": true,
"PROVIDER_DISPLAY_NAME": "Watchlist monitoring"
}