A Customer object represents a customer who performs transactions with a bank.
When you select the Customers menu item, the interface displays the customer search screen. You can enter the following criteria in a customer search. If you enter no criteria, the search returns all customers entered in the database:
| Criteria | Description |
|---|---|
| Customer ID | Enter a valid customer ID. |
| Name | Enter a customer name. |
| Bank | Enter the bank to which the customer is attached. |
After you execute a search, the interface displays a table of returned results. if you are in:
The interface displays the detail window, which comprises the following tabs:
This tab holds general information about the Customer.
| Field | Description |
|---|---|
| Customer ID | Enter a customer identification number |
| Name (mandatory) | Enter a customer name. |
| Name 2 | Optionally enter an additional name |
| Name 3 | Optionally enter an additional name |
| Street | Enter the customer street address and street number |
| Zip code | Enter the customer zip |
| City | Enter the customer city |
| Country | Enter the customer country |
| Phone | Enter the customer phone |
| Fax | Enter the customer fax address |
| Bankinternational ID | Enter a reference to the user in the bank’s main master data application. This value is for information only and is not used elsewhere. |
| Bank | Displays the unique bank access (read-only) |
| Trace EBICS requests | Optionally choose to log EBICS communicationsIf EBICS logging is activated for a customer every communication with this customer is logged in detail. These trace files are stored under the name ebicsServer in the temp directory of the system. Every order receives a unique number and is distributed over several files, each with different file name extension (.in, .out or .insigdata). EBICS orders that the system does not understand are written to the temp directory under the name ebicsInvalid. with this customer. |
The User tab displays a list of the users associated with this customer.
In the overview, the participant ID, name, e-mail address and the different statuses of the individual communication methods are displayed. You can thus see at a glance whether a participant is blocked or waiting for clearance.
Click Details (or Edit if you are in processing mode) to view extended attributes of the user. The extended view of the User comprises the following tabs:
| Field | Description |
|---|---|
| UserID | Id of the user |
| Name | Full name of the participant as it is to be used in the customer log |
| Name 2 | Optional additional name element |
| Name 3 | Optional additional name element |
| Street | User street and number |
| Zip code | User zip |
| City | User city |
| User email | |
| Language | Language of the User |
| Bank internal ID | Local identity of the bank |
| Permission for all accounts | If this option is selected, the user can access all accounts configured for the customer, otherwise the accounts have to be assigned individually on the "Accounts" tab. |
| Permission for all fetch order types | If this option is selected, the user is assigned all fetch order types that are configured on the customer. Otherwise, these have to be configured individually on the "Fetch order types" tab. |
| Permission for all send order types | If this option is selected, the user is assigned all send order types that are configured on the customer. Otherwise, these have to be configured individually on the "Send order types" tab. |
| Default permission | If the participant is authorized for all send order types, he or she is assigned this signature authorization for all business transactions. |
| Limit type | If a limit is set up here, the amount entered in the following field is the maximum that the participant can access. If this is a daily, weekly or monthly limit, the participant may access no more than this amount with all set up files within this time frame. The already utilized amount and the start of the utilization period are displayed below. The limit applies irrespective of limits that might be configured for this participant at a different point. |
| Limit (EUR) | Maximum amount in Euro that the participant may access. This amount is only displayed if a limit has been set. |
| Limit reached | For limits with a time span, this field displays the amount consumed so far. |
| Limit period | For limits with a time span, this field displays the start of the utilization period. |
A list (possibly spanning several pages) is displayed containing the names of the order types assigned to the customer as well as a selection box containing the signature authorizations currently assigned to the participant. When you save, the changes to the signature authorizations are accepted.
For system transport types (HCA, HIA, HSA, INI, PUB, SPR and VPK) the initial, secondary and transport signature authorizations are regarded as sufficient for executing an order.
For order types that support a limit check, you can set a limit for the user (processing mode only). The configuration is made analogous to the limit that you can set up in the general data of the user. The limit then applies to all files of the respective order type, irrespective of the limits configured for the user elsewhere.
A list (possibly spanning several pages) is displayed containing all accounts of the customer with the bank routing number, account number, designation and the signature authorization currently assigned to the customer. These signature authorizations overwrite the authorization that a participant has for a send order type in general. When you save, the changes to the signature authorizations are accepted.
You can set a limit for each account for the participant. The configuration is made analogous to the limit that you set in the general data of the user. The limit then applies to all files submitted for this account, irrespective of the limits configured for the user elsewhere.)
This tab displays all order types that are authorized for the customer. The screen has two sections:
Users of a customer can only be authorized for order types for which the presently selected customer is authorized. If you remove an order authorization from the customer, all users of the customer also lose authorization for this order type.
For send orders, you can individually set the response for D files and the number of required signatures for each customer.
All files sent by the customer are displayed here.
For a detailed description of file characteristics, see Files.
This tab displays all accounts to which the customer has access.
| Field | Description |
|---|---|
| Bank code | Enter the account bank code |
| Account number | Enter the account number |
| SWIFT code | Enter the SWIFT code of the account |
| Additional account number | Enter any additional account number information |
| IBAN | Enter the IBAN |
| Holder | Enter the holder name |
| Description | Enter any description text |
Click Create new account to create a completely new account for the customer.
Click Add accounts to grant the customer access to one or more already existing accounts.When you select this option, the interface displays the account search page. In the results list you can then select any number of accounts and accept them by clicking Add selection.
Click Create permission report to generate a report of all permissions for the customer.
Displays logs that are generated for customer transactions during the period you select.
Displays a list of all changes made to the selected customer.
EBICS Server example: Create a Customer