Document Management

Overview

TEMENOS EDUCATION CENTRE

Warning: This document, is protected by copyright law and international treaties. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of TEMENOS HEADQUARTERS SA Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal
penalties, and will be prosecuted to the maximum extent possible under applicable law.” Information in this
document is subject to change without notice
Objectives

After completing this learning unit/course, you will be able to:

 Differentiate various types of document managed by T24 Document

Management module
 Identify the need for document management

Slide 2
Product Overview

Customer Customer
Level Type

Mandatory

T24
Documents Contract
Required Specific

Application
Level
Non-Contract
Data File Specific

Slide 3
Document Management - An Overview

 Documents obtained from customers could be categorized into:

 Customer level document
 Application level documents

 A Customer level document is one, which would be required to

establish a customer relation with the bank (Example - Birth Certificate,
Passport)

 An Application level Document is required for transaction processing

pertaining to an application

 An Application level Document can be categorized into:

 Contract Specific document
 Non-Contract Specific document

Slide 4
Document Management - An Overview

 A Contract Specific Document is one, which should be separately

obtained from a Customer for each transaction in an Application
(Example – Promissory note)

 A Non-Contract Specific Document is one, which would be obtained

once from a Customer irrespective of any number of transactions in an
Application (Example – Loans condition agreement)

Slide 5
Tracking

 Each application for which DM processing should be invoked, T24

user will specify in DM.APPLICATION.INFO

Slide 6
Document Status

 Status codes are used to track documents

 Document status codes are defined in DOCUMENT.STATUS

 It could be defined as valid or invalid

 Pre-defined status codes in T24 are Received, Not Received and Expired

Slide 7
Document Status

 A predefined example “Received” for DOCUMENT.STATUS

Slide 8
Document Groups

 Required documents for a record input could depend on:

 Application
 Customer Type
 Value of the data input in various fields

 Document grouping is possible for each application and customer type

combination

Slide 9
Document Groups

 This is defined in application DOC.GEN.CONDITION

 Alternatively we can specify at Application level only, for any customer

Slide 10
Document Tracking Requirement

 For each document group in an application, requirement (rules) for

document tracking can be defined.

 This is done in application - DOCUMENT.REQUIRED

 Document types to be tracked for a group

 Track Customer level documents or related application level

 Document is Mandatory or not

 Stop transaction or not which has invalid status (field – STOP.TXN )

 Specify period of time applied from the STATUS.DATE of a Mandatory

Required Document

Slide 11
Document Tracking Requirement

 Document requirements for Document Group FT*202

Slide 12
Confirmation Messages

 Confirmation Message is a new type of Override Message displayed by

T24 in a question format
 “Yes” and “Cancel” or “Yes” and “No”

 Depending on response, further processing would be done by T24

 Scenarios in which Confirmation Message is displayed:

 A CUSTOMER record is input and a Mandatory Required Document is not
already tracked or tracked with a STATUS of 2 (“Not Received)
 A record is input in any application other than CUSTOMER and a
Mandatory Required Contract-Specific Document is not already tracked or
tracked with a STATUS of 2 (“Not Received)

Slide 13
Confirmation Messages

 Response to confirmation message by T24:

 Response to a Confirmation Message with YES, T24 will create or update a
document data record with STATUS of 1 (“Received”)

 If the response is CANCEL or NO, T24 will create or update a document

data record with STATUS of 2 (“Not Received”)

 If the user needs to input any other user defined STATUS (for example, a
status code of 5 for Fax Copy Received), User could later modify the
STATUS in document data records

 When a Confirmation Messages is responded by a User, appropriate

Override Messages would be stored in the application record.

Slide 14
Confirmation Messages

 Appropriate confirmation messages is raised to T24 user on

committing a contract.

Slide 15
Document Management - Workflow

Slide 16
Illustration - 1

 The bank needs to have a scanned copy of Social Security Card in

order to register a new customer. Setup a record in
DM.APPLICATION.INFO for CUSTOMER application

Use Admin Menu  Business Tools  Setup DM applications

Slide 17
DM.APPLICATION.INFO - Illustration 1

 Register CUSTOMER application for document management

Slide 18
DOCUMENT.CLASS - Illustration 2

 Create a Document class for document required for identity purpose

Use Admin Menu  Business Tools  Input Document Classification

Slide 19
DOCUMENT.TYPE - Illustration 3

 You will create a document type for social security card in continuation
to our exercise as described in illustration 1

Use Admin Menu  Business Tools  Input Document Types

Slide 20
DOCUMENT.TYPE

 Document type for social security card ( ID Proof required to open an

account with a bank)

Slide 21
DOCUMENT.TYPE

 Document type for social security card ( ID Proof required to open an

account with a bank)

Slide 22
DOC.GEN.CONDITION – Illustration - 4

 You will create a grouping condition for CUSTOMER application. Use

group number 501 as default and 502 for customer who resides in US.

Use Admin Menu  Business Tools  Setup Document Grouping

Slide 23
DOC.GEN.CONDITION

 Group condition for CUSTOMER application in DOC.GEN.CONDITION

Slide 24
DOCUMENT.REQUIRED

 DOCUMENT.REQUIRED application defines the requirement for

document tracking

 This is defined based on each document group(as defined in

DOC.GEN.CONDITION)

 Records can be reversed

 If no records exists for document group in this application then no

document will be determined as required for that group

Slide 25
DOCUMENT.REQUIRED – Illustration - 5

 Setup document tracking for the identity document for private new
customers as created in illustration before. Check in your document
grouping, which group number to use. This document is mandatory but
does not stop transaction processing

Use Admin Menu  Business Tools  Document Management  Setup

Document Tracking

Slide 26
DOCUMENT.REQUIRED - Illustration

 In this illustration you are defining tracking condition for the respective
group(202 for CUSTOMER) defined in DOC.GEN.CONDITION

Slide 27
Illustration - 6

 Create a new customer (Residence = US). Check if document tracking

works. Get the new customer authorized

 Check the document(s) tracked for your new customer

Slide 28
Illustration 6 – Solution

Use User Menu  Customer  Create New Customer

Slide 29
Illustration 6 - Solution

 Note that when authorizing you can see in audit trail the document has
been asked for and received
Slide 30
Illustration 6 - Solution

Use User Menu  Business Tools  Document Management 

Customer Document Overview

Slide 31
Illustration 6 - Solution

Slide 32
DOCUMENT.STATUS

 Stores details of status codes used in the document data files

CUST.DOCUMENT and TRANS.DOCUMENT

 Available by default: 1("received"), 2("not received") and 3("expired")

 Status 1 is valid, status 2 & 3 are invalid

 Records can not be reversed

Slide 33
DOCUMENT.STATUS - Illustration 7

 Create a document status for a scanned copy. This scanned copy will
have a validity status of 60 days.

Use DOCUMENT.STATUS Application

Slide 34
CUST.DOCUMENT – Illustration 8

 Input a new customer document(Proof of Residence) for the new

customer you just created. The document is valid from today for a
period of 1 year

 Indicate the details of a next document that will replace the first
document after the first document expires. This document is again valid
for a year from the date it comes into effect

Slide 35
CUST.DOCUMENT - Illustration

 Step 1

 Create DOCUMENT TYPE for proof of residence

Slide 36
CUST.DOCUMENT – Illustration 8

 Use
User Menu  Business Tools  Document Operations 
Capture Customer Document

Slide 37
CUST.DOCUMENT – Illustration 8

 Customer document(Proof of Residence) is input. This document is

valid from today for a period of 1 year.

Slide 38
DM.DOCUMENTS.TRACKED

 Stores T24 generated records with details of document tracked for an

authorized application record

Slide 39
Image Management

Slide 40
Product Overview

Signature
scan
Linked to T24
application
Pass port CUSTOMER
scan ACCOUNT View
through
LD …..
Images Normal /
Context
No linkage sensitive
Document Enquiry
scan

Photo scan

Slide 41
Workshop 1

 Click on Admin Menu

 Business Tools  Image Management  Setup Image Types and Locations

Slide 42
Full Path

 Enter value for GB.DESCRIPTION and PATH

Slide 43
Mapped Drive

 The storage location being accessible using a mapped drive reference ‘Z:’
and the directory ‘/IMAGE/SIGNATURE/’

Slide 44
Relative Path

 The storage location “./im.images/Documents/” refers to path relative to

the BrowserWeb root location

Slide 45
IM.DOCUMENT.IMAGE

 The IM.DOCUMENT.IMAGE application is where the individual file (or

image) details are defined
 The ID of these records is a standard Julian date type

Slide 46
IM.DOCUMENT.IMAGE

 Click on User Menu

 Business Tools  Multimedia Operations  Capture & upload an image

Slide 47
IM.DOCUMENT.IMAGE

Slide 48
IM.DOCUMENT.UPLOAD

 The IM.DOCUMENT.UPLOAD application is used to upload an image

file from an import directory
 It stores the image from import directory with a unique id in the image
store for specific type of files

Slide 49
IM.DOCUMENT.UPLOAD

 We’ll do the signature example first in this course

 Click camera icon to import an image file

Slide 50
IM.DOCUMENT.UPLOAD

 Click on Browse to upload the image

file from the image source directory

Slide 51
IM.DOCUMENT.UPLOAD

 Once the image

is selected, click
on validate
button

 Once the validate button is clicked the Image is uploaded by T24 to the directory
defined in IM.IMAGE.TYPE

Slide 52
IM.DOCUMENT.UPLOAD

 FILE.UPLOAD Field will be populated with a unique reference Id

Slide 53
IM.DOCUMENT.IMAGE

 The IMAGE field in IM.DOCUMENT.UPLOAD for the respective record is

updated by T24

Slide 54
ENQUIRY - Display Signature

 Click on User Menu

 Business Tools  Multimedia Operations  Find Image
 Key in the selection criteria and click on Find

Slide 55
ENQUIRY - Display Signature

 Click on User Menu

 Business Tools  Multimedia Operations  Find Image

 Key in the selection criteria and click on Find

Slide 56
Enquiry - Display Document

 Click on User Menu

 Business Tools  Multimedia Operations  Find
Document

 Key in the selection criteria and click on Find

 Click on the hyperlink

Slide 57
Thank You

TEMENOS EDUCATION CENTRE

Warning: This document, is protected by copyright law and international treaties. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of TEMENOS HEADQUARTERS SA Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal
penalties, and will be prosecuted to the maximum extent possible under applicable law.” Information in this
document is subject to change without notice