MT536 Scope
This message is sent by an account servicer (account servicing institution) to an account owner or its designated agent. The account servicer may be a local agent (sub custodian) acting on behalf of their global custodian customer, or a custodian acting on behalf of an investment management institution or a broker/dealer.
This message is used to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for the account owner.
This message may be used as a trade date based (:22F::STBA//TRAD) or a settlement date based statement (22F::STBA//SETT).
This message may also be used to respond to a request for statement/status advice, that is, the MT 549 Request for Statement/Status Advice and to report that there are no transactions for the specified period of time.
MT536 Format Specifications
Status | Tag | Qualifier | Generic Field Name | Detailed Field Name | Content/Options | No. |
---|---|---|---|---|---|---|
Mandatory Sequence A General Information |
||||||
M |
16R |
|
|
GENL | 1 |
|
M |
28E |
|
|
5n/4!c | 2 |
|
O |
13a |
STAT |
Number Identification |
A or J | 3 |
|
M |
20C |
SEME |
Reference |
:4!c//16x | 4 |
|
M |
23G |
|
|
4!c[/4!c] | 5 |
|
O |
98a |
PREP |
Date/Time |
A, C, or E | 6 |
|
M |
69a |
STAT |
Period |
A or B | 7 |
|
-----> |
||||||
M |
22F |
4!c |
Indicator |
:4!c/[8c]/4!c | 8 |
|
-----| |
||||||
-----> Optional Repetitive Subsequence A1 Linkages |
||||||
M |
16R |
|
|
LINK | 9 |
|
O |
13a |
LINK |
Number Identification |
A or B | 10 |
|
M |
20C |
4!c |
Reference |
:4!c//16x | 11 |
|
M |
16S |
|
|
LINK | 12 |
|
-----| End of Subsequence A1 Linkages |
||||||
-----> |
||||||
O |
95a |
4!c |
Party |
L, P, or R | 13 |
|
-----| |
||||||
M |
97a |
4!c |
Account |
A, B, or D | 14 |
|
-----> |
||||||
M |
17B |
4!c |
Flag |
:4!c//1!a | 15 |
|
-----| |
||||||
M |
16S |
|
|
GENL | 16 |
|
End of Sequence A General Information |
||||||
-----> Optional Repetitive Sequence B Sub-safekeeping Account |
||||||
M |
16R |
|
|
SUBSAFE | 17 |
|
-----> |
||||||
O |
95a |
4!c |
Party |
L, P, or R | 18 |
|
-----| |
||||||
O |
97a |
4!c |
Account |
A, B, or D | 19 |
|
-----> |
||||||
O |
94a |
SAFE |
Place |
B, C, F, or L | 20 |
|
-----| |
||||||
O |
17B |
ACTI |
Flag |
:4!c//1!a | 21 |
|
-----> Optional Repetitive Subsequence B1 Financial Instrument |
||||||
M |
16R |
|
|
FIN | 22 |
|
M |
35B |
|
|
[ISIN1!e12!c] | 23 |
|
O |
90a |
4!c |
Price |
A or B | 24 |
|
O |
94B |
PRIC |
Place |
:4!c/[8c]/4!c[/30x] | 25 |
|
O |
98a |
PRIC |
Date/Time |
A or C | 26 |
|
-----> |
||||||
O |
93a |
4!c |
Balance |
B or F | 27 |
|
-----| |
||||||
-----> Mandatory Repetitive Subsequence B1a Transaction |
||||||
M |
16R |
|
|
TRAN | 28 |
|
-----> Mandatory Repetitive Subsequence B1a1 Linkages |
||||||
M |
16R |
|
|
LINK | 29 |
|
O |
13a |
LINK |
Number Identification |
A or B | 30 |
|
M |
20a |
4!c |
Reference |
C or U | 31 |
|
M |
16S |
|
|
LINK | 32 |
|
-----| End of Subsequence B1a1 Linkages |
||||||
Optional Subsequence B1a2 Transaction Details |
||||||
M |
16R |
|
|
TRANSDET | 33 |
|
-----> |
||||||
O |
94a |
4!c |
Place |
B, C, F, H, or L | 34 |
|
-----| |
||||||
-----> |
||||||
M |
36a |
PSTA |
Quantity of Financial Instrument |
B or D | 35 |
|
-----| |
||||||
O |
99A |
DAAC |
Number Count |
:4!c//[N]3!n | 36 |
|
-----> |
||||||
O |
19A |
4!c |
Amount |
:4!c//[N]3!a15d | 37 |
|
-----| |
||||||
-----> |
||||||
M |
22a |
4!c |
Indicator |
F or H | 38 |
|
-----| |
||||||
-----> |
||||||
M |
98a |
4!c |
Date/Time |
A, B, C, or E | 39 |
|
-----| |
||||||
O |
25D |
MOVE |
Status Code |
:4!c/[8c]/4!c | 40 |
|
O |
70E |
TRDE |
Narrative |
:4!c//10*35x | 41 |
|
-----> Optional Repetitive Subsequence B1a2A Settlement Parties |
||||||
M |
16R |
|
|
SETPRTY | 42 |
|
-----> |
||||||
M |
95a |
4!c |
Party |
C, L, P, Q, or R | 43 |
|
-----| |
||||||
O |
97a |
4!c |
Account |
A, B, or D | 44 |
|
O |
20C |
PROC |
Reference |
:4!c//16x | 45 |
|
M |
16S |
|
|
SETPRTY | 46 |
|
-----| End of Subsequence B1a2A Settlement Parties |
||||||
M |
16S |
|
|
TRANSDET | 47 |
|
End of Subsequence B1a2 Transaction Details |
||||||
M |
16S |
|
|
TRAN | 48 |
|
-----| End of Subsequence B1a Transaction |
||||||
M |
16S |
|
|
FIN | 49 |
|
-----| End of Subsequence B1 Financial Instrument |
||||||
M |
16S |
|
|
SUBSAFE | 50 |
|
-----| End of Sequence B Sub-safekeeping Account |
||||||
Optional Sequence C Additional Information |
||||||
M |
16R |
|
|
ADDINFO | 51 |
|
-----> |
||||||
O |
95a |
4!c |
Party |
P, Q, or R | 52 |
|
-----| |
||||||
M |
16S |
|
|
ADDINFO | 53 |
|
End of Sequence C Additional Information |
MT536 Network Validated Rules
C1 If the Activity Flag (field :17B:ACTI) in sequence A General Information is N, then sequence B must not be present. Otherwise, sequence B is mandatory.
Sequence A
if field :17B::ACTI is ...
Sequence B is ...
N
Not allowed
Y
Mandatory
C2 If the instruction is against payment (:22H::PAYM//APMT) then it is mandatory to specify a Posting Amount (field :19A::PSTA). This rule applies to subsequence B1a2.
Subsequence B1a2
if field :22H::PAYM is ...
Subsequence B1a2
then field :19A::PSTA is ...
APMT
Mandatory
Not equal to APMT
Optional
C3 In each occurrence of subsequence B1a, in subsequence B1a2, the following Party Fields cannot appear more than once:
Subsequence B1a2a
:95a::BUYR
:95a::DEAG
:95a::DECU
:95a::DEI1
:95a::DEI2
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL
C4 If a qualifier from the list Deliverers/1 is present in a subsequence B1a2a, in a field :95a::4!c, then all the remaining qualifiers following this qualifier in the list Deliverers/1 (see below) must be present.
In other words, in subsequence B1a2, the following scenarios must be validated:
If :95a::DEI2 is present in subsequence B1a2a, then :95a::DEI1 must be present in another subsequence B1a2a.
If :95a::DEI1 is present in subsequence B1a2a, then :95a::DECU must be present in another subsequence B1a2a.
If :95a::DECU is present in subsequence B1a2a, then :95a::SELL must be present in another subsequence B1a2a.
If a qualifier from the list Receivers/1 is present in a subsequence B1a2a, in a field :95a::4!c, then all the remaining qualifiers following this qualifier in the list Receivers/1 (see below) must be present.
In other words, in subsequence B1a2, the following scenarios must be validated:
If :95a::REI2 is present in subsequence B1a2a, then :95a::REI1 must be present in another subsequence B1a2a.
If :95a::REI1 is present in subsequence B1a2a, then :95a::RECU must be present in another subsequence B1a2a.
If :95a::RECU is present in subsequence B1a2a, then :95a::BUYR must be present in another subsequence B1a2a.
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)
C5 If the message is a cancellation, that is, Function of the Message (field 23G) is CANC, then subsequence A1 (Linkages) must be present at least once in the message, and in one and only one occurrence of A1, field :20C::PREV must be present; consequently, in all other occurrences of A1, field :20C::PREV is not allowed.
Sequence A
if field :23G: is ...
Then subsequence A1 is ...
And field :20C::PREV is ...
CANC
Mandatory (minimum one occurrence of A1 must be present)
Mandatory in one occurrence of subsequence A1, and not allowed in all other occurrences of subsequence A1
NEWM
Optional
Not applicable
C6 In subsequence B1a2a, if field :95a::PSET is present, then field :97a:: is not allowed in the same sequence.
Subsequence B1a2a
if field :95a::PSET is ...
Subsequence B1a2a
then field :97a:: is ...
Present
Not allowed within the same occurrence
Not Present
Optional
C7 If in sequence A field :17B::CONS=Y, then in every occurrence of sequence B Sub-safekeeping Account, field :97a:: and field :17B::ACTI are mandatory.
This check only applies when sequence B Sub-safekeeping Account is present as per rule C1, that is, in sequence A, field :17B::ACTI=Y.
Sequence A
if field :17B::ACTI is ...
Then sequence B is ...
And sequence A
if field :17B::CONS is ...
Then in every occurrence of sequence B
field :97a:: and field :17B::ACTI are ...
Y
Mandatory that is minimum one occurrence
Y
Mandatory
N
Not allowed
N
Not allowed
Not applicable
Not applicable
C8 If the Activity Flag (field :17B::ACTI) in sequence B Sub-safekeeping Account indicates no information to be reported, that is, N, then subsequence B1 Financial Instrument must not be present. subsequence B1 Financial Instrument is otherwise mandatory.
This check only applies when sequence B Sub-safekeeping Account is present per rule C1, that is, in sequence A, field :17B::ACTI=Y.
Sequence A
if field :17B::ACTI is ...
Then sequence B is ...
In every occurrence of sequence B
if field :17B::ACTI is ...
In the same occurrence of sequence B
then subsequence B1 is ...
Y
Mandatory that is minimum one occurrence
Y
Mandatory that is minimum one occurrence
N
Not allowed
Not present
Mandatory that is minimum one occurrence
N
Not allowed
Not applicable
Not applicable
C9 In each occurrence of subsequence B1a2, field :36B::PSTA cannot appear more than twice (maximum two occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR.
Sequence B1a2
if field :36B::PSTA is ...
Then one occurrence of :36B::PSTA must be ...
And the other occurrence of :36B::PSTA must be ...
Repeated
:36B::PSTA//FAMT
:36B::PSTA//AMOR
Not Repeated
Not applicable
Not applicable
C10 A reference to the previously received message must be specified for each transaction reported, that is in each occurrence of subsequence B1a Transaction, field :20C::RELA must be present in one and only one occurrence of subsequence B1a1 Linkages; field :20C::RELA is not allowed in all other occurrences of subsequence B1a1.
C11 In sequence A, if field :95L::ALTE is present, then field :95a::ACOW must be present.
In each occurrence of sequence B, if field :95L::ALTE is present, then field :95a::ACOW must be present.
C12 In each occurrence of sequence B, field :94a::SAFE must not be present more than twice. When repeated, one and only one occurrence must be with format option L (:94L::SAFE).
In subsequence B1a2, field :94a::CLEA must not be present more than twice. When repeated, one and only one occurrence must be with format option L (:94L::CLEA).
In subsequence B1a2, field :94a::SAFE must not be present more than twice. When repeated, one and only one occurrence must be with format option L (:94L::SAFE).
In subsequence B1a2, field :94a::TRAD must not be present more than twice. When repeated, one and only one occurrence must be with format option L (:94L::TRAD).
MT536 Usage Rules
This statement is used by the account servicer to report on increases and decreases of holdings which are held for the account owner.
The frequency of the statement must be bilaterally agreed between the account servicer and the account owner.
The optional balance fields are available to provide opening and closing balances per security within the holding.
Since a SWIFT message as sent is restricted to the maximum input message length, several messages may be needed to accommodate all the information.