Information Exchange

See Concepts - Information Exchange for more information about the concept.

Counterparties

Depending on which flow definition(s) are configured on the dossier definition, the counterparty can be an individual or intermediary FSP. In order to use intermediary FSP as a counterparty, it's also required to add the INTERMEDIARY module.

Limitations for Individual

When performing an information exchange to an individual via the module DOSSIER_INFORMATION_EXCHANGE, there are some limitations compared to module INVESTOR_FLOW:

• The flow definition should not make use of SIGNATORIES.
• The flow definition should not make use of ADVICE.
• The flow definition should not make use of optional responsibilities (see Responsibility cardinality).

These limitations will gradually be supported in future releases.

Limitations for Intermediary

When performing an information exchange to an intermediary FSP, there are some limitations compared to an information exchange to an individual:

• The intermediary FSP cannot be requested to provide data of the IDENTITY responsibility (because the personal data of the intermediary-FSP user is not relevant).
• The intermediary FSP cannot be requested to provide data of the SIGNATORIES responsibility.
• The information exchange won't be able to show test results, because those are also based on 'personal' data.

Migrating from Investor Flow

See Migrating from Investor Flow to Information Exchange for the differences with the module INVESTOR_FLOW and how to adapt the integrations that appoint the counterparty of a dossier.

Security Checks

To add an extra layer of security, it is possible to pose security questions before the counterparty can access the information exchange.

These can be configured on the module settings (see configuration below).

note

Currently, this is only supported for Counterparty Individual, support for security checks on Intermediary FSP will be added in future releases.

tip

The validation class SecurityCheckDataProvided can be configured to ensure that the answers of the security questions are available before the information exchange is started.
E.g. when the date of birth of the counterparty is defined as a security question, this validation class can ensure that the date of birth is known on FSP side. Otherwise it would be impossible to validate the answer provided by the counterparty.

Profile PDF

At the end of the information exchange, a profile PDF can be generated containing all the data provided by the counterparty during the flow.

When configured to be shown (through module settings), all profile PDFs of the dossier are available on the dossier detail page in a separate tab.

All generated PDF's will be shown on that tab when available, even when the information exchange itself has not been successfully completed (e.g. status 'CANCELLED').

Configuration

Add the module DOSSIER_INFORMATION_EXCHANGE.

note

If you are still using the module INVESTOR_FLOW, see Migrating from Investor Flow to Information Exchange.

Settings

Settings Configuration

Examples

Linked actions & validations

The module DOSSIER_INFORMATION_EXCHANGE supports some actions & validations:

• validation SecurityCheckDataProvided

Linked actions & validations

Here are some validations linked to the information exchange via module DOSSIER_INFORMATION_EXCHANGE:

• validation SecurityCheckDataProvided
• validation AssociatedPartiesDueDiligenceValidation if filtered on type COUNTERPARTY_INDIVIDUAL
• validation HarmoneyAssociatedPartiesDataValidation if filtered on type COUNTERPARTY_INDIVIDUAL (in the associatedPartyFilter) More details can be found here

Here are some actions linked to the information exchange:

• action SendMailToDossierRecipient
• action ScheduleInviteCounterpartyReminderV3 / RemindCounterpartyOnInformationExchangeCompletionV3 / InformReminderSentV3, see Reminder mails
• actions using an associatedPartyFilter on type COUNTERPARTY_INDIVIDUAL (e.g. AddTaskToDossier) More details can be found here