This message is sent by a triparty agent after the receipt of a collateral instruction from its client.
In this message, the Sender is the triparty agent and the Receiver is either the collateral taker or the collateral giver.
This message provides valuation results as well as the status of the collateral instruction and the status of the proposed collateral movements (cash and securities).
re-send a message previously sent (Subfunction of the message is DUPL)
provide a third party with a copy of the message for information (Subfunction of the message is COPY)
re-send to a third party a copy of the message for information (Subfunction of the message is CODU)
| Status | Tag | Qualifier | Generic Field Name | Detailed Field Name | Content/Options | No. |
Mandatory Sequence A General Information |
||||||
| M | 16R | Start of Block | GENL | 1 | ||
-----> |
||||||
| M | 20C | 4!c | Reference | (see qualifier description) | :4!c//16x | 2 |
-----| |
||||||
| M | 23G | Function of the Message | 4!c[/4!c] | 3 | ||
-----> |
||||||
| M | 98a | 4!c | Date/Time | (see qualifier description) | A or C | 4 |
-----| |
||||||
-----> |
||||||
| M | 22a | 4!c | Indicator | (see qualifier description) | F or H | 5 |
-----| |
||||||
-----> |
||||||
| O | 13B | 4!c | Number | (see qualifier description) | :4!c/[8c]/30x | 6 |
-----| |
||||||
-----> Mandatory Repetitive Subsequence A1 Collateral Parties |
||||||
| M | 16R | Start of Block | COLLPRTY | 7 | ||
| M | 95a | 4!c | Party | (see qualifier description) | P, Q, or R | 8 |
| O | 97a | SAFE | Account | Safekeeping Account | A or B | 9 |
| M | 16S | End of Block | COLLPRTY | 10 | ||
-----| End of Subsequence A1 Collateral Parties |
||||||
| O | 25D | 4!c | Status | (see qualifier description) | :4!c/[8c]/4!c | 11 |
| O | 24B | 4!c | Reason | (see qualifier description) | :4!c/[8c]/4!c | 12 |
| O | 17B | CAPP | Flag | Collateral Approved Flag | :4!c//1!a | 13 |
| O | 19A | RMAG | Amount | Required Margin Amount | :4!c//[N]3!a15d | 14 |
-----> |
||||||
| O | 70a | 4!c | Narrative | (see qualifier description) | D or E | 15 |
-----| |
||||||
-----> Optional Repetitive Subsequence A2 Linkages |
||||||
| M | 16R | Start of Block | LINK | 16 | ||
| O | 13a | LINK | Number Identification | Linked Message | A or B | 17 |
| M | 20C | 4!c | Reference | (see qualifier description) | :4!c//16x | 18 |
| M | 16S | End of Block | LINK | 19 | ||
-----| End of Subsequence A2 Linkages |
||||||
| M | 16S | End of Block | GENL | 20 | ||
End of Sequence A General Information |
||||||
Mandatory Sequence B Deal Transaction Details |
||||||
| M | 16R | Start of Block | DEALTRAN | 21 | ||
| M | 98a | TERM | Date/Time | Closing Date/Time | A, B, or C | 22 |
-----> |
||||||
| O | 19A | 4!c | Amount | (see qualifier description) | :4!c//[N]3!a15d | 23 |
-----| |
||||||
-----> |
||||||
| O | 92a | 4!c | Rate | (see qualifier description) | A or C | 24 |
-----| |
||||||
| O | 22F | MICO | Indicator | Method of Interest Computation Indicator | :4!c/[8c]/4!c | 25 |
| M | 16S | End of Block | DEALTRAN | 26 | ||
End of Sequence B Deal Transaction Details |
||||||
-----> Optional Repetitive Sequence C Securities Movement |
||||||
| M | 16R | Start of Block | SECMOVE | 27 | ||
| M | 22H | INOU | Indicator | In/Out Indicator | :4!c//4!c | 28 |
| M | 35B | Identification of Financial Instrument | [ISIN1!e12!c] [4*35x] |
29 | ||
| M | 36B | QSEC | Quantity of Financial Instrument | Quantity of Securities | :4!c//4!c/15d | 30 |
| O | 25D | MOVE | Status | Movement Status | :4!c/[8c]/4!c | 31 |
-----> |
||||||
| M | 17B | 4!c | Flag | (see qualifier description) | :4!c//1!a | 32 |
-----| |
||||||
-----> |
||||||
| O | 20C | 4!c | Reference | (see qualifier description) | :4!c//16x | 33 |
-----| |
||||||
| O | 19A | MAGV | Amount | Margined Value Amount | :4!c//[N]3!a15d | 34 |
| M | 16S | End of Block | SECMOVE | 35 | ||
-----| End of Sequence C Securities Movement |
||||||
-----> Optional Repetitive Sequence D Cash Movements |
||||||
| M | 16R | Start of Block | CASHMOVE | 36 | ||
| M | 22H | INOU | Indicator | In/Out Indicator | :4!c//4!c | 37 |
| M | 19A | CASH | Amount | Cash Movement Amount | :4!c//[N]3!a15d | 38 |
-----> |
||||||
| O | 20C | 4!c | Reference | (see qualifier description) | :4!c//16x | 39 |
-----| |
||||||
| O | 25D | MOVE | Status | Movement Status | :4!c/[8c]/4!c | 40 |
-----> |
||||||
| M | 17B | 4!c | Flag | (see qualifier description) | :4!c//1!a | 41 |
-----| |
||||||
| M | 16S | End of Block | CASHMOVE | 42 | ||
-----| End of Sequence D Cash Movements |
||||||
Optional Sequence E Additional Information |
||||||
| M | 16R | Start of Block | ADDINFO | 43 | ||
-----> |
||||||
| O | 95a | 4!c | Party | (see qualifier description) | P, Q, or R | 44 |
-----| |
||||||
| M | 16S | End of Block | ADDINFO | 45 | ||
End of Sequence E Additional Information |
||||||
C1. In sequence A, if field :20C::SCTR is not present, then field :20C::RCTR is mandatory, otherwise field :20C::RCTR is optional .
Sequence A if field:20C::SCTR is ... |
Sequence A then field :20C::RCTR is ... |
Not present |
Mandatory |
Present |
Optional |
C2. In sequence A, the presence of fields :25D:: and :24B:: depends on the value of field :23G:<Function> subfield 1 as follows :
Sequence A |
||
if value of field :23G:4!c[/4!c] subfield 1 is ... |
then field :25D:: is ... |
and field :24B:: is ... |
ADVD |
Not allowed |
Not allowed |
Not ADVD |
Mandatory |
Optional |
C3. If sequence A field :22a::COLA// is other than SLEB, then sequence B field :19A::TRAA must be present .
Sequence A field :22a::COLA is ... |
then sequence B field : 19A::TRAA is ... |
SLEB |
Optional |
not SLEB if the Data Source Scheme is present in field :22F::COLA// then the conditional rule does not apply. |
Mandatory |
The triparty collateral management service is used by two trading parties at the agreement of a business transaction (eg, a repo, a securities loan, ... ) when they want to secure the transaction with collateral. The management of this collateral (ie, agreeing on quantity and type, marking to market, ... ) is done by a third party, the triparty collateral manager.
Before starting to use these services, the three parties will first sign a contract in which they stipulate the rules of the agreement.
collateral management without settlement,
collateral management with settlement of the collateral on the books of the agent,
collateral management with external settlement.
In the first scenario the triparty agent will calculate the necessary quantity of collateral and instruct the trading parties on which movements need to occur. Eg, party A and party B closed a repo deal for 1,000,000 USD. They inform the triparty agent of the deal details. The agent will then calculate which pieces of collateral need to be moved to cover the 1,000,000 USD exposure and will inform the trading parties. Parties A and B then settle the movements as instructed by the agent.
In the second scenario the triparty agent will also execute the settlement. By servicing a safekeeping account for both parties, the agent will not only calculate the necessary movements but will also settle them internally on its books.
The third scenario is only a slight deviation from the second one. In this case the agent has the authority to move securities from party A's and B's safekeeping accounts with their respective subcustodians.
Collateral Management Transaction
The triparty agent will create this transaction on receipt of the deal information from the two trading parties. Eg, when party A and B have agreed on a securities loan and have reported this information to the triparty agent, the agent will create a collateral management transaction to manage this securities loan on its internal systems.
A transaction is created, can be changed and is terminated.
Collateral Management Instruction
The trading parties will request the triparty manager to perform certain instructions on the collateral management transaction. An instruction can be to initiate a transaction, modify the terms of a transaction, or close a transaction (non-exhaustive list of instructions). The triparty agent will send feedback on the requested instruction.
Lifecycle of Collateral Management Transaction
When a transaction is initiated, agreed on by both parties, accepted and declared valid by the triparty agent, the lifecycle of the transaction starts. The transaction will normally last as long as the underlying deal. At the end of its lifecycle a transaction is closed.
Lifecycle of Collateral Management Instruction
The lifecycle of a collateral management instruction starts when the user of the triparty service sends an instruction message. At receipt of the instruction message, the triparty agent will process the instruction and assign a status (ie, valid or rejected). At each step in the lifecycle of an instruction a different status will be assigned. Eg, an instruction can be valid for processing or rejected because it is incorrect. If an instruction needs to be matched (eg, two initiation- instructions from party A and B need to match) it can have a status matched or unmatched. Other statuses describe the sufficiency or eligibility of the collateral.
When the MT558 is sent as an allegement/advice (:23G:ADVD), fields 25D Status, 24B Reason, 17B Collateral Approved Flag, 19A Required Margin Amount must not be used as they have no business meaning in an allegement. Sequences Securities Movement (C) and Cash Movement (D) must neither be used.