Friday, February 16, 2018

Working with Calendars in SWIFT

You can set up multiple calendars for a given year. This enables logical terminals to have their own calendar, which can be useful if the LTs are located in different countries, with different working days or public holidays.

If multiple calendars have been defined, then the available calendars are displayed when the Calendar application is started. This list also shows which Calendar is currently set as the default.
You can use the Calendar application to create additional calendars.
You have to set up a calendar if you want users to be able to schedule Alliance Access processes to occur automatically.

Alliance Access users can only schedule processes if the operator profiles allow them to do so. After you create your calendar, you must modify the appropriate profiles. For example, you may modify a profile so that operators can use the Message File application to schedule message archiving.
Once you have created a calendar and modified the profiles, any users with the appropriate profiles can schedule processes.

Saturday, February 10, 2018

MT n95 Queries

MT n95 Scope

This message type is:
  • sent by a financial institution to another financial institution.
  • sent by a corporate customer to a financial institution.
  • sent by a financial institution to a corporate customer.
It is used to request information or clarification relating to a previous SWIFT or non-SWIFT message or to one or more transactions contained therein.
A query may also be sent to request that an amendment be made to a previous message, except in those cases where a specific message, or facility within a message, has been provided for this purpose in the related category, for example, MT 707, AMEND in field 22 of the MT 300.
The category digit of the MT n95 Queries must be:
  • If related to a SWIFT message, the category digit of the related message.
  • If not related to a SWIFT message, the category digit which best describes the business purpose of the message.
For use of messages in the corporate-to-bank environment, see the MT message implementation guide and the message matrix for corporate customers available on www.swift.com.

MT n95 Format Specifications

Status Tag Field Name Content/Options No.
M 20 Transaction Reference Number 16x 1
M 21 Related Reference 16x 2
M 75 Queries 6*35x 3
O 77A Narrative 20*35x 4
O 11a MT and Date of the Original Message R or S 5
O 79 Narrative Description of the Message to Which the Query Relates 35*50x 6
O Copy of at least the Mandatory Fields of the Original Message Copy of fields 7

MT n95 Network Validated Rules

  • C1 Either field 79 or a 'Copy of at least the mandatory fields of the message to which the query relates', but not both, may be present in the message (Error code(s): C31).

MT n95 Usage Rules

  • The MT n95 should not be used to enquire about the fate of documents sent for collection. The MT 420 is intended for this purpose.
  • All queries that relate to the same initial message, should refer to that initial message in field 21 of this message.
  • The message to which the MT n95 Queries is related may be quoted in part or in full.
  • The MT n95 Queries always requires a response, preferably by an MT n96 Answers.
  • The use of the MT n95 in association with the MT 105 EDIFACT Envelope must be in accordance with the specific guidelines detailed in the appropriate volume of the EDIFACT Message Implementation Guides (MIGs).
SWIFT Documentation
Created: 23-May-2016

MT n96 Answers

MT n96 Scope

This message type is:
  • sent by one financial institution to another financial institution.
  • sent by a corporate customer to a financial institution.
  • sent by a financial institution to a corporate customer.
It is used to respond to an MT n95 Queries or MT n92 Request for Cancellation and other messages where no specific message type has been provided for the response. This message should use the same category digit as the related queries message or request for cancellation.
For use of messages in the corporate-to-bank environment, see the MT message implementation guide and message matrix for corporate customers available on www.swift.com.

MT n96 Format Specifications

Status Tag Field Name Content/Options No.
M 20 Transaction Reference Number 16x 1
M 21 Related Reference 16x 2
M 76 Answers 6*35x 3
O 77A Narrative 20*35x 4
O 11a MT and Date of the Original Message R or S 5
O 79 Narrative Description of the Original Message to Which the Answer Relates 35*50x 6
O Copy of at least the Mandatory Fields of the Original Message Copy of fields 7

MT n96 Network Validated Rules

  • C1 Either field 79 or a 'Copy of at least the mandatory fields of the message to which the answer relates', but not both, may be present in the message (Error code(s): C31).

MT n96 Usage Rules

  • The content of field 20 Transaction Reference Number of the related MT n95 Queries or MT n92 Request for Cancellation must always be quoted.
  • The use of the MT n96 in association with the MT 105 EDIFACT Envelope must be in accordance with the specific guidelines detailed in the appropriate volume of the EDIFACT Message Implementation Guides (MIGs).
  • The message to which the MT n96 Answers is related may be quoted in part or in full.
  • The MT 296 must be used in the cheque truncation environment in answering an MT 295 previously received.
  • An MT 596 must not be used to respond to a cancellation request of any ISO 15022 compliant message. An ISO 15022 compliant status message should be used instead, that is, an MT 509, 548, or 567. In these messages, field 23G, subfield Function, should contain the code CAST (Cancellation Request Status) (see also the Standards Category 5 volumes).

MT n92 Request for Cancellation

MT n92 Scope

This message is:
  • sent by a financial institution to request a second financial institution to consider cancellation of the SWIFT message identified in the request.
  • sent by a corporate customer to request a financial institution to consider cancellation of the SWIFT message identified in the request.
If the Receiver of the request for cancellation has already acted on the message for which cancellation is requested, the MT n92 asks for a retransfer, that is, reversal, with the beneficiary's consent.
For use of messages in the corporate-to-bank environment, see the MT message implementation guide and the message matrix for corporate customers available on www.swift.com.

MT n92 Format Specifications

Status Tag Field Name Content/Options No.
M 20 Transaction Reference Number 16x 1
M 21 Related Reference 16x 2
M 11S MT and Date of the Original Message 3!n
6!n
[4!n6!n]
3
O 79 Narrative Description of the Original Message 35*50x 4
O Copy of at least the Mandatory Fields of the Original Message Copy of fields 5

MT n92 Network Validated Rules

  • C1 Field 79 or a copy of at least the mandatory fields of the original message or both must be present (Error code(s): C25).

MT n92 Usage Rules

  • An MT n92 may be sent only to the Receiver of an initial message.
  • An MT n92 must refer to the cancellation of a SWIFT message only.
  • An MT 292 may not request cancellation of an MT 200/201. To cancel an MT 200/201, the Sender must send a new message to the account with institution of the initial message, requesting a retransfer of the funds.
  • An MT n92 may be sent to cancel one single transaction of a multiple message.
  • The MT n92 always requires a response. The response must be by an MT n96 Answers message.
  • Where country specific policies exist relative to the processing of a request for cancellation, details can be found in the General Country Information file, which is available for download on www.swiftrefdata.com.
  • The use of the MT n92 in association with the MT 105 EDIFACT Envelope must be in accordance with the specific guidelines detailed in the appropriate volume of the EDIFACT Message Implementation Guides (MIGs).
  • To request the cancellation of a category 3 message, there are specific fields and codes in the category 3 messages that must be used. Where such fields and codes exist in a message, the MT 392 must not be used to cancel a previously sent transaction or confirmation.
  • To request the cancellation of any ISO 15022 compliant message, an MT 592 must not be used. Field 23G of the ISO 15022 message, with subfield Function containing code CANC (Cancellation), must be used instead (see also the Standards Category 5 volumes).
  • To request the cancellation of a documentary credit, an authorisation to reimburse or a guarantee, an MT 792 must not be used, but an MT 707, 747 or 767, respectively

MT 110 Advice of Cheque(s)

MT 110 Scope

This multiple message is sent by a drawer bank, or a bank acting on behalf of the drawer bank to the bank on which a/several cheque(s) has been drawn (the drawee bank).
It is used to advise the drawee bank, or confirm to an enquiring bank, the details concerning the cheque(s) referred to in the message.

MT 110 Format Specifications

Status Tag Field Name Content/Options No.
M 20 Sender's Reference 16x 1
O 53a Sender's Correspondent A, B, or D 2
O 54a Receiver's Correspondent A, B, or D 3
O 72 Sender to Receiver Information 6*35x 4
----->
M 21 Cheque Number 16x 5
M 30 Date of Issue 6!n 6
M 32a Amount A or B 7
O 52a Drawer Bank A, B, or D 8
M 59 Payee [/34x]
4*35x
9
-----|

MT 110 Network Validated Rules

  • C1 The repetitive sequence must not be present more than ten times (Error code(s): T10).
  • C2 The currency code in the amount field 32a must be the same for all occurrences of this field in the message (Error code(s): C02).
SWIFT Documentation

Friday, December 29, 2017

File Transfer : File components

File components
• The file transfer header The part of a file transfer request that contains information about the file transfer, such as destination, compression information, delivery type, and so on. The data file usually immediately follows the file transfer header.
• The data file The business content of a file transfer. Parties that receive file transfer headers only do not receive files.

Main file types
• Data file The file exchanged over SWIFTNet.
• Companion parameter file When sending a file using file transfer adapter, a companion parameter file travels along with the data file from the business application to the Alliance Gateway host that processes the data files. A companion parameter file can contain extra information, such as local authentication information, override values, and header information. When receiving a file, the file transfer adapter can generate a companion parameter file to include details contained in the file transfer request header.
• XML parameter file On the sender side, a business application generates an XML parameter file that contains arguments to pass to an FT command or a local transfer agent command.
• Generated XML parameter file Local transfer agent commands store output in generated XML parameter files. A business application that receives such a generated XML parameter file can analyse it to either accept or reject a file transfer request, or to perform additional processing of the transferred file.
• Report file A report file reports about the processing status of a data file
The table that follows gives an overview of the file transfer interface file exchange modes that are possible. The sections that follow provide more information about the exchange modes in this table.

File transfer interface

File transfer interface Alliance Gateway provides the file transfer interface to configure and manage licensed file transfer products: file transfer adapter and file transfer integrated. Both file transfer adapter and file transfer integrated can be present on the same instance of Alliance Gateway.

You can use the Alliance Gateway Administration interface that is available through Alliance Web Platform to access the file transfer interface.

File transfer adapter
File transfer adapter is a licensed product that automates file transfer between correspondents over SWIFTNet. The business application just has to make the file available on the Alliance Gateway host, and the file transfer interface automatically transfers the file over SWIFTNet, using file transfer adapter configuration data.

File transfer integrated
File transfer integrated is a licensed product that can be integrated with the business application through a third-party file transfer connecter: the business application or file transfer connecter can offer automation. To transfer a file over SWIFTNet, the business application must make the file available on the Alliance Gateway host, invoke a file transfer command (ft command), and pass all file transfer parameters to the ft command.

Real-time transfers
With real-time transfers, both parties must be connected to SWIFTNet at the same time. A connection is established between the sender and the receiver, and the file transfer software attempts to transfer the files from one party to the other through SWIFTNet.

Store-and-forward transfers
Sender and receiver do not require to be connected to SWIFTNet at the same time for a storeand-forward file transfer to succeed. The requester sends a file to SWIFT, where it is queued on a SWIFTNet store-and-forward system. When the receiver has acquired the queue, or if the queue was already acquired, then the SWIFT store-and-forward system delivers the files in the acquired queue. Queues are therefore specific to store-and-forward transfers. They are set up on the SWIFTNet store-and-forward system, where they store files from senders and queue the files that are
ready to be delivered to the receivers