Version 1.

0 Requirement Document: Smart acc – Existing Customer Flow

REQUIREMENT DOCUMENT
Smart acc – Existing Customer Flow

Version 1.0
Information Technology

Copyrights © HDFC BANK Page 1 of 7

Version 1.0 Requirement Document: Smart acc – Existing Customer Flow

Document Control
Authorization
TEMPLATE NAME Requirement Document Template

TEMPLATE VERSION 1

EFFECTIVE DATE 5th Feb, 2018

TEMPLATE OWNER Information Technology

TEMPLATE APPROVER Process Owner

DOCUMENT OWNER Vardhan Desai

DOCUMENT CLASSIFICATION Restricted

DOCUMENT VERSION NO. 1.0

Review
TEMPLATE DATE AUTHOR DESCRIPTION
VERSION

1 5th Feb, 2018 Business Head

Copyrights © HDFC BANK Page 2 of 7

Version 1.0 Requirement Document: Smart acc – Existing Customer Flow

Frequency of Review – Annually

Ownership
Bank's Information Technology is the owner of the document. Unless otherwise specified, no part of this
document may be reproduced or utilized in any form or by any means, electronic or mechanical,
including photocopying and microfilm, without permission in writing from Information Technology (IT).
Similarly, distribution of this document to a third party is also prohibited unless specific approval is taken
from IT. This document is allowed to be distributed to vendor by IT Team.

Placement
The most updated copies of the document can be found on the Bank's information portal under
Information Technology (IT) section. All printed copies of this document are to be treated as uncontrolled
and may be obsolete. You shall always consult the current authorized versions before making important
decisions.

Copyrights © HDFC BANK Page 3 of 7

Version 1.0 Requirement Document: Smart acc – Existing Customer Flow

RD Default Version no. 0, Dated: DD/MM/YY

Subsequent versions to be numbered serially

•Preparation by
This document is to be prepared by Business Solutions Group (BSG) / BTG based on the
concept note received and subsequent meetings with and inputs from users, operations,
vendors, etc. It is to be signed off by Application Owners at BSG / BTG and IT and thereafter
forwarded to the Concept Initiator for signoffs by Functional Head of Business/Operations.
•Profile
Project Id:
Project Name: Smart acc – Existing Customer Flow
Business Group: Retail Assets
Project Manager: Taposh Saha

•Introduction
In smart account, account opening is done only for NTB customers. With this enhancement,
smart account application will be able to open new accounts for existing customers also.

•Functional Requirements

 Mobile app will authenticate existing customers by DOB & Mobile number. Once the
user is identified as NTB customer, then its flow will be same as is now.
And if the customer is existing customer, then flow is given below.
 Identifier for existing customer required which will be basis the CUST ID shared by APP
to CRM.
 If address is being changed then Landmark should be editable in CRM. Also only for
these cases address should be sent to IDEA. And Address proof should be mandatory.
 Since editing of DOB, Mobile number, Tel number, Email ID, is not permitted these
details should not be sent to IDEA. Rest fields will be passed to IDEA as per extant.
 Customer ID should be pre-populated in the Bank use section.
 Signature card should not be sent to IDEA for signature cropping for existing
customers, however the same to be sent to FTS as per the extant NTB process.
 REKYC dates to be updated in core wherever the customer has submitted the
documents for address change
 Address in Form 60 to be populated with basis the proof of address submitted in the
lead if provided.
 CUST ID should not be editable for existing customers in CRM.
 Since the UCIC will be selected, signature cropping for such cases will not be required.
 Name of the customer should not sent to IDEA as the same will not be changed
 CRM to get the valued of “ Address edited – Yes / no” for both address types
 Aadhaar number, PAN card if filled in the APP to be sent to IDEA

Copyrights © HDFC BANK Page 4 of 7

Version 1.0 Requirement Document: Smart acc – Existing Customer Flow

 In case an existing customer has filled the Smart app as a NTB customer, at the UCIC
check, the branch to select the UCIC and process.
 This UCIC will be only the Retail CUST ID. Non retail cust id should not be populated for
Smart App lead.

•Requirements from mobile app

xml tag will be shared with MEAP team:
1. Is customer Existing
2. Customer ID
3. Is address Mailing Modified.
4. Is Resi Address Modified
5. Is AADHAR Modified
6. Is PAN Modified

•Target Environment

NOTE: PLEASE ALSO MENTION IF THERE ARE ANY KNOWN SYSTEM CONSTRAINTS

•Interface Requirements
•Graphical User Interface
Please detail comprehensively the Graphical User Interface. Determine the look and feel of
the Interface along with the, navigational flow that the end user is going to use. Please mention
any preexisting standards if applicable to the system input/output from the user’s perspective.
The validations for data that will be input/output on the screen/output can be defined here.
For example, for showing the a/c balance on the Internet, there will be a validation screen
accepting the “Customer Id” and the Net Banking “Password” and a “Submit/OK” button that
will take the users of the Main screen where the “Account number” and “Account type” are the
mandatory fields and a “Get Balance” button to fetch the account details.
NOTE : IF LEFT BLANK IT IS ASSUMED THAT VENDOR IS FREE TO DEFINE THIS
SECTION.

• Hardware Interface
Clearly Indicate the h/w on which the desired system will be resting here. If there are any OS
command/executables/features/tools that the proposed system is may be required to use then
these need to be mentioned here.

NOTE : IF LEFT BLANK IT IS ASSUMED THAT VENDOR IS FREE TO DEFINE THIS

SECTION.

•Communication interface
Clearly indicate the communication Interface that the proposed system will be having with the
external world. An example of this can be the SMPT configuration that will be required for
defining alerts/reminders for the system. Addition this can also include the file format that may
be required for communication and handshake with the other systems and the environment in
which the proposed system will rest. You may also specify any data communication, client or
inter-process communication here.
NOTE : IF LEFT BLANK IT IS ASSUMED THAT VENDOR IS FREE TO DEFINE THIS
SECTION.

Copyrights © HDFC BANK Page 5 of 7

Version 1.0 Requirement Document: Smart acc – Existing Customer Flow

• Software Interface
Indicate the Software Interface that the proposed system will be having with the external world.
An example of this can be the SMPT configuration that will be required for defining
alerts/reminders for the system. Addition this can also include the file format that may be
required for communication and handshake with the other systems and the environment in
which the proposed system will rest. You may also specify any data communication, client or
inter-process communication here.
NOTE : IF LEFT BLANK IT IS ASSUMED THAT VENDOR IS FREE TO DEFINE THIS
SECTION.

•Migration/Transition Plan (if applicable)

Please mention any data/system migration details that may be applicable here. This section is
relevant if the data from the earlier application database needs to be ported over to the new
application database.

•Non-functional Specific/Additional Requirements

Please mention any non-functional specific or additional technical information, which may be
critical for designing/building/execution of the system here. Please validate if the information
that is being provided here needs to be also mentioned in the Function Specification section of
this document. Only details that are out of the scope of the system design as part of vendors
system development but key from the execution/implementation/environmental aspects need
to be mentioned here.
NOTE : IF LEFT BLANK IT IS ASSUMED THAT VENDOR IS FREE TO DEFINE THIS
SECTION.

•Assumptions/Dependencies/Limitations
Clearly mention all Assumption/Dependencies and Limitation that are identified for this system.
The Limitations and Assumptions that are made as part of the concept note will be inherited in
this section. Additionally if there are any ambiguities with the system design, then these need
to be mentioned here.
NOTE: IF LEFT BLANK IT IS ASSUMED THAT THE SYSTEM ASSUMPTION /
DEPENDENCIES / LIMITATIONS ARE NONE.

•Systems Impacted (if any) :

Clearly indicate in detail the systems that may be impacted once this system will come live.
There may be other specific requirements that may be required to be specified in section 7d.
The other systems that may be impacted are live functional systems that are currently running
in the bank.
NOTE : IF LEFT BLANK IT IS ASSUMED THAT VENDOR MAY OVERLOOK ANY SUCH
SPECIFIC NEEDS/CONSTRAINTS.

•Screen Shots (if any)

•Acceptance Criteria
Please specify the acceptance criteria here e.g.
The acceptance criteria can be defined as follows:
 The specification / design documents address the required functionality.

Copyrights © HDFC BANK Page 6 of 7

Version 1.0 Requirement Document: Smart acc – Existing Customer Flow

•Additional Information
Please mention any additional relevant information here.

Prepared by / Date Reviewed by / Date

(BSG / BTG Manager) (IT Manager)

Approved by / Date Approved by / Date

(BSG / BTG Application (IT Application Owner)
Owner)

Copyrights © HDFC BANK Page 7 of 7