Ordering

Important information about your order

• High volume of branch identifiers
  • If you have a lot of branch identifiers to create, contact your local Swift sales office or email your request to E2E-Reference-Data.Generic@swift.com.
  • Read the BIC Policy, which provides a general description of the rules related to the registration and the publication of BICs (login required).
• Connection status of the BIC

  • The connection status of the BIC will determine the connection status of the branch identifier :
    A branch identifier  created on a connected BIC will result in a connected branch identifier .

  • A connected branch identifier  is a three-character code linking to an active 8-character BIC. It appears in the header of a Swift message.

  • A connected branch identifier  with a location code (8th digit) ends with a character other than 1.

           A branch identifier created on an unconnected BIC will be an unconnected branch identifier .  

• An unconnected branch identifier can only be used as a reference in the body of the message and is always published.
• Branch identifier  information

  • A branch identifier must identify a branch, department, service or system that belongs to the same legal institution as the corresponding BIC.

  • An unconnected branch identifier (BIC11) is published in the BIC Directory by default. While not recommended, a Swift User may decide to register an unconnected branch identifier as non-published.

  • A non-published identifier must only be used if it is so agreed on a bilateral basis or within a group of users.

  • The publication of a branch identifier will result in the publication of the related 8-character BIC and its 11-character BIC version (i.e. the 8-character BIC with "XXX" appended) if non-published.

  • You must decide if you need a connected, an unconnected branch identifier or both.

  • You must also decide if you need a test and training BIC for the new requested branch identifier .