Objective :
The Bank Account Details are a necessity, so as to channelize the revenue collection process in a ULB(s). The agenda behind gathering the bank account details is to :
Enable Various Digital Modes of Payment Collection (For Example : Payment Gateways).
Provide assurance to the ULB/State, that the revenue collected from DIGIT Modules is wired to the assured selected bank account.
Template Structure :
To collect the bank account details, we have an existing template having the following tabs :
...
(Note: Fields with * are mandatory to be filled in)
Field(s) Description :
*ULB Name: Represents the Name of ULB, whose bank account details we are gathering.
*Bank Branch Name: Name of the branch from where the bank account is operating from.
*Bank Branch Code: Represents the IFSC Code associated with the bank branch.
Bank Branch Address: The address of the bank branch.
PIN : The PIN Code associated with the address of the bank branch.
Contact Person: The point of contact in the provided bank branch.
Contact Person Designation: The designation representation of the contact person.
Contact Person Phone Number: The phone number details of the contact person.
MICR: The MICR Code associated with the bank branch.
2. Bank Account Details
...
ULB Name*
...
Bank Branch Name *
...
*Bank Account Number
...
*Bank Account Code
...
*Type
...
Description
(Note: Fields with * are mandatory to be filled in)
Field(s) Description:
*ULB Name: Represents the Name of ULB, whose bank account details we are gathering.
*Bank Branch Name: Name of the branch from where the bank account is operating from.
*Bank Account Number: The number associated with the account where the revenue from DIGIT modules will be wired in.
*Bank Account Code: The Chart of Account attached to the bank account number.
*Type: Following are the parameters involved in the type :
Recieve: If the proposed bank account is used to collect the revenue.
Payment: If the proposed bank account is used to make the payments.
Both: If the proposed bank account is used for both the purposes ie to collect the revenue and make the payments as well.
Description: Additional Information (If any) related to the proposed bank account.
Template Validations
All the fields with * sign are mandatory to be filled in. Without this information, the system configurations cannot be executed.
A “single entry” should be made against the respective column. Incase of multiple entries, continuation must be followed.
Template Attachment
...
Introduction
It is a ULB bank account which is operative at least to receive or deposit the day to day revenue collection done by the ULB. It is used by online payment integrator to disburse the amount in ULBs accounts which has been collected through a payment gateway into a pool account managed by payment gateway.
Data Table
Below given data table represents the excel template attached. Data given in the table is a sample data.
Sr. No. | Code* | ULB Name* | Bank Name* | Branch Name* |
|---|
...
Bank Branch Code*
...
Bank Branch Address
...
PIN
...
Contact Person
...
Contact Person Designation
...
Contact Person Phone Number
...
MICR
Account Number* | Account Type* | IFSC* | |||||
|---|---|---|---|---|---|---|---|
1 | dehradun | Dehradun Municipal Corporation | SBI | Rajpur | XXXX0082XX01 | Saving | SBIX0921 |
2 | haridwar | Haridwar Municipal Corporation | PNB | Chauk | XXXX9820XX9 | Saving | PNBX8320 |
Note: Data given in the table is sample data.
Procedure
Data Definition
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory | Definition/ Description |
|---|---|---|---|---|---|
1 | Code | Alphanumeric | 64 | Yes | Unique code given to the bank detail record. E.g. dehradun. |
2 | ULB Name | Text | 256 | Yes | Name of Urban Local Body. |
3 | Bank Name | Text | 256 | Yes | Name of the bank where the account exists. |
4 | Branch Name | Text | 256 | Yes | Name of the bank branch where the account exists. |
5 | Account Number | Alphanumeric | 64 | Yes | Bank account number to be used to transfer the amount. |
6 | Account Type | Text | 256 | Yes | Account type. e.g. Saving, Current etc. |
7 | IFSC | Alphanumeric | 64 | Yes | IFS code of branch as per FBI guidelines. |
Steps to fill data
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.
Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
Identify the bank account which is to be used to transfer the amount which is collected online for various services.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise till the entire data is filled into a template.
Verify the data once again by going through the checklist and taking care of each and every checklist point/ activity mentioned in the checklist.
Checklist
The checklist is a set of activities to be performed after the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
Common Checklist
This checklist covers all the activities which are common across the entities.
To see the common checklist refer to the page Checklist consisting of all the activities which are to be followed to ensure complete and quality data.
Entity Specific Checklist
This checklist covers the activities which are specific to the entity.
Sr. No. | Activity | Example |
|---|---|---|
1 | Code should not consist of any special characters. | E.g. dehrdun is allowed. while dehradun@1 is not allowed |
2 | Account number should should not consist of any special characters. | As issued by bank. |