Você está na página 1de 46

Part III

Fields

Message Format Validation Rules, October 2007

Part III - Fields

Chapter 1 Introduction

This part describes the syntax rules which apply to the fields of a message, and the exceptions which exist when field components are filled with specific values.

In this part:

Chapter 2 gives a complete definition of a field, together with the general formatting rules which apply to it.

Chapter 3 exhaustively lists in table form all the fields, and the sequence of the components of which they are composed.

Chapter 4 lists in table form the special exceptions which exist for specific values of components of some fields, and the error codes resulting from these exceptions.

Message Format Validation Rules, October 2007

Part III - Fields

Chapter 2

Definition

2.1 NON-GENERIC FIELDS

Field Structure of a Non-Generic Field

:2!n[1a]: <data content >

:

- mandatory colon

2!n

2 numeric character, fixed length

[1a]

1 optional alphabetic character, letter option

:

- mandatory colon

<data content > - ref. Part III, chap 3, format definition

A field is a logical subdivision of a message consisting of a sequence of components as

specified by a starting field tag.

A field is always prefaced by a field tag which consists of two digits followed, in certain

cases, by an alphabetic character followed by a colon (:). The alphabetic character is referred to as an option.

A field is always ended by a field separator which consists of ’CrLf:’ for all the fields

included in the text of a message, and ’CrLf-’ for the last field of the text.

Example:

’CrLf’:20:1234

’CrLf’:32A:

’CrLf’-

The general rules which apply to fields are as follows:

a field consists of a field tag, a component or sequence of components (the field content), and the field separator

the sequence of components within the field content is specified by the field tag (refer to Part III Chapter 3 for all field tag formats)

when a field tag appears in a message it must be followed by at least one meaningful component, with the exception of field 15(*), and the 1st subfield of 77E (ref. Part II, Chapter 5, 5.1), 77T (ref. Part II, Chapter 5, 5.3). See character restrictions hereafter.

Note:

(*) all letter options.

Part III - Fields

Message Format Validation Rules, October 2007

The following character restrictions are applied to field content:

first line, first character:

it must not start with ’CrLf’, with the exception of field 15(*), where ’CrLf’ must be used as the first and last character of the field content, and with the exception of field 77E, and 77T , where ’CrLf’ may be used as the first character of the field content. (see example Part II Chapter 5).

it must not be entirely composed of blank characters, with the exception of the 1st subfield of field 77E, and 77T. (see example Part II Chapter 5).

second and subsequent lines (a new line must start with ’CrLf’)

within the field content, a colon ’:’ must never be used as the first character of a line, with the exception of field 77E, and 77T, where a colon may be used as the first character of any line. (except for field 77E, and 77T, the combination ’CrLf:’ always indicates a new field tag)

within the field content, a hyphen ’-’ must never be used as the first character of a line. (the combination ’CrLf-’ always indicates the end of text)

2.2 GENERIC FIELDS

Field Structure of a Generic Field

:2!n1a::4!c’/’[8c]’/’<data content >

:2!n1a: - same format as non-generic fields (*), but “1a” is mandatory

:

- mandatory second colon (required in all generic fields)

4!c

- qualifier

’/’

- first delimiter

[8c]

- issuer code (or Data Source Scheme or DSS)

’/’

- second delimiter

<data content > - ref. Part III, chap 3, format definition

Code Words Validation

- defined in Part V message formats

(*) note : non-generic fields and generic fields don’t share the same field tag letter option id.: hence, they are defined in the same section (PART III, 3) as the non-generic fields, in order to distinguish them easily, a ‘:’ is defined as the first character of the column Component Sequence.

All fields defined in this section must be validated according to the format definitions documented above.

Message Format Validation Rules, October 2007

Part III - Fields

The following error codes will be used for all field structure errors detected in generic fields.

T87

- In a generic field:

-

Colon (“:”) as a delimiter is not present at the expected position.

T89

- In a generic field:

- invalid qualifier,

- duplicated qualifier,

- mandatory qualifier is missing,

- syntax error. (see Part V, Chap 5 ISO 15022 message formats).

T90

- In a generic field:

- issuer code format or syntax error

- mandatory issuer code is missing

- invalid generic field format

T91

- In a generic field:

- Slash (“/”) as delimiter is not present at the expected position.

The sequence of components in the data field content is specified by the field tag (refer to Part III Chapter 3 for all field tag formats)

The following character restrictions are applied to generic fields content:

second and subsequent lines (a new line must start with ’CrLf’)

within the field content, a colon ’:’ must never be used as the first character of a line (the combination ’CrLf:’ always indicates a new field tag)

within the field content, a hyphen ’-’ must never be used as the first character of a line. (the combination ’CrLf-’ always indicates the end of text)

Message Format Validation Rules, October 2007

Part III - Fields

Chapter 3 Field Components Sequences

As mentioned in the chapter introduction, the table hereunder exhaustively lists all the fields and the sequences of components of which they are composed.

The fields are identified with 2 columns in the table: the ‘Field Tag’ and the ‘Permissible Letter Option(s)’.

The third column of the table displays the syntax of the component or the sequence of components forming the field.

The column ‘Error Code’ refers to the “Tnn” error codes table (see Part IV, Chapter 3), these errors are related to specific format and syntax validation checks performed by the S.W.I.F.T. system on the each field [letter option].

ex : field 26P:<CUR>‘/’4x, the system will validate the subfield <CUR>, and may return a “T52” error code for an invalid currency code or price code ‘PCT’, ‘REN’ or ‘YLD’.

26

P

<CUR>’/’4x

T52

Note: the ‘generic’ type validation like “T10 : The repetitive sequence occurred more than the maximum number of times required”, or “T11 : The repetitive sequence occurred less than the minimum number of times required”, or “T33 : Length of field, line, subfield or component is too long”, or “T34 : Length of field, line, subfield or component is too short”, etc. can not be indicated here, those error codes will only be listed in Part IV, Chapter 3.

The following notes refer to additional validations applied to the fields components :

(*)

The optional characters ’Carriage-Return Line-Feed’ ([’CRLF’]) must be used in the case where at least one of the components preceding the ’CRLF’ is used, if all components preceding the ’CRLF’ are missing then the ’CRLF’ must not be used

(**)

see special field exceptions, Chapter 4.

(***)

The <data content> of this field may not begin with a ’/’, nor may it end with a ’/’, nor may it contain ’//’ (2 consecutive slashes) anywhere within its contents. If the field has multiple lines, each line is validated independently; each line must not: begin with a ‘/’, nor end with a ‘/’, nor contain ‘//’.

(****)

At least one optional component must be present.

(*****)

see <X> set validation, Part II, Chapter 5.

Part III - Fields

Message Format Validation Rules, October 2007

Field Tag

Permissible

Component Sequence

Error Code

Letter

Option(s)

00

not used

   

01

not used

   

02

not used

   

03

not used

   

04

not used

   

05

not used

   

06

not used

   

07

not used

   

08

not used

   

09

not used

   

10

not used

   

11

 

A

‘:’4!c ‘//’ <CUR>

T52

R

<MT>’CRLF’<DATE2>

T18 T50

 

[’CRLF’4!n6!n]

 

S

<MT>’CRLF’<DATE2>

T18 T50

 

[’CRLF’4!n6!n]

12

MT= n92, n95, n96,

3!n

T18

n98

MT=

105,

<MT>

T18

 

106

MT=

other

3!n

(**)

T18

 

A

‘:’4!c‘/’[8c] ‘/’30x

B

‘:’4!c’/’[8c]’/’4!c

C

‘:’4!c’//’6!c

E

4!c (**)

F

4!c (**)

13

 

A

‘:’4!c‘//’3!c

 

B

‘:’4!c‘/’[8c] ‘/’30x (***)

T26

C

‘/’8c'/'<HHMM><SIGN>

T38 T15 T16

 

<OFFSET>

 

D

<DATE2><HHMM><SI

T50 T38 T15 T16

 

GN><OFFSET>

 

E

<DATE4><HHMM>

T50 T38

J

‘:’4!c’//’5!c

K

‘:’4!c’//’3!c’/’<NUMBE

 

R>15

14

 

A

9a (**)

 

C

4!n

D

7x (**)

Message Format Validation Rules, October 2007

Part III - Fields

 

F

24x

 

G

1a’/’8!a (**)

J

5a (**)

S

3!a2!n

15

A

’CRLF’

 

B

’CRLF’

C

’CRLF’

D

’CRLF’

E

’CRLF’

F

’CRLF’

G

’CRLF’

H

’CRLF’

I

’CRLF’

J

’CRLF’

K

’CRLF’

L

’CRLF’

M

’CRLF’

N

’CRLF’

16

A

5n

 

R

16c (**)

S

16c (**)

17

A

1a (**)

 

B

‘:’4!c‘//’1a (**)

F

1a (**)

G

1a (**)

N

1a (**)

O

1a (**)

R

1a (**)

T

1a (**)

U

1a (**)

V

1a (**)

18

A

5n

 

19

 

<AMOUNT>17

T40 T43

A

‘:’4!c‘//’

T14 T40 T43 T52

[‘N’]<CUR><NUMBER>

15

B

‘:’4!c‘//’<CUR><NUMBE

T40 T43 T52

R>15

20

 

16x (***)

T26

C

‘:’4!c‘//’16x (***)

T26

D

‘:’4!c‘//’25x (***)

T26

Part III - Fields

Message Format Validation Rules, October 2007

21

 

16x (***)

T26

 

A

16x (***)

T26

B

16x

C

35x

D

35x

E

35x

F

16x (***)

T26

G

16x (***)

T26

N

16x

P

16x (***)

T26

R

16x (***)

T26

22

(MT = 305)

8a’/’<SB-LC> (**)

T22 T63 T94 T95 T96

(MT = OTHER)

8a’/’<SB-LC>

T22 T63 T94 T95 T96

 

A

4!c (**)

B (MT=320, 330, 364, 365)

4!c (**)

B

(MT=other)

4!c

C

<SB-LC>

T22 T63 T94 T95 T96

D

4!c (**)

E (MT=405)

4!c (**)

E

(MT=other)

4!c

F

‘:’4!c‘/’[8c] ‘/’4!c

G

4!c (**)

H

‘:’4!c‘//’4!c

J

4!c (**)

K

4!c['/'35x] (**)

X

4!c

23

MT = 102_not _STP,

6a

 

MT = 102_STP,

6a (**)

T08

MT = 305 MT = 601

4a’/’4a’/’1a’/’<CUR>

T52

(**)

 

4a’/’4a’/’1a (**)

MT = 609

8a (**)

MT = other

16x

A 10a’/’5a (**)

 

B 4!c (**)

 

C 4!c [‘/’30x] (**)

 

D 10a (**)

 

E 4!c [‘/’30x] (**)

F 4!c [‘/’30x] (**)

G 4!c [‘/’4!c] (**)

Message Format Validation Rules, October 2007

Part III - Fields

24

B

‘:’4!c‘/’[8c] ‘/’4!c

 

D

4!c [‘/’35x] (**)

25

 

35x

 

A

’/’34x

D

‘:’4!c‘/’[8c] ‘/’4!c

26

A

<VAR-SEQU-2>

T23 T24 T25

B

<VAR-SEQU-3>

T23 T24 T25

C

[3!a]’/’15x’/’5!a4!a<VAR-

T23 T24 T25

SEQU-4> (**)

D

65x[’CRLF’65x]0-29

E

2n

F (MT=306)

9a (**)

F (MT=other)

9a

H

16x

N

<CUR>’/’4x

T52

P

<CUR>’/’4x

T52

T

3!c

27

 

1n’/’1n

 

28

 

5n[’/’2n]

 

C

5n[’/’5n]

D

5n’/’5n

E

5n’/’4!c (**)

29

A

35x[’CRLF’35x]0-3

 

B

35x[’CRLF’35x]0-3

C

35x

E

4!c’/’<HHMM>

T38

F

35z[’CRLF’35z]0-3

G

1n ‘/’ 33z

[‘CRLF’1n’/’33z]0-8

H

4!c

J

4!c[‘/’<HHMM>]

T38

K

4!c’/’<HHMM>

T38

30

 

<DATE2>

T50

F

<DATE4>

T50

G

<DATE4>’/’<DATE4>

T50

H

<DATE4>

T50

P

<DATE4>

T50

Q

<DATE4>

T50

T

<DATE4>

T50

U

<DATE4>

T50

V

<DATE4>

T50

X

<DATE4>

T50

Part III - Fields

Message Format Validation Rules, October 2007

31

 

C

<DATE2>

 

T50

D

<DATE2>29x

T50

E

<DATE2>

T50

F

<DATE2>[’/’<DATE2>][’

T50

 

//’35x]

 
 

G

<DATE2>’/’<HHMM>’/’

T50 T38

 

12a

 

L

<DATE2>

 

T50

P

<DATE2>[29x]

T50

R

<DATE2>[’/’<DATE2>]

T50

S

<DATE2>

 

T50

X

(<DATE2>[<HHMM>])|7

T50 T38 T62

 

!a

(**)

32

 

A

<DATE2><CUR><AMO

T50 T52 T40 T43

 

UNT>15

 
 

B

<CUR><AMOUNT>15

T52 T40 T43

C

<DATE2><CUR><AMO

T50 T52 T40 T43

 

UNT>15

 
 

D

<DATE2><CUR><AMO

T50 T52 T40 T43

 

UNT>15

 
 

E

<CUR>

T52

F

3!a<NUMBER>15 (**)

T40 T43

G

<CUR><AMOUNT>15

T52 T40 T43

H

[’N’]<CUR><AMOUNT>

T14 T52 T40 T43

 

15

 

J

<NUMBER>15

 

T40 T43

K

<DM>3!n2!a<CUR><AM

T61 T52 T40 T43

 

OUNT>15 (**)

 
 

M

<CUR><AMOUNT>15

T52 T40 T43

N

[’N’]<DATE2><CUR><A

T14 T50 T52 T40 T43

 

MOUNT>15

 
 

P

<DATE2><CUR><AMO

T50 T52 T40 T43

 

UNT>15

 
 

Q

<CUR>’/’<CUR>

T52

U

<CUR><AMOUNT>15

T52 T40 T43

33

 

A

<DATE2><CUR><AMO

T50 T52 T40 T43

 

UNT>15

 

B

(MT = 601 and

3!a<NUMBER>15

(**)

T40 T43

all types of messages appended in common groups n92, n95 and n96)

 

B

(MT = other)

<CUR><AMOUNT>15

T52 T40 T43

C

<DATE2><CUR><AMO

T50 T52 T40 T43

 

UNT>15

 

Message Format Validation Rules, October 2007

Part III - Fields

 

D

<DATE2><CUR><AMO

T50 T52 T40 T43

UNT>15

E

<CUR><AMOUNT>15

T52 T40 T43

F

<CUR><AMOUNT>15

T52 T40 T43

G

<CUR><NUMBER>15[5!

T40 T43 T52

c] (**)

K

<DM>3!n2!a<CUR><AM

T40 T43 T61 T52

OUNT>15 (**)

N

[’N’]<DATE2><CUR><A

T14 T40 T43 T50 T52

MOUNT>15

P

<DATE2><CUR><AMO

T40 T43 T50 T52

UNT>15

R

<DATE2><CUR><AMO

T40 T43 T50 T52

UNT>15

S

3!a<NUMBER>15

(**)

T40 T43

T

3!a<NUMBER>15

(**)

T40 T43

34 A

 

<DATE2><CUR><AMO

T40 T43 T50 T52

UNT>15

B

<CUR><AMOUNT>15

T40 T43 T52

E

[’N’]<CUR><AMOUNT>

T14 T40 T43 T52

15

F

<CUR>[<DC>]<AMOUN

T40 T43 T52 T51

T>15

N

[’N’]<DATE2><CUR><A

T14 T40 T43 T50 T52

MOUNT>15

P

<DATE2><CUR><AMO

T40 T43 T50 T52

UNT>15

R

<DATE2><CUR><AMO

T40 T43 T50 T52

UNT>15

35 A

 

3!a<NUMBER>15 (**)

T40 T43

B

[‘ISIN’1e 12!c]

T12

[‘CRLF’][35x] (*)

[‘CRLF’35x]0-3 (****)

C

3!c

D

<DATE2>

T50

E

50x[’CRLF’50x]0-5

F

50x[’CRLF’50x]0-34

H

[’N’]3!a<NUMBER>15

T14 T40 T43

(**)

L

35x[’CRLF’35x]0-3

N

3!a<NUMBER>15(**)

T40 T43

S

3!a<NUMBER>15(**)

T40 T43

U

3!a<NUMBER>15[1a]

T40 T43

(**)

Part III - Fields

Message Format Validation Rules, October 2007

36

 

<NUMBER>12

T40 T43

A

<NUMBER>12

T40 T43

B

‘:’4!c‘//’4!c ‘/’

T40 T43

<NUMBER>15

C

‘:’4!c’//’4!c

E

‘:’4!c’//’4!c‘/’[’N’]<NUM

BER>15

37

A

<NUMBER>12

T40 T43 T50 T61

[’//’<DATE2><DM>3n][’/

’16x]

B

<NUMBER>12

T40 T43 T50 T61

[’//’<DATE2><DM>3n][’/

’16x]

C

<NUMBER>12

T40 T43 T50 T61

[’//’<DATE2><DM>3n][’/

’16x]

D

<NUMBER>12

T40 T43 T50 T61

[’//’<DATE2><DM>3n][’/

’16x]

E

<NUMBER>12

T40 T43 T50 T61

[’//’<DATE2><DM>3n][’/

’16x]

F

<NUMBER>12

T40 T43 T50 T61

[’//’<DATE2><DM>3n][’/

’16x]

G

[’N’]<NUMBER>12

T14 T40 T43

H

<DC><NUMBER>12

T40 T43 T51

J

<NUMBER>12

T40 T43

K

3!a<NUMBER>12 (**)

T40 T43

L

<NUMBER>12

T40 T43

M

[’N’]<NUMBER>12

T14 T40 T43

N

35x[’CRLF’35x]0-5

P

<NUMBER>12

T40 T43

R

[’N’]<NUMBER>12

T14 T40 T43

U

<NUMBER>12

T40 T43

38

A

3n

 

B

4!c‘/’4!c [‘/’2!n] (**)

T75

D

4n

E

2n1a (**)

G

2n1a '/' 2n1a (**)

H

2n1a '/' 2n1a (**)

J

<DM>3!n (**)

T61

Message Format Validation Rules, October 2007

Part III - Fields

39

A

2n’/’2n

 

B

13x (**)

C

35x[’CRLF’35x]0-3

P

4!c’/’

T52 T40 T43

<CUR><AMOUNT>15

(**)

40

A

24x (**)

 

B

24x’CRLF’24x (**)

C

4!a [’/’35x] (**)

E

30x [’/’35x] (**)

F

30x (**)

41

A

<SWIFTBIC>|<NON-

 

SWIFTBIC> ’CRLF’ 14x (**)

D

35x[’CRLF’35x]0-3

’CRLF’14x (**)

42

A

[’/’<DC>][’/’34x][’CRLF’

T51

]

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

C

35x[’CRLF’35x]0-2

D

[’/’<DC>][’/’34x][’CRLF’

T51 T77

]

35x[’CRLF’35x]0-3

(*)

M

35x[’CRLF’35x]0-3

P

35x[’CRLF’35x]0-3

43

P

35x

 

T

35x

44

A

65x

 

B

65x

C

<DATE2>

T50

D

65x[’CRLF’65x]0-5

E

65x

F

65x

45

A

65x[’CRLF’65x]0-99

 

B

65x[’CRLF’65x]0-99

46

A

65x[’CRLF’65x]0-99

 

B

65x[’CRLF’65x]0-99

47

A

65x[’CRLF’65x]0-99

 

B

65x[’CRLF’65x]0-99

48

 

35x[’CRLF’35x]0-3

 

49

 

7!x (**)

 

Part III - Fields

Message Format Validation Rules, October 2007

50

 

35x[’CRLF’35x]0-3

   

A

[’/’34x’CRLF’]

 

<SWIFTBIC>|<NON-

 

SWIFTBIC>

 

B

35x[’CRLF’35x]0-3

 

C

<SWIFTBIC>|<NON-

SWIFTBIC>

 

D

[’/’<DC>][’/’34x][’CRLF’

T51 T77

]

35x[’CRLF’35x]0-3 (*)

 

F

’/’4!a’/’ 34x’CRLF’

 

T55

 

(**)

 

’/’1!n’/’ 32x

(**)

T56

[’CRLF’ ’/’1!n’/’ 32x]0-3 (**)

   

F

<FLD50F> ’CRLF’ (**) 1!n’/’ 33x (**) [’CRLF’ 1!n’/’ 33x] 0-3 (**)

T54 T55

T56

G

’/’34x ’CRLF’

 

<SWIFTBIC>|<NON-

 

SWIFTBIC>

 

H

’/’34x’CRLF’35x

 

T76

[’CRLF’35x]0-3

K

[’/’34x’CRLF’]

T77

35x[’CRLF’35x]0-3

 

L

35x

51

A

[’/’<DC>][’/’34x][’CRLF’

T51

]

<SWIFTBIC>|<NON-

 

SWIFTBIC> (*)

 

C

’/’34x

D

[’/’<DC>][’/’34x][’CRLF’

T51 T77

]35x

[’CRLF’35x]0-3 (*)

 

52

A

[’/’<DC>][’/’34x][’CRLF’

T51

]

<SWIFTBIC>|<NON-

 

SWIFTBIC> (*)

 

B

[’/’<DC>][’/’34x][’CRLF’

T51

][35x] (*),(****)

 

C

’/’34x

D

[’/’<DC>][’/’34x][’CRLF’

T51 T77

]35x

[’CRLF’35x]0-3

(*)

G

’/’34x ’CRLF’

 

<SWIFTBIC>|<NON-

 

SWIFTBIC>

 

Message Format Validation Rules, October 2007

Part III - Fields

53 A

 

[’/’<DC>][’/’34x][’CRLF’

 

T51

]

 

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

B

[’/’<DC>][’/’34x][’CRLF’

 

T51

][35x] (*),(****)

 

C

’/’34x

D

[’/’<DC>][’/’34x][’CRLF’

 

T51 T77

]35x

 

[’CRLF’35x]0-3

(*)

J

<PARTYFLD/J>

 

T78

54 A

 

[’/’<DC>][’/’34x][’CRLF’

T51

]

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

B

[’/’<DC>][’/’34x][’CRLF’

 

T51

][35x] (*),(****)

 

D

[’/’<DC>][’/’34x][’CRLF’

 

T51 T77

]35x

 

[’CRLF’35x]0-3 (*)

55 A

 

[’/’<DC>] [’/’34x]

 

T51

[’CRLF’]

 

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

B

[’/’<DC>][’/’34x]

 

T51

[’CRLF’][35x](*),(****)

 

D

[’/’<DC>][’/’34x]

 

T51 T77

[’CRLF’]35x

 

[’CRLF’35x]0-3 (*)

56 A

 

[’/’<DC>][’/’34x][’CRLF’

 

T51

]

 

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

B

[’/’<DC>][’/’34x]

 

T51

[’CRLF’][35x] (*), (****)

 

C

’/’34x

D

[’/’<DC>][’/’34x][’CRLF’

 

T51 T77

]35x

 

[’CRLF’35x]0-3

(*)

J

<PARTYFLD/J>

 

T78

57 A

 

[’/’<DC>][’/’34x][’CRLF’

 

T51

]

 

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

B

[’/’<DC>][’/’34x][’CRLF’

 

T51

][35x] (*),(****)

 

C

’/’34x

Part III - Fields

Message Format Validation Rules, October 2007

   

D

[’/’<DC>][’/’34x][’CRLF’

T51 T77

 

]35x

[’CRLF’35x]0-3 (*)

 

J

<PARTYFLD/J>

T78

58

 

A

[’/’<DC>][’/’34x][’CRLF’

T51

 

]

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

 

B

[’/’<DC>][’/’34x][’CRLF’

T51

 

][35x] (*),(****)

 

C

’/’34x

D

[’/’<DC>][’/’34x][’CRLF’

T51 T77

 

]35x

[’CRLF’35x]0-3 (*)

 

J

<PARTYFLD/J>

T78

59

 

[’/’34x’CRLF’]35x[’CRLF

T77

’35x]0-3

 

A

[’/’34x’CRLF’]

 

<SWIFTBIC>|<NON-

SWIFTBIC>

60

F

(MT = 608 and all

<DC><DATE2><3!a><A

T40 T43 T51 T50

types

of messages

MOUNT>15 (**)

appended in common groups n92, n95, and

n96)

F

(MT = other)

<DC><DATE2><CUR><

T40 T43 T51 T50 T52

 

AMOUNT>15

M (MT = 608 and all

<DC><DATE2><3!a><A

T40 T43 T51 T50

types

of messages

MOUNT>15 (**)

appended in common groups n92, n95, and

n96)

M

(MT = other)

<DC><DATE2><CUR><

T40 T43 T51 T50 T52

 

AMOUNT>15

61

MT=940, 942

<DATE2>[<DATE1>]2a[

T50 T18 T23 T24 T25 T40

1a]

T43

<NUMBER>15<SUB6>

<VAR-SEQU-

1>[’CRLF’<ERI_F61>]

(**)

MT=other, i.e. :

<DATE2>[<DATE1>]2a[

T50 T18 T40 T43

608, 950, 970, 972, n92, n95,

1a]

<NUMBER>15<SUB6>

 

n96

<VAR-SEQU-

 

1>[’CRLF’34x](**)

62

F

(MT = 608 and all

<DC><DATE2><3!a><A

T51 T50 T40 T43

types

of messages

MOUNT>15 (**)

appended in common groups n92, n95, and

n96)

Message Format Validation Rules, October 2007

Part III - Fields

 

F (MT = other)

<DC><DATE2><CUR><

T51 T50 T52 T40 T43

AMOUNT>15

M

(MT = 608 and all

<DC><DATE2><3!a><A

T51 T50 T40 T43

types of messages appended in common groups n92, n95, and

MOUNT>15 (**)

n96)

M

(MT = other)

<DC><DATE2><CUR><

T51 T50 T52 T40 T43

 

AMOUNT>15

63

 

not used

   

64

MT = 608 and all types of messages

<DC><DATE2>3!a<AM

T51 T50 T40 T43

OUNT>15 (**)

appended in common groups n92, n95, and

n96

MT = other

<DC><DATE2><CUR><

T51 T50 T52 T40 T43

AMOUNT>15

65

MT = 608 and all types of messages appended in common

groups n92, n95, and

<DC><DATE2>3!a<AM

T51 T50 T40 T43

OUNT>15 (**)

n96

MT = other

<DC><DATE2><CUR><

T51 T50 T52 T40 T43

AMOUNT>15

66

 

not used

   

67

 

A

<DATE2>[’/’<DATE2>]

T50

68

 

A

6n<CUR>6n’/’2n

T52

 

[’/’<AMOUNT>15][’//’10

T40 T43

x]

 

B

<DATE2><DATE2>16x’/

T50 T52 T74 T40 T43

 

’1a

3!a<NUMBER>15’CRLF’

 

<CUR><NUMBER>15’/’

<DATE2><CUR><AMO

UNT>15 (**)

 

C

4a’/’4a’/’1a[<DATE2>]3!a

T50 T52 T74 T40 T43

 

<NUMBER>15’CRLF’

<CUR><NUMBER>15

 

<CUR><NUMBER>15

<CUR><AMOUNT>15

(**)

69

 

A

‘:’4!c’//’

T50

 

<DATE4>‘/’<DATE4>

 

B

‘:’4!c’//’

T50 T38

 

<DATE4><TIME2>‘/’

<DATE4><TIME2>

 

C

‘:’4!c’//’ <DATE4> ‘/’ 4!c

T50

D

‘:’4!c’//’

T50 T38

 

<DATE4><TIME2> ‘/’

Part III - Fields

Message Format Validation Rules, October 2007

   

4!c

 
 

E

‘:’4!c’//’ 4!c ‘/’ <DATE4>

T50

F

‘:’4!c’//’ 4!c ‘/’

T50 T38

 

<DATE4><TIME2>

 

J

‘:’4!c’//’ 4!c

70

 

35x[’CRLF’35x]0-3

 
 

C

‘:’4!c ‘//’ 35x

 

[‘CRLF’35x]0-3

 

D

‘:’4!c ‘//’ 35x

 

[‘CRLF’35x]0-5

 

E

‘:’4!c ‘//’ 35x

 

[‘CRLF’35x]0-9

 

F

‘:’4!c’//’8000z

G

‘:’4!c’//’ 35z

 

[‘CRLF’35z]0-9

71

 

A

3!a (**)

 

B

35x[’CRLF’35x]0-5

C

35x[’CRLF’35x]0-5

F

<CUR><AMOUNT>15

T52 T40 T43

G

<CUR><AMOUNT>15

T52 T40 T43

H

<CUR><AMOUNT>15

T52 T40 T43

J

<CUR><AMOUNT>15

T52 T40 T43

K

<CUR><AMOUNT>15

T52 T40 T43

L

<CUR><AMOUNT>15

T52 T40 T43

72

MT= 206, 300, 303,

<FLD72>

 

304, 305,

306, 320,

330, 340,

341, 350,

360, 361,

362, 364,

365, 405

MT= 200, 201, 202, 203, 204, 205

<REJT/RETN/72> |

<FLD72>

MT= 102_STP,

<FLD72_STP>

103_STP

MT= 102_not_STP,

<REJT/RETN/72 > |

103_not_STP

<FLD72_not_STP>

MT= 104, 107, 207

<REJT/RETN/72 >

MT= 195, 295

<REJT/RETN/72> |

(35x[’CRLF’35x]0-5)

MT=110

<REJT/RETN/72> |

<ERI_F72narrative>

MT=see list on the right =========>

<ERI_F72narrative>

MT=400, 410, 412, 420, 422, 430, 450, 456, 516, 526, 559, 577, 581, 600, 601, 604, 605, 606, 607, 609, 643, 644, 645, 646,

Message Format Validation Rules, October 2007

Part III - Fields

   

700, 705, 707, 710, 720, 730, 732, 734, 740, 742, 747, 750, 752, 754, 756, 760, 767, 768, 769, 800, 802, 812, 813, 820, 821, 822, 823, 824, 900, 910, 935, n90, n91

 

MT=other, i.e :

35x[’CRLF’35x]0-5

 

n92, 395, 495, 595, 695, 795, 895, 995, n96

73

 

35x[’CRLF’35x]0-5

 

74

 

35x[’CRLF’35x]0-5

 

75

 

35x[’CRLF’35x]0-5

 

76

 

35x[’CRLF’35x]0-5

 

77

A

(MT=416, 455,

<ERI_F77A>

 

456, 747, 754,

810)

A

(MT=other, i.e.

35x[’CRLF’35x]0-19

: n92, n95, n96)

 

B

35x[’CRLF’35x]0-2

C

65x[’CRLF’65x]0-149

D

(MT = 303 Seq. C)

(’/ICOM/’29x) |

T47 invalid code word

 

(’/VARICOM/’26x) |

(’/NONICOM/’26x)

[’CRLF’35x]0-5

D

(MT = other,

35x[’CRLF’35x]0-5

including MT 303 Seq.

B)

 

E

73x[’CRLF’78x]0-n

 

(*****) (note 1)

 

F

1800y

G

9800y

H

6a[’/’<DATE4>][’//’<YE

T50

 

AR>] (**)

 

J

35x[’CRLF’35x]0-39

T

9000z (note 2)

Note 1

refer to Part II Chapter 2, Part II Chapter 5, and Part III Chapter 2

for field 77E

exceptions.

 

note 2

refer to Part III Chapter 2 for field 77T exceptions.

 

78

 

65x[’CRLF’65x]0-11

 

79

MT = 195, 199, 295, 299

<REJT/RETN/FLD79> |

 

(50x[’CRLF’50x]0-34)

MT=582, 649,

<ERI_F79>

705, 707, 810,

986

Part III - Fields

Message Format Validation Rules, October 2007

 

MT = other, i.e :

50x[’CRLF’50x]0-34

 

960, 964, 965, 966, 967, n92, 395, 495, 595, 695, 795, 895, 995, n96, 399, 499, 599, 699, 799, 899, 999

80

C

35x[’CRLF’35x]0-5

 

82

A

[’/’<DC>][’/’34x][’CRLF’

T51

]

<SWIFTBIC>|<NON-

SWIFTBIC>

(*)

B

[’/’<DC>][’/’34x][’CRLF’

T51

]

[35x] (*),(****)

 

D

[’/’<DC>][’/’34x][’CRLF’

T51 T77

]35x

 

[’CRLF’35x]0-3 (*)

J

<PARTYFLD/J>

 

T78

S

<CC>

 

T73

['/'34x]

[‘CRLF’35x

T70

['CRLF'35x]0-3]

 

83

A

[’/’<DC>][’/’34x][’CRLF’

T51

]

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

 

C

’/’34x

 

D

[’/’<DC>][’/’34x][’CRLF’

T51 T77

]35x

 

[’CRLF’35x]0-3

(*)

J

<PARTYFLD/J>

T78

84

A

[’/’<DC>][’/’34x][’CRLF’

T51

]

(*)

<SWIFTBIC>|<NON-

SWIFTBIC>

 

B

['/'<DC>]['/'34x]

 

T51

['CRLF']

 

[35x] (*), (****)

 

D

[’/’<DC>][’/’34x]

T51 T77

[’CRLF’] 35x (*)

[’CRLF’35x]0-3

J

<PARTYFLD/J>

T78

Message Format Validation Rules, October 2007

Part III - Fields

85

A

[’/’<DC>][’/’34x][’CRLF’

T51

]

<SWIFTBIC>|<NON-

SWIFTBIC>

(*)

 

B

['/'<DC>]['/'34x]

 

T51

['CRLF']

 

[35x] (*), (****)

D

[’/’<DC>][’/’34x][’CRLF’

 

T51 T77

]35x

   

[’CRLF’35x]0-3

(*)

J

<PARTYFLD/J>

 

T78

86

MT=940, 942

<ERI_F86>

   

MT=other, i.e. :

65x[’CRLF’65x]0-5

941, n92, n95,

n96

A

[’/’<DC>][’/’34x][’CRLF’

 

T51

]

(*)

 

<SWIFTBIC>|<NONSWI

FTBIC>

 

B

[’/’<DC>][’/’34x][’CRLF’

 

T51

]

 

[35x]

(*),(****)

 

D

[’/’<DC>][’/’34x]

 

T51 T77

[’CRLF’] 35x (*)

 

[’CRLF’35x]0-3

J

<PARTYFLD/J>

 

T78

87

A

[’/’<DC>][’/’34x][’CRLF’

 

T51

]

 

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

 

B

[’/’<DC>][’/’34x][’CRLF’

 

T51

]

 

[35x]

(*),(****)

 

D

[’/’<DC>][’/’34x][’CRLF’

 

T51 T77

]35x

   

[’CRLF’35x]0-3 (*)

J

<PARTYFLD/J>

   

T78

88

A

[’/’<DC>][’/’34x][’CRLF’

 

T51

]

 

<SWIFTBIC>|<NON-

SWIFTBIC> (*)

 

B

[’/’<DC>][’/’34x][’CRLF’

 

T51

]

 

[35x]

(*),(****)

 

D

[’/’<DC>][’/’34x][’CRLF’

T51 T77

]35x

 

[’CRLF’35x]0-3 (*)

J

<PARTYFLD/J>

   

T78

Part III - Fields

Message Format Validation Rules, October 2007

90 A

 

‘:’4!c‘//’4!c ‘/’

T40 T43

<NUMBER>15

B

‘:’4!c‘//’4!c ‘/’

T52 T40 T43

<CUR><NUMBER>15

C

5n<CUR><AMOUNT>15

T40 T43 T52

D

5n<CUR><AMOUNT>15

T40 T43 T52

E

‘:’4!c‘//’4!c

F

‘:’4!c‘//’4!c”/”

T40 T43 T52

<CUR><NUMBER>15

“/”4!c“/”<NUMBER>15

J

‘:’4!c‘//’4!c”/”

T40 T43 T52

<CUR><NUMBER>15

“/”

<CUR><NUMBER>15

91 A

 

‘CSM(MCL/RSI’ 1e

 

‘RCV/’4!a[2!a[2!c[8c]]] 1e

‘ORG/’4!a[2!a[2!c[8c]]]

1e

’SVR/CVO)’

B

‘CSM(MCL/RSM’ 1e

‘RCV/’4!a[2!a[2!c[8c]]] 1e

‘ORG/’4!a[2!a[2!c[8c]]]

1e

’CV/’ 160-288h ’)’

C

‘CSM(MCL/KSM’ 1e

‘RCV/’4!a[2!a[2!c[8c]]] 1e

‘ORG/’4!a[2!a[2!c[8c]]]

1e

’CV/’ 160-288h 1e

‘BE/’ 128-256h 1e

‘BES/’ 128-256h 1e

‘ND/.’1!n’.’16!c1e

‘EDK/’<DATE2><TIME2