MT537 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, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending.
The statement may also include future settlement or forward transactions which have become binding on the account owner.
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 pending transactions.
In the framework of a settlement penalties regime, the message can be sent by a market infrastructure or an account servicer to an account owner or its designated agent to provide the details of the penalties calculated on instructions that matched or settled late. In this case, the instructions referred to in the report may no longer be pending at the moment of reporting.
MT537 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 |
|
-----> |
||||||
M |
98a |
4!c |
Date/Time |
A, C, or E | 6 |
|
-----| |
||||||
-----> |
||||||
M |
22a |
4!c |
Indicator |
F or H | 7 |
|
-----| |
||||||
-----> Optional Repetitive Subsequence A1 Linkages |
||||||
M |
16R |
|
|
LINK | 8 |
|
O |
13a |
LINK |
Number Identification |
A or B | 9 |
|
M |
20C |
4!c |
Reference |
:4!c//16x | 10 |
|
M |
16S |
|
|
LINK | 11 |
|
-----| End of Subsequence A1 Linkages |
||||||
-----> |
||||||
O |
95a |
4!c |
Party |
L, P, or R | 12 |
|
-----| |
||||||
M |
97a |
4!c |
Account |
A, B, or D | 13 |
|
M |
17B |
ACTI |
Flag |
:4!c//1!a | 14 |
|
M |
16S |
|
|
GENL | 15 |
|
End of Sequence A General Information |
||||||
-----> Optional Repetitive Sequence B Status |
||||||
M |
16R |
|
|
STAT | 16 |
|
M |
25D |
4!c |
Status Code |
:4!c/[8c]/4!c | 17 |
|
-----> Optional Repetitive Subsequence B1 Reason |
||||||
M |
16R |
|
|
REAS | 18 |
|
M |
24B |
4!c |
Reason Code |
:4!c/[8c]/4!c | 19 |
|
O |
70D |
REAS |
Narrative |
:4!c//6*35x | 20 |
|
M |
16S |
|
|
REAS | 21 |
|
-----| End of Subsequence B1 Reason |
||||||
-----> Mandatory Repetitive Subsequence B2 Transaction |
||||||
M |
16R |
|
|
TRAN | 22 |
|
-----> Mandatory Repetitive Subsequence B2a Linkages |
||||||
M |
16R |
|
|
LINK | 23 |
|
O |
13a |
LINK |
Number Identification |
A or B | 24 |
|
M |
20a |
4!c |
Reference |
C or U | 25 |
|
M |
16S |
|
|
LINK | 26 |
|
-----| End of Subsequence B2a Linkages |
||||||
Optional Subsequence B2b Transaction Details |
||||||
M |
16R |
|
|
TRANSDET | 27 |
|
-----> |
||||||
O |
94a |
4!c |
Place |
B, C, F, H, or L | 28 |
|
-----| |
||||||
M |
35B |
|
|
[ISIN1!e12!c] | 29 |
|
-----> |
||||||
M |
36a |
4!c |
Quantity of Financial Instrument |
B or D | 30 |
|
-----| |
||||||
-----> |
||||||
O |
19A |
4!c |
Amount |
:4!c//[N]3!a15d | 31 |
|
-----| |
||||||
-----> |
||||||
M |
22a |
4!c |
Indicator |
F or H | 32 |
|
-----| |
||||||
-----> |
||||||
M |
98a |
4!c |
Date/Time |
A, B, C, or E | 33 |
|
-----| |
||||||
O |
70E |
TRDE |
Narrative |
:4!c//10*35x | 34 |
|
-----> Optional Repetitive Subsequence B2b1 Settlement Parties |
||||||
M |
16R |
|
|
SETPRTY | 35 |
|
-----> |
||||||
M |
95a |
4!c |
Party |
C, L, P, Q, or R | 36 |
|
-----| |
||||||
O |
97a |
4!c |
Account |
A, B, or D | 37 |
|
O |
20C |
PROC |
Reference |
:4!c//16x | 38 |
|
M |
16S |
|
|
SETPRTY | 39 |
|
-----| End of Subsequence B2b1 Settlement Parties |
||||||
M |
16S |
|
|
TRANSDET | 40 |
|
End of Subsequence B2b Transaction Details |
||||||
M |
16S |
|
|
TRAN | 41 |
|
-----| End of Subsequence B2 Transaction |
||||||
M |
16S |
|
|
STAT | 42 |
|
-----| End of Sequence B Status |
||||||
-----> Optional Repetitive Sequence C Transactions |
||||||
M |
16R |
|
|
TRANS | 43 |
|
-----> Mandatory Repetitive Subsequence C1 Linkages |
||||||
M |
16R |
|
|
LINK | 44 |
|
O |
13a |
LINK |
Number Identification |
A or B | 45 |
|
M |
20a |
4!c |
Reference |
C or U | 46 |
|
M |
16S |
|
|
LINK | 47 |
|
-----| End of Subsequence C1 Linkages |
||||||
Optional Subsequence C2 Transaction Details |
||||||
M |
16R |
|
|
TRANSDET | 48 |
|
-----> |
||||||
O |
94a |
4!c |
Place |
B, C, F, H, or L | 49 |
|
-----| |
||||||
M |
35B |
|
|
[ISIN1!e12!c] | 50 |
|
-----> |
||||||
M |
36a |
4!c |
Quantity of Financial Instrument |
B or D | 51 |
|
-----| |
||||||
-----> |
||||||
O |
19A |
4!c |
Amount |
:4!c//[N]3!a15d | 52 |
|
-----| |
||||||
-----> |
||||||
M |
22a |
4!c |
Indicator |
F or H | 53 |
|
-----| |
||||||
-----> |
||||||
M |
98a |
4!c |
Date/Time |
A, B, C, or E | 54 |
|
-----| |
||||||
O |
70E |
TRDE |
Narrative |
:4!c//10*35x | 55 |
|
-----> Optional Repetitive Subsequence C2a Settlement Parties |
||||||
M |
16R |
|
|
SETPRTY | 56 |
|
-----> |
||||||
M |
95a |
4!c |
Party |
C, L, P, Q, or R | 57 |
|
-----| |
||||||
O |
97a |
4!c |
Account |
A, B, or D | 58 |
|
O |
20C |
PROC |
Reference |
:4!c//16x | 59 |
|
M |
16S |
|
|
SETPRTY | 60 |
|
-----| End of Subsequence C2a Settlement Parties |
||||||
M |
16S |
|
|
TRANSDET | 61 |
|
End of Subsequence C2 Transaction Details |
||||||
-----> Optional Repetitive Subsequence C3 Status |
||||||
M |
16R |
|
|
STAT | 62 |
|
M |
25D |
4!c |
Status Code |
:4!c/[8c]/4!c | 63 |
|
-----> Optional Repetitive Subsequence C3a Reason |
||||||
M |
16R |
|
|
REAS | 64 |
|
M |
24B |
4!c |
Reason Code |
:4!c/[8c]/4!c | 65 |
|
O |
70D |
REAS |
Narrative |
:4!c//6*35x | 66 |
|
M |
16S |
|
|
REAS | 67 |
|
-----| End of Subsequence C3a Reason |
||||||
M |
16S |
|
|
STAT | 68 |
|
-----| End of Subsequence C3 Status |
||||||
M |
16S |
|
|
TRANS | 69 |
|
-----| End of Sequence C Transactions |
||||||
-----> Optional Repetitive Sequence D Penalties |
||||||
M |
16R |
|
|
PENA | 70 |
|
O |
69a |
STAT |
Period |
A or B | 71 |
|
M |
22F |
CODE |
Indicator |
:4!c/[8c]/4!c | 72 |
|
-----> |
||||||
O |
95a |
4!c |
Party |
L or P | 73 |
|
-----| |
||||||
-----> Optional Repetitive Subsequence D1 Penalties per Currency for a Party |
||||||
M |
16R |
|
|
PENACUR | 74 |
|
O |
11A |
PECU |
Currency |
:4!c//3!a | 75 |
|
-----> |
||||||
O |
98a |
4!c |
Date/Time |
A or C | 76 |
|
-----| |
||||||
O |
97a |
CASH |
Account |
A or E | 77 |
|
O |
20C |
CPRF |
Reference |
:4!c//16x | 78 |
|
-----> |
||||||
M |
95a |
4!c |
Party |
L, P, Q, or R | 79 |
|
-----| |
||||||
M |
22F |
TRCA |
Indicator |
:4!c/[8c]/4!c | 80 |
|
-----> |
||||||
O |
19A |
4!c |
Amount |
:4!c//[N]3!a15d | 81 |
|
-----| |
||||||
-----> Optional Repetitive Subsequence D1a Penalties per Counterparty |
||||||
M |
16R |
|
|
PENACOUNT | 82 |
|
-----> |
||||||
M |
95a |
4!c |
Party |
L, P, Q, or R | 83 |
|
-----| |
||||||
M |
22F |
TRCA |
Indicator |
:4!c/[8c]/4!c | 84 |
|
M |
19A |
AGNT |
Amount |
:4!c//[N]3!a15d | 85 |
|
-----> Optional Repetitive Subsequence D1a1 Penalty Details |
||||||
M |
16R |
|
|
PENDET | 86 |
|
-----> |
||||||
M |
20C |
4!c |
Reference |
:4!c//16x | 87 |
|
-----| |
||||||
-----> |
||||||
M |
22H |
4!c |
Indicator |
:4!c//4!c | 88 |
|
-----| |
||||||
-----> |
||||||
O |
17B |
4!c |
Flag |
:4!c//1!a | 89 |
|
-----| |
||||||
O |
25D |
PNST |
Status Code |
:4!c/[8c]/4!c | 90 |
|
-----> |
||||||
O |
24B |
4!c |
Reason Code |
:4!c/[8c]/4!c | 91 |
|
-----| |
||||||
O |
70D |
REAS |
Status Narrative |
:4!c//6*35x | 92 |
|
M |
19A |
AMCO |
Amount |
:4!c//[N]3!a15d | 93 |
|
M |
99A |
DAAC |
Number Days |
:4!c//[N]3!n | 94 |
|
-----> Optional Repetitive Subsequence D1a1A Calculation Details |
||||||
M |
16R |
|
|
CALDET | 95 |
|
M |
98a |
PEDA |
Date/Time |
A, C, or E | 96 |
|
O |
17B |
MRED |
Missing Reference Data Flag |
:4!c//1!a | 97 |
|
Optional Subsequence D1a1A1 Financial Instrument Attributes |
||||||
M |
16R |
|
|
FIA | 98 |
|
M |
35B |
|
|
[ISIN1!e12!c] | 99 |
|
O |
12a |
CLAS |
Type of Financial Instrument |
A or C | 100 |
|
-----> |
||||||
O |
17B |
4!c |
Flag |
:4!c//1!a | 101 |
|
-----| |
||||||
O |
90a |
AMNT |
Price |
A or B | 102 |
|
-----> |
||||||
O |
94a |
4!c |
Place |
B or L | 103 |
|
-----| |
||||||
-----> |
||||||
O |
98a |
4!c |
Date/Time |
A or C | 104 |
|
-----| |
||||||
-----> |
||||||
O |
92a |
4!c |
Rate |
A or B | 105 |
|
-----| |
||||||
O |
70E |
FIAN |
Narrative |
:4!c//10*35x | 106 |
|
M |
16S |
|
|
FIA | 107 |
|
End of Subsequence D1a1A1 Financial Instrument Attributes |
||||||
-----> |
||||||
O |
92a |
4!c |
Rate |
A or B | 108 |
|
-----| |
||||||
-----> |
||||||
O |
19A |
4!c |
Amount |
:4!c//[N]3!a15d | 109 |
|
-----| |
||||||
O |
70E |
ADTX |
Narrative |
:4!c//10*35x | 110 |
|
M |
16S |
|
|
CALDET | 111 |
|
-----| End of Subsequence D1a1A Calculation Details |
||||||
Optional Subsequence D1a1B Related Transaction |
||||||
M |
16R |
|
|
RELTRAN | 112 |
|
-----> |
||||||
M |
20C |
4!c |
Reference |
:4!c//16x | 113 |
|
-----| |
||||||
Optional Subsequence D1a1B1 Transaction Details |
||||||
M |
16R |
|
|
TRAN | 114 |
|
-----> |
||||||
M |
22a |
4!c |
Indicator |
F or H | 115 |
|
-----| |
||||||
-----> |
||||||
M |
98a |
4!c |
Date/Time |
A, B, C, or E | 116 |
|
-----| |
||||||
-----> |
||||||
O |
97a |
4!c |
Account |
A, B, D, or E | 117 |
|
-----| |
||||||
-----> |
||||||
O |
95a |
4!c |
Party |
L, P, Q, or R | 118 |
|
-----| |
||||||
-----> |
||||||
M |
36a |
4!c |
Quantity of Financial Instrument |
B or D | 119 |
|
-----| |
||||||
-----> |
||||||
O |
19A |
4!c |
Amount |
:4!c//[N]3!a15d | 120 |
|
-----| |
||||||
-----> Optional Repetitive Subsequence D1a1B1a Status |
||||||
M |
16R |
|
|
STAT | 121 |
|
M |
25D |
4!c |
Status Code |
:4!c/[8c]/4!c | 122 |
|
-----> Optional Repetitive Subsequence D1a1B1a1 Reason |
||||||
M |
16R |
|
|
REAS | 123 |
|
M |
24B |
4!c |
Reason Code |
:4!c/[8c]/4!c | 124 |
|
O |
70D |
REAS |
Narrative |
:4!c//6*35x | 125 |
|
M |
16S |
|
|
REAS | 126 |
|
-----| End of Subsequence D1a1B1a1 Reason |
||||||
M |
16S |
|
|
STAT | 127 |
|
-----| End of Subsequence D1a1B1a Status |
||||||
O |
70E |
ADTX |
Narrative |
:4!c//10*35x | 128 |
|
M |
16S |
|
|
TRAN | 129 |
|
End of Subsequence D1a1B1 Transaction Details |
||||||
M |
16S |
|
|
RELTRAN | 130 |
|
End of Subsequence D1a1B Related Transaction |
||||||
O |
70E |
ADTX |
Narrative |
:4!c//10*35x | 131 |
|
M |
16S |
|
|
PENDET | 132 |
|
-----| End of Subsequence D1a1 Penalty Details |
||||||
O |
70E |
ADTX |
Narrative |
:4!c//10*35x | 133 |
|
M |
16S |
|
|
PENACOUNT | 134 |
|
-----| End of Subsequence D1a Penalties per Counterparty |
||||||
O |
70E |
ADTX |
Narrative |
:4!c//10*35x | 135 |
|
M |
16S |
|
|
PENACUR | 136 |
|
-----| End of Subsequence D1 Penalties per Currency for a Party |
||||||
O |
70E |
ADTX |
Narrative |
:4!c//10*35x | 137 |
|
M |
16S |
|
|
PENA | 138 |
|
-----| End of Sequence D Penalties |
||||||
Optional Sequence E Additional Information |
||||||
M |
16R |
|
|
ADDINFO | 139 |
|
-----> |
||||||
O |
95a |
4!c |
Party |
P, Q, or R | 140 |
|
-----| |
||||||
M |
16S |
|
|
ADDINFO | 141 |
|
End of Sequence E Additional Information |
MT537 Network Validated Rules
C1 In sequence A General Information, if the Activity Flag (field :17B::ACTI) indicates no information to be reported, that is, N, then sequence B Status and sequence C Transactions and sequence D Penalties must not be present.
If the Activity Flag (field :17B::ACTI) indicates that there is information to be reported, that is, Y and Statement Structure Type Indicator is per statuses (field :22H::STST//STAT), then sequence B Status is mandatory and sequence C Transactions is not allowed and sequence D Penalties is not allowed.
If the Activity Flag (field :17B::ACTI) in sequence A General Information indicates that there is information to be reported, that is, Y and Statement Structure Type Indicator is per transactions (field :22H::STST//TRAN), then sequence B Status is not allowed and sequence C Transactions is mandatory and sequence D Penalties is not allowed.
If the Activity Flag (field :17B::ACTI) in sequence A General Information indicates that there is information to be reported, that is, Y and Statement Structure Type Indicator is penalties (field :22H::STST//PENA), then sequence B Status is not allowed and sequence C Transactions is not allowed and sequence D Penalties is mandatory.
Sequence A
if field :17B::ACTI is ...
And sequence A
field :22H::STST is
Then sequence B is ...
And sequence C is ...
And sequence D is ...
N
STAT
Not allowed
Not allowed
Not allowed
N
TRAN
Not allowed
Not allowed
Not allowed
N
PENA
Not allowed
Not allowed
Not allowed
Y
STAT
Mandatory
Not allowed
Not allowed
Y
TRAN
Not allowed
Mandatory
Not allowed
Y
PENA
Not allowed
Not allowed
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 B2b and C2 and D1a1B1.
Subsequence B2b
if field :22H::PAYM is ...
Subsequence B2b
then field :19A::PSTA is ...
APMT
Mandatory
Not equal to APMT
Optional
Subsequence C2
if field :22H::PAYM is ...
Subsequence C2
then field :19A::PSTA is ...
APMT
Mandatory
Not equal to APMT
Optional
Subsequence D1a1B1
if field :22H::PAYM is ...
Subsequence D1a1B1
then field :19A::PSTA is ...
APMT
Mandatory
Not equal to APMT
Optional
C3 The following party fields cannot appear more than once in the same occurrence of subsequence B2b:
Subsequence B2b1
:95a::BUYR
:95a::DEAG
:95a::DECU
:95a::DEI1
:95a::DEI2
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL
The following party fields cannot appear more than once in the same occurrence of subsequence C2:
Subsequence C2a
:95a::BUYR
:95a::DEAG
:95a::DECU
:95a::DEI1
:95a::DEI2
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL
C4 If the instruction is a delivery (:22H::REDE//DELI in subsequence B2b) and the Settlement Parties subsequence B2b1 is used, then it is mandatory to specify a receiving agent: one occurrence of Settlement Parties subsequence B2b1 must contain party field :95a::REAG.
If the instruction is a receipt (:22H::REDE//RECE in subsequence B2b) and the Settlement Parties subsequence B2b1 is used, then it is mandatory to specify a delivering agent: one occurrence of Settlement Parties subsequence B2b1 must contain party field :95a::DEAG.
Subsequence B2b
if field :22H::REDE is ...
And if subsequence B2b1 is ...
Then in one occurrence of subsequence B2b1 field :95a::REAG is ...
DELI
Present
Mandatory
Subsequence B2b
if field :22H::REDE is ...
And if subsequence B2b1 is ...
Then in one occurrence of subsequence B2b1 field :95a::DEAG is ...
RECE
Present
Mandatory
If the instruction is a delivery (:22H::REDE//DELI in subsequence C2) and the Settlement Parties subsequence C2a is used, then it is mandatory to specify a receiving agent: one occurrence of Settlement Parties subsequence C2a must contain party field :95a::REAG.
If the instruction is a receipt (:22H::REDE//RECE in subsequence C2) and the Settlement Parties subsequence C2a is used, then it is mandatory to specify a delivering agent: one occurrence of Settlement Parties subsequence C2a must contain party field :95a::DEAG.
Subsequence C2
if field :22H::REDE is ...
And if subsequence C2a is ...
Then in one occurrence of subsequence C2a field :95a::REAG is ...
DELI
Present
Mandatory
Subsequence C2
if field :22H::REDE is ...
And if subsequence C2a is ...
Then in one occurrence of subsequence C2a field :95a::DEAG is ...
RECE
Present
Mandatory
C5 If subsequence B2b is present: if a qualifier from the list Deliverers is present in a subsequence B2b1, 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 words, in subsequence B2b1, the following scenarios must be validated:
If :95a::DEI2 is present in subsequence B2b1, then :95a::DEI1 must be present in another subsequence B2b1.
If :95a::DEI1 is present in subsequence B2b1, then :95a::DECU must be present in another subsequence B2b1.
If :95a::DECU is present in subsequence B2b1, then :95a::SELL must be present in another subsequence B2b1.
If a qualifier from the list Receivers is present in a subsequence B2b1, 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 words, in subsequence B2b1, the following scenarios must be validated:
If :95a::REI2 is present in subsequence B2b1, then :95a::REI1 must be present in another subsequence B2b1.
If :95a::REI1 is present in subsequence B2b1, then :95a::RECU must be present in another subsequence B2b1.
If :95a::RECU is present in subsequence B2b1, then :95a::BUYR must be present in another subsequence B2b1.
If subsequence C2 is present: if a qualifier from the list Deliverers is present in a subsequence C2a, 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 words, in subsequence C2, the following scenarios must be validated:
If :95a::DEI2 is present in subsequence C2a, then :95a::DEI1 must be present in another subsequence C2a.
If :95a::DEI1 is present in subsequence C2a, then :95a::DECU must be present in another subsequence C2a.
If :95a::DECU is present in subsequence C2a, then :95a::SELL must be present in another subsequence C2a.
If a qualifier from the list Receivers is present in a subsequence C2a, 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 words, in subsequence C2, the following scenarios must be validated:
If :95a::REI2 is present in subsequence C2a, then :95a::REI1 must be present in another subsequence C2a.
If :95a::REI1 is present in subsequence C2a, then :95a::RECU must be present in another subsequence C2a.
If :95a::RECU is present in subsequence C2a, then :95a::BUYR must be present in another subsequence C2a.
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)
C6 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
PENA
Optional
Optional
C7 In subsequence B2b1, if field :95a::PSET is present, then field :97a:: is not allowed in the same sequence..
Subsequence B2b1
if field :95a::PSET is ...
Subsequence B2b1
then field :97a:: is ...
Present
Not allowed within the same occurrence
Not present
Optional
In subsequence C2a, if field :95a::PSET is present, then field :97a:: is not allowed in the same sequence..
Subsequence C2a
if field :95a::PSET is ...
Subsequence C2a
then field :97a:: is ...
Present
Not allowed within the same occurrence
Not present
Optional
C8 Within each occurrence of subsequence B1, the qualifier in field 24B must be the same as the code (Status Code) used with the appropriate qualifier in field 25D of its surrounding sequence B.
In each occurrence of sequence B Status
In each occurrence of subsequence B1 Reason (if present)
if field :24B:: is ...
Then in sequence B Status
field :25D:: must be ... (1)
:24B::CAND
:25D::IPRC//CAND
:24B::CANP
:25D::IPRC//CANP
:24B::CGEN
:25D::IPRC//CGEN
:24B::PACK
:25D::IPRC//PACK
:24B::NMAT
:25D::MTCH//NMAT
:25D::INMH//NMAT
:24B::PEND
:25D::SETT//PEND
:24B::PENF
:25D::SETT//PENF
:24B::REPR
:25D::IPRC//REPR
:24B::PPRC
:25D::IPRC//PPRC
Within each occurrence of subsequence C3a Reason, the qualifier in field 24B must be the same as the code (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence C3 Status.
In each occurrence of subsequence C3 Status
In each occurrence of subsequence C3a Reason (if present)
if field :24B:: is ...
Then in subsequence C3 Status
field :25D:: must be ... (1)
:24B::CAND
:25D::IPRC//CAND
:24B::CANP
:25D::IPRC//CANP
:24B::CGEN
:25D::IPRC//CGEN
:24B::PACK
:25D::IPRC//PACK
:24B::NMAT
:25D::MTCH//NMAT
:25D::INMH//NMAT
:24B::PEND
:25D::SETT//PEND
:24B::PENF
:25D::SETT//PENF
:24B::REPR
:25D::IPRC//REPR
:24B::PPRC
:25D::IPRC//PPRC
Within each occurrence of subsequence D1a1B1a1 (Reason), the qualifier in field 24B must be the same as or linked to the code (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence D1a1B1a (Status).
In each occurrence of subsequence D1a1B1a Status
In each occurrence of subsequence D1a1B1a1 Reason (if present)
if field :24B:: is ...
Then in subsequence D1a1B1a Status
field :25D:: must be ... (1)
:24B::NMAT
:25D::MTCH//NMAT
:24B::PENF
:25D::SETT//PEND
:25D::SETT//PENF
C9 In each occurrence of subsequence B2b, 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 B2b
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
In each occurrence of subsequence C2, 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 C2
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 B2 Transaction, field :20C::RELA must be present in one and only one occurrence of subsequence B2a Linkages; field :20C::RELA is not allowed in all other occurrences of subsequence B2a.
A reference to the previously received message must be specified for each transaction reported, that is in each occurrence of sequence C Transaction, field :20C::RELA must be present in one and only one occurrence of subsequence C1 Linkages; field :20C::RELA is not allowed in all other occurrences of subsequence C1.
C11 In sequence A, if field :95L::ALTE is present, then field :95a::ACOW must be present.
In each occurrence of sequence D, if field :95L::ALTE is present, then field :95P::ASDP must be present in the same occurrence of the sequence D.
In each occurrence of subsequence D1a, if field :95L::ALTE is present, then field :95a::ASDP must be present in the same occurrence of the subsequence D1a.
In each occurrence of subsequence D1a, if field :95L::ALRP is present, then field :95a::REPA must be present in the same occurrence of the subsequence D1a.
C12 In subsequence B2b, 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 B2b, 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 B2b, 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).
In subsequence C2, 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 C2, 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 C2, 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).
C13 In subsequence D1a1B1 (Transaction Details), if field 95a is present, all qualifiers of field 95a are optional, but either ACOW or CACO (not both) must be present.
C14 In subsequence D1a (Penalties per Counterparty) all qualifiers of field 95a are optional, but either ASDP or REPA must be present.
C15 In subsequence D1a1 (Penalty Details), if field 24B is present, or field 70D, then field 25D must be present.
C16 In sequence A (General Information), if field 23G:PENA is present, then field 22H::STST//PENA must be present.
C17 In sequence A (General Information), if field 22H::STST//PENA is present and if field 22F::SFRE//MNTH is present and if field 17B::ACTI//Y is present, then field 69a::STAT in sequence D (PENA) must be present.
C18 In sequence A (General Information), if field 22H::STST//PENA is present and if field 22F::SFRE//MNTH is present and if field 17B::ACTI//Y is present, then field 98a::PAYD in sequence D1 (PENACUR) must be present.
MT537 Usage Rules
This statement is used by the account servicer to report on all pending activity to the account owner.
The frequency and structure type of the statement must be bilaterally agreed between the account servicer and the account owner.
The statement can be sent reflecting all outstanding pending activity information or may contain only changes since the previously sent statement.
Since a SWIFT message as sent is restricted to the maximum input message length, several messages may be needed to accommodate all the information.