TI Host to Host Client User Manual v52 - Raw Dump¶
Source: TI_Host_to_Host_Client_User_Manual_v52.pdf
Page 1¶
Nedbank Group Limited Internal Use Only
Transactional i nformation
Host to Host User Manual
Page 2¶
COPYRIGHT | TRANSACTIONAL INFORMATION
HOST TO HOST USER MANUAL
Nedbank Group Limited Internal Use Only Copyright notice
Copyright 2011, 2012 updated. Nedbank Limited. All rights reserved.
All product names referred to in this manual remain the property of Nedbank. No part of this manual may be reproduced in any manner or form without written permission being obtained from Nedbank.
Statement of confidentiality
The recipient of this manual agrees to keep this manual confidential and not to use its contents in any form or by any means without permission from Nedbank. Moreover, the recipient agrees not to place this manual at the disposal of any third party without permission from Nedbank. The recipient of this manual or of information contained therein will be held responsible to Nedbank for the confidentiality of the manual or information.
Trademarks
All the trademarks used in this manual remain the property of their rightful owners.
Gender
Throughout this manual the user / reader is referred to as he/him/his. We mean this to include she/her equally.
Page 3¶
TRANSACTIONAL INFORMATION | CONTENTS
HOST TO HOST USER MANUAL
Nedbank Group Limited Internal Use Only
Transactional Information
Host to Host User Manual
Table of contents page
1 Transactional Information 10 1.1 Introduction 10 1.2 Qualifying criteria 12 1.3 TI file naming convention 13 1.4 Nomination of a contact person 15 1.5 Resend of transactions and files 16 1.6 Responsibilities 17 1.7 System Availability 17 1.8 TI service support 17 1.8.1 Host connectivity support 17 1.8.2 Internet banking (NetBank Business) connectivity support 17 1.9 Delivery protocols 18 1.9.1 Real time delivery protocol 18 1.9.2 Near real time delivery protocol 25 1.10 Pricing 30 1.11 Security 34 1.12 High level onboarding process for TI host to host delivery protocols 35 1.13 TI Keys 36 1.14 TI Templates 36 1.15 Testing your TI functionalities for host protocols 40 1.16 Checklists for required documents 41 2 Notifications 41 2.1 What is the Notification service? 41 2.2 Key features of Notifications 42 2.3 Adding or maintaining Notification instances 46 2.4 Benefits of Notifications to your business 48 2.5 Pricing 48 2.6 Frequently Asked Questions (FAQ) 48 3 Provisional Transactional Information (PTI) 49 3.1 What is the PTI solution? 49 3.2 Key features of PTI 50 3.3 Benefits of the PTI to your business 50 3.4 Delivery protocol 51 3.5 Delivery preference 51 3.6 Available PTI settings at an instance level 52 3.7 PTI Template groups 57 3.8 Channel and transaction type combinations 58 3.9 Adding or maintaining PTI instances 61 3.10 Pricing 62 3.11 Frequently Asked Questions (FAQ) 62 4 Final Transaction Information (FTI) 63 4.1 What is the FTI solution? 63 4.2 Key features of FTI 63 4.3 Statement number 66 4.4 Benefits of FTI to your business 66
Page 4¶
CONTENTS | TRANSACTIONAL INFORMATION
HOST TO HOST USER MANUAL
Nedbank Group Limited Internal Use Only 4.5 Benefits of Notifications to your business 66 4.6 Value-added services Error! Bookmark not defined. 4.7 Delivery protocol 67 4.8 Available FTI settings at an instance level Error! Bookmark not defined. 4.9 FTI Template groups 67 4.10 Transaction codes 69 4.11 Adding or maintaining FTI instances 74 4.12 Pricing 75 4.13 Frequently Asked Questions (FAQ) 76 5 Images on demand (IOD) 76 5.1 What is Images on demand? 76 5.2 Key features of IOD 76 5.3 IOD file naming convention 78 5.4 Benefits of IOD to your business 81 5.5 Adding or maintaining IOD instances 81 5.6 Pricing 83 5.7 Frequently Asked Questions (FAQ) 83 6 Appendix A - PTI Templates 84 6.1 Near real time templates 84 6.1.1 PTI XML (NRT) Template 1 84 6.1.2 PTI CSV (NRT) Template 1 87 6.1.3 PTI CSV (NRT) Template 2 90 6.1.4 PTI CSV (NRT) Template 3 93 6.1.5 PTI CSV (NRT) Template 4 96 6.1.6 PTI TXT (NRT) Template 1 99 6.1.7 PTI TXT Balance Only (NRT) Template 1 102 6.1.8 PTI CSV Balance Only (NRT) Template 1 104 6.1.9 SWIFT MT942 (NRT) Template 1 106 6.1.10 SWIFT MT942 (NRT) Template 2 109 6.1.11 TI SWIFT MX942 (NRT) 111 6.1.12 Multicash AUSZUG (Header) (NRT) 112 6.1.13 Multicash UMSATZ (Line Items) (NRT) 113 6.2 Real time templates 115 6.2.1 PTI XML (RT) Template 1 115 6.2.2 PTI CSV (RT) Template 1 117 6.2.3 PTI TXT (RT) Template 1 120 6.2.4 PTI TXT (RT) Template 2 122 6.2.5 PTI TXT (RT) Template 3 122 6.2.6 SWIFT MT900 Template 1 123 6.2.7 SWIFT MT910 Template 1 124 6.2.8 SWIFT MX900 Template 1 125 6.2.9 SWIFT MX910 Template 1 125 6.2.10 SWIFT MX941 (NRT) Template 1 125 6.2.11 SWIFT MT941 (NRT) Template 1 126 7 Appendix B - FTI Templates 128 7.1 Near real time templates 128 7.1.1 FTI XML Template 1 128 7.1.2 FTI XML Template 2 131 7.1.3 FTI CSV Template 1 135 7.1.4 FTI CSV Template 2 137 7.1.5 FTI CSV Template 3 140 7.1.6 FTI TXT Template 1 143 7.1.7 FTI TXT Template 2 147 7.1.8 SWIFT MT940 Template 1 150
Page 5¶
TRANSACTIONAL INFORMATION | CONTENTS
HOST TO HOST USER MANUAL
Nedbank Group Limited Internal Use Only 7.1.9 SWIFT MT940 Template 2 153 7.1.10 SWIFT MT940 Template 3 153 7.1.11 SWIFT MT940 Template 4 154 7.1.12 TI SWIFT MT950 154 7.1.13 NED SWIFT MT940 156 7.1.14 NED SWIFT MT950 158 7.1.15 TI SWIFT MX940 159 7.1.16 TI SWIFT MX950 159 7.1.17 Multicash AUSZUG (Header) Template 1 160 7.1.18 Multicash UMSATZ (Line Items) Template 1 161 7.1.19 Multicash UMSATZ (Line Items)- Template 2 163 7.1.20 NedInform Fixed Width Layout Template 1 165 8 Appendix C - IR Templates 166 8.1 Near real time templates 166 8.1.1 SWIFT MT940 166 8.1.2 SWIFT MT942 169 8.1.3 SWIFT MT950 172 8.2 Real time templates 173 8.2.1 SWIFT MT941 173 8.2.2 SWIFT MT920 175 9 Appendix D - SWIFT Standards Document 176 Special Characters: 176 10 Appendix E - CASA Statement Combined Transaction Codes 177 11 Appendix F - Enotes PTI Web Service Contract 178
Page 6¶
DEFINITIONS | TRANSACTIONAL INFORMATION
HOST TO HOST USER MANUAL
Nedbank Group Limited Internal Use Only
Definition of terms / initialisms / acronyms
No Term / Initialism /
Acronym
Definition
1 ATM Automated Teller Machine
2 Bank Nedbank Ltd
3 Batch Grouping of transactions into a file and transmitted at the
requested intervals
4 CASA Statement number
CASA statement number is generated after every 20
transactions on an account, i.e. you can receive multiple
statement numbers per account per day.
5 CAP Channel Administration Profile
6 CE Client Enablement
7 Channel A channel is a client interface of a product through which the
bank or third party offers and renders services to the client.
8 Client Corporate, Business Banking (BB), as well as Small Business
Services (SBS)
9 CIS Client Integration Services
10 Comma-separated values (CSV)
A CSV file consists of any number of records, separated by line
breaks of some kind. Each record consists of fields, separated
by another character or string, most commonly a literal comma
or tab
11 Delivery protocol
A mechanism for clients to connect to Nedbank in order to
enable the transfer of data. Examples of delivery mechanisms
are: SFTP, Connect: Direct , Web Service etc
12 File format
A file format tells the computer how to display, print, process
and save the data. It has a specific structure or arrangement of
data code stored as a computer file
13 File layout A file layout is a description of the arrangement of the data in a
file
14 Host to host, eg host to host
environment
A secure method of direct data interchanges between the
organisation's host (mainframe) system and Nedbank's host
(mainframe) system
15 Line-of-business (LOB) system A core system run and maintained by the client to process
generic and financial transactions
16 Middleware The software and hardware that interface the frontend systems
with the host system
17 MT900 A SWIFT confirmation of a debit message that advises an
account owner of a debit to his account
18 MT910 A SWIFT confirmation of a credit message that advises an
account owner of a credit to his account
19 MT941
A SWIFT balance report, which provides balance information of
an account to a financial institution on behalf of the account
holder(Balance report)
Page 7¶
TRANSACTIONAL INFORMATION | DEFINITIONS
HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Definition of terms / initialisms / acronyms (continued)
No Term / Initialism /
Acronym
Definition
20 MT942
A SWIFT interim transaction report, which provides balance and
transaction details of an account for a specified period, to a
financial institution on behalf of the account holder
21 MT950
A SWIFT statement message, sent by an account servicing
institution to an account owner. It is used to transmit detailed
information about all entries, whether or not caused by a SWIFT
message, booked to the account (Statement message)
22 NetBank Business (NBB) Nedbank's internet banking platform offered to Nedbank
business and corporate clients
23 Organisation For the purposes of this manual 'organisation' refers to a TI user
or client
24 Provisional Transactional
Information (PTI) service
Provisional transaction information is a service that allows a
centralised Nedbank host system to push provisional transaction
information directly into the environment of the client. This is not
a final statement.
25 Profile number A CAP generated profile number for corporate, business
banking and small business services clients
26 Quality Assurance (QA)
A 'mirror' of the production environment used for integrated
system testing. It is the last step in the testing cycle before
promoting any applications into the production environment
27 Real time payment A payment that is done immediately or straight through to the
receiving account
28 Resend If a client requests for a file to be sent to them again, after the
file has been sent successfully for the first time
29 Retry
If the first attempt to send a transaction / fi le fails, the system
will persistently try to send transactions / files until it has been
successfully sent. Alternatively, the system will try to send the
transactions / files to a client, a certain number of times
30 RMA Relationship Management Application (SWIFT)
31 SBS Small Business Services
32 Service
A service is the realisation of the features and terms and
conditions of the product through work performed by the bank.
Services can be client or bank initiated
33 Service level agreement (SLA)
The participating banks' agreed maximum response time, ie not
exceeding two hours for near real time and 60 seconds for real
time transactions, subject to the cutoff times specified in the
manual
34 Server Notification
A central IP address at the client's environment where
Notifications are delivered. The client is responsible for the
further distribution to preferred SMS and email addresses and
the maintenance thereof
Page 8¶
DEFINITIONS | TRANSACTIONAL INFORMATION
HOST TO HOST USER MANUAL
Nedbank Group Limited Internal Use Only
Definition of terms / initialisms / acronyms (continued)
No Term / Initialism /
Acronym
Definition
35 Service level agreement (SLA)
The participating banks' agreed maximum response time, ie not
exceeding two hours for near real time and 60 seconds for real
time transactions, subject to the cutoff times specified in the
manual
36 Single statement number Single statement number is generated per account per day.
37 SST Self Service Terminal
38 SOAP Simple Object Access Protocol ( Web Services)
39 Trailer The last record in the CSV files succeeding the detail record or
body. It contains information common to the file
40 Web Services Description
Language (WSDL) file
WSDL is an XML-based interface description language that is
used for describing the functionality offered by a Web Service. A
WSDL description of a Web Service (also referred to as a WSDL
file) provides a machine-readable description of how the service
can be called, what parameters it expects and what data
structures it returns. Therefore, it serves a purpose that
corresponds generally with a method signature in a
programming language
41 Extensible Mark-up Language
(XML)
It is a web friendly format that you can use to publish data in
multiple formats
Page 9¶
TRANSACTIONAL INFORMATION | 9 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only Using the manual This manual is divided into sections that describe the high-level and technical processes involved when setting up the near real time and/or real time functionality for the TI host to host environment between Nedbank and the organisation.
Each section of this manual uses icons to highlight information items and tasks that must be completed by the organisation, Nedbank or both. These icons are depicted below:
Icon Description
Client
Nedbank
Critical point / Important item to remember
Page 10¶
10| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
1 Transactional Information 1.1 Introduction
Transactional information (TI) consists of the following set of products:
A. Notifications
The Notification service will send you a sms or email, informing you of any transaction processed on your account as well as other value added Notification options eg low balance alert. You can receive Notifications on any current or savings account you hold with Nedbank.
The Notification service is a dynamic solution that will allow you to customise the Notification to suit your business needs. You can set up to 10 000 different types of Notifications, each on a separate Notification instance ie you can have different Notification instance for the Chief financial Officer and a different Notification instance for the debtors clerk. Each instance is customisable to send out specific Notifications to specific recipients, ie each instance setup allow you to:
Specify the account/s to be notified on Specify the type of transaction to be notified on Specify the value of the transaction to be notified on eg if a company has mandates in place you can setup the instance to only send transaction above a certain value to the CFO Transactional Information
FFTTII
((iinncclluuddiinngg
SSWWIIFFTT))
PPTTII
((iinncclluuddiinngg
SSWWIIFFTT))
NNoottiiffiiccaattii
oonnss
IInnffoorrmmaattii
oonn
RReeqquueesstt
IImmaaggeess oonn
DDeemmaanndd
Page 11¶
TRANSACTIONAL INFORMATION | 11 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only The option of receiving certain Value Added Notifications eg to be notified if your account balance drops below a specified amount or if the usage of your account overdraft limit reaches a certain percentage. Specify a time preference, if you would not like to receive Notifications during specific hours of the day eg only send Notifications between 8am and 5pm Specify up to 10 email addresses or cellphone numbers
B. Provisional Transactional Information (PTI)
The Provisional Transaction Information (PTI) service will send you a Notification in a machine-readable format when a provisional transaction has been processed to your current and/or savings accounts. This PTI service will send a Notification that can be integrated directly into your line-of-business (LOB) system providing you with the ability to automate operational processes. Note, this is only provisional information so it is up to the client if they would like to rely on this information for operational decisions.
Example: If you sell 'prepaid electricity' as soon as money is deposited into your account, PTI will send a Notification to your line of business system and based on the information your system will release the prepaid electricity to your client in a real time manner.
C. Final Transaction Information (FTI)
The Final Transaction Information (FTI) service offers you a statement in a machine- readable format of confirmed financial transactions that have been processed through your current or savings accounts. These confirmed transactions are extracted from your accounts, formatted and delivered to you as per your selected preferences. This file can be integrated directly into your line of business system allowing you the ability to automate the reconciliation of your bank statement.
Example: you will receive a file between 3am and 8am (client preference) of all confirmed financial transactions for the previous day, allowing your system to complete the bank recon and create an exception file of un-reconcilable items before your next business day starts.
D. Information Request (IR)
Information Request (IR) is an automated solution that will allow you or an authorised third party bank to request statement information on your current or savings account using the SWIFT network.
The authorised requester of the statement information will require a valid SWIFT address and will send Nedbank a MT920 SWIFT message requesting the relevant statement information. On receipt of the MT920 message the TI system will validate if the SWIFT address has been given permission to request statement information on the
Page 12¶
12| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
selected account, it will then generate the relevant SWIFT message and send it to the requestor via the SWIFT gateway. The following statement information can be requested:
MT940 (Final statement, bank-to-customer) MT950 (Final statement, bank-to-bank) MT941(Balance report) MT942 (Provisional statement, intra-day-statement)
E. Images on Demand (IOD)
The Images On Demand (IOD) solution will deliver images of cheques, cash slips and/or deposit slips, processed through your current or savings accounts. These images can be delivered directly to your LOB on a secure host protocol or via email. These images are indexed which will allow you to build your own image viewer or image search functionality on your LOB system. Alternatively, you can elect to use the image viewer provided by Nedbank.
IOD can assist you with;
Bank account reconciliation ie, the additional information (eg contact number of
the depositor) available on the image can help you to identify irreconcilable cash
or cheque transactions.
Risk mitigation ie, you will be receiving the image directly from the bank,
removing the risk of dispatching goods or services based on fraudulent / altered
deposit slip.
Controlling access to your bank statements ie, images can be sent to your
employees so that they can make the relevant operational decisions. Your
employees do not need access to your bank accounts.
Improving operational processes ie, employees are no longer required to contact
the bank to verify the validity of a cheque or cash deposit.
1.2 Qualifying criteria
You must hold at least one current or savings account with Nedbank. You must have a profile created to maintain the required profile settings.
Note: A minimum of one current account must be opened or must exist as a charge account. The account must be held with Nedbank and must be specified as the charge account on your profile
These details are:
Client name
Your company name is required for capturing on the system.
Client contact details
Your contact details are required for capturing on the system.
Page 13¶
TRANSACTIONAL INFORMATION | 13 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only The following legal requirements are applicable:
You must ensure that the relevant consent has been obtained to allow you to disclose your data to Nedbank and allow Nedbank to use the data in relation to the provision of the service. The onus is on you to ensure that the information provided to Nedbank is correct.
1.3 TI file naming convention
A TI file, used for the near real time delivery protocols, contains all transactions that occurred during the intervals you specified. This file will have the following naming convention.
Example: PNGG00.CDTIPK. A13OP678.EN0610.I1234C.SQ1234
Field numbers Data Element Valid
Values Description Notes
1 2 3 4 5 6
Applicable
environment
QNGG00
PNGG00
Q = Test
environment
P = Production
environment
These are standard
fields and cannot be
amended
Field 1 - 4 are
alpha
Field 5 and 6 are
numeric ie zero,
zero
P N G G 0 0
7
Separator . To separate data
elements
The full stop
cannot be
replaced with a
comma as the
file validation will
fail
.
8 9 10 11 12 13 Product
environment CDTIPK
To identify the file as
a Transaction
Information product
C D T I P K
14
Separator . To separate data
elements
The full stop
cannot be
replaced with a
comma as the
file validation will
fail
.
15 16 17
Client Prefix
Please refer
to
description
Field 15:Only alpha
character are valid
Field 16 and 17:
Only alphanumeric
characters are valid
To identify the
client to whom
the file will be
delivered. This
prefix will be
issued by
Nedbank
A 1 3
18
Input / Output
indicator
O = Output
I = Input
Only the specified
alphanumeric
characters are valid
O = When you
receive a file
from Nedbank
I = When you
send the file
back to Nedbank
eg this will only
be applicable if
you use a
delivery protocol
that has the
capability for file
acknowledgeme
nt
O
19
Product ID
N =
Notifications
P = PTI
I = IOD
F = FTI
R = IR
Only specified
alphanumeric
characters are valid
To identify which
product you are
receiving the file
for P
Page 14¶
14| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Example: PNGG00.CDTIPK.A13OP 678.EN0610.I1234 C.SQ1234
Field numbers Data Element Valid
Values Description Notes
20 21 22
File sequence
numbers 001 to 999
These fields
represent the file's
sequential numbers
and will be numeric
It will be
sequentially
incremented by
1 for every file
sent for that day.
The number is
reset to 001 the
next day at
midnight
6 7 8
23
Separator . To separate data
elements
The full stop
cannot be
replaced with a
comma as the
file validation will
fail
.
24
File type
D = Data file
and
E = End of
day file
Only the specified
alpha characters are
valid
E = End of day
file is applicable
to the PTI end of
day file only D
25
Resend
indicator
R = Resend
N = Normal
Only the specified
alpha characters are
valid
If you receive a
file with a R
value in the field
the system must
not automatically
process the file
N
26 27
Day indicator 01 to 31 Only numeric
characters are valid
DD = Indicates day of the month that the file was created and does not indicate the date of the transactions
0 6 28 29 Month indicator 01 to 12 Only numeric characters are valid MM = Indicates the month of the year that file was created and does not indicate the date of the transactions
1 0 30 Separator . To separate data elements The full stop cannot be replaced with a comma as the file validation will fail . 31 Instance ID I = Instance Only the specified alpha character is valid
I
32 33 34 35
Instance
number
0001 to
9999
Each TI product can
have up to 9999
instances per profile
An instance is a
grouping of your
accounts,
settings and
delivery protocol
eg Instance
0001 account1
selected -
settings 'credits
only' and
delivered via
email
1 2 3 4
Page 15¶
TRANSACTIONAL INFORMATION | 15 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Example: PNGG00.CDTIPK.A13OP678.EN0610.I1234 C.SQ1234
Field numbers Data Element Valid
Values Description Notes
36
Protocol ID
C =
Connect:
Direct
E= Email
S = Swift
W = Web
Services
M = IBM MQ
A = FileAct
F = FTP
P = SFTP
Q = IBM MQ
FTP
Only the specified
alpha characters are
valid
This is the
delivery protocol
selected for this
instance. Please
note if the file is
resent to the
alternative email
address the file
name will
contain the
original protocol
ID and not the
email ID
C
37
Separator . To separate data
elements
The full stop
cannot be
replaced with a
comma as the
file validation will
fail .
38 39
Sequential SQ
Only the specified
alpha characters are
valid
These values
cannot be
amended S Q
40 41 42 43
Data record
length
0001 to
9999
These fields will
indicate the fixed
length of the data
record. Only numeric
characters are valid
All TI files are
fixed length 1 2 3 4
Note: The file name for all delivery protocols for the IOD product will always end with .ZIP and not end with .SQ1234. All IOD files have a fixed length of 256 bytes. For all other TI products files that are sent on the email, the delivery protocol will include the file format as an extension at the end of the file name eg, .xml, .csv etc. This is to enable the opening of the file in the correct application. 1.4 Nomination of a contact person
You must nominate a person with proper authority to deal with all communication matters to Nedbank. Nedbank will direct all correspondence and enquiries to the nominated contact person who is the acting authority of the organisation and will be perceived as such if any instructions are received from him/her.
Note: The contact person must be from the data processing department of the organisation. Technical consultations during the development phase may be at a different level.
Page 16¶
16| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
1.5 Resend of transactions and files
A. Resend of transactions
a) Products to receive resent transactions The resend of real time transactions is only available to Notifications and PTI.
b) Resend addresses For the PTI product you can request the bank to resend transactions to the delivery address on the instance or to the alternate email address. Transactions can only be sent to the alternate email address if the alternate email address is currently captured on your PTI instance.
If the alternate email address is not currently captured on the instance you can update it on NetBank Business or for Host clients send through a maintenance request. If the resend key is greater than 0 it indicates that this is a resend of a previous transaction.
B. Resend of files
a) Products to receive resent files This functionality is only available for files that were sent for the IOD, FTI and PTI products.
b) Resend addresses You can request the bank to resend the file to the delivery address on the instance or to the alternate email address. The file can only be sent to the alternate email address if the alternate email address is currently captured on your instance.
If the alternate email address is not currently captured on the instance you can update it on NetBank Business or for Host clients send through a maintenance request. In field 25 of the TI file name the R indicates that this is a resend of a previous file.
C. How to request a resend
a) Host Clients
You may contact Client Integration Support should you require any of your transactions
or files to be resent.
Refer to 1.8.1 for contact details
b) NetBank Business Clients (SMS / Email delivery protocol only) You may contact the NetBank Business Help Desk to request your transactions or files to be resent. Refer to 1.8.2 for Internet banking contact details
Note: You can only request to resend the original file once a day. If you do not receive the resend, you will have to wait for the next business day to request the resend of that file.
Page 17¶
TRANSACTIONAL INFORMATION | 17 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Note: Nedbank holds your data of previous transactions or files sent for a period of 90 days, therefore you can only request a resend of a transaction or file up to 90 days in the past. The resend transaction or file will be formatted and sent based on the current template and delivery address captured on your instance, and not the original settings at the time the file was first sent.
1.6 Responsibilities
It is your responsibility to ensure that connectivity is active and operational in order to receive transaction information. 1.7 System Availability
You are responsible for the provision and cost of the delivery protocol. The TI service will be interrupted periodically for hardware and software maintenance.
Note: Nedbank system maintenance is scheduled daily between 23:45 and 00:30.
All transactions processed during this maintenance slot will be delivered
once the maintenance has been completed.
1.8 TI service support
1.8.1 Host connectivity support
Client integration services (CIS) will provide you with contact details for a support person to handle all host to host related queries:
Contact number: 011 295 8737 / 083 627 7712
Email: h2hcs@nedbank.co.za
1.8.2 Internet banking (NetBank Business) connectivity support
For any queries related to Notifications, PTI, FTI and IOD on NetBank Business (NBB) contact NCCS for support:
Corporate Banking clients: 0860 102 187 Business Banking clients: 0860 111 055 NCC Relationship Banking clients: 0860 116 400 From outside South Africa: +27 (0)11 710 4311
Page 18¶
18| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
1.9 Delivery protocols
1.9.1 Real time delivery protocol
A. IBM MQ
a) What is IBM MQ? IBM MQ is sometimes referred to as message-oriented middleware and is an IBM standard for program-to-program messaging across multiple platforms. It is a protocol that sends data in real time and is a reliable messaging service that guarantees delivery through persistent sending capability. It can provide feedback on successfully sent messages and if no confirmation is received, the message can be resent. IBM MQ is offered over a leased line.
b) Information required from you Your MQ Manager name Your MQ Queue name Your Static Public IP Address which is hosting the MQ Manager Port number the MQ listener is running on Channel name is based on the names of the two MQ Managers involved
Note: Depending on your environment you may have different configurations for your test, disaster recovery and production environment. If applicable, Nedbank will require all these data.
c) Nedbank Information you would require
Nedbank will provide you with the following information:
Leased Line:
MQ Manager Name
QA -
PROD -
DR -
Static Public IP Addresses
QA -
PROD -
DR -
Internet:
MQ Manager Name
QA -
PROD -
DR -
Page 19¶
TRANSACTIONAL INFORMATION | 19 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Static Public IP Addresses
QA -
PROD -
DR -
Security protocol ie SSL using a trusted public security certificates
d) Hardware / Software requirements
The IBM MQ software is compatible with the following platforms and operating
systems:
AIX
HP -UX
Linux for System x
Linux for System P
Linux for System z
Solaris
Windows
I5/OS
IBM
z/OS
Note: Contact your CIS manager for detailed IBM MQ hardware and software requirements related to your platform or operating system.
e) Licensing Dedicated IBM MQ Manager licenses are required from both ends of the connection.
f) Security infrastructure IBM MQ Manager version 7.5 and above have advanced message security which includes: End-to-end, message-level security that offers data protection for your point-to-point messaging infrastructure Data encryption and authentication that provides security-rich data transport throughout the messaging cycle
g) Applicable charges for connectivity Security Certificates
B. Web Services
a) What is Web Services? A Web Service is a method of communication between two electronic devices over a network. The Web Service protocol sends data in real time. Nedbank's standard is to send / push the data to your Web Service. A WSDL (Web Service Definition Language) will be provided by Nedbank, to which you must conform. Web Services is offered over either a leased line or the internet.
Page 20¶
20| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
b) Information required from you Static Public IP Addresses Fully qualified URL Require your Certificates for mutual authentication. If required, Nedbank can provide you with a Certificate. For this an additional fee may apply Require the format / template of the encapsulated content which will be sent in the Web Service call
Note: Depending on your environment you may have different configurations for your test, disaster recovery and production environment. If applicable, Nedbank will require all these data.
c) Nedbank Information you would require
Leased Line:
Static Public IP Addresses
QA -
PROD -
DR -
Internet:
Static Public IP Addresses
QA -
PROD -
DR -
WSDL (Web Service Definition Language) supplied by Nedbank which
will form the base for the development of your Web Service protocol
Require Nedbank Certificates for mutual authentication
d) TI third-party Web Service contract Step 1: Extract the four files below to a folder on your machine Step 2: Open you development environment Step 3: Initiate or create a Web Service wizard (Wizard name may be different depending on the development tool you are using) Step 4: Use the TIWebDistribution _2013-11-01.wsdl as your primary file Step 5: Continue implementation as per your development environment
TIWebDistribution_2
013-11-01.htm
TIWebDistribution_2
013-11-01.wsdl
EnterpriseContext_2
008-09.wsdl
EnterpriseContext_2
008-09.xsd
Page 21¶
TRANSACTIONAL INFORMATION | 21 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Note: Take note that the data contained in the
e) Web Services Hardware / Software requirements The Web Service software is compatible with the following platforms and operating systems:
Z/OS UNIX LINUX Windows HP Non-Stop (Tandem) Open VMS OS/600 Series VM/VSE Gentran Integration Suite Java .NET
Note: Contact your CIS manager for detailed Web Services hardware and software requirements related to your platform or operating system.
f) Licensing
The licenses for Web Services can be classified as proprietary or open:
Proprietary software licenses allow for the execution of the software
(including components) in your computing environment
Open source licenses allow you to view, modify and share the source
code as well as redistributing the software either for commercial and/or
non-commercial purposes
g) Security infrastructure When using Web Services you must consider the following security aspects:
Authentication
Authorisation
Protection of sensitive data on the network and
Handling potentially malicious input
In order to address the above mentioned security aspects Nedbank enforces Mutual SSL, which will address the following:
message security or transport security to encrypt and sign messages platform-provided cryptography platform features for key management
Page 22¶
22| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Periodically changing both our and your keys (renewal of certificates on a periodic basis)
h) Standards utilised by Nedbank for Web Services: SOAP 1.1 or 1.2 XML 1.1 XML Schema 1.0 Web Services definition language (WSDL) 1.0
i) Applicable charges for connectivity There will be charges applicable if you require a security certificate or a leased line.
j) Describing the Web Service contract Nedbank initiates a Web Services-ready platform where the enterprise context will already have been populated; you are expected to echo it back on your response message.
Enterprise context headers for all message layouts (request and response)
Field name Type (Max
Length)
Mandatory/
Optional
Min
occurs
Max
occurs Description Comment
Process
context ID String (36) O 0 1
This identifier
indicates that the
request is part of
a bigger
process. It is a
unique ID for
each process
request and it
must be a
globally unique
identifier (GUID).
Usually
populated with a
GUID/UUID,
used for
tracing/tracking.
Execution
context ID String (36) M 1 1
This identifier is
uniquely used to
identify the
request and it
must be a GUID.
Usually
populated with a
GUID/UUID,
used for
tracing/tracking.
Machine IP
address String (20) M 1 1
This field
contains the IP
address of the
machine.
Source IP
Address
User principle
name String (32) M 1 1
This field
contains the
username that is
used to log on to
a machine.
Machine DNS name String (50) M 1 1 This field contains the full qualified domain name of the machine. Source Machine Name Channel ID Long (3) M 1 1 This is the unique identifier for the channel and is used to initiate the request.
Parent instrumentation String (36) M 1 1 This is the instrumentation Usually populated with a
Page 23¶
TRANSACTIONAL INFORMATION | 23 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only ID ID of the parent instrumentation entry and it must be a GUID. GUID/UUID, used for tracing/tracking. Child instrumentation ID String (36) M 1 1 This is the instrumentation ID of the child instrumentation entry and it must be a GUID. Usually populated with a GUID/UUID, used for tracing/tracking.
Sample Enterprise Context format
Description of the request message
Tag name Type (Max
Length) Usage Min
occurs
Max
occurs Description
Format NC-10 Required 1 1 The format of the data as provided
by the TI backend
SecurityProxyType NC-10 Required 1 1 A value indicating the security
gateway to use.
DestinationKey Long(9) Required 1 1 Destination Key
TransformedData NC-5000 Required 1 1 The generated data
Sample of request message
Description of the response message (message generated by you in response to the
request message)
Tag name Type (Max
Length) Usage Min
occurs
Max
occurs Description
ResultCode NC-3 Required 1 1
R00 - is the required response for a
successful transmission of the
message (all other codes will be
treated as an error to be defined by
the client, this list of error codes
must be maintained by the client)
Page 24¶
24| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Sample of the response message
C. Enotes PTI Web Services Refer to Appendix F for more information on Enotes PTI Web Services.
Note: Enotes PTI Web Services is for informational purposes for clients migrated to TI from Enotes PTI. New clients must use the TI Third-party Web Services contract.
D. SWIFT (Society for Worldwide Interbank Financial Telecommunication)
a) What is SWIFT? SWIFT uses a standardised proprietary communications platform to facilitate the transmission of information about financial transactions. This information, including payment instructions, is securely exchanged between financial institutions.
b) Information required from you SWIFT Address for QA and Production.
c) Nedbank Information you would require
Nedbank SWIFT Address for QA and Production:
NEDSZAJ0 - QA
NEDSZAJJ - Production
d) Hardware / Software requirements
SWIFT is compatible with the following platforms and operating systems:
Windows
Solaris
Linux
IBM AIX
Note: Contact your CIS manager for detailed SWIFT hardware and software requirements related to your platform or operating system.
e) Licensing You need to have an agreement with SWIFT to utilise the SWIFT cloud and have a SWIFT Address.
f) Security infrastructure As per SWIFT standards and requirements.
Page 25¶
TRANSACTIONAL INFORMATION | 25 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only g) Applicable charges for connectivity You will incur the charges as per your agreement with SWIFT.
E. Email
a) What is email? Electronic mail, most commonly referred to as email is a method of exchanging digital messages from an author to one or more recipients.
b) Information required from you In order to use this protocol you must have a valid email address.
c) Software requirements Functioning email server.
d) Security Nedbank will digitally sign the email.
e) Applicable charges for connectivity None.
1.9.2 Near real time delivery protocol
A. Connect: Direct
a) What is Connect: Direct? The Connect: Direct protocol is a file transfer protocol that sends data in near real time. Connect:Direct can be used over a leased line or over a public internet connection to connect to Nedbank. It can be configured to provide feedback on successfully sent files. The Connect: Direct configuration is required once the Connect: Direct software has been loaded. When the Connect: Direct configuration has been completed, the connection will be tested end to end. In most cases, Nedbank coordinates the installation.
b) Information required from you Your Static Public IP Address Your Server name Directory Connect:Direct will connect to port 1364 which must be provisioned on your firewall
Note: The email protocol does not guarantee delivery ie Nedbank can confirm the email has been sent but cannot confirm that you have received it.
Page 26¶
26| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
c) Nedbank information you would require
Leased Line:
Static Public IP Addresses
QA -
PROD -
DR -
Internet:
Static Public IP Addresses
QA -
PROD -
DR -
User name
Unique per client
Nedbank will issue one CA Certificate to you to upload on to your
Connect:Direct software.
d) Hardware / Software requirements The Connect: Direct software is compatible with the following platforms and operating systems: Z/OS UNIX LINUX Windows Select HP Non-Stop (Tandem) Open VMS OS/600 Series VM/VSE Gentran Integration Suite
Note: Contact your CIS manager for detailed Connect: Direct hardware and software requirements related to your platform or operating system. Certain LINUX versions are not supported.
e) Licensing You will require your own Connect:Direct license or a spoke license can be issued from Nedbank. If you already have an existing spoke license with Nedbank you can use the same license to receive your TI files if capacity allows.
Note: You will not be able to use a spoke license issued by another entity to connect to Nedbank.
Page 27¶
TRANSACTIONAL INFORMATION | 27 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only f) Security infrastructure Connect:Direct ensures that your information stays private and that your file transfers are auditable for regulatory compliance through a proprietary protocol, authorisation and encryption.
g) Applicable charges for connectivity If you require a spoke license from Nedbank there is a monthly license fee and a once off installation fee applicable.
Note: Contact your Transactional Banker for further information.
B. Secure file transfer protocol (SFTP)
a) What is SFTP?
SFTP is a secure file transfer protocol that sends data in near real time. This
is a much preferred and enhanced version of transferring files in a more
secured manner when compared with FTP (unsecured protocol for file
transfer). There are licensing implications for both.
A 'staging area' is required where the files will be put in your business
environment to be picked up by an application for internal processing. It uses
a fire-and-forget pattern and therefore no acknowledgment of receipt is
required. You have two options when using SFTP protocol:
You must exchange security keys with Nedbank and vice versa and You must supply Nedbank with a user name.
b) Information required from you
Static Public IP Address
User name
Public key
Port number 22 must be open on your firewall
c) Nedbank information you would require
Leased Line:
Static Public IP Addresses
QA -
PROD -
DR -
Internet:
Static Public IP Addresses
QA -
PROD -
DR -
Page 28¶
28| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Public key and IP Address Unique per client
d) Software requirements You will require a SFTP server that is compatible with Nedbank's system.
Note: Nedbank uses a Unix operating system SFTP software. Please confirm with your Nedbank Integration Manager.
e) Hardware requirements The SFTP protocol is compatible with the following platforms and operating systems:
Z/OS UNIX Windows Windows NT Mac OS X
Note: Contact your CIS manager for detailed SFTP hardware and software requirements related to your platform or operating system.
f) Licensing The SFTP is for your own account.
g) Security infrastructure Mutual SSL ie certificates issued from the SFTP software.
h) Applicable charges for connectivity None
C. SWIFT FileAct
a) What is SWIFT FileAct? SWIFT FileAct provides a way to transfer large volumes of data in different formats to your correspondents, whether you need to transfer mass payments information, documents, images, or other data. In the case of TI you can opt to receive your FTI, PTI and / or IOD files using SWIFT FileAct.
The mechanism used by Nedbank to transfer TI files on SWIFT FileAct is to use store and forward.
Note: Nedbank only uses store and forward for TI, ie realtime is not available.
Page 29¶
TRANSACTIONAL INFORMATION | 29 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
b) Information required from you: Your SWIFT Address for QA and Production environment. Nedbank will accept the BIC8 or BIC11 SWIFT address. Requester DN Example: o="Client BIC",o=swift
c) Nedbank information you would require:
Nedbank SWIFT Address for QA and Production environments are
NEDSZAJJ.
This information will be applicable to PTI, FTI and IOD:
- Request Type
o PTI = pain.xxx.irtrpt or pacs.xxx
o FTI = pain.xxx.eodrpt or pacs.xxx
o IOD = pacs.xxx
- Responder DN: o=nedszajj,o=swift
- Files for File Act must not be compressed
- SWIFT Fileact Service to be used for store and forward:
o QA = swift.generic.fast!p
o Prod = swift.generic.fast
d) Hardware / Software requirements
SWIFT Alliance Gateway
e) Licensing There are no licencing requirements from Nedbank but you need to have a valid SWIFT Address.
f) Security infrastructure FileAct uses SWIFTNet Public Key Infrastructure (PKI) that enables the authentication and the integrity control for every file transferred.
g) Applicable charges for connectivity SWIFT charges a FileAct usage fee per transferred file. The transfer fees vary according to the size (in bytes) of the file and the institution's global tier. Nedbank will not levy a charge for connectivity, you will be charged as per your agreement with SWIFT.
D. Email
a) What is email? Electronic mail, most commonly referred to as email is a method of exchanging digital messages from an author to one or more recipients.
b) Information required from you In order to use this protocol you must have a valid email address.
Page 30¶
30| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
c) Software requirements WinZip and a functioning email server.
d) Licensing None
e) Security
Any file sent using the email protocol will be zipped using WinZip. The Zip file
will be attached to the email and password protected. In addition the email will
be digitally signed by Nedbank.
f) Applicable charges for connectivity None 1.10 Pricing
A. Charge account
You can use the same charge account for all your TI products or if required, you will have the ability to choose different charge accounts for each TI product. Each product can have a separate transaction, subscription and administrative charge account.
Note: Only Nedbank current and savings accounts that belong to the same legal entity can be used as a charge account.
B. Billing date
All charges will be posted to the nominated charge account(s) on your profile billing date.
Note: If you change your profile billing date on any of the TI application or maintenance forms, it will update your billing date for all products on the profile.
C. Product charges
Based on your pricing agreement with Nedbank, you may be charged a different pricing structure (transaction fee or a monthly subscription fee) eg, for PTI a transaction fee and for Notifications a monthly subscription fee. In each pricing structure, the FTI and PTI products will have different charges based on the delivery protocol selected.
Note: Only the zipped file is password protected ie once the file is extracted no password is required.
Page 31¶
TRANSACTIONAL INFORMATION | 31 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only a) Transaction fee pricing structure
The transaction fee is calculated based on the number of Notifications sent to you, which can be subject to a minimum and maximum fee per month. Up to three transaction fees may be applicable for PTI and FTI based on the delivery protocol selected, ie:
A transaction fee for the SWIFT delivery protocol, subject to a minimum and maximum per month A transaction fee for the email delivery protocol, subject to a minimum and maximum per month A transaction fee for all other delivery protocols, subject to a minimum and maximum per month
If a financial transaction is sent to multiple destinations, you will be charged for the delivery to each destination eg, if a cash deposit of R500 is deposited into your account and you request to send the information to:
two destination addresses you will be charged 'two times' your Notification fee five destination addresses you will be charged 'five times' your Notification fee
Fees are accumulated and billed to your nominated transaction charge account once a month. This will appear as a separate line item on your charge account statement ie:
Contact your Transactional Banker to confirm your actual pricing.
Note: You can have the same or a different transaction charge account per product. However, the billing date cannot be different to your profile billing date.
Page 32¶
32| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
b) Monthly subscription fee pricing structure
Your monthly subscription fee will be billed to your nominated subscription charge account on your profile billing date. This will appear as a separate line item on your charge account statement ie:
Contact your Transactional Banker to confirm your actual pricing.
Note: You can have the same or a different subscription charge account per product. However, the billing date cannot be different to your profile billing date.
D. Additional PTI fee if applicable
PTI end of day file charges
You will be billed a monthly fee to your nominated subscription charge account on your profile billing date. This will appear as a separate line item on your charge account statement ie:
- PTI end of day fee
eg PTI end of day fee(1) Contact your Transactional Banker to confirm your actual pricing.
Note: You can have the same or a different transaction charge account per product. However, the billing date cannot be different to your profile billing date.
E. Other charges
The below fees are only applicable if you request the bank to resend a Notification or if you have submitted a maintenance request to be actioned.
Resend fee
If you request the bank to resend a Notification or file you may be charged a resend fee per request. Fees will be accumulated and billed to your nominated
Page 33¶
TRANSACTIONAL INFORMATION | 33 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only administration charge account on your profile billing date. This will appear as a separate line item on your charge account statement ie:
resend fee eg PTI resend fee(1) eg FTI resend fee(2) eg IOD resend fee(1) eg Notifications resend fee(4)
Contact your Transactional Banker to confirm your actual pricing.
Note: You can have the same or a different transaction charge account per product. However, the billing date cannot be different to your profile billing date.
F. Administration charges
If you request the bank to add or maintain any TI instances, you may be charged an administration fee per maintenance request.
Fees will be accumulated and billed to your nominated administration charge account monthly on your profile billing date. This will appear as a separate line item on your charge account statement ie:
TI admin fee
Note: You can have the same or a different administration charge account per product. However, the billing date cannot be different to your profile billing date.
G. Connectivity charges
a) Leased line Nedbank does not charge you any leased line fees. Your service provider will charge you directly for any leased line costs. If capacity is available on your existing leased line, you may choose to enable the TI products on this line.
b) Connect: Direct license
There will be a once off implementation fee and a monthly license fee. If you have an
existing Connect: Direct license with Nedbank, you can use the existing license if
capacity is available. Contact your Transactional Banker to confirm these fees.
Page 34¶
34| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
c) IBM MQ Nedbank does not charge you any IBM MQ fees unless Nedbank issues you with the security certificate. The Nedbank issued certificate will attract an annual fee. Contact your Transactional Banker to confirm these fees.
d) SFTP Nedbank does not charge you any SFTP fees unless Nedbank issues you with the security certificate. The Nedbank issued certificate will attract an annual fee. C ontact your Transactional Banker to confirm these fees. In order to use this protocol you will be required to have SFTP software compatible with Unix operating system, which could attract a software license fee.
e) SWIFT FileAct Nedbank does not charge you any SWIFT FileAct fees. All SWIFT FileAct fees will be charged as per your SWIFT agreement.
f) SWIFT Nedbank does not charge you any SWIFT fees. All SWIFT fees will be charged as per your SWIFT agreement.
g) Web Services Nedbank does not charge you any Web Services fees unless Nedbank issues you with the security certificate. The Nedbank issued certificate will attract an annual fee. Contact your Transactional Banker to confirm these fees.
h) Email Nedbank does not charge you for any email connectivity, this must be negotiated with your service provider.
Note: All Nedbank fees can be discussed with your Relationship Manager or Transactional Banker.
1.11 Security
Due to the implementation of the Protection of Personal Information Act (POPIA) all sensitive information sent, must be delivered using a secure delivery protocol.
The following protocols are supported:
Connect: Direct Email attachment IBM MQ SFTP SWIFT SWIFT FileAct Web Services
Page 35¶
TRANSACTIONAL INFORMATION | 35 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Note: FTP is no longer supported by Nedbank.
1.12 High level onboarding process for TI host to host delivery protocols
Identifies client
need for TI
Sales manager Client CIS
Generates proposal
of TI offering for
client
Setup meeting with
client to discuss
proposal
Initiate client
application
Setup initial meeting
with CIS and client
to discuss options
End
Client accepts
proposal
Yes, client wants to take
up TI
Initial workshop to discuss TI product - connectivity
protocol requirements
Setup technical
workshop with client
and Nedbank
Technical workshop to gather and explain technical process to
be followed for TI to setup - connectivity protocol requirements,
file formats etc.
Project plan to be put together Provide client with
application form for
signature
Submit document for
vetting and loading
Vetting and loading
successful
Client to sign
documents and
fax to Nedbank
or hand to
sales manager
Client confirms
connectivity
working
Client confirms
receipt of
transactions
Client confirms
transactions
received in
production
Ensure
connectivity
setup between
client and
Nedbank Generate test
transactions
Schedule
production
release date
Start 30 day
client support
Page 36¶
36| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
1.13 TI Keys
A. Transaction key
Every transaction is allocated a 16 digit key. If you receive the same transaction key on more than one message it is reporting information about the same transaction. However, note the key is only unique at a product level and not across TI products ie, the same transaction will have different transaction keys on PTI and FTI.
B. Process key
Every process is allocated a 9 digit key. A process uniquely identifies the current client preferences for the transaction. This value is for internal purposes and does not have to be interpreted by you in processing this transaction.
C. Resend key
Every message is allocated a 9 digit key. Any value greater than zero means that the transaction was resent. A resent transaction will have the same transaction key as the initial transaction.
D. Destination key
If a single instance has more than one destination address it will have a different destination key, per delivery address. However, note the key is not uniquely linked to the destination address ie, the same delivery address on the same instance can have a different destination key on two different messages.
1.14 TI Templates
A. TI Template groups
The template groups contain a selection of templates that make a logical fit into a specific group eg any SWIFT proprietary template will be available under the SWIFT group.
Currently the following groups are available:
Nedbank
SWIFT
SAP
Other
Client Specific
Page 37¶
TRANSACTIONAL INFORMATION | 37 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Note: To view the format and detail of the above templates refer to Appendix A for PTI, Appendix B for FTI and Appendix D for IR.
B. The 'Nedbank' Template group
a) Near real time templates
PTI Templates: - TI PTI XML (NRT) - TI PTI CSV (NRT) - TI PTI TXT (NRT) - Enotes PTI CSV (NRT) - Enotes PTI SWIFT MT940 - Enotes NedAcad - Enotes PTI EOD XML - Enotes PTI EOD CSV
Note: To view the format and detail of the above templates refer to Appendix A. The Enotes PTI templates are only applicable to existing clients that are already utilising the templates and will not be available to new clients for selection.
b) Real time templates
PTI Templates: - TI PTI XML (RT) - TI PTI CSV (RT) - TI PTI TXT (RT) - Enotes PTI XML (RT) - Enotes PTI CSV (RT)
Note: To view the format and detail of the above templates refer to Appendix A. The Enotes PTI templates are only applicable to existing clients that are already utilising the templates and will not be available to new clients for selection.
FTI Templates:
- TI FTI XML
- TI FTI CSV
- TI FTI TXT
- NedAcad 4 digit statement - 29 character statement narrative
- NedAcad 6 digit statement - 27 character statement narrative
- NedAcad 6 digit statement - 30 character statement narrative
- NedAcad 4 digit single statement - 29 character statement narrative
Page 38¶
38| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
- NedAcad 6 digit single statement - 27 character statement narrative
- NedAcad 6 digit single statement - 30 character statement narrative
Note: To view the format and detail of the above templates refer to Appendix B. The NedAcad templates are only applicable to existing clients that are already utilising the templates and will not be available to new clients for selection.
C. The 'SWIFT' Template group
a) Near real time templates
FTI Templates: - TI SWIFT MT940 - TI SWIFT MT950 - NED SWIFT MT940 - NED SWIFT MT950 - TI SWIFT MX940 - camt.053 (Bank to customer statement) - TI SWIFT MX950 - camt.053 (Bank to customer statement)
PTI Templates: - TI SWIFT MX942 - camt.052 (Bank to customer account report) - TI SWIFT MT942
IR Templates - TI SWIFT MT940 - TI SWIFT MT950 - TI SWIFT MT942
Note: To view the format and detail of the above templates refer to Appendix A, B and C. The NED SWIFT templates are only applicable to existing clients that are already utilising the templates and will not be available to new clients for selection.
b) Real time templates
PTI Templates: - TI SWIFT MT900 - TI SWIFT MT910 - TI SWIFT MT941 - TI SWIFT MX900 - camt.054 (Bank to customer credit / debit Notification) - TI SWIFT MX910 - camt.054 (Bank to customer credit / debit Notification) - TI SWIFT MX941 - camt.052 (Bank to customer account report)
Page 39¶
TRANSACTIONAL INFORMATION | 39 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
IR Templates: - TI SWIFT MT941 - SWIFT MT920 You will be required to use t his template when requesting final or provisional statement information from Nedbank.
Note: To view the format and detail of the above templates refer to Appendix A and C.
D. The 'SAP' Template group
a) Near real time templates
PTI Templates:
- Multicash AUSZUG
- Multicash UMSATZ
FTI Templates:
- TI SWIFT MT940
- Multicash AUSZUG
- Multicash UMSATZ
Note: To view the format and detail of the above templates refer to Appendix A and B.
b) Real time templates
None currently available
E. The 'Other' Template group
a) Near real time templates
XXXXXX XXXXXX
b) Real time templates XXXXX
Page 40¶
40| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
F. The 'Client Specific' Template group
a) Near real time templates None currently available
b) Real time templates Vodacom - PTI
1.15 Testing your TI functionalities for host protocols
A. Process for quality assurance (QA) testing
Due to the complexity of the TI environment, all organisations must go through a testing phase before going into production with the system. This is mainly to verify connectivity, data integrity and client system changes and/or development. During the test phase the following key aspects must be verified:
Connectivity using your chosen delivery protocol must be stable and in place Specified file layout must be adhered to Business processes align with business requirements
The organisation must meet the following requirements before testing may begin:
The TI file layouts must be set up The organisation and Nedbank must have parallel QA environments in place
During testing the following naming convention will be used:
Example: QNGG00.CDTIPK.A13OP678.EN0610.I1234C.SQ1234
A Q is used instead of a P. (Q refers to a QA testing file, while P refers to a production file)
B. Testing scenarios
Tests could possibly cover the following scenarios, but can be tailored to your needs:
The sending of high-volume files (inclusive of high- and low-volume data) The integrity of the data contained in the files sent (layout of data and file format) The use of a nominated account(s) set up in accordance with the intended production profile The transfer of corrupt files and/or transactions (file-handling process)
Note: QA data is for testing purposes only and is not to be used for any decision-making processes regarding your customers.
Page 41¶
TRANSACTIONAL INFORMATION | 41 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only 1.16 Checklists for required documents
Use these checklists for near real time and real time functionality to ensure that you have provided all the required documents to Nedbank and that you have completed all the required steps to make your TI products operational.
Documentation required by Nedbank:
For near real time and real time functionality
No Item Comment
a TI application form Depending on which TI product you have
selected.
b Main participant resolutions
c Master Electronic Banking Agreement (MEBA) Required with a new profile or MEBA that
was signed before 2009
d Services Required (Schedule 1) Only when a new application for a product
is required
e Pricing fees schedule (Schedule 2) Only when a new application for a product
is required
f Participant resolution
h Signature card Only required with a new profile
2 Notifications
2.1 What is the Notification service?
The Notification service will send you a SMS or email, informing you of any transaction processed on your account as well as other value added Notification options eg low balance alert. You can receive Notifications on any current or savings account you hold with Nedbank.
The Notification service is a dynamic solution that will allow you to customise the Notification to suit your business needs. You can set up to 9 999 different types of Notifications, each on a separate Notification instance ie you can have different Notification instances for the Chief financial Officer and a different Notification instance for the debtors clerk.
Each instance is customisable to send out specific Notifications to specific recipients, ie each instance setup allow you to:
Specify the account/s to be notified on Specify the type of transaction to be notified on Specify the value of the transaction to be notified on eg if a company has mandates in place you can setup the instance to only send transaction above a certain value to the CFO
Page 42¶
42| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
The option of receiving certain Value Added Notifications eg to be notified if your account balance drops below a specified amount or if the usage of your account overdraft limit reaches a certain percentage. Specify a time preference, if you would not like to receive Notifications during specific hours of the day eg only send Notifications between 8am and 5pm Specify up to 10 email addresses or cellphone numbers
2.2 Key features of Notifications
A. Real time Notifications
Nedbank will send out the Notification within 60 seconds of the transaction reflecting on
your current or savings account.
Note: Nedbank will delay sending your Notifications if it is outside your
selected time preference (eg 8am to 5pm) and only send the
Notification when your time preference has been met.
B. Notification instances
You have the option of setting up to 9999 different Notification instances. You can customise each instance with the following settings:
Instance name
Specify accounts
Choose delivery method
Choose language preference
Specify the transactions you would like to be notified on for the selected accounts
Specify if you would like to be notified only if the transaction is above a certain
value
Option to receive Value Added Notifications
Option to receive NetBank Business Notifications
Option to receive Notifications only during a specified time of day
Example: You can set up an instance and name it 'Debtors Clerk Notifications'. This instance can then be customised so that Notifications are sent only to the debtors clerks in your company. You can select the accounts the de btors clerks should receive Notifications on, as well as which Notifications they should receive.
C. Customised Notifications
Each Notification instance can be customised with the following options:
a) Instance name You as the customer can decide on the instance name that will best suite your business needs eg, CEO Notification or Accounting department Notification. The instance name can accommodate alphanumeric characters up to a maximum of 30 characters, no special characters are allowed.
Page 43¶
TRANSACTIONAL INFORMATION | 43 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only Note: After adding a new Notification instance, Nedbank will allocate each instance a unique instance number. If you require Nedbank to perform any changes to an existing Notification instance on your behalf, the relevant maintenance form will need to be submitted. All maintenance forms must include the instance name and number.
b) Specify accounts You can select one or multiple accounts on which to receive Notifications for this instance. The only accounts types that are available for selection are current and/or savings accounts loaded on your profile.
Note: If an account is closed it will automatically be deleted of all Notification instances. If it is the only account loaded on the instance the instance will also be deleted.
c) Choose delivery method You can choose to receive your Notifications via SMS or email at an instance level. If you require the Notification to be sent via email and SMS, you will need to load a separate instance for each delivery method.
d) Choose language preference You can choose to receive your Notification in English or Afrikaans at an instance level. If you require the Notification to be sent to some recipients in English and some in Afrikaans you will need to load a separate instance for each language preference.
e) Specify the transactions you would like to be notified on for the selected
accounts
You can choose to receive a Notification on all transactions processed on the
selected accounts or
You can choose to receive a Notification on specific transaction types. The following transaction types are available for selection:
Credit Notifications (money in)
o All credits, or specify on or more of the following transactions:
~ Cash deposits
~ Cheque deposits
~ Mixed deposits
~ Electronic deposits
Debit Notifications (money out) o All debits, or specify on or more of the following transactions: ~ Cash withdrawals ~ Debit orders ~ Electronic payments ~ Electronic transfers ~ POS purchases
Page 44¶
44| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Note: You can select a combination of debit and credit transaction types on which to be notified.
No transaction Notification
You will select this option if you do not want to be notified about any
transactions on the account, but still want to receive value added and/or
NetBank Business limit Notifications.
f) Specify if you would like to be notified only if the transaction is above a certain amount You can choose to receive Notifications, only if it is above a certain amount for the selected transaction types eg, cash deposits more than R500.
g) Option to receive Value Added Notifications
Low-balance alerts
You can choose to receive a Notification when your account reaches a specified
balance. The amount you specify applies to your current / book balance and not
your available balance.
Balance only
You will receive a separate Notification for each account selected. This
Notification will provide you a view of the available and current / book balance for
each account at that time. You can select to receive this Notification once in the
morning and/or once in the afternoon.
Changes in client information
You can choose to receive a Notification if any change has been made to your
customer record eg contact numbers or addresses.
Consolidated information only
You can choose to receive a Notification that will provide you with a summary of
all transactions processed on your account. The Notification will include the value
of the total debits and credits processed on your account up until the time of
sending the Notification. When sending the Notification Nedbank will check your
account available balance and include it in the Notification. The first Notification
will be sent at 9am and the second Notification will be sent at 5pm
Overdraft limit
You can choose to receive a Notification when usage of your overdraft limit has
reached a specified percentage. The usage of your overdraft limit is checked at
9am and 5pm. This only applies to account overdraft limits and not to group
limits.
h) Option to receive NetBank Business limit Notifications:
You can choose to be notified on any one or combination of the following limits:
Page 45¶
TRANSACTIONAL INFORMATION | 45 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
NetBank Business payment limits: Profile (monthly and/or daily) User (daily only) Account (monthly and/or daily)
NetBank Business transfer limits:
Profile (monthly and/or daily)
User (daily only)
Account (monthly and/or daily)
NetBank Business collection limit:
Profile (monthly and/or daily)
User (daily only)
You will receive a Notification when the usage of your specified limits have been reached. This only applies to client-imposed limits or Nedbank credit limits for payments, transfers and collections.
i) Option to receive Notifications only during a specified time of day You can choose to receive Notifications all day, or only during a specified time interval. If a transaction is processed on your account outside your selected time the Notification will be generated in real time but not delivered until your time preference has been met. The selected time preference does not apply to the following Notification types:
Balance only
You will always receive the Notification at the selected time(s)
Consolidated information You will always receive a Notification at 9am and 5pm
Overdraft usage You will always receive a Notification at 9am and 5pm
Overnight transactions (Debit orders, interbank electronic deposits) You will receive these Notifications between 7am and 8am
Page 46¶
46| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
D. Notification details
Depending on the transaction and the Notifications you requested, you will receive the following details:
The channel through which the transactions occurred, eg ATM, Branch or Electronic Banking. The type of transaction, eg payment or transfer. The transaction amount. Your statement reference. The location or area where the transaction occurred, for Notifications generated for card transactions. The date and time that the Notification was generated. The available balance on the account at the time indicated on the Notification. The current / book balance on the account at the time indicated on the Notification (only available on the email Notification)
2.3 Adding or maintaining Notification instances
Notification instances can be added or maintained electronically or via paper forms.
a) An administrator who has self-maintenance on NetBank Business that can set up and maintain Notification instances electronically, available on NBB under the Admin > Transaction Information Settings > Notifications menu items.
b) Clients who do not have NetBank Business can add or maintain instances by completing and submitting a new application or maintenance form. The following maintenance forms are available on NetBank Business or via the helpdesk:
MR5D: Profile settings
To add the Notification product to an existing profile.
MRTIN1: Add Nedbank account same legal entity
Add a same legal entity account on to your existing Notification instances. Please note, an account has to be on your profile before it can be added to an instance. If the requested accounts are currently not on your profile it will be added to your profile.
MRTIN2: Add Nedbank account other legal entity
Add another legal entity account on to your existing Notification instances. Please note, an account has to be on your profile before it can be added to an instance. If the requested accounts are currently not on your profile, a participant resolution or power of attorney will be required.
Page 47¶
TRANSACTIONAL INFORMATION | 47 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only MRTIN5A: Add Notification instance
Add a new Notification instance to an existing profile. This form can only be used, if the Notification product is already activated on the profile. To activate the product please complete the MR5D.
MRTIN5B: Amend /Delete Notification instance
To amend the settings or delete an existing Notification instance. Please note you
cannot amend or delete the recipients or accounts on existing instances using this
maintenance request. You will need to complete the MRTIN25 to delete / amend
recipients and the MRTIN8 to delete an account.
MRTIN6: Charge detail amendment
To amend your nominated charge accounts for the Notifications product.
MRTIN8: Delete accounts from Notification instances
To delete accounts from existing instances. Please note it will not be deleted off your profile. If it is the only account linked to the existing instance, the instance will be systematically deleted.
MRTIN25: Update recipient details
To add / amend / delete recipients on existing instances.
c) Maintenance Forms can be submitted to Nitro in the following ways:
Fax: 0860 110 782 Only Tiff, Tif or PDF files will be processed
E-Mail:
Transactionalbankingmaintenance@nedbank.co.za
- Only Tiff, Tif or PDF files will be processed
- There must be an attachment
- If no valid attachments are found in the email then the email is rejected and a mail is sent to the sender to notify them that no valid attachments were found
Page 48¶
48| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
2.4 Benefits of Notifications to your business
A. Cashflow management You will be aware of any movement of funds in your accounts, which will assist with your cashflow management.
B. Fraud / Risk awareness You will be aware of any changes in your details, eg cellphone numbers. You will be able to identify any unauthorised activity on your accounts.
C. Convenience Your business will be mobile - you will be able to keep track of transactional activities on your accounts no matter where you are. Assistance with inventory control / goods dispatching will result in improved service delivery to your customers.
2.5 Pricing Refer to section 1.10 in the manual.
2.6 Frequently Asked Questions (FAQ)
Q: What is a Notification instance? A: A Notification instance is a grouping of accounts, preferences and recipients.
Example: You can have a Notification instance for the CEO and a different instance for the debtors clerk ie you can set up an instance and name it 'Debtors Clerk Notifications'. This instance can then be customised so that Notifications are sent only to the debtors clerks in your company. You can select the accounts the debtors clerks should receive Notifications on, as well as which Notifications they should receive.
Q: How many instances can be setup on a profile? A: You can setup 9999 different Notification instances on a single profile.
Q: How many recipients can I have on each instance? A: You can add up to 10 recipients on an instance.
Q: What delivery methods are available for Notifications? A: You have the option to select email or SMS. An instance can only have one delivery method. TIP: If you require a Notification for a specific group of preferences to be sent to both delivery methods, then 2 instances will need to be setup.
Page 49¶
TRANSACTIONAL INFORMATION | 49 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only Q: What is a consolidated information Notification? A: It is a Notification containing the summary of your transactions for the day ie, it will include the sum of all credit and debit amounts from the previous banking day's cutoff up until the time you receive the Notification. It will also include the available balance on the account at the time indicated on the Notification. The Notification is sent at 7:30am and 5:30pm.
Q: What is a balance only Notification? A: It is a Notification that provides you with the current and available balance of the account. You have the option to receive this Notification once or twice a day at client specified time(s).
3 Provisional Transactional Information (PTI)
3.1 What is the PTI solution?
The Provisional Transaction Information (PTI) service will send you a Notification in a machine-readable format when a provisional transaction has been processed to your current and/or savings accounts. This PTI service will send a Notification that can be integrated directly into your line-of-business (LOB) system providing you with the ability to automate operational processes. Note, this is only provisional information so it is up to the client if they would like to rely on this information for operational decisions.
Example: If you sell 'prepaid electricity' as soon as money is deposited into your account, PTI will send a Notification to your line of business system and based on the information your system will release the prepaid electricity to your client in a real time ma nner. The solution will allow you to:
a) Select the type of transactions you would like to be notified on, ie all transactions, credit s only, debits only or account balances.
b) Select the account you would like to receive provisional statement information on.
c) Specify the Nedbank channels you want to receive transaction information on.
d) How often you want to receive the information ie real time or near real time.
e) The preferred file format eg swift MT942.
f) The protocol to be used for delivery of the transaction information.
Page 50¶
50| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Note: This is provisional data only and not yet confirmed transactions, which you can rely on for operational reasons eg the release of goods. You will not be notified on transactions that are not processed on a Nedbank online channel eg payments from agent banks, debit orders, etc.
3.2 Key features of PTI
a) Provisional transaction information can be sent to you in real time or near real time .
b) You will have the option of receiving an end-of-day file that will contain all transactions sent to you during the day.
c) Delivery protocols are available for PTI.
d) A selection of file formats e.g. Multicash and SWIFT, are available to you.
e) You can define the timeframe in which you want to receive provisional transactions e.g. 08:00 to 14:00 daily.
3.3 Benefits of the PTI to your business
This product creates greater value for your business, beyond other services you may have with the bank. It enables you to manage your day-to-day operations more efficiently by providing information that will allow you to:
a) Reactivate services
b) Update key transactional activity in the relevant accounts
c) Improve forecasting
d) Manage day to day operations Estimate your daily cash flows Estimate the close-of-business balances in your accounts Track your own customers' payments Dispatch goods in accordance with your business function
e) Fraud and risk awareness You will be able to identify any unauthorised activity on your account
f) Convenience Regular updates of key transactional activity in relevant accounts. Inventory control / goods dispatching Provisional transaction information sent directly into your LOB systems to assist you in automating operational processes. (Finalised statement information can be
Page 51¶
TRANSACTIONAL INFORMATION | 51 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only sent via Nedbank's NedAcad statements service. Please contact your Transactional Banker for more information. Greater customer satisfaction with the service you render
Note: Provisional transaction information is for operation purposes only and must not be used as final statement information to update financial systems.
3.4 Delivery protocol
Provisional transactions can be delivered in real time or near real time. Transactions can be
be delivered in real time manner only as a single transaction, via a real time delivery protocol.
Transactions can be delivered in near real time manner i.e., transactions are batched at your
specified intervals and can be delivered via a real time or near real time delivery protocol.
If it is delivered on a near real time protocol it is delivered as a file with the file name specified
in section 1.3. If a batch of transactions is delivered via a real time protoco l it does not have a
file name and the message will be contained in the data payload(s). The following delivery
protocols are available for PTI:
a) Real time delivery protocols
Email (only delivery protocol available on NetBank Business) Web Services (Host to host solution) IBM MQ (Host to host solution) SWIFT
b) Near real time delivery protocols
Email (only delivery protocol available on NetBank Business) SFTP (Host to host solution) Connect: Direct (Host to host solution) SWIFT FileAct (Host to host solution)
See section 1.8 for more detail.
Note: Nedbank will only be able to connect to static public IP addresses.
3.5 Delivery preference
You have the option to receive provisional transactions processed on your account in
real time ie, as the transaction takes place, or near real time, ie receive a file containing
provisional transactions, which have taken place over a specified interval.
Page 52¶
52| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
a) Real time
Provisional transactions will be sent to you within 60sec of the transaction being processed on your account. Transactions can only be sent real time on a real time delivery protocol.
Note: This SLA will not apply during Nedbank system maintenance ie software or hardware updates. Daily maintenance is scheduled between 23:45 and 00:30. All transactions processed during this maintenance slot will be delivered once the maintenance has been completed. The SLA provided refers to provisional transactions leaving the Nedbank infrastructure.
b) Near real time
If you choose to use a near real time delivery protocol any provisional transaction processed during your specified time interval will be batched and sent to you in a file.
If you choose to use a real time delivery protocol all transactions that are processed during your specified interval will be held back and only delivered when your time preference has been met.
You have a choice of the following time intervals: 15min 30 min 60 min or Once a day (You can specify the time)
Note: In reference to the time interval, each subsequent file will be dependent on when the previous file was sent. For example, if you are on a 15 min time interval and the first file was sent at 13:05 the next file will be sent at approximately 13:20.
Note: Transactions are sent dependent on the type of transactions (eg debits only) and time preference (eg 8:00 to 17:00) selected.
3.6 Available PTI settings at an instance level
A. Type of transactions
You can select one of the following types of transactions to be notified on:
a) All transactions
b) Debits only (money leaving your account) This will include debit transactions and reversals of debits.
Page 53¶
TRANSACTIONAL INFORMATION | 53 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only c) Credits only (money coming in to your account) or; This will include credit transactions and reversals of credits.
d) Balance only
B. Threshold limit
You can choose to receive transactions for all amounts or specify to receive transactions only if it is above a certain amount.
C. Accounts and channels
At an instance level you have the option to specify the accounts you would like to be notified on. In addition for each selected account you can choose to be notified only if the transaction is processed through one of the following channels:
a) Electronic Banking NetBank Business (NBB) NetBank Retail (NRB) SST CPS Real time payments (RTC, RTGS) Manual unpaid Interbank EFT
b) Mobile Banking
Mobile banking including the Nedbank App
Telephone banking
USSD
WAP
c) Branch
Teller
d) Card
Online purchases
International transactions (POS, ATM, TELLER)
e) ATM Local ATMs Intelligent deposit device (Local cardless cash deposits)
f) Point Of Sale (POS) Local POS transactions
Page 54¶
54| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
g) Cash solutions Cash online Cash vault device
h) All the above
D. Template groups
You have the ability to select a template that will best suite your business needs. The templates available are dependent on the delivery protocol and type of transactions selected.
Available templates
Real time
- TI PTI XML (RT)
- TI PTI CSV (RT)
- TI PTI TXT (RT)
- TI SWIFT MT900
- TI SWIFT MT910
- TI SWIFT MX900 - camt.054 (Bank to customer credit / debit Notification)
- TI SWIFT MX910 - camt.054 (Bank to customer credit / debit Notification)
- TI SWIFT MX941 - camt.052 (Bank to customer account report)
- TI SWIFT MT941
Near real time
- TI PTI XML (NRT)
- TI PTI CSV (NRT)
- TI PTI TXT (NRT)
- TI SWIFT MX942 - camt.052 (Bank to customer account report)
- TI SWIFT MT942
- Multicash AUSZUG
- Multicash UMSATZ
Refer to 1.12 and Appendix A and D for detailed information on PTI templates
Note: If SWIFT has been selected as a delivery protocol only the SWIFT templates can be selected, however SWIFT templates can be sent on all delivery protocols.
Page 55¶
TRANSACTIONAL INFORMATION | 55 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only E. Time preference
You can select to receive provisional transaction information all day or during a specified time. Nedbank will delay sending your Notifications if it is outside your selected time preference (eg 8am to 5pm) and only send the Notification when your time preference has been met.
F. PTI end of day file
a) Introduction End of day files are optional and are generally used to identify any transactions that was sent by Nedbank but not received by you. This can occur if you select a delivery protocol that does not assure delivery (eg Web Services, email).
The end of day file is a summary of all transactions sent to you since the previous end
of day file. This will only include transactions based on the settings for this instance.
However, for each instance you have the option to select a different delivery protocol
and template for the end of day file.
Note: End of day file is not available if you select balance only as your transaction type.
b) Delivery of end of day file:
If your time preference selection is all day then your end of day file will contain all transactions sent to you from 6pm the previous day to 6pm today.
If you have specified a time preference to receive Notifications your end of day file will be generated to include all transactions sent to you from your previous end of day file to the end of the your selected time preference.
Example: If your selected time preference is 9am to 5pm, the end of day file will include transactions from 5pm the previous day to 5pm today.
The SLA is an hour to receive an end of day file.
c) Available delivery protocols
Only near real time protocols can be used for the end of day file.
Refer to section 1.8 for more detail
Note: For the email delivery protocol, you can only have one address for the end of day file.
Page 56¶
56| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
d) Available templates groups Only near real time templates are available for the end of day file. Refer to 1.12 and Appendix A for detailed information on P TI templates
Note: End of day files can only be sent using a near real time delivery protocol.
G. Enotes PTI file naming convention
Note: This file naming convention is only for information purposes for clients that were migrated from the old PTI solution and will not be available to new clients. All new clients will be required to use the TI file naming convention as defined in section1.3.
The Enotes PTI file naming convention is not applicable to TI PTI clients and is only a
reference for the old PTI clients that migrated from the old system to the new system.
A PTI file, used for the near-real-time delivery protocols, contains all transactions that
occurred during the interval specified by the client. The PTI file (from Nedbank host to
the client's LOB system) must adhere to the following naming convention:
PNGG00.CDPACK.**OTnn.D0.SQ730
Nedbank will assign a unique two-letter alpha code to each of the PTI clients. The '**' represents the alpha code, ie AA, AB, AC. This unique alpha code will be incorporated into the file name, as displayed above. The O character is for the output file. The two- digit number, represented by nn, is a sequential number (starting from 01 and going up to a maximum of 99) that Nedbank will increment when sending out new files. This number will be reset to 01 at the beginning of each day.
Note: A file should not contain a duplicate file name, as the file will not be processed, even though it might contain new client data.
During testing the following naming convention will be used:
QNGG00.CDPACK.**OTnn.D0.SQ730
A Q is used instead of a P. ('Q' refers to a QA testing file, while 'P' refers to a production file.)
Page 57¶
TRANSACTIONAL INFORMATION | 57 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only OUTGOING FILE
This is the file that Nedbank will produce and send/push to the client's LOB system for processing. Each and every field within the file must be in the specified fixed format (ie if a field is stated as being 20 characters long and only 12 characters are actually used, that field must be appropriately padded to 20 characters with spaces for alphanumeric fields and with zeros for numeric fields). For numeric fields the data is right-justified and padded with leading zeros; for alphanumeric fields the data is left-justified and padded with trailing spaces.
Note: Any invalid field in the header, detail record or trailer will invalidate the entire file.
3.7 PTI Template groups
The template groups contain a selection of templates that make a logical fit into a specific
group eg any SWIFT proprietary template will be available under the SWIFT group.
Currently the following groups are available:
Nedbank
SWIFT
SAP
Other
Client Specific
Note: If SWIFT has been selected as a delivery protocol only the SWIFT templates can be selected, however SWIFT templates can be sent on all delivery protocols.
Refer to 1.12 and Appendix A for detailed information on PTI templates.
Page 58¶
58| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
3.8 Channel and transaction type combinations Channel and TranType Comb.xlsx
Channel
Name Transaction Type
C / RC /
D / RD
indicator
ENC
Applicable
(Uncleared
funds)
Description
ATM DEPOSIT C / RC Y Cheque or mixed deposits at ATM
ATM CASH DEPOSIT C / RC N Cash deposit at an electronic Teller
(ATM )
ATM PREPAID D / RD N Prepaid purchase at ATM eg airtime
ATM PREPAID AIRTIME D / RD N Prepaid airtime at ATM
ATM PREPAID
ELECTRICITY D / RD N Prepaid electricity at ATM
ATM LOTTO D / RD N Lotto purchase at ATM
ATM SEND IMALI D / RD N Send Imali at ATM
ATM TRANSFER D / C / RD
/ RC N Transfer money between accounts
loaded on the ATM card
ATM WITHDRAWAL D / RD N Cash withdrawal from an ATM
TELLER BANKS OWN
CHEQUES D / RD N
Issuing of a Nedbank cheque on
behalf of the client (Bank certified
cheque)
TELLER EFT DEPOSIT C / RC N Electronic payment into your
account done at Teller
TELLER CASH DEPOSIT C / RC N Cash deposit at Teller
TELLER CHEQUE DEPOSIT C / RC Y Cheque deposit at Teller
TELLER MIXED DEPOSIT C / RC Y Cash and cheque deposit at Teller
TELLER EFT WITHDRAWAL D / RD N Electronic payment from your
account at Teller
TELLER WITHDRAWAL D / RD N Cash withdrawal at Teller using
card, cheque or ID
CAMS PURCHASE D / RD N
Card purchases not processed on
the South African Switch eg Pay Pal,
International purchases
IBOX CASH DEPOSIT C N Deposit done into a Cash Vault
device or using cash online
IBOX UNPAIDS D / C N
Corrections or reversals made to the
deposit on behalf of Cash Vault or
cash online
CPS EFT DEPOSIT C N Any credit to the account of the
client done via an electronic channel
CPS EFT PAYMENT D N Any debit to the account of the client
done via an electronic channel
CPS PREPAID D N Prepaid airtime, prepaid electricity
and lotto purchases
CPS PREPAID AIRTIME D N Prepaid airtime purchase
CPS PREPAID
ELECTRICITY D N Prepaid electricity purchase
CPS LOTTO D N Lotto purchase
CPS SEND IMALI D N Send Imali transaction
CPS EFT TRANSFER D / C / RD
/ RC N Electronic transfer of funds between
accounts linked to a profile
EF DEPOSIT C N Any credit to the account of the
client done via an electronic channel
Page 59¶
TRANSACTIONAL INFORMATION | 59 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only EF PAYMENT D N Any debit to the account of the client done via an electronic channel EF PREPAID D N Prepaid airtime, prepaid electricity and lotto purchases EF TRANSFER D / C / RD / RC N Electronic transfer of funds between accounts linked to a profile NRB EFT DEPOSIT C N Any credit to the account of the client done via an electronic channel NRB EFT PAYMENT D N Any debit to the account of the client done via an electronic channel NRB PREPAID D N Prepaid airtime, prepaid electricity and lotto purchases NRB PREPAID AIRTIME D N Prepaid airtime purchase on internet banking NRB PREPAID ELECTRICITY D N Prepaid electricity purchase on internet banking NRB LOTTO D N Lotto purchase on internet banking NRB SEND IMALI D N Send Imali done on internet banking NRB EFT TRANSFER D / C / RD / RC N Electronic transfer of funds between accounts linked to a profile NBB EFT DEPOSIT C N Any credit to the account of the client done via an electronic channel NBB EFT PAYMENT D N Any debit to the account of the client done via an electronic channel NBB PREPAID D N Prepaid airtime, prepaid electricity and lotto purchases NBB PREPAID AIRTIME D N Prepaid airtime purchase on internet banking NBB PREPAID ELECTRICITY D N Prepaid electricity purchase on internet banking NBB LOTTO D N Lotto purchase on internet banking NBB SEND IMALI D N Send Imali done on internet banking NBB EFT TRANSFER D / C / RD / RC N Electronic transfer of funds between accounts linked to a profile INTTELLER CASH DEPOSIT C / RC N Cash deposit at international Teller INTTELLER CHEQUE DEPOSIT C / RC Y Cheque deposit at international Teller INTTELLER MIXED DEPOSIT C / RC Y Cash and cheque deposit at international Teller INTTELLER WITHDRAWAL D / RD N Cash withdrawal at international Teller INTATM DEPOSIT C / RC Y Cheque or mixed deposits at international ATM INTATM WITHDRAWAL D / RD N Cash withdrawal from an international ATM INTPOS PURCHASE D / RD N International POS purchase MG DEPOSIT C N Credit to client's account originating from another bank MG PAYMENT D N Debit to client's account originating from another bank MG REVERSALS RD / RC N Reversal of a transaction originating from another bank MG UNPAIDS RD / RC N Reversal of a transaction initiated by Nedbank to other bank MOBILE BANKING EFT DEPOSIT C N Any credit to the account of the client done via the mobile channel MOBILE BANKING EFT PAYMENT D N Any debit to the account of the client done via the mobile channel MOBILE BANKING PREPAID D N Prepaid airtime, prepaid electricity and lotto purchases via a mobile
Page 60¶
60| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
device
MOBILE
BANKING PREPAID AIRTIME D N Prepaid airtime purchase on mobile
banking
MOBILE
BANKING
PREPAID
ELECTRICITY D N Prepaid electricity purchase on
mobile banking
MOBILE
BANKING LOTTO D N Lotto purchase on mobile banking
MOBILE
BANKING SEND IMALI D N Send Imali done on mobile banking
MOBILE
BANKING EFT TRANSFER D / C / RD
/ RC N Mobile transfer of funds between
accounts linked to a profile
POS PURCHASE D / RD N Any purchase (card swipes) done at
a POS device
POS WITHDRAWALS D / RD N
A client withdrawing cash from a
store eg Pick and Pay using the
POS device ie cash back
RTGS DEPOSIT C N Credit of funds to the account of the
client via RTGS
RTGS PAYMENT D N Debit of funds to the account of the
client via RTGS
SST EFT DEPOSIT C N Any credit to the account of the
client done via the mobile channel
SST EFT PAYMENT D N Any debit to the account of the client
done via the self service terminal
SST PREPAID D N
Prepaid airtime, prepaid electricity
and lotto purchases via a self-
service terminal
SST PREPAID AIRTIME D N Prepaid airtime purchase on SST
SST PREPAID
ELECTRICITY D N Prepaid electricity purchase on SST
SST LOTTO D N Lotto purchase on SST
SST SEND IMALI D N Send Imali done on SST
SST EFT TRANSFER D / C / RD
/ RC N
Transfer of funds between accounts
linked to a profile done via a self-
service terminal
SWIFT BALANCE D / C N
Balance on the account of the client
using a standard SWIFT message ie
MT941
SWIFT DEPOSIT C / RC N Credit on the account of the client
received via a SWIFT message
SWIFT PAYMENT D / RD N Debit on the account of the client
received via a SWIFT message
TELEPHONE
BANKING EFT DEPOSIT C N Any credit to the account of the
client done via telephone banking
TELEPHONE
BANKING EFT PAYMENT D N Any debit to the account of the client
done via telephone banking
TELEPHONE
BANKING PREPAID D N
Prepaid airtime, prepaid electricity
and lotto purchases telephone
banking
TELEPHONE
BANKING PREPAID AIRTIME D N Prepaid airtime purchase on
telephone banking
TELEPHONE
BANKING
PREPAID
ELECTRICITY D N Prepaid electricity purchase on
telephone banking
TELEPHONE
BANKING LOTTO D N Lotto purchase on telephone
banking
TELEPHONE
BANKING SEND IMALI D N Send Imali done on telephone
banking
TELEPHONE
BANKING EFT TRANSFER D / C / RD
/ RC N
Transfer of funds between accounts
linked to a profile done via telephone
banking
Page 61¶
TRANSACTIONAL INFORMATION | 61 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
C = Credit; RC = Reversal of Credit; D = Debit; RD = Reversal of Debit
3.9 Adding or maintaining PTI instances
PTI instances can be added or maintained electronically (for the email delivery protocol only) or via maintenance request forms submitted to the bank.
a) An administrator who has self-maintenance on NetBank Business that can set up and maintain PTI instances electronically for email delivery protocol, available on NBB under the Admin > Transaction Information Settings > Provisional Transaction Information menu items.
b) Clients who do not have NetBank Business can add or maintain instances by completing and submitting a new application or maintenance form. The following maintenance forms are available on NetBank Business or via the helpdesk:
MR5D: Profile settings
To add the PTI product to an existing profile.
MRTIPTI1: Add Nedbank account same legal entity
Add a same legal entity account on to your existing PTI instances. Please note, an account has to be on your profile before it can be added to an instance. If the requested accounts are currently not on your profile it will be added to your profile.
MRTIPTI2: Add Nedbank account other legal entity
Add another legal entity account on to your existing PTI instances. Please note, an account has to be on your profile before it can be added to an instance. If the requested accounts are currently not on your profile, a participant resolution or power of attorney will be required.
MRTIPTI5A: Add Provisional Transaction Information instance
Add a new PTI instance to an existing profile for email or SWIFT protocols only. This form can only be used, if the PTI product is already activated on the profile. To activate the product please complete the MR5D. For all other protocols please speak to your transactional banker.
Page 62¶
62| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
MRTIPTI5B: Amend /Delete Provisional Transaction Information instance
To amend the settings or delete an existing PTI instance. Please note you cannot amend / delete accounts, delivery protocol or templates on existing instances using this maintenance request. You will need to complete the MRTIPTI8 to delete an account. To update protocols or templates, please speak to your transactional banker.
MRTIPTI6: Charge detail amendment
To amend your nominated charge accounts for the PTI product.
MRTIPTI8: Delete accounts from Provisional Transaction Information instances
To delete accounts from existing instances. Please note it will not be deleted off your profile. If it is the only account linked to the existing instance, the instance will be systematically deleted.
c) Maintenance Forms can be submitted to Nitro in the following ways:
Fax: 0860 110 782 Only Tiff, Tif or PDF files will be processed
E-Mail:
Transactionalbankingmaintenance@nedbank.co.za
- Only Tiff, Tif or PDF files will be processed
- There must be an attachment
- If no valid attachments are found in the email then the email is rejected and a mail is sent to the sender to notify them that no valid attachments were found 3.10 Pricing Refer to section 1.10 in the manual.
3.11 Frequently Asked Questions (FAQ)
Q: What is a provisional transaction information instance? A: A provisional transaction information instance is a grouping of accounts, preferences, and recipients. You can setup 9999 different Notification instances on a single profile.
Q: How many instances can be setup on a profile? A: You can setup 9999 different PTI instances on a single profile.
Q: How many recipients can I have on each instance? A: You can add up to 10 email recipients on an instance
Page 63¶
TRANSACTIONAL INFORMATION | 63 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Q: What delivery methods are available for PTI on NetBank Business? A: Provisional transaction information is available via email on NetBank Business and can be sent in real time and/or near real time.
Q: Is pricing Volume Based? A: Yes, pricing can be tiered but pricing needs to be discussed with your transactional banker. 4 Final Transaction Information (FTI)
4.1 What is the FTI solution?
The Final Transaction Information (FTI) service offers you a statement in a machine -readable format of confirmed financial transactions that have been processed through your current or savings accounts. These confirmed transactions are extracted from your accounts, formatted and delivered to you as per your selected preferences. This file can be integrated directly into your line of business system allowing you the ability to automate the reconciliation of your bank statement.
Example: you will receive a file between 3am and 8am (client preference) of all confirmed
financial transactions for the previous day, allowing your system to complete the ba nk recon
and create an exception file of un-reconcilable items before your next business day starts.
4.2 Key features of FTI
A. Push of transactions
Daily confirmed transactions are pushed directly into your LOB systems using a secure delivery method (protocol).
B. Ease of reconciliation
Your LOB system extracts any relevant data for automated reconciliation process. Exception items can then be dealt with separately (eg where a reference used is not aligned with the formatting in your LOB system).
Page 64¶
64| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
C. Multiple accounts
You can choose to receive one FTI file containing confirmed transactions for multiple accounts.
D. Delivery methods
You can choose between the following delivery methods: Email Web Services IBM MQ SWIFT SFTP Connect: Direct SWIFT FileAct
E. Frequency of file delivery
You can choose to receive a file: Daily Weekly Monthly
F. FTI file runs
In addition you can choose to receive files:
In the morning, containing all confirmed transactions for the previous day
including the transactions processed overnight, ie 'normal run'
In the afternoon, containing all confirmed transactions for the previous day
including transactions processed late, ie 'final run'
Or both,
one file sent in the morning, containing all confirmed transactions for the
previous day including the transactions processed overnight, ie 'normal
run'
one file sent in the afternoon, containing all confirmed transactions
processed late and back dated. This file will only contain the transactions
that were not included in the morning file , i.e. 'final run'.
G. File format
Multiple file formats are available eg SWIFT MT940, MT950 Please contact your Transactional Banker for available formats.
Page 65¶
TRANSACTIONAL INFORMATION | 65 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only H. File resend
FTI has the ability to resend a file, once a day, to either the same delivery settings or to the alternate email address which was set up on the FTI instance.
I. Time preference
You can define the timeframe during which you want to receive FTI Transaction Information: Normal Run - between 02:00 and 08:00 Final Run - between 14:00 and 20:00
J. Empty file
You can choose to receive and empty file, which means, should there be no activity on your account from the time of your last file, you will receive an empty file.
K. FTI Instances
An instance is a grouping of accounts and preferences. You have the option of setting up multiple instances to receive FTI. These Instances can be customised to receive data on specific accounts sent to specific delivery protocols.
Example: You can setup an instance and name it 'Host FTI'. This instance can then be customised to deliver Final Transaction Information via one of the Host delivery methods. A second instance can be setup and name it 'Email FTI'. This instance can be setup to receive Final Transaction Information via Email.
L. Adding new or maintaining FTI Instances
An Administrator who has self-maintenance on NetBank Business (NBB) can setup Final Transaction Information Instances. Should you choose to set up an instance on NBB, you can only select Email as your Delivery method. For all Host delivery methods, you may contact your Transactional Banker for assistance. If you don't have NBB, you may contact your Transactional Banker for assistance in adding or maintaining your instances.
Page 66¶
66| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
4.3 Statement number
A. Single statement number Each FTI file you receive will contain a single statement number per account. The statement numbers will start at 000001 and increment by 1 for every file sent. The statement number will reset every year ie, the first FTI file you receive in the New Year will start at 000001.
B. Nedbank CASA statement number
A new statement number is generated on the statement cycle date and / or for every 20
transactions processed on your account. The FTI file you receive will contain the
statement number as per your official bank statement ie, the statement numbers will
correspond with the final statements you view on NetBank Business or your e-
statements.
4.4 Benefits of FTI to your business
A. Improved reconciliation
Improved and timely reconciliation can be done.
B. Secure data transfer
Data is sent securely via a host connectivity protocol or encrypted email.
C. Direct FTI file
The FTI files are sent directly to your LOB system to minimise human intervention.
4.5 Benefits of Notifications to your business
This solution creates great value for your business by offering you the following benefits:
Enabling you to make informed decisions about your day-to-day operations
Reconciling your bank statements
Transaction tracking
Working capital management / forecasting
Inventory control / Goods dispatching
Fraud prevention / management
FTI sent directly to your line-of-business system
Greater customer satisfaction with the service rendered by you
Page 67¶
TRANSACTIONAL INFORMATION | 67 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
4.6 Delivery protocol
Final transactions can be delivered by using a near real time delivery protocol.
The following near real time delivery protocols are available for FTI:
Email (only delivery protocol available on NetBank Business) SFTP (Host to host solution) Connect: Direct (Host to host solution) Swift FileAct (Host to host solution) See section 1.8 for more detail.
Note: Nedbank will only be able to connect to a public IP addresses. 4.7 FTI Template groups
A template groups contain a selection of templates that make a logical fit into a specific group eg any SWIFT proprietary template will be available under the SWIFT group. Currently the following groups are available:
Nedbank
SWIFT
SAP
Other
Client Specific
a) Available templates
Near real time
- TI FTI XML
- TI FTI CSV
- TI FTI TXT
- NedAcad 4 digit statement - 29 character statement narrative
- NedAcad 6 digit statement - 27 character statement narrative
- NedAcad 6 digit statement - 30 character statement narrative
- NedAcad 4 digit single statement - 29 character statement narrative
- NedAcad 6 digit single statement - 27 character statement narrative
- NedAcad 6 digit single statement - 30 character statement narrative
- TI SWIFT MT940
- TI SWIFT MT950
- NED SWIFT MT940
- NED SWIFT MT950
- TI SWIFT MX940 - camt.053 (Bank to customer statement)
- TI SWIFT MX950 - camt.053 (Bank to customer statement)
Page 68¶
68| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
- Multicash AUSZUG
- Multicash UMSATZ
Refer to 1.12 and Appendix B, D and E for detailed information on F TI templates
Note: If SWIFT has been selected as a delivery protocol only the SWIFT templates can be selected, however SWIFT templates can be sent on all delivery protocols.
Page 69¶
TRANSACTIONAL INFORMATION | 69 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only 4.8 Transaction codes Transaction Codes.xlsx
Transaction
code
NedAcad
Transaction
code
C / D /
RC / RD
Indicator
Vat
Applicable
ENC
Applicable
(Uncleared
funds)
Description
1301 101 C N Y
Cheque or Mixed Deposit
Note: Non cash amount will
accrue to effects not cleared
1302 102 C N N Cheque payment reversed
1303 103 C N N Interest Paid
1306 106 C / RC N N
Reversal of a Debit
transaction (Stop orders,
auto transfers and cheque
recall)
Note: Insufficient funds may
attract an unpaid fee
1308 108 C N N Dividends or Stock or Share
payments made by Nedbank
1309 109 C N Y
Auto Transfer into your
account from another
Nedbank account subject to
ENCs
1310 110 C N N
Your cheque has been
unpaid due to various
reasons or Cheque deposits
greater than industry
regulated amounts
authorised by the bank
Note: Need to check your
narrative for additional
information
Can be accompanied by an
unpaid fee
1311 111 C N N Cleared funds for cheque
deposits
1313 113 C N N Interest paid on investments
held at Nedbank
1316 116 C / RC N N
Reversal of POS transaction
or credit for prepaid
vouchers
1317 117 C / RC N N
Reversal of a Teller Debit
Transaction
Note: Need to check your
narrative for further
information
1318 118 C N N Payment of Investment at
maturity held with Nedbank
1319 119 C N N Electronic deposit
1321 121 C N N Cash Management transfers
1322 122 C N N Interest on investment
1323 123 C N N Stop order credit into your
account
1324 124 C N N
Electronic deposit into your
account from another bank
ie interbank EFT
1325 125 C N Y Additional cash or cheque
deposit that was not on the
Page 70¶
70| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
original deposit slip
1326 126 C N N
Cleared Cheque deposit ie
is not included in ENCs.
Usually used for Salary and
Pension Payments
1327 127 C / RC Y N
Reversal of Bank Charges
Note: It will also reverse the
VAT impact ie reduce your
VAT declaration
1329 129 C N N
Unpaid debit order.
Note: Insufficient funds may
attract an unpaid fee
1330 130 C / RC N N
Reversal of SASWITCH
cash withdrawal or send
iMali transactions if the cash
is not redeemed within 7
days
1336 136 C N N
Merchant settlement for
POS devices or movement
of funds from a card account
to your transactional account
1340 140 C N N
Used when net service fee is
set of against credit interest
paid (1923 = 2 on ACMC)
1342 142 C N N
Auto Transfer into your
account from another
Nedbank account not
subject to ENCs
1344,1345 144, 145 C / RC N N Reversal of a card purchase
1351 151 C N N Cash Deposit
1352 152 C N N
Electronic deposit
processed into your account
by Nedbank
1353 153 C N N Interest paid on Cash
Management
1359 159 C / RC N N ATM Reversal
1361 161 C Y Y Manual credit by bank check
narritive
1364 164 C N N Electronic deposit
1365 165 C N N Electronic deposit for Salary
1366 166 C N N Cash Management sweeps
1390 190 C N N Cash Deposit (Using a
Nedmatic Card at Teller)
1392 192 C N Y Uncleared deposit
1394 194 C N EFT Credit transferred from
or into a closed account
1395 195 C N N EFT Credit into your account
eg SWIFT and RTGS
1398 198 C N
Y (zero
amount so no
impact)
Non-financial information
line on your statement
1335 ,1337
,1338, 1341,
1355, 1367,
1369 - 1380,
1385 - 1389,
1391, 1396,
1399
135,137,138,
141,155, 167,
185 to 189,
191, 196, 199
C N Y
Manual Credit into your
account processed by the
bank
Note: Need to check your
narrative for further
information
1304, 1305,
1307, 1312,
1314, 1315,
1320,1328,
1331 to 1334,
104,105,107, 112,114,115,1 20 C N N Manual Credit into your account processed by the bank Note: Need to check your narrative for further
Page 71¶
TRANSACTIONAL INFORMATION | 71 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
1339, 1343,
1346 to 1350,
1354, 1356 to
1358, 1360,
1362, 1363,
1368, 1381 to
1384,
1393, 1397
128,131 to
134,
139, 143,
146 to 150,
154, 156 to
158,
160, 162, 163,
168, 181 to
184,
193, 197
information
1401 201 D N N Electronic Debit (SWIFT
payment eg RTGS)
1402 202 D N N Cheque Drawn or Encashed
1403 203 D N N EFT Payment or Transfer
1404 204 D N N
Account Debit Interest on
authorised overdrafts or
excess balances
1405 205 D Y N Bank generated Service fee
1406 206 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1407 207 D Y N Bank generated Service fee
1408 208 D N N Stop order
1409 209 D N N Unpaid cheques and
returned debit orders
1410 210 D / RD N N Reversal
1411 211 D N N
Authorised item ie, forced
debit to your account if
initially rejected due to an
account status
1413 213 D Y N Bank fee for cheque book
1415 215 D Y N Bank fee for Safe Custody
1416 216 D N N POS purchase and/or POS
cash withdrawal
1419 219 D N N
Electronic Transfer ie
payment from a Nedbank
account to another Nedbank
account on the same profile
1420 220 D N N ATM card withdrawal
1421 221 D N N Debit order (Internal)
1422 222 D Y N Bank Fee for deposit book
1423 223 D N N Stop order
1424 , 1425 224, 225 D Y N Debit order (External)
1426 226 D N N
Shortfall cash or cheque
deposit that was not on the
original deposit slip
1427 227 D Y N Bank fee
1428 228 D N N Bank fee to recover legal
costs
1429 229 D / RD N N Reversal of a debit order
collection
1430 230 D N N
Cheque payment greater
than industry regulated
amounts authorised by the
bank
1431 231 D N N
Purchase of Forex. Outward
telegraphic transfers
(Electronic Payment from
South Africa to another
monetary area)
Page 72¶
72| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
1433 233 D N N EFT Debit transferred from
or into a closed account
1435 235 D Y N Bank fee for Cash deposits
1436 236 D N N POS purchase
1437 237 D N N Electronic debit processed
by the bank
1438 238 D N N Stop order reversal
1439 239 D N N Unpaid cheque due to
technical reasons
1440 240 D Y N Bank Charge for setoff
against interest if applicable
1441 241 D N N Debit order (internal)
1442 242 D N N
Automatic Transfer of funds
between accounts
Debit order for Nedfleet
1443 243 D Y N Bank charge for overdraft
facilities
1444 244 D N N
Unpaid cheque due to
technical reason (Non-
transferable)
1445 245 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1446 246 D N N
Internal debit order
processed by Nedbank
Vehicle Asset Finance(VAF)
or fleet management
Note: This trancode is only
posted in final run
1447 247 D N N
Correction of overstated
cheque deposit
Note: Compare the credit
trancode for a understated
cheque deposit
1450 250 D / RD N N
Reversal of Teller Cash
Deposit
Reversal of CPS debit order
collections
1451 251 D N N
Cash Withdrawals and
Banks own cheque
Teller Transfer (From any
Nedbank account to any
Nedbank account
irrespective of product eg
CASA to credit card)
1452 252 D N N
Electronic payment or
transfer into a Nedbank
home loan, Vehicle Asset
Finance (VAF) or investment
account
1454 254 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1455 255 D / RD N N
Reversal of a cheque
deposit due to physical
cheque not being present or
if the code line of cheque
failing validation
1456 256 D N N
Debit interest posted by
current accounts when
account moves into
Page 73¶
TRANSACTIONAL INFORMATION | 73 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Cashman
1457, 1476,
1492, 1497
257, 276, 292,
297 D Y N Bank Fees
1460 260 D N N Debit order (Internal)
1461 261 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1463 263 D N N Transfer to a Justsave
account
1464,1465 264, 265 D N N Electronic payment
1466 266 D N N Cash management auto
transfer
1468 268 D N N Debit order (External)
1469 269 D N N Unpaid Cheque (Technical
reason - post-dated)
1473 273 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1476 276 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1479 279 D N N Bank Fee (VAT exempt -
currency conversion fee)
1481 281 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1485 285 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1486 286 D Y N Bank Fee for unpaids
1487 287 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1490 290 D N N Cash withdrawal with
Nedmatic card
1491 291 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1492 292 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1493 293 D N N Debit order (External
AEDOS)
1495 295 D N N Prepaid Purchase
(cellphone top-ups at ATM)
1496 296 D Y N
Manual debit processed by
the bank.
Note: Need to check your
Page 74¶
74| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
narrative for further
information
1497 297 D Y N
Manual debit processed by
the bank.
Note: Need to check your
narrative for further
information
1498 298 D N N Interest paid (Debited from
Cash Management)
1412, 1414,
1417, 1418,
1432, 1434,
1445, 1448,
1449, 1453,
1454,
1458,1459,14
61 1462,
1470 to 1475,
1477, 1478,
1480 to 1485,
1487 to 1489,
1491, 1494,
1496, 1499
212, 214, 217,
218, 232, 234,
245, 248, 249,
253, 254,
258,259,
261,262,
270 to 275,
277, 278, 280
to 285,
287 to 289,
291, 294, 296,
299
D N N
Manual Debit processed on
your account by the bank
Note: Need to check your
narrative for further
information
C = Credit; RC = Reversal of Credit; D = Debit; RD = Reversal of Debit
4.9 Adding or maintaining FTI instances
FTI instances can be added or maintained electronically (for the email delivery protocol only) or via maintenance request forms submitted to the bank. a) An administrator who has self-maintenance on NetBank Business that can set up and maintain FTI instances electronically for email delivery protocol, available on NBB under the Admin > Transaction Information Settings > Final Transaction Information menu items.
b) Clients who do not have NetBank Business can add or maintain instances by completing and submitting a new application or maintenance form. The following maintenance forms are available on NetBank Business or via the helpdesk:
MR5D: Profile settings
To add the FTI product to an existing profile.
MRTIFTI1: Add Nedbank account same legal entity
Add a same legal entity account on to your existing FTI instances. Please note, an account has to be on your profile before it can be added to an instance. If the requested accounts are currently not on your profile it will be added to your profile.
MRTIFTI2: Add Nedbank account other legal entity
Add another legal entity account on to your existing FTI instances. Please note, an account has to be on your profile before it can be added to an instance. If the requested accounts are currently not on your profile, a participant resolution or power of attorney will be required.
Page 75¶
TRANSACTIONAL INFORMATION | 75 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
MRTIPTI5A: Add Final Transaction Information instance
Add a new FTI instance to an existing profile for email or SWIFT protocols only. This form can only be used, if the FTI product is already activated on the profile. To activate the product please complete the MR5D. For all other protocols please speak to your transactional banker.
MRTIFTI5B: Amend /Delete Final Transaction Information instance
To amend the settings or delete an existing FTI instance. Please note you cannot amend / delete accounts, delivery protocol or templates on existing instances using this maintenance request. You will need to complete the MRTIFTI8 to delete an account. To update protocols or templates, please speak to your transactional banker.
MRTIFTI6: Charge detail amendment
To amend your nominated charge accounts for the FTI product.
MRTIFTI8: Delete accounts from Final Transaction Information instances
To delete accounts from existing instances. Please note it will not be deleted off your profile. If it is the only account linked to the existing instance, the instance will be systematically deleted.
c) Maintenance Forms can be submitted to Nitro in the following ways:
Fax: 0860 110 782
Only Tiff, Tif or PDF files will be processed
E-Mail:
Transactionalbankingmaintenance@nedbank.co.za
- Only Tiff, Tif or PDF files will be processed
- There must be an attachment
- If no valid attachments are found in the email then the email is rejected and a mail is sent to the sender to notify them that no valid attachments were found
4.10 Pricing Refer to section 1.10 in the manual.
Page 76¶
76| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
4.11 Frequently Asked Questions (FAQ)
Q: How many instances can be setup on a profile? A: You can setup 9999 different FTI instances on a single profile.
Q: How many recipients can I have on each instance? A: You can add up to 10 recipients on an instance.
Q: Is pricing Volume Based? A: Yes, pricing can be tiered but pricing needs to be discussed with your transactional banker. 5 Images on demand (IOD)
5.1 What is Images on demand?
The Images On Demand (IOD) solution will deliver images of cheques, cash slips and/or deposit slips, processed through your current or savings accounts. These images can be delivered directly to your LOB on a secure host protocol or via email. These images are indexed which will allow you to build your own image viewer or image sear ch functionality on your LOB system. Alternatively, you can select to use the image viewer provided by Nedbank.
IOD can assist you with;
Bank account reconciliation ie, the additional information (eg contact number of the
depositor) available on the image can help you to identify irreconcilable cash or cheque
transactions.
Risk mitigation ie, you will be receiving the image directly from the bank, removing the
risk of dispatching goods or services based on fraudulent / altered deposit slip.
Controlling access to your bank statements ie, images can be sent to your employees
so that they can make the relevant operational decisions. Your employees do not need
access to your bank accounts.
Improving operational processes ie, employees are no longer require d to contact the
bank to verify the validity of a cheque or cash deposit.
5.2 Key features of IOD
A. Image Viewer
Nedbank will provide you with an Image viewer to enable you to view the images sent.
B. Search images
You can search for images using either the amount of reference (narrative) on the deposit or cheque as your search criteria.
C. Types of images
Page 77¶
TRANSACTIONAL INFORMATION | 77 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only You have the option to receive the following images:
Cheques only or Deposit slips only or Deposit slips and associated cheques and/or cash slips
When selecting "Deposit slips only" or "Deposit slips plus associated cheques and/or cash slips" you have the following options to choose from:
All deposits or Cash deposits only or Mixed deposits/cheque deposits
D. Delivery methods
You can choose from among the following delivery methods:
Email SFTP Connect: Direct Swift FileAct
E. File delivery frequency
IOD files are sent daily.
F. Time preference
IOD files can be sent between 15:00 and 22:00, you have the option to choose a time ie 15:00, 16:00, 17:00, etc.
G. IOD Instances
An instance is a grouping of accounts and preferences. You have the ability to setup multiple instances to receive images. These instances can be customised to receive images on specific accounts, sent via specific delivery methods.
Example: You can set up an instance and name it "Host IOD". This instance can then be customised to images via one of the Host delivery methods. A second instance can be set up and name it "Email IOD". This instance can be setup to receive Images via Email.
Page 78¶
78| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
H. Adding new or maintaining IOD Instances
An Administrator who has client self-maintenance on NetBank Business (NBB) can setup IOD instances. You can however only select email as your delivery method if you choose to setup an instance on NBB. For all Host delivery methods, you may contact your Transactional Banker for assistance.
If you do not have NBB, you may contact your Transactional Banker for assistance in adding or maintaining your instances. 5.3 IOD file naming convention
An IOD file, used for the near real time delivery protocols, contains multiple images of deposit slips and associated cheques and/or cash slips. These images will be zipped into a single zip file. This file will have the following naming convention.
Example: PNGG00.CDTIPK.A13O P678.EN0610.I1 234C.ZIP
Field numbers Data Element Valid
Values Description Notes
1 2 3 4 5 6
Applicable
environment
QNGG00
PNGG00
Q = Test
environment
P = Production
environment
These are standard
fields and cannot be
amended
Field 1 - 4 are
alpha
Field 5 and 6 are
numeric ie zero,
zero
P N G G 0 0
7
Separator . To separate data
elements
The full stop
cannot be
replaced with a
comma as the
file validation will
fail
.
8 9 10 11 12 13 Product
environment CDTIPK
To identify the file as
a Transaction
Information product
C D T I P K
14
Separator . To separate data
elements
The full stop
cannot be
replaced with a
comma as the
file validation will
fail
.
15 16 17
Client Prefix
Please refer
to
description
Field 15:Only alpha
character are valid
Field 16 and 17:
Only alpha or
numeric characters
are valid
To identify the
client to whom
the file will be
delivered. This
prefix will be
issued by
Nedbank
A 1 3
18
Input / Output
indicator
O = Output
I = Input
Only the specified alphanumeric characters are valid
O = When you
receive a file
from Nedbank
I = When you
send the file
back to Nedbank
eg this will only
be applicable if
you use a
delivery protocol
that has the
capability for file
acknowledgeme
nt
O
Page 79¶
TRANSACTIONAL INFORMATION | 79 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only Example: PNGG00.CDTIPK.A13O P678.EN0610.I1234 C.ZIP
Field numbers Data Element Valid
Values Description Notes
19
Product ID
N =
Notifications
P = PTI
I = IOD
F = FTI
R = IR
Only specified
alphanumeric
characters are valid
To identify which
product you are
receiving the file
for P
20 21 22
File sequence
numbers 001 to 999
These fields
represent the file's
sequential numbers
and will be numeric
It will be
sequentially
incremented by
1 for every file
sent for that day.
The number is
reset to 001 the
next day at
midnight
6 7 8
23
Separator . To separate data
elements
The full stop
cannot be
replaced with a
comma as the
file validation will
fail
.
24
File type
D = Data file
and
E = End of
day file
Only the specified
alpha characters are
valid
E = End of day
file is applicable
to the PTI end of
day file only E
25
Resend
indicator
R = Resend
N = Normal
Only the specified
alpha characters are
valid
If you receive a
file with a R
value in the field
the system must
not automatically
process the file
N
26 27
Day indicator 01 to 31 Only numeric
characters are valid
DD = Indicates day of the month that the file was created and does not indicate the date of the transactions
0 6 28 29 Month indicator 01 to 12 Only numeric characters are valid MM = Indicates the month of the year that file was created and does not indicate the date of the transactions
1 0 30 Separator . To separate data elements The full stop cannot be replaced with a comma as the file validation will fail . 31 Instance ID I = Instance Only the specified alpha character is valid
I
32 33 34 35
Instance
number
0001 to
9999
Each TI product can
have up to 9999
instances per profile
An instance is a
grouping of your
accounts,
settings and
delivery protocol
eg Instance
0001 account1
selected -
settings 'credits
only' and
delivered via
email
1 2 3 4
Page 80¶
80| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Example: PNGG00.CDTIPK.A13OP678.EN0610.I1234 C.ZIP
Field numbers Data Element Valid
Values Description Notes
36
Protocol ID
C =
Connect:
Direct
E= Email
S = Swift
W = Web
Services
M = IBM MQ
A = FileAct
F = FTP
P = SFTP
Q = IBM MQ
FTP
Only the specified
alpha characters are
valid
This is the
delivery protocol
selected for this
instance. Please
note if the file is
resent to the
alternative email
address the file
name will
contain the
original protocol
ID and not the
email ID
C
37
Separator . To separate data
elements
The full stop
cannot be
replaced with a
comma as the
file validation will
fail .
38 39 40
Compressed
file zip
Only the specified
alpha characters are
valid in fields 38, 39
and 40.
ZIP is a format
that compresses
large files
allowing them to
be sent more
conveniently
over the
Internet. Files
that are zipped
will end with a
.zip extension.
When you open
a zipped file or
"unzip" it, you
will often find
that multiple files
have been
compressed into
a single zip file.
An example of
this would be if
you wanted to
send a large
number of
images to
someone and
you compressed
all of the images
into a single zip
file.
Z I P
Note: If you happen to get an error message when you attempt to open or extract the zip file then you should report the problem to your local IT staff. Chances are that you do not have a WinZip program loaded on your computer and they can remedy this problem fairly easily.
Page 81¶
TRANSACTIONAL INFORMATION | 81 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only 5.4 Benefits of IOD to your business
A. Identify transactions
Identify cash and cheque payments by the additional information that is available on the deposit slips and cheques. This will assist you in allocating funds which previously would have been in a suspense account.
B. Images for branches
Give your staff at branches access to the images of cash and cheque deposits, without having to give them access to your statements. This means they will not have sight of the balances in your accounts or any additional transactions processed.
C. Secure data transfer
Data is sent securely via a host connectivity protocol or email.
D. Direct IOD file
IOD file can be sent directly to your Line of business (LOB) system to enable you to view the images on your systems. This means these images can be easily retrieved in future, and won't deteriorate over time, as paper images do.
E. Access to images
Upload images to a central point in your environment and allow multiple users to view the images using the Image viewer provided by Nedbank.
5.5 Adding or maintaining IOD instances
IOD instances can be added or maintained electronically (for the email delivery protocol only) or via maintenance request forms submitted to the bank.
a) An administrator who has self-maintenance on NetBank Business that can set up and maintain IOD instances electronically for email delivery protocol, available on NBB under the Admin > Transaction Information Settings > Images on Demand menu items.
b) Clients who do not have NetBank Business can add or maintain instances by completing and submitting a new application or maintenance form. The following maintenance forms are available on NetBank Business or via the helpdesk:
MR5D: Profile settings
To add the IOD product to an existing profile.
MRTIIOD1: Add Nedbank account same legal entity
Add a same legal entity account on to your existing IOD instances. Please note, an account has to be on your profile before it can be added to an instance. If the requested accounts are currently not on your profile it will be added to your profile.
Page 82¶
82| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
MRTIOD2: Add Nedbank account other legal entity
Add another legal entity account on to your existing IOD instances. Please note, an account has to be on your profile before it can be added to an instance. If the requested accounts are currently not on your profile, a participant resolution or power of attorney will be required.
MRTIIOD5A: Add Images on Demand instance
Add a new IOD instance to an existing profile for email protocol only. This form can only be used, if the IOD product is already activated on the profile. To activate the product please complete the MR5D. For all other protocols please speak to your transactional banker.
MRTIIOD5B: Amend /Delete Images on Demand instance
To amend the settings or delete an existing IOD instance. Please note you cannot amend / delete accounts or delivery protocol on existing instances using this maintenance request. You will need to complete the MRTIIOD8 to delete an account. To update delivery protocols, please speak to your transactional banker.
MRTIIOD6: Charge detail amendment
To amend your nominated charge accounts for the IOD product.
MRTIIOD8: Delete accounts from Images on Demand instances
To delete accounts from existing instances. Please note it will not be deleted off your profile. If it is the only account linked to the existing instance, the instance will be systematically deleted.
c) Maintenance Forms can be submitted to Nitro in the following ways:
Fax: 0860 110 782
Only Tiff, Tif or PDF files will be processed
E-Mail:
Transactionalbankingmaintenance@nedbank.co.za
- Only Tiff, Tif or PDF files will be processed
- There must be an attachment
- If no valid attachments are found in the email then the email is rejected and a mail is sent to the sender to notify them that no valid attachments were found
Page 83¶
TRANSACTIONAL INFORMATION | 83 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
5.6 Pricing
Refer to section 1.10 in the manual.
5.7 Frequently Asked Questions (FAQ)
Q: What is an IOD instance?
A: An instance is a grouping of accounts and preferences. You have the option of setting
up multiple instances to receive IOD. These instances can be customised to receive
data on specific accounts sent to specific delivery protocols.
Q: How many instances can be setup on a profile? A: You can setup 9999 different IOD instances on a single profile.
Q: How many recipients can I have on each instance? A: You can add up to 10 recipients on an instance.
Q: Is pricing Volume Based? A: Yes, pricing can be tiered but pricing needs to be discussed with your transactional banker.
Page 84¶
84| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Appendix A 6 Appendix A - PTI Templates
6.1 Near real time templates
6.1.1 PTI XML (NRT) Template 1
Herewith the layout for the standard XML transaction feeds for near real time:
TI PTI XML (NRT) field lengths are variable and indicated below are maximum lengths
XML Tag name Data type Expected
Maximum size Description Sample
value
PTI
1234
HEADER
(Example)
TI PTI XML (NRT) field lengths are variable and indicated below are maximum lengths
XML Tag name Data Type Expected
Maximum size Description Sample
value
Alpha N/A Start of XML body N/A
Page 85¶
TRANSACTIONAL INFORMATION | 85 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
transaction.
INTERNET
BANKING
C=Credit, RD=Reversal
of Debit,
RC=Reversal of Credit
RD
Numeric 16.2 Actual account balance
plus account overdraft limit less any uncleared funds
635406.46Alpha Numeric 30 Statement description / narrative NarrText 0899
Alpha End of XML body
BODY
(Example)
Page 86¶
86| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
141.11
TI PTI XML (NRT) field lengths are variable and indicated below are maximum lengths
XML Tag name Data type Expected
Maximum size Description Sample
value
FOOTER
(Example)
PTI XML layout - near real time.txt
Sample file layout
Page 87¶
TRANSACTIONAL INFORMATION | 87 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
6.1.2 PTI CSV (NRT) Template 1 Herewith the layout for the standard Nedbank format for CSV and Excel transaction feeds for PTI and FTI:
TI PTI CSV (NRT) 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" Date Numeric 8 Displays the date on which the file is being sent. CCYYMMDD 20140916
HEADER
(Example)
1234,30000000014,"Product",1234,"ADMIN",20130130
TI PTI CSV (NRT) field lengths are variable and indicated below are maximum lengths
CSV Field name Data Type Expected
Maximum size Description Sample
value
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
Page 88¶
88| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
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 e.g.
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 e.g. 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 -
CCYYMMDD
20140916
Time Alpha Numeric 11
Time at which the
provisional transaction
was processed to the
account. Format -
HH:MM:SS:ss
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"
BODY
(Example)
1,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,"C Deposit","INTERNET
BANKING",141.11,"D",20130916,12:37:28:33,622000.54,635406.46,"NarrText 0899"
1234565781,0001,1200,0012,1234567890,"Cash
","N/A",1000.00,"D",20130130,00:00:00:00,1002.00,1001.00,"Deposit/EFT narrative"
Page 89¶
TRANSACTIONAL INFORMATION | 89 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
TI PTI CSV (NRT) field lengths are variable and indicated below are maximum lengths
CSV Field name Data type Expected
Maximum size Description Sample
value
Record Count Numeric 18
Number of TI records in
the file i.e. excluding
header and footer
FOOTER
(Example)
3
PTI CSV (NRT) Template 1.txt
Sample file layout
1234,30000000014,"Product",1234,"ADMIN",20130130 1,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,"C Deposit","INTERNET BANKING",141.11,"D",20130916,12:37:28:33,622000.54,635406.46,"NarrText 0899" 1234565781,0001,1200,0012,1234567890,"Cash ","N/A",1000.00,"D",20130130,00:00:00:00,1002.00,1001.00,"Deposit/EFT narrative" 3
Page 90¶
90| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
6.1.3 PTI CSV (NRT) Template 2 Herewith the layout for the standard Nedbank format for CSV and Excel transaction feeds for PTI, with record identifiers and with balance information:
PTI CSV (NRT) Template 2 field lengths are variable and indicated below are maximum lengths.
FILE HEADER RECORD CSV Field name Data type Expected maximum size Description Record Identifier Numeric 2 Record will start with "01" to indicate file header record CIS Number Numeric 12 Unique client number issued by Nedbank Profile Number Numeric 10 Profile number on which the PTI product is setup Product Alpha Numeric 10 Will contain the value PTI to indicate it is a provisional transaction file Instance Number Numeric 4 You can load up to 9999 different instances per profile. An instance is a group of accounts, settings and destination Instance Name
Alpha Numeric 30 Instance name as specified by the client will always be displayed with quotation marks Date Numeric 8 Displays the date on which the file is being sent. CCYYMMDD
ACCOUNT HEADER RECORD CSV Field name Data type Actual field length Description Record Identifier Numeric 2 Record will start with "02" to indicate Account header record
Account
Numeric 23 The transactions that follow are for this account
Page 91¶
TRANSACTIONAL INFORMATION | 91 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
TRANSACTION DETAIL RECORD
CSV Field name Data
Type
Expected
Maximum
size
Description
Record Identifier Numeric 2 Record will start with "03" to indicate
transaction detail record
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
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.
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.
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
Account Numeric 23 The account number on which the
transaction was processed.
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
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
Amount Numeric 16.2 The amount of the transaction
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
Date Numeric 8
The date on which the transaction was
processed to the account. Format -
CCYYMMDD
Time Alpha
Numeric 11
Time at which the provisional transaction
was processed to the account. Format -
HH:MM:SS:ss
Account Book Balance Numeric 16.2
Actual account balance including any
uncleared funds (eg cheque deposits -7
days clearance).
Account Available Balance Numeric 16.2 Actual account balance plus account
overdraft limit, less any uncleared funds
User Ref Alpha
Numeric 30 Statement description / narrative will
always be displayed in quotation marks
Page 92¶
92| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
ACCOUNT FOOTER RECORD CSV Field name Data type Actual field length Description Record Identifier Numeric 2 Record will start with "04" to indicate account footer record
Account
Numeric 23 The transaction reported are for this account Transaction Record Count Numeric 18 Number of transaction records reported for the account above
FILE FOOTER RECORD
CSV Field name Data
type
Expected
Maximum
size
Description
Record Identifier Numeric 2 Record will start with "04" to indicate File
footer record
Account Record Count Numeric 18 Number of accounts reported in this file
Transaction Record Count Numeric 18 Total number of transaction records reported in this file for all accounts PTI CSV (NRT) Template 2.txt
Sample file layout
01,100200001234,3000000014,"Product",1234,"ADMIN",20130130 02,1009000951 03,1,0001,1200,0012,1009000951,"Cash Deposit","INTERNET BANKING",- 141.11,"RD",20130916,12:34:28:33,622000.54,635406.46,"NarrText 0899" 03,2,0001,1200,0012,1009000951,"C Deposit","INTERNET BANKING",141.11,"D",20130916,12:37:28:33,622000.54,635406.46,"NarrText 0899" 04,1009000951,2 05,1,2
Page 93¶
TRANSACTIONAL INFORMATION | 93 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only 6.1.4 PTI CSV (NRT) Template 3 Herewith the layout for the standard Nedbank format for CSV and Excel transaction feeds for PTI, with record identifiers and without balances:
PTI CSV (NRT) Template 2 field lengths are variable and indicated below are maximum lengths
FILE HEADER RECORD CSV Field name Data type Expected maximum size Description Record Identifier Numeric 2 Record will start with "01" to indicate file header record CIS Number Numeric 12 Unique client number issued by Nedbank Profile Number Numeric 10 Profile number on which the PTI product is setup Product Alpha Numeric 10 Will contain the value PTI to indicate it is a provisional transaction file Instance Number Numeric 4 You can load up to 9999 different instances per profile. An instance is a group of accounts, settings and destination Instance Name
Alpha Numeric 30 Instance name as specified by the client will always be displayed with quotation marks Date Numeric 8 Displays the date on which the file is being sent. CCYYMMDD
ACCOUNT HEADER RECORD CSV Field name Data type Actual field length Description Record Identifier Numeric 2 Record will start with "02" to indicate Account header record
Account
Numeric 23 The transactions that follow are for this account
Page 94¶
94| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
TRANSACTION DETAIL RECORD
CSV Field name Data
Type
Expected
Maximum
size
Description
Record Identifier Numeric 2 Record will start with "03" to indicate
transaction detail record
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
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.
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.
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
Account Numeric 23 The account number on which the
transaction was processed.
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 an d
Transaction type combinations
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
Amount Numeric 16.2 The amount of the transaction
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
Date Numeric 8
The date on which the transaction was
processed to the account. Format -
CCYYMMDD
Time Alpha
Numeric 11
Time at which the provisional transaction
was processed to the account. Format -
HH:MM:SS:ss
User Ref Alpha
Numeric 30 Statement description / narrative will
always be displayed in quotation marks
ACCOUNT FOOTER RECORD CSV Field name Data type Actual field length Description Record Identifier Numeric 2 Record will start with "04" to indicate account footer record
Account
Numeric 23 The transaction reported are for this account Transaction Record Count Numeric 18 Number of transaction records reported for the account above
Page 95¶
TRANSACTIONAL INFORMATION | 95 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
FILE FOOTER RECORD
CSV Field name Data
type
Expected
Maximum
size
Description
Record Identifier Numeric 2 Record will start with "04" to indicate File
footer record
Account Record Count Numeric 18 Number of accounts reported in this file
Transaction Record Count Numeric 18 Total number of transaction records reported in this file for all accounts PTI CSV (NRT) Template 3.txt
Sample file layout
01,100200001234,3000000014,"Product",1234,"ADMIN",20130130 02,1009000951 03,1,0001,1200,0012,1009000951,"Cash Deposit","INTERNET BANKING",- 141.11,"RD",20130916,12:34:28:33,"NarrText 0899" 03,2,0001,1200,0012,1009000951,"C Deposit","INTERNET BANKING",141.11,"D",20130916,12:37:28:33,"NarrText 0899" 04,1009000951,2 05,1,2
Page 96¶
96| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
6.1.5 PTI CSV (NRT) Template 4 Herewith the layout for the standard Nedbank format for CSV and Excel transaction feeds for PTI, with record identifiers, without balances, and credit transactions only:
PTI CSV (NRT) Template 3 field lengths are variable and indicated below are maximum lengths
FILE HEADER RECORD CSV Field name Data type Expected maximum size Description Record Identifier Numeric 2 Record will start with "01" to indicate file header record CIS Number Numeric 12 Unique client number issued by Nedbank Profile Number Numeric 10 Profile number on which the PTI product is setup Product Alpha Numeric 10 Will contain the value PTI to indicate it is a provisional transaction file Instance Number Numeric 4 You can load up to 9999 different instances per profile. An instance is a group of accounts, settings and destination Instance Name
Alpha Numeric 30 Instance name as specified by the client will always be displayed with quotation marks Date Numeric 8 Displays the date on which the file is being sent. CCYYMMDD
ACCOUNT HEADER RECORD CSV Field name Data type Actual field length Description Record Identifier Numeric 2 Record will start with "02" to indicate Account header record
Account
Numeric 23 The transactions that follow are for this account
Page 97¶
TRANSACTIONAL INFORMATION | 97 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
TRANSACTION DETAIL RECORD
CSV Field name Data
Type
Expected
Maximum
size
Description
Record Identifier Numeric 2 Record will start with "03" to indicate
transaction detail record
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
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.
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.
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
Account Numeric 23 The account number on which the
transaction was processed.
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 Ch annel and
Transaction type combinations
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
Amount Numeric 16.2 The amount of the transaction
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
Date Numeric 8
The date on which the transaction was
processed to the account. Format -
CCYYMMDD
Time Alpha
Numeric 11
Time at which the provisional transaction
was processed to the account. Format -
HH:MM:SS:ss
User Ref Alpha
Numeric 30 Statement description / narrative will
always be displayed in quotation marks
ACCOUNT FOOTER RECORD CSV Field name Data type Actual field length Description Record Identifier Numeric 2 Record will start with "04" to indicate account footer record
Account
Numeric 23 The transaction reported are for this account Transaction Record Count Numeric 18 Number of transaction records reported for the account above
Page 98¶
98| TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
FILE FOOTER RECORD
CSV Field name Data
type
Expected
Maximum
size
Description
Record Identifier Numeric 2 Record will start with "04" to indicate File
footer record
Account Record Count Numeric 18 Number of accounts reported in this file
Transaction Record Count Numeric 18 Total number of transaction records reported in this file for all accounts PTI CSV (NRT) Template 3.txt
Sample file layout
01,100200001234,3000000014,"Product",1234,"ADMIN",20130130 02,1009000951 03,1,0001,1200,0012,1009000951,"Cash Deposit","INTERNET BANKING",- 141.11,"RD",20130916,12:34:28:33,"NarrText 0899" 03,2,0001,1200,0012,1009000951,"C Deposit","INTERNET BANKING",141.11,"D",20130916,12:37:28:33,"NarrText 0899" 04,1009000951,2 05,1,2
Page 99¶
TRANSACTIONAL INFORMATION | 99 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
6.1.6 PTI TXT (NRT) Template 1 Herewith the layout for the standard Nedbank format for TXT transaction feeds:
TI PTI TXT (NRT) 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 Date Numeric 8 Displays the date on which the file is being sent. CCYYMMDD 20140916
HEADER
(Example)
00000000123430000000014Product 0000001234ADMIN 00000000123430000000014Product
0000001234ADMIN20130130
Page 100¶
100 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
TI PTI TXT (NRT) field lengths are variable and indicated below are maximum lengths
TXT Field name Data Type Actual Field
Length Description Sample
value
TI Request
Alpha N/A Start of TXT body N/A
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 -
CCYYMMDD
20140916
Page 101¶
TRANSACTIONAL INFORMATION | 101 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Time Alpha Numeric 11
Time at which the
provisional transaction
was processed to the
account. Format -
HH:MM:SS:ss
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
TI Request
Alpha End of TXT body
BODY
(Example)
000000000000000100000000100000120000000001200000000000001009000951C Deposit INTERNET
BANKING -
00000000000000141.11RD2013091612:34:28:33+0000000000622000.54+0000000000635406.46NarrText 0899
000000000000000200000000100000120000000001200000000000001009000951C Deposit INTERNET
BANKING +00000000000000141.11D
2013091612:37:28:33+0000000000622000.54+0000000000635406.46NarrText 0899
000000123456578100000000100000120000000001200000000000001234567890CashN/A
+0000000000001000.00D 2013013000:00:00:00+0000000000001002.00+0000000000001001.00Deposit/EFT
narrative
TI PTI TXT (NRT) field lengths are variable and indicated below are maximum lengths
TXT Field name Data type Actual Field
Length Description Sample
value
Record Count Numeric 18
Number of TI records in
the file ie excluding
header and footer
+000000003
FOOTER
(Example)
+000000003
PTI TXT layout - near real time.txt
Fixed width length file: Record length = 1000
Page 102¶
102 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Sample file layout
00000000123430000000014Product 0000001234ADMIN 00000000123430000000014Product
0000001234ADMIN20130130
000000000000000100000000100000120000000001200000000000001009000951C Deposit INTERNET
BANKING -
00000000000000141.11RD2013091612:34:28:33+0000000000622000.54+0000000000635406.46NarrText 0899
000000000000000200000000100000120000000001200000000000001009000951C Deposit INTERNET
BANKING +00000000000000141.11D
2013091612:37:28:33+0000000000622000.54+0000000000635406.46NarrText 0899
000000123456578100000000100000120000000001200000000000001234567890CashN/A
+0000000000001000.00D 2013013000:00:00:00+0000000000001002.00+0000000000001001.00Deposit/EFT
narrative
+000000003
6.1.7 PTI TXT Balance Only (NRT) Template 1
Herewith the layout for the standard Nedbank format for TXT transaction feeds:
PTI TXT Balance on ly (NRT) field lengths are variable and ind icated below are maximum lengths Field Name Data type Actual field length Description Record Identifier Numeric 2 Record will start with "01" to indicate file header CIS Number Numeric 12 This field will display the client's CIS number Profile Number Numeric 10 This field will display the client's profile number Product Alpha 10 Will contain the PTI for the Final Transaction Information product Instance number Numeric 4 You can load up to 9999 different instances per profile for the PTI product. An instance is a group of accounts, settings and destination Instance name Alpha Numeric 30 Instance name as specified by the client Date Numeric 8 Displays the date on which the file is being sent. CCYYMMDD Filler Alpha 924 Spaces
HEADER
(Example)
010000000012343000000014Product 1234ADMIN 20130130
PTI TXT Balance only (NRT) field lengths are variable and ind icated below are maximum lengths Field Name Data type Actual field length Description Record Identifier Numeric 2 Record will start with "02" to indicate Account Balance Record
Account
Numeric 23 The transactions that follow are for this account Date Numeric 8 Displays the date the balance was checked. CCYYMMDD Time Numeric 6 Displays the time the balance was checked. HH:MM:SS Opening Available Balance Decimal 16,2 (20 characters long This is the opening available balance for this statement. Available balance=
Page 103¶
TRANSACTIONAL INFORMATION | 103 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only including sign) (Actual balance + Account Overdraft facility) less uncleared funds (Cheque deposits). All Value fields with be preceded by the sign = "+" (Credit balance) or "-" (Debit balance) Opening Book Balance Decimal 16,2 (20 characters long including sign) Actual opening balance including uncleared funds but excluding overdraft. All Value fields with be preceded by the sign = "+" (Credit balance) or "-" (Debit balance). Total Debits Decimal 16,2 (20 characters long including sign) The value of the debit transactions on this statement for this account. All Value fields with be preceded by the sign = "+" (Credit balance) or "-" (Debit balance). Total Credits Decimal 16,2 (20 characters long including sign) The Value of all the credit transactions on this statement for this account. All Value fields with be preceded by the sign = "+" (Credit balance) or "-" (Debit balance). Total Debit Count Numeric 10 Number of debit transactions reported for this account Total Credit Count Numeric 10 Number of credit transactions reported for this account Closing Available Balance Decimal 16,2 (20 characters long including sign) This is the closing available balance for this statement. Available balance= (Actual balance + Account Overdraft facility) less uncleared funds (Cheque deposits). All Value fields with be preceded by the sign = "+" (Credit balance) or "-" (Debit balance). Closing Book Balance Decimal 16,2 (20 characters long including sign) Actual closing balance including uncleared funds but excluding overdraft facilities. All Value fields with be preceded by the sign = "+" (Credit balance) or "-" (Debit balance). Filler Alpha 823 Spaces
BODY
(Example)
020000000000000123456789020130130000000+0000000000001000.00+0000000000001003.00+00000000000010
05.00+0000000000001006.0000000000250000000023+0000000000001001.00+0000000000001002.00
020000000000000123456789120130130000000+0000000000001003.00+0000000000001007.23+00000000000010
09.00+0000000000001010.0000000000150000000013+0000000000001005.00+0000000000001006.00
PTI TXT Balance only (NRT) field lengths are variable and ind icated below are maximum
lengths
Field Name Data
type
Actual field
length Description
Record Identifier Numeric 2 Record will start with "03" to indicate file
footer record
Account Record Count Numeric 18 Number of accounts reported in this file
Filler Alpha 962 980 Filler
FOOTER
(Example)
03000000000000000002
Page 104¶
104 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
TI_PTI_TXT_Balance_Only.txt
Fixed width length file: Record length = 1000
All Value fields with be preceded by the sign = + (Credit balance) and - (Debit balance)
Sample file layout
010000000012343000000014Product 1234ADMIN 20130130 020000000000000123456789020130130000000+0000000000001000.00+0000000000001003.00+00000000000010 05.00+0000000000001006.0000000000250000000023+0000000000001001.00+0000000000001002.00 020000000000000123456789120130130000000+0000000000001003.00+0000000000001007.23+00000000000010 09.00+0000000000001010.0000000000150000000013+0000000000001005.00+0000000000001006.00 03000000000000000002
6.1.8 PTI CSV Balance Only (NRT) Template 1
Herewith the layout for the standard Nedbank format for CSV transaction feeds:
PTI CSV Balance only (NRT) field lengths are variable and ind icated below are expected maximum lengths Field Name Data type Expected maximum field length Description Record Identifier Numeric 2 Record will start with "01" to indicate file header CIS Number Numeric 12 This field will display the client's CIS number Profile Number Numeric 10 This field will display the client's profile number Product Alpha 10 Will contain the PTI for the Final Transaction Information product Instance number Numeric 4 You can load up to 9999 different instances per profile for the PTI product. An instance is a group of accounts, settings and destination Instance name Alpha Numeric 30 Instance name as specified by the client Date Numeric 8 Displays the date on which the file is being sent. CCYYMMDD
HEADER
(Example)
01,1234,3000000014,Product,1234,ADMIN,20130130
PTI CSV Balance only (NRT) field lengths are variable and ind icated below are expected maximum lengths Field Name Data type Expected maximum field length Description Record Identifier Numeric 2 Record will start with "02" to indicate Account Balance Record
Account
Numeric 23 The transactions that follow are for this account Date Numeric 8 Displays the date the balance was checked. CCYYMMDD Time Numeric 6 Displays the time the balance was
Page 105¶
TRANSACTIONAL INFORMATION | 105 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
checked. HH:MM:SS
Opening Available Balance Decimal 16,2
This is the opening available balance for
this statement. Available balance=
(Actual balance + Account Overdraft
facility) less uncleared funds (Cheque
deposits). All Negative Value fields will
be preceded by the sign "-" (Debit
balance). All Positive Value fields will
NOT be preceded by a sign.
Opening Book Balance Decimal 16,2
Actual opening balance including
uncleared funds but excluding overdraft.
All Negative Value fields will be
preceded by the sign "-" (Debit
balance). All Positive Value fields will
NOT be preceded by a sign.
Total Debits Decimal
16,2 (20
characters long
including sign)
The value of the debit transactions on
this statement for this account. All
Negative Value fields will be preceded
by the sign "-" (Debit balance). All
Positive Value fields will NOT be
preceded by a sign.
Total Credits Decimal
16,2 (20
characters long
including sign)
The Value of all the credit transactions
on this statement for this account. All
Negative Value fields will be preceded
by the sign "-" (Debit balance). All
Positive Value fields will NOT be
preceded by a sign.
Total Debit Count Numeric 10 Number of debit transactions reported
for this account
Total Credit Count Numeric 10 Number of credit transactions reported
for this account
Closing Available Balance Decimal
16,2 (20
characters long
including sign)
This is the closing available balance for
this statement. Available balance=
(Actual balance + Account Overdraft
facility) less uncleared funds (Cheque
deposits). All Negative Value fields will
be preceded by the sign "-" (Debit
balance). All Positive Value fields will
NOT be preceded by a sign.
Closing Book Balance Decimal
16,2 (20
characters long
including sign)
Actual closing balance including
uncleared funds but excluding overdraft
facilities. All Negative Value fields will
be preceded by the sign "-" (Debit
balance). All Positive Value fields will
NOT be preceded by a sign.
BODY
(Example)
02,1234567890,20130130,000000,1000.00,1003.00,1005.00,1006.00,25,23,1001.00,1002.00
02,1234567891,20130130,000000,1003.00,1007.23,1009.00,1010.00,15,13,1005.00,1006.00
Field Name Data type Expected maximum field length Description Record Identifier Numeric 2 Record will start with "03" to indicate file footer record Account Record Count Numeric 18 Number of accounts reported in this file
Page 106¶
106 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
FOOTER
(Example)
03,2
TI_PTI_CSV_Balance
_Only.txt
All Negative Value fields will be preceded by the sig n "-"(Debit balance)
All Positive Value fields will NOT be preceded by a sign.
Fixed width files length of 1000 characters.
Sample file layout
01,1234,3000000014,Product,1234, ADMIN,20130130 02,1234567890,20130130,000000,1000.00,1003.00,1005.00,1006.00,25,23,1001.00,1002.00 02,1234567891,20130130,000000,1003.00,1007.23,1009.00,1010.00,15,13,1005.00,1006.00 03,2
6.1.9 SWIFT MT942 (NRT) Template 1
It is used to transmit information about provisional entries debited or credited to the account
for a specified interval.
The SWIFT template is to be read in conjunction with the SWIFT Standards Document 2011.
Refer to Appendix D to access to the respective document
SWIFT MT942 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 28C Statement Number /
Sequence Number 5n[/5n] 4
M 34F Floor Limit Indicator 3!a[1!a]15d 5
M 13D Date / Time Indication 6!n4!n1!nx4!n 6
O 61 Statement Line 6!n[4!n]2a[1!a]15d1!a3!c1 6x[//16x] [34x] 7 O 86 Information to Account Owner 6*65x 8
M 90D Number and Sum of Entries 5n3!a15d 9 O 90C Number and Sum of Entries 5n3!a15d 10 O 86 Information to Account Owner 6*65x 11 M = Mandatory O = Optional
SWIFT MT942 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
Page 107¶
TRANSACTIONAL INFORMATION | 107 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only 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 M 34F Floor Limit Indicator If you have specified to only be notified for transactions above a certain value this amount is indicated in this field. If you have chosen to receive all transactions amounts then this field will contain the value zero. Applicable to both debit and credit amounts. M 13D Date / Time Indication Date is expressed as YYMMDD. Time is expressed as HHMM Sign is either "+" or "-". Refer to SWIFT Standards document O 61 Statement Line * Refer to Field 61 -definition below O 86 Information to Account Owner 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)
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 M 90D Closing Balance (Booked Funds) This field indicates the total number and total amount of debit entries in this report O 90C Closing Available Balance (Available Balance) This field indicates the total number and total amount of credit entries in this report O 86 Information to Account Owner Is not used
Page 108¶
108 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
- Field 61: Statement Line This field contains the details of each transaction as listed below: Subfield Format Name Description 1 6!n Value Date Date the financial is posted to the account for the transaction 2 [4!n] Entry Date Is not used 3 2a Debit / Credit Mark C = Credit D = Debit RC = Reversal of credit RD = Reversal of debit 4 [1!a] Funds Code Is not used 5 15d Amount Transaction amount 6 1!a3!c Transaction Type Identification Code Will always be populated with NMSC 7 16x Reference for the Account Owner Will always insert 'NONREF' 8 [//16x] Account Servicing Institution's Reference Will Insert the transaction type (A list of transaction types will be provided by Nedbank) 9 [34x] Supplementary Details Your statement narrative will be populated in this field (Maximum 34 characters)
MT942 Sample Message:
{1:F01NEDSZAJ0AXXX0001000001}{2:I942XXXXXXXXXXXXN}{4:
:20:PNS0000003847690
:21:4000402493+27
:25:1454023619
:28C:23/1
:34F:ZAR0,00
:13D:1501231115+0200
:61:150123C89,89NMSCNONREF//EFT PAYMENT
MIB GROUP PTY LTD 05/13081/07
:86:104091806+81
0+1
Electronic Banking
EFT PAYMENT
:90D:0ZAR0,00
:90C:1ZAR89,89
-}
Page 109¶
TRANSACTIONAL INFORMATION | 109 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
6.1.10 SWIFT MT942 (NRT) Template 2
It is used to transmit information about provisional entries debited or credited to the account
for a specified interval.
The SWIFT template is to be read in conjunction with the SWIFT Standards Document 2016.
Refer to Appendix D to access to the respective document
SWIFT MT942 Standard Statement Message
Status Tag Field Name Content / Option No.
M 20 Transaction Reference
Number 16x 1
O 21 Related Reference 16x 2
M 25P Account Identification 35x
4!a2!a2!c[3!c] 3
M 28C Statement Number /
Sequence Number 5n[/5n] 4
M 34F Floor Limit Indicator 3!a[1!a]15d 5
M 13D Date / Time Indication 6!n4!n1!nx4!n 6
O 61 Statement Line 6!n[4!n]2a[1!a]15d1!a3!c1 6x[//16x] [34x] 7 O 86 Information to Account Owner 6*65x 8
M 90D Number and Sum of Entries 5n3!a15d 9 O 90C Number and Sum of Entries 5n3!a15d 10 O 86 Information to Account Owner 6*65x 11 M = Mandatory O = Optional
SWIFT MT942 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 25P Account Identification This will be the Nedbank account number for which the statement is sent And the senders address, which will always be populated with Nedbank's Swift address.
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
Page 110¶
110 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
number/2 and so on M 34F Floor Limit Indicator If you have specified to only be notified for transactions above a certain value this amount is indicated in this field. If you have chosen to receive all transactions amounts then this field will contain the value zero. Applicable to both debit and credit amounts. M 13D Date / Time Indication Date is expressed as YYMMDD. Time is expressed as HHMM Sign is either "+" or "-". Refer to SWIFT Standards document O 61 Statement Line * Refer to Field 61 -definition below O 86 Information to Account Owner 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)
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 M 90D Closing Balance (Booked Funds) This field indicates the total number and total amount of debit entries in this report O 90C Closing Available Balance (Available Balance) This field indicates the total number and total amount of credit entries in this report O 86 Information to Account Owner Is not used
- Field 61: Statement Line This field contains the details of each transaction as listed below: Subfield Format Name Description 1 6!n Value Date Date the financial is posted to the account for the transaction 2 [4!n] Entry Date Is not used 3 2a Debit / Credit Mark C = Credit D = Debit RC = Reversal of credit RD = Reversal of debit 4 [1!a] Funds Code Is not used
Page 111¶
TRANSACTIONAL INFORMATION | 111 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only 5 15d Amount Transaction amount 6 1!a3!c Transaction Type Identification Code Will always be populated with NMSC 7 16x Reference for the Account Owner Will always insert 'NONREF' 8 [//16x] Account Servicing Institution's Reference Will Insert the transaction type (A list of transaction types will be provided by Nedbank) 9 [34x] Supplementary Details Your statement narrative will be populated in this field (Maximum 34 characters)
MT942 Sample Message:
{1:F01NEDSZAJ0AXXX0001000001}{2:I942XXXXXXXXXXXXN}{4:
:20:PNS0000050945104
:21:4000367932+16
:25P:1339407027
NEDSZAJJ
:28C:348/1
:34F:ZAR0,00
:13D:1612131148+0200
:61:161213C951,00NMSCNONREF//EFT DEPOSIT
PENSION AND PROVIDENT FUND
:86:406617658+8
0+1
NBB
EFT DEPOSIT
PENSION AND PROVIDENT FUND
:90D:0ZAR0,00
:90C:1ZAR951,00
-}
6.1.11 TI SWIFT MX942 (NRT)
Page 112¶
112 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
6.1.12 Multicash AUSZUG (Header) (NRT)
All Numeric fields should be right aligned and Zero filled.
All amount / value fields have two implied decimal points.
Multicash format description:
Filename: AUSZUG (header)
Examples:
Multi-cash - AUSZUG.txt
The files have to be ASCII coded The delimiter between the fields is a semicolon (;) Type description: A (Alphanumeric) N (Numeric) X (Date in format DD.MM.YY)
Multicash AUSZUG (Header) Field Type Minimum Maximum Optional Description 1 A 0 12 Bank key (ibt) 2 A 0 24 Bank account number 3 N 1 4 Statement number 4 X 8 8 Statement date 5 A 3 3 Currency key (zar) 6 N 1 18.2 Opening balance 7 N 1 18.2 Debit total 8 N 1 18.2 Credit total 9 N 1 18.2 Closing balance amount 10 A 0 35 Bank account holder 11 A 0 35 Special account name 12 0 0 Not used 13 0 0 Not used 14 0 0 Not used 15 0 0 Not used 16 0 0 Not used 17 0 0 Not used 18 N 1 5 Number of memo records in account statement
Page 113¶
TRANSACTIONAL INFORMATION | 113 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
6.1.13 Multicash UMSATZ (Line Items) (NRT)
All Numeric fields should be right aligned and Zero filled.
All amount / value fields have two implied decimal points.
Multicash format description:
Filename: UMSATZ (line items)
Examples:
Multi-cash - UMSATZ.txt
The files have to be ASCII coded The delimiter between the fields is a semicolon (;) Type description: A (Alphanumeric) N (Numeric) X (Date in format DD.MM.YY)
Multicash UMSATZ (Line Items) Field Type Minimum Maximum Optional Description 1 A 0 12 Bank key (ibt) 2 A 0 24 Bank account number 3 N 1 4 Statement number 4 X 8 8 Value date - transaction date 5 N 1 10 X Primary zero's note number 6 A 0 27 X Note to payee 7 A 0 27 Bank posing text - statement description 8 0 0 Not used 9 0 0 Not used 10 A 0 16 Cheque number 11 N 1 18.2 Amount 12 0 0 Not used 13 0 0 Not used 14 X 8 8 Posing date - transaction date 15 0 0 Not used 16 0 0 Not used 17 A 0 27 X Note to payee2 18 A 0 27 X Note to payee3 19 A 0 27 X Note to payee4 20 A 0 27 X Note to payee5 21 A 0 27 X Note to payee6 22 A 0 27 X Note to payee7 23 A 0 27 X Note to payee8
Page 114¶
114 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
24 A 0 27 X Note to payee9 25 A 0 27 X Note to payee10 26 A 0 27 X Note to payee11 27 A 0 27 X Note to payee12 28 A 0 27 X Note to payee13 29 A 0 27 X Note to payee14 30 A 0 27 X Business partner 31 A 0 27 X Business partner 32 A 0 12 X Bank key of business partner's bank 33 A 0 24 X Bank account of business partner 34 A 0 3 X Business transaction code 35 0 0 Not used
IMPORTANT: Field 34 (Business Transaction Code) or Field 7 (Bank Posing Text) are used as the 'External Business Transaction' in Table T028G Please use Field 7 if Field 34 is too short. In this case, Field 34 has to have the Value Space
Page 115¶
TRANSACTIONAL INFORMATION | 115 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
6.2 Real time templates
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
Start of XML body
PTI
1234
Page 116¶
116 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
allowed per instance
Values are indicated
by;
D=Debit,
C=Credit,
RD=Reversal of Debit,
RC=Reversal of Credit
RD
Sample file layout
Page 117¶
TRANSACTIONAL INFORMATION | 117 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
ountBookBalance>622000.54
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
Page 118¶
118 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
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 -
CCYYMMDD
20140916
Page 119¶
TRANSACTIONAL INFORMATION | 119 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
Time Alpha Numeric 11
Time at which the
provisional transaction
was processed to the
account. Format -
HH:MM:SS:ss
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"
Page 120¶
120 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
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
Page 121¶
TRANSACTIONAL INFORMATION | 121 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
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
Page 122¶
122 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
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 -
CCYYMMDD
20140916
Time Alpha Numeric 11
Time at which the
provisional transaction
was processed to the
account. Format -
HH:MM:SS:ss
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)
Page 123¶
TRANSACTIONAL INFORMATION | 123 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
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
Information
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
Page 124¶
124 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
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
Page 125¶
TRANSACTIONAL INFORMATION | 125 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only O 56a Intermediary This field will not be used O 72 Sender or Receiver Information 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
Page 126¶
126 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
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
Page 127¶
TRANSACTIONAL INFORMATION | 127 HOST TO HOST U SER MANUAL
Nedbank Group Limited Internal Use Only
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
Page 128¶
128 | TRANSACTIONAL INFORMATION
HOST TO HOST U S E R MANUAL
Appendix B 7 Appendix B - FTI Templates
7.1 Near real time templates 7.1.1 FTI XML Template 1
Herewith the layout for the standard XML transaction feeds for near real time: