Connecting an ERP or CRM system
With our API, any system whatsoever (SAP, MS Dynamics, Salesforce and so on) can be connected to sanctions list screening. It is equally possible to build the screening directly into your own system.
Section 1 describes how to connect your system to easycompliance; the focus there is on data import. Section 2 describes how to integrate sanctions list screening directly into your system.
1. Connecting third-party systems to easycompliance
Scenario: you use an ERP or CRM system and want current customer and supplier master data to be transferred into easycompliance, so that it is covered by automatic list screening.
How to proceed: first, do an initial import of all existing customers and suppliers from your system into easycompliance using a CSV file. A bulk initial import of several thousand records via the API is technically possible, but not advisable in this scenario.
Once the initial data is in easycompliance, it is screened automatically every day. Now you have to make sure that newly created customers and suppliers – and changes to existing master data – reach easycompliance as well. To do this, send an API request (method=2) whenever a record is created or changed in your system. The record you send is added to automatic list screening and is screened automatically every day from then on. At the same time the API returns the screening result, which you can store in your system or display to the user.
If you also want future hit notifications and screening results imported into your system – to set delivery blocks automatically when changes to the sanctions lists produce a hit, for example – you can send an API request with method=3 at a fixed interval, say every 24 hours. That returns all hits generated by sanctions list screening in the past 24 hours. Please note that with this approach members of your staff should review the sanctions list results in every case: if a hit turns out to be a false positive – a hit that is not really one – the delivery block has to be lifted again by a member of staff. You should agree internal processes accordingly.
2. Integrating sanctions list screening directly into your system
Scenario: you want a sanctions list check as an individual check on every transaction in your system (creating a customer, issuing a delivery note, issuing an invoice and so on). This screens against the sanctions lists as they stand that day, but the names checked are not added to automatic list screening – they are therefore not screened automatically every day, and are not stored in easycompliance. This approach can be used instead of option 1 if you do not want automatic sanctions list screening.
How to proceed: for every screening-relevant transaction in your system – creating a new customer, issuing a delivery note, writing an invoice, paying supplier invoices and so on – send an individual check via the API (method=1). You receive the result of the check and can store it in your system or use it directly to trigger further processes (a delivery block, for example). It should also be shown to the relevant member of staff, or to someone designated in advance, so that they can decide whether or not it is a false positive.
Which option is the right one?
There is no blanket answer. Every system landscape is built differently, and internal processes vary from company to company. Our experience, however, is that option 1 usually makes the most sense. It is also easier to implement, because option 2 first requires you to define what counts as a screening-relevant transaction in your system and then to wire each of those up individually in code.
If you are unsure which option is right for you, please contact us.
Related articles
Last reviewed: