Creating a bank access for colleagues

Explanation

To create a bank access for a colleague, you first select a colleague. You also select a bank access from the created customer bank accesses or a global bank access. Subsequently you add data and save the bank access.

Afterwards, your colleague can initialise the saved bank access.

Colleague means a user of your own customer whose data you can manage due to your rights assignment.

Prerequisite

You are assigned the rights Protocol user bank accesses: read (customer) and Protocol user bank accesses: edit (customer).

Procedure for creating an EBICS bank access for a colleague

1.

Select Management ➔ Colleagues.

2.

Open the data record of a user in edit mode.

3.

Select the tab Bank accesses.

4.

Click on .

5.

Only if you can also create FinTS bank accesses: click on Create EBICS bank access.

6.

In the mask area Basic data enter the name of the bank access.

7.

In the mask area Bank access, enter the data of the bank access.

After saving the bank access, the data in the mask area Bank access can no longer be changed, bar the following exceptions:

	EBICS profile EBICS-DE: authorisation procedures
	EBICS profile EBICS-FR: CFONB profile
	Signature procedure

a)

From the selection list Financial institution, select a customer bank access.

In the selection list you can see the name of the bank access as well as the URL and the host ID of the EBICS server.

b)

Enter the customer ID and the protocol user ID your colleague uses to identify himself at the financial institution.

c)

Only for bank accesses with the EBICS profile EBICS-DE: choose how you want to authorise your payment orders.

Radio button	Description
Release with electronic signature	The application requests the user to give an electronic signature while the payment file is being sent.
Release by accompanying note	You send the order to the financial institution without an electronic signature (D file). The payment files have to be post-edited by the financial institution. Note: If you have already signed the payment files before they are sent, the signature that you gave is lost!
Ask upon sending	During each sending process of a payment file, the application asks whether the payment order shall be signed or not.

In the fields Customer ID and Protocol user ID, only uppercase and lowercase letters, digits, and the characters = and , may be entered. The length may not exceed 35 characters.

8.

Do not change the default value in the field Signature procedure. The value is preset by your financial institution.

9.

Save the data.

10.

The label of the tab for the assignment of the business transactions depends on the EBICS version of the customer bank access that the bank access for your colleague is based on.

EBICS version of the customer bank access	Tab
EBICS 2.5	Order types
EBICS 3.0	BTFs
EBICS 2.x and 3.0	Order types/BTFs

Go to the respective tab.

All assigned order types/BTFs are displayed.

All business transactions that were assigned to the customer bank access on which the bank access is based are now also assigned to the bank access.

11.

Check if the assignment of the order types/BTFs for the bank access of your colleague is correct.

12.

If a push server has been configured for your global bank access (not part of the standard scope of the application): to configure push notifications, switch to the tab Notifications.

13.

In edit mode, choose the events for which your colleague shall receive notifications.

Which events are shown to you in the selection list depends on the push server.

The bank access is ready for your colleague.

The colleague you assigned this bank access to is informed after his next login via a notification on the start page that a new bank access has been created which he can initialise.

Procedure for creating a FinTS bank access for a colleague

This function is not part of the standard scope of the application.

1.

Select Management ➔ Colleagues.

2.

Open the data record of a user in edit mode.

3.

Select the tab Bank accesses.

4.

Click on .

5.

Select Create FinTS bank access.

6.

In the mask area Basic data enter the name of the bank access.

7.

In the mask area Bank access click on Select financial institution....

A pop-up window opens with a list of the financial institutions that you can select for the bank access.

8.

Select a financial institution and click on Accept.

The data in the mask area Bank access can no longer be changed after saving the bank access.

9.

If the colleague is permitted to use this bank access for the execution of automatic download orders with the download agent in the menu File manager, activate the checkbox Activate automatic download orders.

Please note that costs can arise from TAN requests via a mobile device.

10.

11.

Enter the customer ID and the protocol user ID your colleague uses to identify himself at the financial institution.

Note:

If your financial institution has not provided you with a protocol user ID, enter the customer ID for the protocol user ID as well.

The names Customer ID and Protocol user ID can be different at your financial institution. If your financial institution uses other names, they will be displayed in this mask after you complete the initialisation of the bank access.

12.

Save the data.

13.

Go to the tab Order types.

All assigned order types are displayed.

All order types that were assigned to the customer bank access on which the bank access is based are now also assigned to the bank access.

14.

Check if the assignment of the order types for the bank access of your colleague is correct.

The bank access is ready for your colleague.

The colleague you assigned this bank access to is informed after his next login via a notification on the start page that a new bank access has been created for which he must enter a PIN and which he can initialise.