Friday, February 3, 2017

Information in a SWIFT message - Workstation

You can insert the following types of information in a message:
  • Header: the identity of the sender and the receiver of the message.
    You can also provide other details, which are different for a SWIFT message. For example, for a SWIFT message, you must specify what type of message that you are creating. For more information about completing message headers,
  • Text : the text of the message.
    This layout is different for SWIFT messages. .
  • Network: the network application that is used to send the message.
    The range of networks is restricted to those for which your organisation is licensed. After you select the network, other fields appear so that you enter additional information.
  • Comments: comments about the content of the message.
    Comments are not transmitted on the SWIFT network.
  • Security: the information required to authenticate the message.
    The authentication data depends on the network used to send the message.

To complete the message Header

  1. Click Unit to select the unit to which the message is assigned. Only operators who are members of the same unit are able to access the message.
  2. Click Type to select the type of correspondent sending the message: Institution, Department, or Individual. If you select Department or Individual, then extra fields appear so that you can enter additional details.
  3. Enter the BIC-11 address of the sender institution in the Institution field. This must be the address of an internal correspondent whose details are recorded in your Correspondent Information File. An internal correspondent is a correspondent that has at least the same BIC-4 (bank code) as your organisation.
    To record new correspondent details in the Correspondent Information File, run the Correspondent Info application. If you modify internal correspondent information in the Correspondent Information File, then you must restart Alliance Access.
  4. If the correspondent Type is Department or Individual, then complete the extra fields so that the Department or Individual is clearly identified. The combination of details in the Institution field and these other fields make up a Full Name which uniquely identifies the correspondent to Alliance Access.
  5. Click Sender LT to select the logical terminal that the message is to be sent from. You can only send a message from a logical terminal that is licensed to your installation. The logical terminal that you select must belong to a destination that you have permission to send messages from.
  6. Click Application and select:
    • FIN, to send a financial or system message to the Financial Messaging Service.
    • APC, to send a system message to the Application Control.
  7. The FIN-Copy field only appears if you set the Application to FIN. Only use this field if you have installed a FINCopy service. Use the SWIFT Support application to install and control the FINCopy service. Select the three-character ID of the FINCopy service that corresponds to the Central Institution Destination (a local regulatory body) you want to copy the message to.
    The FINCopy service lets you copy messages in one of three ways:
    • "Y copy" in which the central institution either authorises the message and delivers it to the receiver, or rejects the message, that is aborts the copy process, and notifies the sender.
    • "T copy" in which the central institution only receives a copy of the message. The original is sent directly from the sender to the receiver. The central institution does not authorise the message before it is delivered.
    • "Bypassed" in which the message is not sent or copied to the central institution.
  8. In the Message Type field, type the number of the message type that you want to create. If you do not know the exact number, then type the first one or two digits and press the Tab key. A list of all matching message types and descriptions appears.
    Double-click the message type that you want to create.
  9. For certain message types, an additional field appears where you can specify an extension. This extension determines the layout of the message.
    For example, when you create an MT 103, you can select the Message Types 103, 103.REMIT, or 103.STP. Alliance Access automatically puts the extension into the validation flag (field 119 of block 3).
    Note
    For other messages types, no additional field appears for you to fill in. Instead, Alliance Access automatically places the contents of a field or subfield in the message text into field 119.
    Some examples are:
    • the collateral reason for MT 503, MT 504, MT 505, MT 506, and MT 507
    • the RFDD flag for MT 104.
  10. The message priority determines the priority with which SWIFT delivers a message.
    Click Priority to select the priority for the message:
    • N: normal priority
    • U: urgent priority
    SWIFT delivers urgent user-to-user messages first, then normal user-to-user messages. If you do not specify a priority, then system messages are always delivered first, followed by messages with urgent priority, and then messages with normal priority.
    The message priority affects the delivery monitoring options that you can specify for a message.
  11. When you create a message, you can request that SWIFT sends system messages in response so that you can monitor the progress of your message.
    Click Monitoring and select an option for monitoring the delivery of the message:
    Priority
    Monitoring
    Description
    Normal
    N
    no monitoring
    2
    delivery notification(1)
    Urgent
    1
    non-delivery warning(2)
    3
    both non-delivery warning and delivery notification
    (1) SWIFT sends an MT 011 (delivery notification) to you after the message has been delivered to your correspondent
    (2) SWIFT sends an MT 010 (non-delivery warning) if the message is not delivered to your correspondent within a fixed period.
  12. You can specify that the message is sent to an alias as long as the alias is defined in the CIF. An alias is an alternative name for one or more correspondents. Check the Alias box.
  13. If you check Alias, then select or enter an alias name in the field that appears. If the alias is for a group of correspondents, then the message type must be SWIFT MT999. The message is broadcast to the group of correspondents.
    If the alias represents only one correspondent, then there is no restriction on the message type. If the alias is for a group, then you do not have to complete the next few steps - continue at step 18 To complete the message Header
  14. Click Type to select the type of correspondent receiving the message: Institution, Department, or Individual. If you select Department or Individual, then extra fields appear so that you can enter additional details. For sending messages to the SWIFT network, Institution is the only valid type.
  15. In the Institution field, type the BIC-11 address of the Receiver correspondent. This is usually a BIC-11 address for an external correspondent, that is, one not owned by your organisation, and so having a different BIC-11 to your organisation. It can, however, be an internal one.
    When you move the cursor from the field where you identified the institution, if a record exists for this BIC-11 address in the Correspondent Information File, Alliance Access completes the Address Expansion fields automatically. If the BIC is not found in the Correspondent Information File, then the Address Expansion fields remain empty. It is possible that the BIC you have typed is not yet included in the Correspondent Information File on your system. If Alliance Access does not complete the Institution and other fields, then you can type the data yourself, although this is not mandatory.
    If the message requires authentication and therefore, also authorisation, then the Institution field shows the default error colour, a beep sounds, and an error message is displayed if the one or several of the following conditions exist:
    • no valid authorisation to send is present
    • a valid and enabled authorisation to send is present, but the authorisation does not the allowed permissions for this message type
    • a FINCopy service has been selected but the FINCopy server has not been set up to bypass message authorisation
    • the message is a FIN T&T message and RMA authorisation is required for T&T but it has not been configured
  16. If you specified the correspondent Type as Department or Individual, then complete the extra fields so that the Department or Individual is clearly identified.
  17. Click User PDE if you want to add a PDE trailer to the message. By default, messages are sent without a PDE trailer.
  18. In the Banking Priority field, type a priority with which your correspondent processes the message. This field is optional. Any value that you enter in this field must be agreed with the correspondent in advance.
  19. In the M.U.R. field, enter a message user reference of up to 16 alphanumeric characters. This field is optional. How the reference is derived and how it is used is for individual organisations to decide.

No comments:

Post a Comment