- Knowledgebase
- SWIFT MT
- Option
-
Glossary
-
XML / ISO 20022 Standard
-
ISO 20022 Messages
-
XML Schema
- Miscellaneous
- Attribute
- Closing Tag
- Comment
- Content
- Cvc-complex-type
- Cvc-elt
- Cvc-id
- Cvc-identity-constraint
- Cvc-minexclusive-valid
- Cvc-mininclusive-valid
- Cvc-type
- Cvc-totaldigits-valid
- Cvc-attribute
- Cvc-datatype-valid
- Maximum Length
- Cvc-enumeration-valid
- Cvc-fractiondigits-valid
- Cvc-length-valid
- Cvc-maxexclusive-valid
- Cvc-maxinclusive-valid
- Cvc-maxlength-valid
- Cvc-minlength-valid
- Cvc-pattern-valid
- Element Value
- Encoding
- Length
- Mandatory element
- Missing
- Missing Tag
- Missing Child Element
- MIXD
- Root
- Unsupported Characters
- UTF-8
- Value
- Wrong Declaration
-
EPC SEPA
-
CGI-MP
-
US ACH (Nacha)
-
SWIFT MT
-
Finvoice
-
Bank-Specific
-
XMLdation Service Guides
-
Studio Guide
-
Simulator
Option A: Identifier Code Format
Page contains information on rules for Swift MT messages, specific to different options. Field is identified by a tag which consists of two digits, or two digits followed by a letteroption. Letter identifier specifies further restrictions for field
Format
[/1a][/34x] (Party Identifier)
4!a2!a2!c[3!c] (Identifier Code)
Definition
Identifier code such as a BIC. Optionally, the account of the party.
Network validated rules
Identifier Code must be a registered BIC (Error codes T27, T28, T29 and T45).
For institutions which are not SWIFT users, that is, which are not yet connected, the eighth position must consist of the digit '1'.
Usage rules
The time zone in which Time is expressed is to be identified by means of the offset against the UTC (Coordinated Universal Time - ISO 8601).
Examples
The following example shows BICs of non-connected users, without, and with, a branch identifier:
:53A:CHBAKHH1
:54A:CHBLGB21BBB