The core concept of the Entity Sharing feature is simple:
a network member can report some entities to the Bridge network
other members can then conduct queries against Bridge, using their own data
if there is a match, results will be shown to the querying organisation. No central list of reported entities is visible to any of the organisations and Salv cannot access any of the data reported.
💡 Although in this manual we focus on the workflows via Bridge UI, it is also possible to integrate the product with other systems via API. This would enable real-time reporting and querying.
📔 There can be a multitude of use cases for the feature, depending on the business needs of the organisations and legal environments they are operating in.
For example, network members could report IBAN accounts that they have identified as fraudulent. Other members could perform automatic checks against Bridge when conducting transactions to prevent money from moving to fraudulent accounts.
Another example could be reporting suspicious entities (either private persons or companies) and the basis for suspicion. Other network members could then make queries against Bridge when onboarding new customers or conducting enhanced due diligence to see if there are any risk flags.
💡 Depending on the use case and data structure agreed among the network participants, Salv can configure reporting and querying templates as needed.
Entity Sharing has 2 main workflows:
Reporting entities
Querying entities
Figure showing the Entity Sharing components in Bridge navigation bar
🚨 Note that the screenshots you see in this manual might look slightly different from what you see in the product. This is due to the difference in data structure – the data structure you see in your environment is specifically tailored for your use case.