Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

BFS Version: 2.X


To create a user from the back office interface navigate to the dashboard and click on the add user icon or use the menu User Management.


The "Create User" dialogue is displayed with a number of sections.
 

User type

Start by selecting the user type.



Admin
This is an administrative user who can access the back office tool or it could be an API-user. 
Note! If you create an API-user the username needs to contain API, for example, usernameAPI, companyAPI

Customer
This is an end user who can access the customer portal.

Partner
This is a reseller, broker, advisor or another type of partner who can access the partner front.

Basic information

Next is the basic information for the user. If your instance of Bricknode Broker is enabled for address lookup you can use this function for supported countries. If the lookup is supported for the selected country the button will be enabled, 

Natural Person: if the user is a natural person or not. 

User information

The user information for persons contains the First Name, Last Name, requested username and password for the user.


The user information for company contains the Company Name, User name, and password for the company.


Contact information

It is possible to enter a primary postal address as well as the registered address. If you enter a primary postal address, it will be used in PDF´s like note, account statement, activity reports and commitment statement. 

For contact information, a valid e-mail address should be entered together with a phone number.

Other information

Other information is generally not required.

Passport number and comment is self-explanatory.

BIC
If you are entering information for a company which has a BIC-code it should be entered here.

External Reference
If you are working with external systems this is an important part. Here you can enter a text string representing, for example, the id of the legal entity in a separate system like a CRM.


MiFID II


Information about your customers for the TRS 2 reporting. This is an add-on available in our Marketplace. 

BirthDate: enter DD/MM/YYYY
Country: which TRS country the person belongs to. If the person doesn't belong to a TRS country, XX should be used. 
Branch Country: When creating a user branch country is by default set to the same as selected MiFID ll country. It is always possible to change, both when creating the user and on the detail tab under Legal information.
Type: Is prefilledThe id type for TRS reporting regarding natural persons. Can be either NID, PASSPORT or CONCAT. For Companies: LEI
Id: The TRS identification code that should be used for natural persons when performing TRS2 reporting

Manual Handling: if you want to review transactions before sending the TRS file to FI.
Mifid ok: All information is available to comply with the MiFID regulations to trade. 

For Company

LEI:
Manual Handling: if you want to review transactions before sending the TRS file to FI.
Mifid ok: All information is available to comply with the MiFID regulations to trade. 

Settings


Under System Data > System Settings can you specify which settings should be default in this ticket. 

Is Approved: By enabling this setting the user can immediately log on to the system.

Tax Payer: If enabled the user will be included in tax reporting for the relevant country if taxable transactions are being conducted.

Professional: 

Send welcome mail: If enabled an e-mail will be sent to the user containing the pre-defined welcome e-mail template.

Partner: A partner can be defined for the user by clicking the "Choose" button.

It´s also possible to create these kinds of users directly from the ticket:

-Fund Entity
-Fund Company
-Insurance Company
-Issuer
-Counterparty

It is also possible to register this afterward in the detail page of the User. 

If we create a company we can now also specify if it should be a counterparty. 

If we create an administrator, we will have fewer settings, but we need to specify Access level


  • No labels