STP SWIFT Messages

8.4.5.1 STP SWIFT Messages

The SWIFT messages that you receive are either uploaded into Oracle Banking Trade Finance as new BC contracts or they trigger changes (events) to the existing BC contracts. The message upload process takes one message at a time and applies a sequence of logical steps to derive information required to derive the BC contract upload tables.

The various SWIFT messages supported in Oracle Banking Trade Finance are listed below:

MT754 - Advice of Payment/Acceptance/Negotiation
MT412 - Advice of Acceptance
MT416 - Advice of Non Payment/Non Acceptance
MT430 - Amendment of Instructions
MT400 - Advice of Payment
MT742 - Reimbursement Claim
MT410 - Acknowledgment Received

The Straight Through Processing (STP) of each of the above messages is discussed in the following sections.

As part of STP processing, for some of the messages, Generated Reference Number needs to be updated in the Incoming message data source with Contract Reference Number. They are:

MT742Reimbursement Claim
MT754Advice of Payment/Acceptance/Negotiation
MT700Issue of a Documentary Credit
MT710Documentary Credit
MT740Authorization to Reimburse
MT747Amendment to an Authorization to reimburse
MT707Amendment to documentary credit
MT705 Pre-Advice

For MT202 the value in tag 21 is updated as Generated reference Number

The Generated Reference Number is not updated automatically for the following messages:

MT400Advice of Payment
MT410 Acknowledgment
MT430 Amendment For Instructions
MT730 Acknowledgment Message
MT768 Acknowledgment for guarantee amendment

If the above messages are processed successfully, then the processed contract reference number is updated as Generated Reference Number.

Parent topic: Straight through Processing of SWIFT Messages