Skip to content

5 Images on demand (IOD)

Source: TI_Host_to_Host_Client_User_Manual_v52.pdf Document pages: 76-83 PDF pages: 76-83

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.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

  • 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

1
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.

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

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

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.

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.

  • 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

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.