6.2.6 SWIFT MT900 Template 1

Source: TI_Host_to_Host_Client_User_Manual_v52.pdf Document pages: 123 PDF pages: 123

It is used to notify the account owner of an entry, which has been debited to its account. The entry will be further confirmed by statement. The SWIFT template is to be read in conjunction with the SWIFT Standards document. Refer to Appendix D to access to the respective document SWIFT MT900 Standard Statement Message Status Tag Field Name Content / Option No. M 20 Transaction Reference Number 16x 1 M 21 Related Reference 16x 2 M 25 Account Identification 35x 3 M 32A Value Date, Currency Code, Amount 6!n3!a15d 4 O 52a Ordering Institution A or D 5 O 72 Sender or Receiver Information 6*35x 6 M = Mandatory O = Optional

SWIFT MT900 Definitions of fields Status Tag Field Name Field Description M 20 Transaction Reference Number A unique reference number will be created by Nedbank for each message O 21 Related Reference This will be populated with your Nedbank profile number and instance number. The profile number and instance number will be separated by a "+" sign. Your profile number is always 10 numeric and instance number can be from 1 to 9999. Each PTI instance is a group of accounts, settings and destination. Client can load up to 9999 different PTI instances per profile M 25 Account Identification This will be the Nedbank account number for which the provisional transaction is sent M 32A Value Date, Currency Code, Amount This field specifies the value date, currency code and amount of the debit. In the case of Nedbank the value date will be the date the provisional transaction is posted to your account and depending on bank cutoff times the date can be different on your final statement. O 52a Ordering Institution This field will not be used O 72 Sender or Receiver Line 1 - Will include Transaction Key, Separator ("+") and Process Key Line 2 - Will include the Resend Key, Separator ("+") and Destination Key Line 3 - Will include the channel through which this transaction was processed (List of valid channels to be provided by Nedbank) Line 4 - Will include the transaction type (A valid list of transaction types to be provided by Nedbank) Line 5 - Will include your statement narrative.

Transaction Key: Each transaction in Nedbank is allocated a unique key for PTI. IF you receive the same transaction key on another PTI message it is for the same transaction ie a duplicate. Transaction Keys are not unique across FTI and PTI

Process Key: Uniquely identifies the client preferences effective for this statement ie