Swift Codes and MT 527

To all Guru's....

I know that you want to keep people properly informed and I respect and appreciate that, especially when the information is positive and exciting.

These Swift Codes and MT 527, can be extremely complicated and unless you have Specific Knowledge in these areas, they should NOT be referenced.

My reason for stating this, is simply to avoid confusion and endless comments and questions, which nobody in the RV, needs to know about.

Respectfully, you are opening Pandor's Box and there is No Need To Do So.

These MT's etc, are designed primarily for the movement of Large Sums of money, in very Specialised, Private Transactions, that the ordinary person, doesn't even know exist

All Dinar Holders need to know, is that the Swifts and MT 527 are a Very, Very, Good Sign.

Let's Not Confuse Issues and Create Unnecessary Complications

As our beloved OKIE would say....

"NUFF SAID"

Feel free to copy this to other forums

Hey

Found this on mt527


MT527 Usage Rules

Triparty Scenario's

The triparty collateral management service is used by two trading parties at the agreement of a business transaction (for example, a repo, a securities loan, ... ) when they want to secure the transaction with collateral. The management of this collateral (that is, 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.

There are three types of triparty collateral management:

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. For example, 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.

Triparty Definitions

Collateral Management Transaction

The triparty agent will create this transaction on receipt of the deal information from the two trading parties. For example, 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 (that is, valid or rejected). At each step in the lifecycle of an instruction a different status will be assigned. For example, an instruction can be valid for processing or rejected because it is incorrect. If an instruction needs to be matched (for example, 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.

Delivery by Value (DBV) Scenario

A Delivery by Value (DBV) is a collateral mechanism whereby the collateral giver and collateral taker do not specify specific securities, but supply a value and a category of securities to the third party, for example, a CSD, which then allocates an appropriate basket of securities to the DBV transaction.

Collateral is automatically returned from the taker to the giver the next day, due to automated transactions created by the CSD in response to the DBV instruction. Each return transaction is created against a proportional payment of the original consideration of the DBV transaction (which may differ from the value of the basket of securities). This return is executed using regular settlement confirmation messages.



Does this mean good for us?

Go RV


Feisty136

Yes, very good.

Now, please drop the subject matter

We don't need to know this
and possibly cause unnecessary
complications

Feisty136 wrote:Hey

Found this on mt527


MT527 Usage Rules

Triparty Scenario's

The triparty collateral management service is used by two trading parties at the agreement of a business transaction (for example, a repo, a securities loan, ... ) when they want to secure the transaction with collateral. The management of this collateral (that is, 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.

There are three types of triparty collateral management:

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. For example, 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.

Triparty Definitions

Collateral Management Transaction

The triparty agent will create this transaction on receipt of the deal information from the two trading parties. For example, 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 (that is, valid or rejected). At each step in the lifecycle of an instruction a different status will be assigned. For example, an instruction can be valid for processing or rejected because it is incorrect. If an instruction needs to be matched (for example, 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.

Delivery by Value (DBV) Scenario

A Delivery by Value (DBV) is a collateral mechanism whereby the collateral giver and collateral taker do not specify specific securities, but supply a value and a category of securities to the third party, for example, a CSD, which then allocates an appropriate basket of securities to the DBV transaction.

Collateral is automatically returned from the taker to the giver the next day, due to automated transactions created by the CSD in response to the DBV instruction. Each return transaction is created against a proportional payment of the original consideration of the DBV transaction (which may differ from the value of the basket of securities). This return is executed using regular settlement confirmation messages.



Does this mean good for us?

Go RV


Feisty136