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

Compare with Current View Page History

« Previous Version 3 Next »

Statement is a document that contains summary information on agreements/reports/master agreements in the registry for a certain period of time. Client receives astatement report at the end of the operation day, if any documents were registered during the day. The statement report is also sent to the client upon request, which can be created in the Message Preparation form. To find details about statement format, refer to NSD’s trade repository messages specifications. In the Web-client statements are displayed in tables (Fig. 1), where each row contains information about one message thread: statement request→statement.


Fig. 1 – Statement form

These tables are subject to information display settings, described in section General Settings. 

Form elements

The Statements form contains the following information about documents:

  • Date – the date of the statement/report;

  • Party 1 – name of the company, acting as the first party to the contract, transaction, master agreement;

  • Party 2 – name of the company, acting as the second party to the contract, transaction, master agreement;

  • Сomment – comment to the report;
  • Status – type of a report;
  • Correlation ID – unique identification number of a notification chain.

Name of the user’s company, for which the current user is an RA or a party MA, is written in green.

Hovering the mouse pops up a toolbar. Description of the toolbar buttons is shown in Table 1.

Table 1 – Toolbar buttons

ButtonFunction
Print statement
Keep the first message of the chain in the xml file
Add a comment
Mark as read
Mark as unread

There are two ways to view report or statement:

  • click on the row in the table. This will open the additional information block, which contains the type and the identification number of the statement/report. The example of information block for the Statements form is presented in Fig. 2.  If the system has not identified which program the message was sent with (via personal user's system or the Web-client) the "" element will be displayed. Clicking on the icon or putting a mouse cursor over displays the message ID number.;


    Fig. 2 – information on
    registry statements

    After that click on the statement name, which is an active link. Then close the print settings dialog of your Web browser to view the report print form (Fig. 3).

    Fig. 3 – viewing a registry statement

  • сlick the  button, then close the print settings dialog of your Web browser to view the report print form.

 

Section contains information about the processing of messages.


Fig. 1 – Registration form

On this page:

 

 

 

Subforms

 

The Registration section contains Processing, Rejected, Requests, Registered and Pending subforms. Each form includes information about the individual registration chains – a sequence of messages between the party (reporting agent) and the repository associated with the registration of a single contract/report/master agreement. The registration of changes to the contract or master agreement is a separate chain. 

 

Icon

For example, if a party sends message for registration of agreement or changes of the registered contract to the repository, the chain will consist of following messages:

  1. Agrement registration message (message nonpublicExecutionReport) – message sent;
  2. Status notification message (message eventStatusResponse) – incoming message is about that the second party received the first message;
  3. Registration notification message (message nonpublicExecutionReportAcknowledgement) – incoming message that informs that the second party has confirmed the agreement and the repository has registered the chain.

Sending corrections to a previously sent message to the repsitory would initiate a child chain. For example, if a party sends an incorrect message to the repository, and the repository system rejects it because of wrong format, the chain will consist of two messages:

  1. Message for registration of changes from the client to the repository (message nonpublicExecutionReport);
  2. Error notification from the repository to the client (message nonpublicExecutionReportException).

To find out which message types a chain can contain, refer to NSD’s trade repository messages specifications.

 

The information on which registration chains contain subforms is provided in Table 1.

 

Table 1 – Description of the Registration section subforms

 

Form
Description

 

Processing

Contains chains in an idle state from the Web-client user’s viewpoint. There are two types of chains:

  • chains, in which the participant has sent a message and has not yet received a response from the repository;
  • chains, in which the party has received a notice by repository saying his message was sent to the counterparty for approval;
  • child chains of changing a previously sent (and not yet registered) message.
 Rejected

Contains:

  • chains, in which a notice has been received from the repository about processing rejection or a notice of registration rejection;
  • chains, in which the user has sent a rejection to a confirmation request. The reason for the rejection could be, for example, the discrepancy of the message and an xsd-scheme of the message format or the counterparty’s disagreement with the report terms;
  • child chains to cancellation of a previously sent (and not yet registered) message.
 Requests

Contains incoming request chains that for the given party start with an Approval request sent by the repository. This means that the registration process was initiated by the other party and the repository sent a request for approval to the current party.

If a user sends a message containing a mistake, then, according to its type, the following will happen:

  • if the error is critical (for example, the master agreement specified in the document has been canceled), the chain will move into Rejected form, and it will be impossible to perform any operations with the chain;
  • if the error is not critical (for example, the chain contains a validation error message), the chain will be available for further work.
 RegisteredContains completed chains of registered documents
Pending

Contains the electronic workflow system messages, encrypted on the party certificate and the servers of the Web-client cannot decrypt and display their contents to the user. Users must  decrypt them on their own

 

Form elements

 

Main table

 

Chains of messages are displayed in tables. Fig. 2 shows an example of a Registered form table.

 

 

Fig. 2 – example of a Registered form table

 

Each row corresponds to one registration chain. 

 

Icon

Chains of inactive master agreements are written in yellow. Name of the user’s company responsible for a certain role in the chain (under the MA this chain is associated with), is written in green.

 

A set of columns of the main table of the registration section form table is shown in Table 2.

 

Table 2 – Registration chain data

 

Column
Description

Date

Date of the last message in the chain (the date of receipt of the Pending form package)
ProductFinancial instrument
TypeChain object
Master agreementMaster agreement  identification code
Transaction number forparty 1Number of transaction assigned to the first part of the master agreement (optional)
Transaction number forparty 2Number of transaction assigned to the second part of the master agreement (optional)
Repository transaction numberNumber the repository assigns when processing a transaction
Party 1Name of the organization, acting as a party to the Master agreement
Party 2 Name of the organization, acting as a party to the Master agreement
RA of party 1 Name of the organization, designated the first party’s RA
RA of party  2Name of the organization, designated the second party’s RA
Сomment Comment to the chain  
BRA of party  1Name of the organization, designated the first party’s BRA
BRA of party  2Name of the organization, designated the second party’s BRA
StatusChain status. Depending on the tab can be either Processing, Rejected or Registered
Correlation IDChain ID number. If the chain has child chain of changing or cancellation, the ID of this chain is displayed in the column   

 

Icon

These tables are subject to information display settings, described in section General Settings.

 

Additional table

 

To view all messages associated with the chain, click on the row in the main table. An additional table with the entire message chain will appear to the right of the main table (Fig. 3).

 


Fig. 3 – example of a Registered tab table

 

The messages that belong to a child chain are displayed in red. If the sent message hasn't been delivered to the repository then the "" element will be displayed next to the message name. When the message will be delivered  the "" element will be displayed (Fig. 4). If the system has not identified which program the message was sent with (via personal user's system or the Web-client) the "" element will be displayed. Clicking on the icon or putting a mouse cursor over (Fig. 4) displays the message ID number.

 

 

Fig. 4 – the message ID number

 

 Each message can be viewed by clicking on its name, an active link (Fig. 5).

 


Fig. 5 – viewing messages

 

During message exchange process the user receives notifications. One of them is Matching differences report. For convenience of viewing of the data the background color of rows filled by user are orange, the background color of rows filled by contractor are violet (Fig. 6).

 

 

Fig. 6 – matching differences report

 

Clicking on the message button you can view the file in XML-format. This format is used for importing files.

 

Filter settings

 

The principle of filtering data in the table described in Filter settings. In the Statement form the following filters are available:

 

  • Date (from/to) – the date of receiving statement;
  • Unread – display all unread messages; 
  • Search by string – search by the comment, correlation id and the transaction number;
  • Parties – the parties of the fill.


  • No labels