| ISO20022

Note

The use of this message type requires Message User Group (MUG) registration.

Important!

The user header of the message (block 3) is mandatory and must contain a code in the Validation Flag field 119 ( {3:{119:xxxx}} ) to identify the exposure type or collateral reason.

These codes may be used for routing purposes.

MT507 Scope

This message is sent by the Receiver of a collateral claim, a collateral proposal or a proposal/request for collateral substitution.

It is used to advise the status of the received message.

It may also be used to:

reject a collateral claim, collateral proposal or the proposal/request of a collateral substitution
accept a collateral claim, collateral proposal or the proposal/request of a collateral substitution
advise the settlement details of proposed collateral
reply to a cancellation request previously sent by the Receiver
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)

MT507 Format Specifications

The status and processing advice consists of two sequences:

Sequence A General Information provides general information about the message the status and processing advice refers to, that is, the function of the message, the identification of the collateral transaction, the references of the linked messages, the identification of the underlying agreement(s), the identification of the parties, the reason for which collateral is needed (the exposure type), the contact information and the status and reason information.

Note
More than one occurrence of the agreement is only authorised for cross-product collateralisation and when there is no overall master agreement in place yet.
Sequence B Collateral Details provides status and reason information related to specific pieces of collateral and contains further settlement details for the accepted collateral pieces of securities or cash collateral.

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
-----> Mandatory Repetitive Subsequence A1 Agreement
M	16R			Start of Block	AGRE	4
O	22F	AGRE	Indicator	Agreement Indicator	:4!c/[8c]/4!c	5
O	98A	AGRE	Date/Time	Agreement Date	:4!c//8!n	6
O	13B	AGRE	Number Identification	Agreement Version Number	:4!c/[8c]/30x	7
O	70C	AGRE	Narrative	Agreement Narrative	:4!c//4*35x	8
M	16S			End of Block	AGRE	9
-----\| End of Subsequence A1 Agreement
O	98a	PREP	Date/Time	Preparation Date/Time	A, C, or E	10
M	22a	COLA	Indicator	Exposure Type Indicator	F or H	11
----->
M	95a	4!c	Party	(see qualifier description)	P, Q, or R	12
-----\|
M	25D	4!c	Status Code	(see qualifier description)	:4!c/[8c]/4!c	13
O	24B	4!c	Reason Code	(see qualifier description)	:4!c/[8c]/4!c	14
----->
O	70a	4!c	Narrative	(see qualifier description)	C or D	15
-----\|
-----> Mandatory 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
-----> Optional Repetitive Sequence B Collateral Details
M	16R			Start of Block	COLD	21
M	20C	COLR	Reference	Collateral Reference	:4!c//16x	22
M	22H	COLL	Indicator	Collateral Type Indicator	:4!c//4!c	23
M	25D	COLL	Status Code	Collateral Status	:4!c/[8c]/4!c	24
O	24B	REJT	Reason Code	Rejection Reason	:4!c/[8c]/4!c	25
O	70D	REAS	Narrative	Reason Narrative	:4!c//6*35x	26
Optional Subsequence B1 General Settlement Details
M	16R			Start of Block	SETTL	27
Optional Subsequence B1a Settlement Details
M	16R			Start of Block	SETDET	28
----->
M	22a	4!c	Indicator	(see qualifier description)	F or H	29
-----\|
-----> Optional Repetitive Subsequence B1a1 Settlement Parties
M	16R			Start of Block	SETPRTY	30
----->
M	95a	4!c	Party	(see qualifier description)	C, P, Q, R, or S	31
-----\|
O	97a	4!c	Account	(see qualifier description)	A, B, or D	32
O	70C	PACO	Narrative	Party Narrative	:4!c//4*35x	33
M	16S			End of Block	SETPRTY	34
-----\| End of Subsequence B1a1 Settlement Parties
M	16S			End of Block	SETDET	35
End of Subsequence B1a Settlement Details
Optional Subsequence B1b Cash Settlement Details
M	16R			Start of Block	CASHSET	36
O	22F	STCO	Indicator	Settlement Transaction Condition Indicator	:4!c/[8c]/4!c	37
-----> Optional Repetitive Subsequence B1b1 Cash Parties
M	16R			Start of Block	CSHPRTY	38
----->
M	95a	4!c	Party	(see qualifier description)	P, Q, R, or S	39
-----\|
----->
O	97a	4!c	Account	(see qualifier description)	A or E	40
-----\|
O	70C	PACO	Narrative	Party Narrative	:4!c//4*35x	41
M	16S			End of Block	CSHPRTY	42
-----\| End of Subsequence B1b1 Cash Parties
M	16S			End of Block	CASHSET	43
End of Subsequence B1b Cash Settlement Details
M	16S			End of Block	SETTL	44
End of Subsequence B1 General Settlement Details
M	16S			End of Block	COLD	45
-----\| End of Sequence B Collateral Details
Optional Sequence C Additional Information
M	16R			Start of Block	ADDINFO	46
----->
O	95a	4!c	Party	(see qualifier description)	P, Q, or R	47
-----\|
M	16S			End of Block	ADDINFO	48
End of Sequence C Additional Information

MT507 Network Validated Rules

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

Sequence A if field :20C::SCTR is ...	Sequence A then field :20C::RCTR is ...
Not present	Mandatory
Present	Optional

C2 The presence of sequence B depends on the value of field :25D::4!c//<Status> in sequence A and the value of field :13A::LINK//<Number Id> in subsequence A2 as follows:

Sequence A if field :25D::4!c/[8c]/4!c Qualifier is ...	Sequence A and field :25D::REST/[8c]/4!c Data Source Scheme [8c] is ...	Sequence A and field :25D::REST/[8c]/4!c is ...	Subsequence A2 and field :13A::LINK//3!c is ...	Then sequence B is ...
REST	Not present	:25D::REST//ACCP	503	Optional
		:25D::REST//ACCT	503	Optional
		:25D::REST//ACCP	504	Mandatory
		:25D::REST//ACCT	504	Mandatory
		:25D::REST//ACCP	505	Optional
		:25D::REST//ACCT	505	Optional
		:25D::REST//SUBR	Not applicable	Optional
		:25D::REST//REJT	Not applicable	Not allowed
	Present	Not applicable	Not applicable	Optional
CPRC	Not applicable	Not applicable	Not applicable	Not allowed
IPRC	Not applicable	Not applicable	Not applicable	Not allowed

C3 In each occurrence of sequence B, the presence of subsequence B1 depends on the value of field :25D::COLL//<Status> and :22H::COLL//<Indicator> as follows:

In each occurrence of sequence B
If for field :25D::COLL/[8c]/4!c Data Source Scheme [8c] is ...	And field :25D::COLL/[8c]/4!c is ...	And field :22H::COLL//4!c is ...	Then subsequence B1 is ...
Not present	:25D::COLL//ACCT	BCOL	Not allowed
	:25D::COLL//ACCT	CCOL	Mandatory ⁽¹⁾
	:25D::COLL//ACCT	SCOL	Mandatory ⁽¹⁾
	:25D::COLL//REJT	Not applicable	Not allowed
Present	Not applicable	BCOL	Not allowed
	Not applicable	CCOL	Optional ⁽¹⁾
	Not applicable	SCOL	Optional ⁽¹⁾

⁽¹⁾ see rule C11 for additional checks.

C4 In each occurrence of sequence B, for subsequences B1a1 and B1b1, the following party fields cannot appear more than once:

Subsequence B1a1	Subsequence B1b1
:95a::BUYR	:95a::ACCW
:95a::DEAG	:95a::BENM
:95a::DECU	:95a::PAYE
:95a::DEI1	:95a::DEBT
:95a::DEI2	:95a::INTM
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL

C5 It is mandatory to specify a Receiving Agent for the Securities Settlement Parties (subsequences B1a1):
In each occurrence of sequence B (if present), if subsequence B1a1 Securities Settlement Parties is present, then field :95a::REAG must be present in one and only one occurrence of subsequence B1a1 in the same occurrence of sequence B.

Note
See also Network Validated Rule C4.

C6 In each occurrence of sequence B, if a qualifier from the list Deliverers is present in one occurrence of subsequence B1a1 in a field :95a::4!c, then all the remaining qualifiers following this qualifier in the list Deliverers (see below) must be present in other subsequences B1a1 of the same occurrence of sequence B.

In other words, in each occurrence of sequence B, the following scenarios must be validated:

If :95a::DEI2 is present in subsequence B1a1, then :95a::DEI1 must be present in another subsequence B1a1.
If :95a::DEI1 is present in subsequence B1a1, then :95a::DECU must be present in another subsequence B1a1.
If :95a::DECU is present in subsequence B1a1, then :95a::SELL must be present in another subsequence B1a1.

In each occurrence of sequence B, if a qualifier from the list Receivers is present in one occurrence of subsequence B1a1 in a field :95a::4!c, then all the remaining qualifiers following this qualifier in the list Receivers (see below) must be present in other subsequences B1a1 of the same occurrence of sequence B.

In other words, in each occurrence of sequence B, the following scenarios must be validated:

If :95a::REI2 is present in subsequence B1a1, then :95a::REI1 must be present in another subsequence B1a1.
If :95a::REI1 is present in subsequence B1a1, then :95a::RECU must be present in another subsequence B1a1.
If :95a::RECU is present in subsequence B1a1, then :95a::BUYR must be present in another subsequence B1a1.

Deliverers		Receivers
DEI2	Deliverer's Intermediary 2	REI2	Receiver's Intermediary 2
DEI1	Deliverer's Intermediary 1	REI1	Receiver's Intermediary 1
DECU	Deliverer's Custodian	RECU	Receiver's Custodian
SELL	Seller (Deliverer)	BUYR	Buyer (Receiver)

C7 In each occurrence of subsequence B1a, the presence of the subsequence B1a1 depends on the presence of field :22F::STCO//NSSP as follows:

In each occurrence of subsequence B1a
if field :22F::STCO//NSSP is ... ⁽¹⁾

In the same occurrence of subsequence B1a
then subsequence B1a1 is ...

Not present

Optional

Present

Mandatory

⁽¹⁾ if the Data Source Scheme is present in field :22F::STCO//NSSP then the conditional rule does not apply.
C8 In each occurrence of subsequence B1b, the presence of the subsequence B1b1 depends on the presence of field :22F::STCO//NSSP as follows:

In each occurrence of subsequence B1b
if field :22F::STCO//NSSP is ... ⁽¹⁾

In the same occurrence of subsequence B1b
then subsequence B1b1 is ...

Not present

Optional

Present

Mandatory

⁽¹⁾ if the Data Source Scheme is present in field :22F::STCO//NSSP then the conditional rule does not apply.
C9 In each occurrence of subsequence A1, if field :22F::AGRE is not present, then field :70C::AGRE is mandatory, otherwise field :70C::AGRE is optional.

In each occurrence of subsequence A1
if field :22F::AGRE is ...

In the same occurrence of subsequence A1
then field :70C::AGRE is ...

Not present

Mandatory

Present

Optional
C10 The user header of the message (block 3) is mandatory and must contain a valid code in the Validation Flag field 119 ( {3:{119:xxxx}} ). This code must be identical to the code contained in field :22a::COLA//xxxx (Exposure Type Indicator) in sequence A of the message content (text block 4).

In each occurrence of subsequence B1a if field :22F::STCO//NSSP is ... ⁽¹⁾	In the same occurrence of subsequence B1a then subsequence B1a1 is ...
Not present	Optional
Present	Mandatory

In each occurrence of subsequence B1b if field :22F::STCO//NSSP is ... ⁽¹⁾	In the same occurrence of subsequence B1b then subsequence B1b1 is ...
Not present	Optional
Present	Mandatory

In each occurrence of subsequence A1 if field :22F::AGRE is ...	In the same occurrence of subsequence A1 then field :70C::AGRE is ...
Not present	Mandatory
Present	Optional

C11 In each occurrence of sequence B (if present), if subsequence B1 is present, the presence of subsequences B1a and B1b depends on the value of field :22H::COLL//<Indicator> in sequence B as follows:

In each occurrence of sequence B
If subsequence B1 is ...	Sequence B and field :22H::COLL//4!c is ...	Then subsequence B1a is ...	And subsequence B1b is ...
Present	CCOL	Not allowed	Mandatory
	SCOL	Mandatory	Not allowed
	BCOL Not applicable see rule C3 (Error code(s): C70).	Not applicable	Not applicable
Not present	Not applicable	Not applicable	Not applicable

C12 Field :13a::LINK must be present in one and only one occurrence of subsequence A2.

Note
See also Network Validated Rule C13.
C13 Field:20C::RELA must be present in the same occurrence of subsequence A2 where field :13a::LINK is present.

Note
See also Network Validated Rule C12.

MT507 Usage Rules

The exchange of information related to the trade itself as well as to the settlement of the collateral is done with the existing confirmation and settlement messages of the relevant categories (categories 2, 3, 5, 7, 9).