Skip to content

6.2 Real time templates

Source: TI_Host_to_Host_Client_User_Manual_v52.pdf Document pages: 115-127 PDF pages: 115-127

6.2.1 PTI XML (RT) Template 1 Herewith the layout for the standard XML transaction feeds for real time: Standard Nedbank XML field lengths are variable and indicated below are maximum lengths XML Tag name Data Type Expected Maximum size Description Sample value

<?xml version="1.0"?>
<TIRequest>

Start of XML body

<TIRealtimeRecord>

1
2
3
4
5
<CISNumber> Numeric 12 Unique client number
issued by Nedbank 1234
<ProfileNumber> Numeric 10
Profile number on which the PTI product is setup 30000000014
<Product> Alpha Numeric 10
Will contain the value PTI to indicate it is a provisional transaction file

PTI

<InstanceNumber> Numeric 4
You can load up to 9999 different instances per profile. An instance is a group of accounts, settings and destination

1234

1
2
3
4
5
6
7
8
9
<InstanceName> Alpha Numeric 30 Instance name as
specified by the client ADMIN
<TransactionKey> Numeric 16
Each PTI transaction is allocated a unique key. If you receive the same transaction key on another PTI message then it will be for the same transaction ie the key is not unique across TI products 1
<ProcessKey> Alpha Numeric 9
Uniquely identifies the current client preferences for this transaction. This value is for internal purposes and does not have to be interpreted by you in processing this transaction. 0001
<ResendKey> Numeric 9
Any value greater than zero means that the transaction was resent. It will have the same transaction key as the initial transaction. 1
<DestinationKey> Numeric 9
If a single instance has more than one destination address it will have different destination keys. In the case of using Web Service only one destination address is 0012

allowed per instance

<Account> Numeric 23
The account number on which the transaction was processed. 1009000951
<TranType> Alpha Numeric 30
This field indicates the type of transaction eg Cash or Cheque. Refer to no 3.8 for a list of Channel and Transaction type combinations C Deposit
<Channel> Alpha Numeric 30
Indicates the channel through which the transaction was processed eg Teller. Refer to no 3.8 for a list of Channel and Transaction type combinations INTERNET BANKING
<Amount> Numeric 16.2 The amount of the
transaction -141.11
<DebitCredit> Alpha 2
Is the transaction a debit (Money out) or credit (Money in) to the account which is being reported on? Values are indicated by; D=Debit, C=Credit, RD=Reversal of Debit, RC=Reversal of Credit RD
<Date> Numeric 8
The date on which the transaction was processed to the account. Format - 20140916
<Time> Alpha Numeric 11
Time at which the provisional transaction was processed to the account. Format - 12:34:28:33 Numeric 16.2 Actual account balance including any uncleared funds (eg cheque deposits - 7 days clearance).

622000.54 Numeric 16.2 Actual account balance plus account overdraft limit, less any uncleared funds 635406.46

1
2
3
4
<UserRef> Alpha Numeric 30 Statement description
/ narrative NarrText 0899
<TIRequest> End of XML body
<TIRealtimeRecord>
New PTI XML layout - real time.txt

Sample file layout

1
2
3
4
5
6
7
8
9
<?xml version="1.0"?>
<TIRequest>
<TIRealtimeRecord>
<CISNumber>1234</CISNumber><ProfileNumber>30000000014</ProfileNumber><Product>Product</Product><In
stanceNumber>1234</InstanceNumber><InstanceName>ADMIN</InstanceName>
<TransactionKey>1</TransactionKey><ProcessKey>0001</ProcessKey><ResendKey>1200</ResendKey><Destin
ationKey>0012</DestinationKey><Account>1009000951</Account><TranType>C
Deposit</TranType><Channel>INTERNET BANKING</Channel><Amount>-
141.11</Amount><DebitCredit>RD</DebitCredit><Date>20130916</Date><Time>12:34:28:33</Time><Acc
1
2
3
4
ountBookBalance>622000.54</AccountBookBalance><AccountAvailableBalance>635406.46</AccountAvail
ableBalance><UserRef>NarrText 0899</UserRef>
</TIRealtimeRecord>
</TIRequest>

6.2.2 PTI CSV (RT) Template 1 Herewith the layout for the standard Nedbank format for CSV and Excel transaction feeds for PTI:

CSV and Excel field lengths are variable and indicated below are maximum lengths CSV Field name Data Type Expected Maximum size Description Sample value CIS Number Numeric 12 Unique client number issued by Nedbank 1234 Profile Number Numeric 10 Profile number on which the PTI product is setup 30000000014 Product Alpha Numeric 10 Will contain the value PTI to indicate it is a provisional transaction file

PTI

Instance Number Numeric 4 You can load up to 9999 different instances per profile. An instance is a group of accounts, settings and destination

1234

Instance Name Alpha Numeric 30 Instance name as specified by the client will always be displayed with quotation marks "ADMIN" Transaction Key Numeric 16 Each PTI transaction is allocated a unique key. If you receive the same transaction key on another PTI message then it will be for the same transaction ie the key is not unique across TI products 1

Process Key Alpha Numeric 9 Uniquely identifies the current client preferences for this transaction. This value is for internal purposes and does not have to be interpreted by you in processing this transaction. 0001 Resend Key Numeric 9 Any value greater than zero means that the transaction was resent. It will have the same transaction key as the initial transaction. 1 Destination Key Numeric 9 If a single instance has more than one destination address it will have different destination keys. In the case of using Web Service only one destination address is allowed per instance 0012 Account Numeric 23 The account number on which the transaction was processed. 1009000951 Tran Type Alpha Numeric 30 This field indicates the type of transaction eg Cash or Cheque. Refer to no 3.8 for a list of Channel and Transaction type combinations C Deposit Channel Alpha Numeric 30 Indicates the channel through which the transaction was processed eg Teller. Refer to no 3.8 for a list of Channel and Transaction type combinations INTERNET BANKING Amount Numeric 16.2 The amount of the transaction -141.11 Debit / Credit Alpha 2 Is the transaction a debit (Money out) or credit (Money in) to the account which is being reported on? Values are indicated by; D=Debit, C=Credit, RD=Reversal of Debit, RC=Reversal of Credit RD Date Numeric 8 The date on which the transaction was processed to the account. Format - 20140916

Time Alpha Numeric 11 Time at which the provisional transaction was processed to the account. Format - 12:34:28:33 Account Book Balance Numeric 16.2 Actual account balance including any uncleared funds (eg cheque deposits - 7 days clearance).

622000.54 Account Available Balance Numeric 16.2 Actual account balance plus account overdraft limit, less any uncleared funds 635406.46 User Ref Alpha Numeric 30 Statement description / narrative will always be displayed in quotation marks "NarrText 0899" CSV layout for PTI- real time.txt

Sample file layout

1234,30000000014,"Product",1234,"ADMIN",2013013,01,0001,1200,0012,1009000951, "C Deposit","INTERNET BANKING",-141.11,"RD",20130916,12:34:28:33,622000.54,635406.46,"NarrText 0899" 2,0001,1200,0012,1009000951,"CDeposit","INTERNETBANKING",-141.11,"D",20130916, 12:37:28:33,622000.54,635406.46,"NarrText 0899"

6.2.3 PTI TXT (RT) Template 1 Herewith the layout for the standard Nedbank format for TXT transaction feeds for PTI:

TXT field lengths are variable and indicated below are maximum lengths TXT Field name Data Type Actual Field Length Description Sample value CIS Number Numeric 12 Unique client number issued by Nedbank 1234 Profile Number Numeric 10 Profile number on which the PTI product is setup 30000000014 Product Alpha Numeric 10 Will contain the value PTI to indicate it is a provisional transaction file

PTI

Instance Number Numeric 4 You can load up to 9999 different instances per profile. An instance is a group of accounts, settings and destination

1234

Instance Name Alpha Numeric 30 Instance name as specified by the client ADMIN

Transaction Key Numeric 16 Each PTI transaction is allocated a unique key. If you receive the same transaction key on another PTI message then it will be for the same transaction ie the key is not unique across TI products 1 Process Key Alpha Numeric 9 Uniquely identifies the current client preferences for this transaction. This value is for internal purposes and does not have to be interpreted by you in processing this transaction. 0001 Resend Key Numeric 9 Any value greater than zero means that the transaction was resent. It will have the same transaction key as the initial transaction. 1 Destination Key Numeric 9 If a single instance has more than one destination address it will have different destination keys. In the case of using Web Service only one destination address is allowed per instance 0012 Account Numeric 23 The account number on which the transaction was processed. 1009000951 Tran Type Alpha Numeric 30 This field indicates the type of transaction eg Cash or Cheque. Refer to no 3.8 for a list of Channel and Transaction type combinations C Deposit Channel Alpha Numeric 30 Indicates the channel through which the transaction was processed eg Teller. Refer to no 3.8 for a list of Channel and Transaction type combinations INTERNET BANKING Amount Numeric 16.2 The amount of the transaction 141.11

Debit / Credit Alpha 2 Is the transaction a debit (Money out) or credit (Money in) to the account which is being reported on? Values are indicated by; D=Debit, C=Credit, RD=Reversal of Debit, RC=Reversal of Credit RD Date Numeric 8 The date on which the transaction was processed to the account. Format - 20140916 Time Alpha Numeric 11 Time at which the provisional transaction was processed to the account. Format - 12:34:28:33 Account Book Balance Numeric 16.2 Actual account balance including any uncleared funds (eg cheque deposits - 7 days clearance).

622000.54 Account Available Balance Numeric 16.2 Actual account balance plus account overdraft limit, less any uncleared funds 635406.46 User Ref Alpha Numeric 30 Statement description / narrative NarrText 0899 PTI TXT layout - real time.txt

Fixed width length file: Record length = 1000

Sample file layout

00000000123430000000014Product 0000001234ADMIN 000000000000000100000000100000120000000001200000000000001009000951C Deposit INTERNET BANKING -

00000000000000141.11RD2013091612:34:28:33+0000000000622000.54+0000000000635406.46NarrText 0899

6.2.4 PTI TXT (RT) Template 2

Friendly Layout (Finalising Layout)

6.2.5 PTI TXT (RT) Template 3 No Balance (finalising Layout)

6.2.6 SWIFT MT900 Template 1 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

format, accounts, destination addresses, etc

Resend Key: Any value greater than zero means this statement was resent on customer request

Destination Key: If your PTI instance has more than one destination address it will have different destination keys ie you request to send the same statement to multiple swift addresses, the first one will have a destination key "1", the second swift address will have a destination key "2", etc

6.2.7 SWIFT MT910 Template 1 It is used to notify the account owner of an entry, which has been credited 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 MT910 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 50a Ordering Customer A, F or K 5 O 52a Ordering Institution A or D 6 O 56a Intermediary A or D 7 O 72 Sender or Receiver Information 6*35x 8 M = Mandatory O = Optional

SWIFT MT910 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 statement 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 56a Intermediary 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 format, accounts, destination addresses, etc

Resend Key: Any value greater than zero means this statement was resent on customer request

Destination Key: If your PTI instance has more than one destination address it will have different destination keys ie you request to send the same statement to multiple swift addresses, the first one will have a destination key "1", the second swift address will have a destination key "2", etc

6.2.8 SWIFT MX900 Template 1

6.2.9 SWIFT MX910 Template 1

6.2.10 SWIFT MX941 (NRT) Template 1

6.2.11 SWIFT MT941 (NRT) Template 1

It is used to transmit balance information, reflecting the situation at the identified time in field 13D. The SWIFT template is to be read in conjunction with the SWIFT Standards document. Refer to Appendix D to access to the respecti ve document.

SWIFT MT941 Standard Statement Message Status Tag Field Name Content / Option No. M 20 Transaction Reference Number 16x 1 O 21 Related Reference 16x 2 M 25 Account Identification 35x 3 M 28 Statement Number / Sequence Number 5n[/2n] 4 O 13D Date / Time Indication 6!n4!n1!nx4!n 5 O 60F Opening Balance 1!a6!n3!a15d 6 O 90D Number and Sum of Entries 5n3!a15d 7 O 90C Number and Sum of Entries 5n3!a15d 8 M 62F Closing Balance (Booked Funds) 1!a6!n3!a15d 9 O 64 Closing Available Balance (Available Funds) 1!a6!n3!a15d 10

O 65 Forward Available Balance 1!a6!n3!a15d 11

O 86 Information to Account Owner 6*65x 12 M = Mandatory O = Optional

SWIFT MT941 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 statement is sent M 28C Statement Number / Sequence Number One statement number per statement sent. Will reset to zero on the 1st of January every year If only one message is sent for the same statement then this will be the statement number/1 If more than one message is sent for the same statement then this will be the statement number followed by the sequence number of the statement E.g. statement number/1, statement number/2 and so on

O 13D Date / Time Indication This filed indicates the date, time and time zone at which the report was created O 60F Opening Balance This field specifies the opening balance whether it is a debit or credit balance, the date, the currency and the amount of the balance. It should be the same as field 62F, the closing balance from the previous statement (MT940 or MT950) or balance report (MT941) for this account for the same day. If there were no previous statements or balance reports sent for that day then this must be the closing balance of the previous day O 90D Number and Sum of Entries This is the total number and total amount of debit entries since the last statement (MT940 or MT950) or balance report (MT941) for this account for the same day. If there were no previous statements or balance reports sent for that day then this must be the sum of debit entries from the closing balance of the previous day O 90C Number and Sum of Entries This is the total number and total amount of credit entries since the last statement (MT940 or MT950) or balance report (MT941) for this account for the same day. If there were no previous statements or balance reports sent for that day then this must be the sum of credit entries from the closing balance of the previous day M 62F Closing Balance (Booked Funds) This field contains the closing book balance for the account as at the requested time. O 64 Closing Available Balance (Available Funds) This will be the debit or credit closing available balance as at the requested time O 65 Forward Available Balance Is not used O 86 Information to Account Owner Is not used

Amount Decimal 16,2 The value in rands for the transaction. 124,6 Date / Time Date Time 25 The date on and time at which the transaction was performed. 07Jul11 09:45 User Reference Alpha Numeric 30 The reference entered by the user. SARS 334233 payment