PD Client and GDB (NL)
Manage all your NVWA declarations easily and error-free, automate processes and ensure full compliance within your supply chain.
International trade also involves compliance risks. Customers, suppliers, and other trading partners may appear on national or international sanctions lists—and those lists are constantly changing.
Stream Software's Denied Party Screening (DPS) helps you automatically screen your trading partners against relevant sanctions lists.
But screening goes beyond simply finding a potential match. You also want to understand why a party is matched, what data plays a role in that process, and exactly what was verified.
That's why DPS combines screening with transparent results, automatic logging, and integration into your existing Streamliner workflow.
In many organizations, the screening of business partners is still carried out through manual checks or separate tools. This may be manageable when the number of checks is limited, but it becomes increasingly complex as volumes increase or when relationships need to be re-evaluated on a regular basis.
At the same time, compliance processes are becoming increasingly important. A potential match must be evaluated correctly, and it must be clear afterward which controls were carried out.
DPS can help you with that:
Not every agreement means that you are dealing with a sanctioned party. For example, a similar name may be used by multiple organizations or individuals.
That is why DPS not only provides a match score but also explains the reason for a potential match.
Depending on the data found, the results may indicate, for example:
The results are categorized into High, Medium, or Low match levels. You can also adjust the search sensitivity to suit your needs: Strict, Balanced, or Extended.
This gives you more context for each result and allows you to determine more precisely which matches should be investigated further.
DPS uses OpenSanctions as its primary data source, supplemented by relevant national and international sanctions lists.
These include, among other things:
A record is kept of the list versions used, so that it is possible to verify later which data were used for a screening.
Not every organization has the same screening needs. That is why DPS offers various ways to screen parties.
Conduct a screening whenever you need to. For example, when dealing with a new customer, supplier, or other business partner.
Through the DPS web application, you can perform manual screenings, view results, and review your screening history.
Are you already using Streamliner Classic? If so, you can screen shipments directly from your existing customs workflow.
Using " Run Screening Now," you can perform a check directly from the claims screen. You can also view the most recent screening date and available screening information from the contact record.
Would you like to check multiple records at once? With batch screening, you can have larger batches screened all at once.
This also makes DPS suitable for periodic re-screening of existing customers.
Would you like to incorporate screening into your own automated processes?
The DPS API supports individual and batch screenings and can be integrated with, for example, your ERP, CRM, or other business systems.
Conducting a screening is one thing. Being able to demonstrate afterward what was checked is just as important.
DPS automatically records screening activities. These include, among other things:
This creates a clear audit trail of your screening activities.
Screening history remains available, and results can be exported for internal use or audits.
The main difference isn't just in the screening itself.
DPS was developed as part of the Stream Software ecosystem. This allows screening to integrate with the processes you’re already using today.
Screening no longer needs to be separate from your customs and compliance processes.
Screen batches directly from Streamliner or automate checks using batch screening and the API.
Don't just look at the result; also consider the information behind a potential match.
Screenings are automatically recorded so that you can document which checks were performed afterward.
DPS can adapt to your way of working.
A single screening during customer onboarding. A check based on a customs declaration. A nightly batch screening of existing customers. Or an automated screening using your own systems.
And because screening, results, and logging are all combined into a single solution, compliance becomes an integrated part of your daily workflow.
Denied Party Screening isn't just about finding a potential match.
The key is to know who you are screening, understand why a result is flagged, and be able to demonstrate what checks were performed.
With DPS, Stream Software brings these elements together into a single, integrated solution for screening and compliance.
Find out how Denied Party Screening can integrate with your existing customs and compliance processes.
Please contact your Stream Software account manager for more information or a personalized demo.
