1 ECONS I User Handbook · 2019. 7. 24. · 1 ECONS I User Handbook 1.1.1 Use of ECONS I Version 13.0 – 24 July 2019 - TARGET2 ECONS I User handbook 1 1 ECONS I User Handbook 1.1

1 ECONS I User Handbook

1.1.1 Use of ECONS I

Version 13.0 – 24 July 2019 - TARGET2 ECONS I User handbook 1


1.1 Basics

The Enhanced Contingency Solution is common tool developed in order to

substitute the SSP in case of a whole unavailability. Information regarding

RBAC ROLES, users’ roles, login and security are described in the relevant

UDFS chapters.

1.1.1 Use of ECONS I

The following non-exhaustive list gives an overview of the different functions available in ECONS I.

A general description how ECONS I works, is available in book 1, chapter 4.

Each CB is responsible for managing his participants, meaning that the CB is responsible for:

• designating the users

• assigning specific roles to each user

General aspects

Responsibility for participants


1.1.2 Overview of users’ roles for CBs


1.1.2 Overview of users’ roles for CBs

The following list gives an overview of the CB user roles which have access to ECONS I.

For each user role the availability in the two eyes/four eyes principle as well as the specific actions characterizing the role are provided.

Short name User role Two eyes/ four eyes principle

Specific actions

APPLICBTE Application Two eyes principle Used to access ECONS I in A2A mode.

CBINFRTE CB Read In-formation

Two eyes principle Used to access ECONS I in U2A mode. Only allowed to read data

CBMANATE

CBMANAFE

CB Manager Two eyes principle and four eyes principle

Used to access ECONS I in U2A mode.

Allowed to read and to modify data:

• enter payments • enter liquidity injections/liquidity

drains • agree/disagree payments inserted by

the participants

Overview


1.1.3 Overview of users’ roles for Participants


1.1.3 Overview of users’ roles for Participants

The following list gives an overview of the Participants user roles which have access to ECONS I.

For each user role the availability in the two eyes/four eyes principle as well as the specific actions characterizing the role are provided.

Short name User role Two eyes/ four eyes principle

Specific actions

CUINFOTE

ASINFOTE

ASMANATE

CU/AS Read Information

Two eyes principle Used to access ECONS I in U2A mode. Only allowed to read data

CUBAUPTE

CUBAUPFE

CU Manager

AS Manager

Two eyes principle and four eyes principle

Used to access ECONS I in U2A mode.

Allowed to read and to modify data:

• enter payments

1.1.4 Login

The following steps are necessary to access ECONS I in U2A mode:

• Via the SWIFT Alliance WebPlatform the user must first gain access to SWIFTNet by entering its username and password. Once the “SWIFT user“ data are verified (username and password), the login procedure performs a mapping with the single, corresponding “SWIFT user“ where-by the system recognises the user and assigns the respective RBAC role.

• After the recognition has been processed, the user can select the brows-ing option.

Overview


1.1.4 Login


In the browsing window for navigation the user has to enter the following specific Universal Resource Locator (URL) in order to access the En-hanced Contingency Solution:

• https://trgt-cm.ssp.browse.swiftnet.sipn.swift.com (from version 13.0 onwards)

In order to access the Enhanced Contingency Solution for testing purposes, the following different URL has to be used:

• https://trgt-cm-cust.ssp.browse.swiftnet.sipn.swift.com (from version 13.0 onwards)

Only in the exceptional case the SWIFT WebAccess has not yet been acti-vated during WebAccess migration, the previous URL have to be used. Please refer to the release note.

For production environment:

• https://trgt-cm.ssp.swiftnet.sipn.swift.com

For testing purposes:

• https://trgt-cm-cust.ssp.swiftnet.sipn.swift.com


1.2 Security


1.2 Security

ECONS I can be used to initiate sensitive interventions by CBs and Partici-pants. ECONS I must therefore guarantee an appropriate level of security.

This is achieved by:

• the use of security features provided by SWIFT as part of the SWIFTNet-services. The Services defined for the use of the Enhanced ContingencySolution are “trgt.cm“ (for the live environment) and “trgt.cm!p“ (for thetest environment)

• defining different roles for the users (CBs and Participants)

• offering the “four eyes“ principle as an option. Each CB and Participantcan decide to which of the roles available to its users the “four eyes“principle will have to apply

Note: The “four eyes“ principle is not available for the application-to-application mode. In this mode the application developed by the CB has to support this feature.

General remarks

Security elements


1.2 Security


The following diagram shows the flow of a successful process of authenti-cation:

Step Description

1 The user logs into the SIPN. Therefore the security elements requested by SWIFT are needed.After the successful login the user selects the ECONS I service.

2 The user sends a request to the server of the ECONS I.

3 SWIFT checks whether the user is registered in the RBAC service for ECONS I and adds the roles that are assigned to him to the message.

4 The message together with the roles is forwarded to the ECONS I server.

Authentication of users


1.3.1 ECONS I Menu


1.3 Description of screens

In the following the screens available in ECONS I are described.

1.3.1 ECONS I Menu

CM menu item Function Explanation

Payments Payments Through this menu item/function the user is able to display information about transactions in the ECONS I.

Liquidity Liquidity Through this menu item/function the user is able to display information about the liquidity available on accounts in the ECONS I and to manage the liquidity through:

• liquidity injection/liquidity drain (transfer of liquidity from/to the account of the CB to/ from the account of a participant)

• entry of payments (transactions between accounts of different participants)

Services System Status Through this function the user is able to display the status of the ECONS I and the SSP Operator can change the Business Date.

Open Account Through this function the SSP Operator is able to open a new account in ECONS I.

Task Queue Through this function the user is able to manage the task queue.

Basics


1.3.2 Single screens



ECONS I screen structure within menu item

Menu item Screen Explanation

Payments

Select Criteria Pay-ments

Allows to choose different selection criteria for performing inquiries on transactions.

Display Payments Shows the list of all transactions fulfilling the requested selection criteria.

Liquidity

Select Participant Allows to select a specific participant.

Display Current Liquidity

Allows users to display information about liquidity on accounts in the ECONS I. A link to specific popups to perform liquidity injection/ drain or payments is available.

Services/System Status

Display system status

Allows to display information about the status of the ECONS I.

Allows the SSP Operator to manage the contin-gency session.

Services/Open Account

Open Account Allows the SSP Operator to open a new account in ECONS I.

Services/Task Queue

Select Task Queue Allows to display the list of tasks. A link to a specific popup to manage the task (confirm/reject it) is available and for CBs to agree/disagree a transaction.




1.3.2.1 Screen: Login




1.3.2.2 Menu item: Payments

1.3.2.2.1 Screen: Select Criteria Payments

This screen allows participants to select payments by means of special cri-teria.

• SSP: All data

• CBs: Own data and all data on participants in their explicit area of re-sponsibility

• CIs: All data in their explicit area of responsibility

Screen

Screen descrip-tion

Access authoriza-tion




• ASs: Files in their explicit area of responsibility

The following actions are possible in this screen:

Field Meaning

All transactions [selection]

Used to select all transactions.

Business Date Specifies the Business Date.

Single transaction [selection]

[selection] Used to select a single transaction identified by the TRN plus the sender BIC.

Transaction Refer-ence Number [text box]

Specifies the TRN of the specific transaction to be selected. Note: the TRN must be specified if the “single transaction“ option is selected.

Sender BIC [text box]

Specifies the BIC of the sender of the transaction to be selected. Note: the Sender BIC must be specified if the “single transaction“ option is selected.

Transaction filter [selection]

Used to select a set of transactions by means of different criteria.

Participant BIC [text box]

Select transactions related to a specific participant BIC. Note: this selection criteria can be used only if the “Transaction Filter“ option is selected.

Actions in screen




Field Meaning

Debtor-Creditor [selection]

Selects either debit or credit transactions Note: this selection criteria is used only if the “Transaction Filter“ op-tion is selected.

Responsible Central Bank

Selects the responsible Central Bank

Note: this selection criteria is used only if the “Transaction Filter“ op-tion is selected.

Entry Time After or Equal (>=)/Before(<)

Select all transactions arrived in the ECONS I in the indicated time range. Note: this selection criteria is used only if the “Transaction Filter“ op-tion is selected.

File Filter Used to select a single AS file.

AS File Group Id Specifies the Group Id of the specific file to be selected. Note: the Group Id must be specified if the “File Filter“ option is se-lected.

The following action button is available in this screen:

Action button Function

Submit Accepts the settings and links to the “Display Payments“ screen ac-cording to the selected criteria.

The AS files is sent by the CB on behalf of the Ancillary Systems via A2A.

Validation performed on the files are described on UDFS book 4.

Once the Contingency Services have verified that all debits can be settled, then the whole file is processed. If one of the payments can’t be settled, then the process “debits first” is terminated and debits already settled is re-versed via automatic procedure.

Action buttons in screen




1.3.2.2.2 Screen: Display Payments

In this screen the list of all transactions fulfilling the selection criteria previ-ously specified by the user (see screen “Select Criteria Payment“) is dis-played.

• SSP: All data



• ASs: Files in their explicit area of responsibility

Fields in this screen:

Field Meaning

Internal Transfer Identifier

Unique transaction identifier assigned by ECONS I

TRN Transaction Reference Number of the single transaction (Related reference of the original message or “new“)

Debit Credit Indica-tor

Debit (D)/Credit (C) Indicator

Amount Amount of the transaction

Sender BIC BIC of the sender of the transaction

Participant BIC BIC of the participant to which transactions are referred; this can be either the debtor or the creditor, depending on the value of the debit/

Screen

Screen descrip-tion


Fields in screen




Field Meaning

credit indicator.

Counterpart BIC BIC of the transaction counterpart

Status Status of the transaction. Possible values are “Pending“, “Settled“, “Rejected“ or “Waiting for NCB approval”.

Entry time Date and time when the transaction arrived in ECONS I

Finality time Date and time at which the transaction has been settled in ECONS I

Error code Error Code (in case of rejected transactions)

Error Description Error description (in case of rejected transactions)

The following actions button are available in this screen:


Export CSV Allows to export in CSV format the payments displayed

Export XLS Allows to export in XLS format the payments displayed

In case of a contingency session opened for several business days, ECONS I directly provides statements of accounts via current Display Payment screen, setting a specific Business date, and an “export function” allowing users to download, after a query, the whole result via XLS/CSV file while MT940/MT950 are sent, at the end of the session, containing only the information related to the last business day.

In case of a contingency session opened and closed into the same busi-ness day, the process remains unchanged (MT940/MT950 sent after the closure of the contingency session).





1.3.2.3 Menu item: Liquidity

1.3.2.3.1 Screen: Select participant

This screen allows to select a specific participant in order to display the par-ticipant’s liquidity.

• SSP: All data



The following action is possible in this screen:

Field Meaning


Selects a participant by its BIC

Screen

Screen descrip-tion


Action in screen




The following action button is available in this screen:


Submit Links to the screen “Display current liquidity“ for the selected partici-pant

1.3.2.3.2 Screen: Display Current Liquidity

This screen allows to display the current liquidity of a specific participant and to perform liquidity injections/drains (only CBs) or to submit payments through specific popups.

• SSP: All data



Action button in screen

Screen

Screen descrip-tion






Field Meaning

Participant BIC BIC of the participant

Participant Name Name of the participant

Available liquidity (€) Amount of the liquidity on the account of the participant in ECONS I. It can be negative only for CBs accounts

The following action buttons are available in this screen:


Modify liquidity Opens the Modify liquidity popup (only CBs)

Insert payment Opens the Insert payment popup

The following popups are available in this screen:

Popup Function

Modify liquidity Used to inject or drain liquidity on the account of the selected partici-pant in ECONS I (only CBs)

Insert payment Used to insert payments

Fields in screen


Popups in screen




Field in the popup Modify Liquidity (only for CBs):

Field Function

Participant BIC BIC of the participant

The following entries are required in the popup:

Field Meaning

Select type of opera-tion [option buttons]

Allows the selection of the type of operation (liquidity injection or li-quidity drain)

Amount (€) [text box] Defines the amount of the liquidity injection or drain

Popup Modify Liquidity

Fields in popup Modify liquidity

Actions in popup Modify Liquidity




The following action button is available in the popup:


Submit Accept the settings

Field in the popup:

Field Function

Participant (Debtor) BIC

BIC of the participant (debtor)

Action button in popup Modify Liquidity

Popup Insert payment

Fields in popup Insert payment




The following entries are required in the popup:

Field Meaning

Counterpart (Credi-tor) BIC [text box]

Allows to enter the BIC of the counterpart (creditor)

Amount € [text box] Defines the amount of the payment

Payment type [text box]

Defines the type of payment (eg CLS). The field is optional and can contain a maximum of 4 characters. If used, the content of this field will be reported in the first 4 characters of the TRN (automatically generated ECONS I)

The following action button is available in the popup:



Actions in popup Insert Payment

Action buttons in popup Insert Payment




1.3.2.4 Menu item: Services

1.3.2.4.1 Screen: Display System Status

Screen




This screen allows the users to display the status of ECONS I.

• SSP: All data

• CBs: All data

• CIs: All data

• ASs: All data

Screen descrip-tion Access authoriza-tion




Field in this screen:

Field Meaning

ECONS I Status Displays the current status of ECONS I. Possible values are: “Open“ (ECONS I is open), “Closing“ (ECONS I is closing), “Locked“ (the closing procedure has not succeeded and ECONS I is locked) or “Closed“ (ECONS I is closed)

Reference Date Display the Reference Date

Business Date Display the Business Date

The following action buttons are available in this screen only for SSP Opera-tor:


Open/Close Contingency

Opens or Closes the Contingency Session

Edit Opens the popup “Edit Date“

Change Business Date

Opens the popup “Change Business Date” to change the Business Date in the same Contingency session

Fields in screen





The following popups are available in this screen:

Popup Function

Open/Close Contingency

Opens or Closes the Contingency Session

Edit Opens the popup “Edit Date“

Change Business Date

Opens the popup “Change Business Date” to change the Business Date in the same Contingency session

After having selected “Open/Close Contingency” button a Receipt is shown in the screen.

Popups in screen

Popup Open/Close Contingency




The following entry is required in the popup:

Field Function

Reference Date Defined the new reference business date (yyyy-mm-dd)

The following action button is available in this screen only for SSP Operator:



Action in popup Edit Date

Action button in popup Edit Date

Popup Edit Date




The following entry is required in the popup:

Field Function

Business Date Defined the new business date (yyyy-mm-dd)

The following action button is available in this screen only for SSP Opera-tor:



It is possible to use ECONS I for a number of consecutive days (up to 5) and to close the business day.

General Ledger and Raw Data files will be respectively sent out and pro-vided at the end of each EoD performed in Contingency Service session spanning over several business days.

ECONS I sends out general ledger files and raw data files for each affected day of the contingency session, using the same transmission channel al-ready in place.

Popup Change Business Date

Action in popup Change Business Date

Action button in popup Edit Date




The total balances per ECONS I accounts are transferred only at the end of the contingency session to PM even if the contingency session is lasting longer than one business day.

The affected days of the contingency session have to be set as closing days in the T2 calendar in SD.

The possible consideration of the additional liquidity provided in the ECONS I for the interim business days of the contingency session for the compulsory reserve has to be managed by the CBs manually.

The contingency session is kept open till the other T2 modules (incl. PM) have been aligned with the ECONS I business day, i.e. the business day of the restart have been opened and the interim days have been skipped. Af-ter opening the aligned business day in the other TARGET2 modules the contingency session can be closed and the balances will be transferred from the ECONS I to PM.




1.3.2.4.2 Screen: Open Account

In this screen the SSP Operator can create a new account.

It is mandatory that the created account is present in SD/PM when the ECONS I session will be closed otherwise the balance transfer process will be blocked.

• SSP: All data

Screen

Screen descrip-tion






Field Meaning

Responsible Central Bank

Possible values are:

• Country Code



Participant Type Possible values are:

• “Credit Institution“ • “Central Bank“

Account Code [text box]

Selects a participant account number

Balance Report Possible values are:

• “MT940“ • “MT950“ • “None“

BIC used for Notifi-cation [text box]


The following action button is available in this screen only for SSP Operator:



Fields in screen





1.3.2.4.3 Screen: Select Task “Queue“

In this screen the user can select one tasks for displaying, confirmation or rejection in the following screens.

• SSP: All data




Field Meaning

Kind of task Kind of task; possible values are:

Open Contingency (only SSP Operator)

Open Account (only SSP Operator)

“Liquidity Transfer“ (in case of payments or liquidity injec-tions/liquidity drains)

Close Contingency (only SSP Operator) Re-Open Contingency (only SSP Operator)

Record ID This is the functional key the task is related to. i.e. If kind of task is “Liquidity Transfers“, then the Record ID is the amount of the liquidity transfer.

Screen

Screen descrip-tion


Fields in screen




Field Meaning

Status Status of the task; possible values are:

• “To confirm“ • “Completed“ • “Rejected“ • “Revoked“ • “Waiting for NCB approval”

Entry Time Displays the entry timestamp (yyyy-mm-dd-hh:mm:ss)

User Distinguish name of the user who inserted the task

Central Bank BIC Selects a CB by its BIC

The following actions are available in this screen:

Field Meaning

Kind of task [combo box]

Used to select a specific kind of task

Record ID [text box]

Used to select tasks with a specific Record ID

Status [combo box]

Used to select tasks with a specific status

Central Bank BIC Selects a CB by its BIC

[selection] Selects a single task in the displayed list

Actions in screen




The following action buttons are available in this screen:


Details Opens the popup “Task Details“

Submit Displays the list of tasks according to the selected criteria

The following popup is available in this screen:

Popup Function

Task Details Displays detailed information about the selected task and allows to confirm/reject, agree/disagree it

The Contingency Services attempt settlement of a payment order immedi-ately after it has been submitted for settlement by the party (2 eyes or 4 eyes) and agreed (only in 2 eyes mode) by the Central Bank. If the first at-tempt fails, the Contingency Services reject the payment order (no queuing mechanism is in place).


Popups in screen




Field in the popup

Field Meaning

Record ID This is the functional key the task is related to.

User Distinguish name of the user who previously inserted the task

Kind of task Kind of task

Status Status of task

Amount Transaction Amount Note: this field is available for the following kind of tasks:

• “Liquidity Transfer“

Popup - Task de-tails (Liquidity transfer)

Fields in popup Task Details




Field Meaning

Debtor ID Debtor BIC Note: this field is available for the following kind of tasks:


Creditor ID Creditor BIC Note: this field is available for the following kind of tasks:


TRN Transaction Reference Number Note: this field is available for the following kind of tasks:


The following action buttons are available in the popup:


Confirm Is used to confirm the task in status “To confirm”.

Reject Is used to reject the task in status “To confirm”.

Agree Is used to confirm the task “Waiting for NCB approval”

Disagree Is used to reject the task “Waiting for NCB approval”

Note: These action buttons will be available only in case of tasks in status “To confirm“ or “Waiting for NCB approval”.

Action buttons in popup

Documents

1 ECONS I User Handbook · 2019. 7. 24. · 1 ECONS I User Handbook 1.1.1 Use of ECONS I Version 13.0 – 24 July 2019 - TARGET2 ECONS I User handbook 1 1 ECONS I User Handbook 1.1