Skip to main content
Version: 17

Financial Service Provider

An FSP is the entity that owns the actual data (dossiers, parties, documents, …) that is gathered and used in the platform.

Some examples:

  • Bank X is a large organization with local agencies that manage their own data: an FSP will be created for each agency (e.g. Agency Brussels, Agency Ghent, Agency Paris, …)
  • Bank X is a large organization with data-separation between countries: an FSP will be created for each country (e.g. X Belgium, X France, …)
  • Bank X is a large organization with data-separation between business units: an FSP will be created for each BU (e.g. BU insurance, BU investments, …)
  • Bank X is a large organization with data-separation between teams: an FSP will be created for each team (e.g. Team Compliance, Team High Risk Compliance, …)
  • Bank X is a small organization with a single office: a single FSP will be created

Employees of the organization (users of the platform) will typically receive access (roles) to one or more FSPs where they can interact with the data and do their job.

For example:

  • John Doe works in the insurance BU of Bank X. His job is to process the identity information of customers of Bank X with an active insurance contract. Via the platform, John can reach out to the customers to keep their identity data up-to-date and use that data for legal purposes.
  • Jane Doe also works in the insurance BU of Bank X. Her job is to make sure John and his colleagues keep all identity information up to date. She also reports to the management of the organization.

Each FSP can be configured as desired, but uses the configuration that is defined on organization-level. This allows configuring FSPs in the exact same way, without having to manage duplicate configurations.

FSPs are created and configured by the administrator, but the data and access control are managed by users with access to the FSP. Minimal settings concerning the FSP can be managed by users with the Office Manager role such as FSP details (logo, name, address,...) and user access.

There are two types of FSP: front office and back office (legacy):

  • In the legacy setup, a front office can share dossiers with a back office, so the users with access to the back office FSP can see the same dossiers of the front office.
  • In the standard setup, dossiers are not shared over FSPs. It’s however possible to perform an outreach from one FSP to another one using the information exhange.

Users & Roles​

A user can have one or more roles on the platform. A role can be linked to an FSP. Specific dossier status transitions can be limited to dedicated roles.

Following roles are available in Harmoney:

  • Investor (not linked to an FSP): used when a user is contacted by an FSP in an outreach.
  • Advisor (linked to a front office FSP): sees only dossiers of the FSP assigned to himself in the dashboard
  • Office manager (linked to a front office FSP): sees all dossiers of the FSP in the dashboard. They have the FSP settings tab available.
  • Analyst (only available to a back office FSP)
  • Compliance officer (only available to a back office FSP)
  • Administrator: used for technical configuration, not available to customers.
  • Observer: can only view but not edit in the FSP.