Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Once the Trade Categories are defined, the next task is to -
Define Trade Types
Map Trade Category to listed Trade Types
The Trade Type can be defined as the next (2nd) level classification of Trade. There can be multiple trade types and the list may vary from one State/ULB to another.
The table above contains sample Trade Type data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Select the relevant Trade Category Code from the available drop-down list of Trade Category. This will map the listed Trade Type to the corresponding Trade Category.
Enter a unique Trade Type Code to identify the type of trade.
Enter a Trade Type Name (In English).
Enter the Trade Type Name (In Local Language).
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Sr. No.
Trade Type Code*
Trade Type Name* (In English)
Trade Type Name* (In Local Language)
Trade Category Code*
1
TRADE_TYPE_MEDICAL
Hospital
अस्पताल
TC1
2
TRADE_TYPE_HOTEL
Hotels
होटल
TC2
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Trade Type Code
Alphanumeric
64
Yes
The Code assigned to the Trade Type. Eg: TRADE_TYPE_MEDICAL is assigned to Hospitals
3
Trade Type Name (In English)
Text
256
Yes
Name of the Trade Type in English. Eg: Goods, Services etc.
3
Trade Type Name (In Local Language)
Text
256
Yes
Name of the Trade Type in Local Language (as decided). Eg: Service is described as “सर्विस” in Hindi
4
Trade Category Code
Reference
64
Yes
The Code assigned to the Trade Category. Eg: TC1 For Goods, TC2 for Services
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
The format of the Trade Type Code defined should be alphanumeric and unique
TRADE_TYPE_MEDICAL
TRADE_TYPE_HOTELS
2
Trade Type Name (in either language) should not contain any special characters
Hospital: [Allowed]
#Hospital! : [Not allowed]
The Trade License application, developed on the eGov-DIGIT platform, makes the process of obtaining a Trade License easy, smooth, and transparent. The module, hence, removes the need for manual processing and streamlines the key trade license management functions to provide a better user experience.
DIGIT Trade License module enables citizens to -
Apply for new trade license or renew an existing trade license.
Upload all the relevant documents required for the license.
Make payment for the Trade License (New/Renewal) fee using the online payment gateway.
Receive notifications and alerts by emails or SMS for new application status updates and pending renewals.
Download Trade License, Payment & Acknowledgement Receipts online.
DIGIT Trade License module enables employees to -
Create flexible role-based workflows.
Configure license fees calculation logic.
View custom dashboards for module statistics.
Filter search results using advanced configurable search parameters.
Receipt Register
Application Status
Cancelled Receipt Register
ULBwise Collection Report
ULBwise Application Status
Along with the rates, the Trade License application process does require certain documents as an attachment of proof. The proof can be defined by a set of documents ranging from
Identification Proof (Drivers License/ Voter Card/ Adhaar/ Pan etc.)
Trade Premises Proof (Lease Agreement, Electricity Bills, etc).
Misc Documents (Affidavit, Self- Declaration, etc).
The Number and the Documents required could vary across the State, ULB(s), and might be dependent on Trade Subtypes, all of which are totally configurable on DIGIT.
The table above contains sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify the “Trade Sub Types” that exists at a ULB/ State level.
Collect the above information and feed it below the “Trade Sub Type Name” column accordingly. The Description of Trade Sub Type Name must be provided as per the language specified in the respective column.
Add the “Trade Sub Type Code” respectively against the identified trade type(s).
Fill in the *Document 1 & *Document 2 columns respectively.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
The structure type is the first level of classification of the premises where the trade has to be established and conducted. This is mostly used as management information in the trade detail.
The table above contains sample data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.
Contact the person who shared this template with you to discuss and clear your doubts.
Enter the relevant structure types.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
The separate entity-specific checklist is not needed for this entity data template.
Trade Type can be further sub-classified into Trade Sub Type depending on the trade ontology existing in the ULBs or States. Hence, Hotels can be further classified into Dhabas in North India or Udupis in South India.
Once the are defined, the next task is to -
Define Trade Sub Types
Map Trade Types to corresponding Trade Sub Types
The table above contains sample data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Select the relevant Trade Type Code from the Trade Type master data. This will map the listed Trade Sub Type to the selected Trade Type.
Enter a unique value for Trade Sub Type Code.
Enter the English name for Trade Sub Type Name (English).
Enter the local name for the Trade Sub Type Name (Local Language).
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Sr. No.
*Trade Subtype Code
*Trade Subtype Name (In English)
*Application Type
*Document 1
*Document 2
1
TRADE_SMALL_BAKERY
Small Bakery
New
PAN/VOTER ID
LAND LEASE
2
TRADE_SMALL_BAKERY
Small Bakery
Renewal
PAN/VOTER ID
ELEC BILL
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Trade Sub Type Code
Reference
64
Yes
The Code assigned to the Trade Sub Type. Eg: TRADE_SMALL_BAKERY is assigned to Bakery
2
Trade Sub Type Name (English)
Text
256
Yes
Name of the Trade Sub Type in English Eg: Clinic
3
Application Type
Text
256
Yes
Type of application for which the documents related to trade are configured. It can either be new or renewal
4
Document 1
Reference
256
Yes
The primary document required as a verification parameter. Refer to the Standard Document List
5
Document 2
Reference
256
Yes
The Secondary Document required as a verification parameter. Refer to the Standard Document List
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
Trade Sub Type Name (In either Language) should not contain any special characters
Small Bakery: [Allowed]
#Small_Bakery! : [Not allowed]
Sr. No. | Code* | Structure Type* (In English) | Structure Type* (In Local Language) |
1 | IMMOVABLE | Immovable | अचल |
2 | MOVABLE | Movable | चल |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Code | Alphanumeric | 64 | Yes | Unique code to identify the records uniquely |
2 | Structure Type* (In English) | Text | 256 | Yes | Structure type in English |
3 | Structure Type* (In Local Language) | Text | 256 | Yes | Structure type in local language e.g. Hindi, Telugu etc. |
Sr. No. | Checklist Parameter | Example |
1 | The format of the Trade Sub Type Code defined should be text and unique | TRADE_SUBTYPE_CLINIC |
2 | Trade Type Name (in either language) should not contain any special characters | Clinic: [Allowed] #Clinic! : [Not allowed] |
DIGIT Property Tax facilitate ULBs and citizens to automate the assessment/ re-assessment of property tax for a property and its demand billing and collection. It also enables the ULBs as well as citizens to process the transfer of title of a property in case of a sale, gift or will and captures the history of ownership.
The main features of the product are as given below.
Completely automated assessment and re-assessment of property tax against a property.
Online self-assessment process
Integrated workflow for ULB staff to perform the check and approve.
Transfer of title (Mutation)
Online application
Integrated workflow for ULB staff to perform the check and approve.
Generating the demand
Collection of property tax through various modes (Cash, Cheque, POS (Credit/ Debit Card), NEFT/RTGS, Online - Through Payment Gateway)
Auto calculation of rebate, interest and penalty.
Receipt Register
Cancelled Receipt Register
Demand Register
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Trade Sub Type Code* | Trade Sub Type Name* (In English) | Trade Sub Type Name* (In Local Language) | Trade Type Code* |
1 | TRADE_SUBTYPE_CLINIC | Clinic | क्लिनिक | TRADE_TYPE_MEDICAL |
2 | TRADE_SUBTYPE_DHABA | Dhaba | ढाबा | TRADE_TYPE_HOTEL |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Trade Sub Type Code | Alphanumeric | 64 | Yes | The Code assigned to the Trade Sub Type. Eg: TRADE_TYPE_Dhaba is assigned to Hotels |
2 | Trade Sub Type Name (In English) | Text | 256 | Yes | Name of the Trade Sub Type in English. Eg: Clinic |
3 | Trade Sub Type Name (In Local Language) | Text | 256 | Yes | Name of the Trade Sub Type in Local Language (as decided). Eg: Dhaba is described as “ढाबा” in Hindi |
4 | Trade Type Code | Reference | 64 | Yes |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
The Construction Type refers to the list of Building construction types in the ULB limits considered for tax calculation.
DIGIT Property Tax system has certain pre-defined categories namely :
Pucca
Semi Pucca
Kuccha
The data described in the above table is a sample.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify the construction types applicable and fill into the given template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
There is no checklist applicable separately to this entity.
Roads are constructed in order to facilitate the locomotion of people from a place to another.
The roads constructed in a state are classified into certain categories which could be on the basis of the width of the road, construction material or the function and location. Road type is one of factor defining the unit rates and hence configuration is needed for DIGIT module in order to describe the property and what are the taxes it could attract.
Given below is the sample data table from the template in which the data has to be collected:
Please note that the values mentioned in the data table are sample values and the states are free to add/update according to their specific requirements.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Firstly identify all the classifications of road types which are present in the state.
Secondly get the codes for that classification, if not present form the codes with abbreviated terms.
After which start filling the template with the proper codes and description.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
The Trade Category List can be defined as the primary or the 1st level classification “head” for trade(s) defined at a ULB/State Level.
The table above contains sample Trade Category data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Enter a unique Trade Category Code for each trade head.
Enter the Trade Category Name. Some trade categories are already defined in the master. Add new categories as required.
Enter the Trade Category Name (Local Language).
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Structure sub type is the second level of classification of the premises where the trade has to be established and conducted. This is mostly used as management information in the trade detail.
The table above contains sample data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.
Contact the person who shared this template with you to discuss and clear your doubts.
Enter the relevant structure sub types with its proper mapping with structure type.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
The separate entity-specific checklist is not needed for this entity data template.
Master data templates allow users to configure the key parameters and details required for the effective functioning of the modules. This section offers comprehensive information on how to configure the master data templates for each module.
Once the Trade Ontology is defined, the next step is to allocate the license fee associated with the Trades.
Dependent on the Trade Classification Level (Types/ Subtypes), the fee allocated might be the same across the Sate or could vary from ULB to ULB. There could be a distinct fee(s) for two different types of applications (new and renewal).
Following are the key tasks to be executed :
Allocate the License Fee according to Trade Classification Level (Types/Subtypes).
Map the License fee with respective Trade Classification Level.
The table above contains sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
Identify the “Trade Sub Types” that exists at a ULB/ State level.
Collect the above information and feed it below the “Trade Sub Type Name” column accordingly. The Description of Trade Sub Type Name must be provided as per the language specified in the respective column.
Add the “Trade Sub Type Code” respectively against the identified trade type(s).
Fill in the New License Fee & New Renewal Fee accordingly. The New License Fee & Renewal Fee can be the same as well as distinct, depending on the by-laws/ mandate followed by the State/ULB.
Fill in the fields related to Units of Measurement (UOM Unit, From/To) for the available trades only.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
A property can be used for a variety of things such as to live or to do some trading/selling etc activity or for any other purpose. Properties can be classified into various categories on the basis of there usage. Ideally, property usage is categorized as residential, non-residential or a mix of both.
The data described in the above table is a sample.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify all the property usages categorized at first level and fill into the given template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
This is a further sub-classification of the usage types into sub minor category. Here the properties can be further classified such as commercial food joints etc.
Below mentioned is the data table from the template used to collect the data:
Data given in the table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify all the sub minor categories used across the state.
After which identify the codes of all the sub minor categories, if not present abbreviate the description.
Get the details(description) of these codes.
Start filling the template with the codes and description in English and one native language would be helpful.
Get the exemption maximum amounts and their respective percentages.
Most importantly do get a mapping of these sub minor codes to their parent which is minor usage type.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed on 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
Usage Category Minor is nothing but a further classification of “ Usage Category Major’s ”, which can be explained as a broad diversification of the usage of your property.
This broad diversification is ideally used to classify the tax amount to which a property could be exempted from.
Below mentioned is the data table that is used for collecting data:
Please note that the data mentioned in the table is sample data, however, the state might further update this on the basis of their requirements.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Gather all the details available for the usage category minor type.
Start collecting the codes for the same, if not available abbreviate the description to create a relevant code.
Start filling the template with the codes and descriptions for details in the relevant columns.
After that start mapping them with the relevant Usage Category major codes.
Get the rates as well as amounts for the exemption if any.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
The Property Sub Type represents 2nd level classification to the and provides the option to further classify the property type in sub types. For example property type ‘Built-up’ is further classified into Independent House, A Flat In Apartment and Half Constructed Half Open and considered differently on tax calculation procedure.
The data described in the above table is a sample.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify all the property sub types applicable and fill into the given template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
There is no separate checklist is applicable to this entity.
The Code assigned to the . Eg: TRADE_TYPE_MEDICAL is assigned to Hospitals
Sr. No.
Construction Type Code*
Construction Type (In English)*
Construction Type (In Local Language)*
1
PUCCA
Pakka Building With R.C.C. Roof or R.B. Roof
पक्का भवन, आर0सी0सी0छत या आर0बी0 छत सहित
2
SEMIPUCCA
Any Other Pakka Building
अन्य पक्का भवन
3
KUCCHA
Kuccha building that is all other building not covered in clauses (a) and (b)
कच्चा भवन अर्थात समस्त अन्य भवन जो (एक) और (दो) में अच्छादित नही है
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Construction Type Code
Alphanumeric
64
Yes
Unique Identifier for Construction Type as defined in the Property Master.
2
Construction Type ( In English)
Text
256
Yes
Nomenclature of “Construction Type” in English.
3
Construction Type (In Local Language)
Text
256
Yes
Nomenclature of “Construction Type” in the local language as Telugu, Hindi etc.
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Road Type Code*
Road Type* (In English)
Road Type* (In Local Language)
1
RD1
Less than 12 meters in width
12 मीटर से कम चौड़ाई वाले मार्ग पर
2
RD2
From 12 meters to 24 meters in width
12 मीटर से 24 मीटर तक की चौड़ाई वाले मार्ग पर
3
RD3
More than 24 meters in width
24 मीटर से अधिक की चौड़ाई वाले मार्ग पर
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Road Type Code
Alphanumeric
64
Yes
This is a unique code given for the classification of road types
2
Road Type (In English)
Text
256
Yes
This describes the category of the road in the English language
3
Road Type (In Local Language)
Text
256
Yes
This describes the category of the road in the local language e.g. Telugu, Hindi etc.
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr.No.
Trade Category Code*
Trade Category Name* (In English)
Trade Category Name* (In Local Language)
1
TC1
Goods
सामग्री
2
TC2
Services
सर्विस
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Trade Category Code
Alphameric
64
Yes
The Code assigned to the Trade Category. Eg: TC1 For Goods, TC2 for Services
2
Trade Category Name (In English)
Text
256
Yes
Name of the Trade Category in English. Eg: Goods, Services etc.
3
Trade Category Name (In Local Language)
Text
256
Yes
Name of the Trade Category in Local Language (as decided). Eg: Service is described as “सर्विस” in Hindi
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
The format of the Trade Category Code defined should be alphanumeric and unique
TC1: Goods
TC2: Services
2
Trade Category Name (In either Language) should not contain any special characters
Goods: [Allowed]
#Goods! : [Not allowed]
Sr. No.
Code*
Structure Sub Type* (In English)
Structure Sub Type* (In Local Language)
Structure Type Code*
1
PUCCA
Pucca
पक्का
IMMOVABLE
2
KUTCHA
Kutcha
कच्चा
IMMOVABLE
3
HDV
Hand Driven Vehicle
हाथ चालित वाहन
MOVABLE
4
MDV
Motor-Driven Vehicle
मोटर चालित वाहन
MOVABLE
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Code
Alphanumeric
64
Yes
Unique code to identify each and every record uniquely
2
Structure Sub Type* (In English)
Text
256
Yes
Structure sub type in English
3
Structure Sub Type* (In Local Language)
Text
256
Yes
Structure sub type in local language e.g. in Hindi, Telugu etc.
4
Structure Type Code*
Reference
64
Yes
Unique code of structure type to establish the mapping with Structure Type
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of.
Sr. No
Trade Sub Type Code*
Trade Sub Type Name (In English)
New License Fee*
Renewal License Fee*
UOM
UOM From
UOM To
1
TRADE_SMALL_BAKERY
Small Bakery
2500
2000
Workers
1
20
2
TRADE_SMALL_BAKERY
Small Bakery
3000
2500
Workers
21
30
2
TRADE_MED_BAKERY
Medium Bakery
5000
4500
Workers
1
30
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Trade Sub Type Code
Reference
64
Yes
The Code assigned to the Trade Sub Type. Eg: TRADE_SMALL_BAKERY is assigned to Bakery
2
Trade Sub Type Name (In English)
Text
256
Yes
Name of the Trade Sub Type in English. Eg: Small Bakery
3
New License Fee
Decimal
(6,2)
Yes
The fee charged as when the license applied for the respective trade for the first time.
4
Renewal License Fee
Decimal
(6,2)
Yes
The fee charged as when the license applied for the respective trade for the renewal.
5
UOM
Text
64
No
The Units of Measurement” associated with the Trade. Eg: Workers is the UOM associated with the trade “Bakery”
6
UOM From
Integer
6
No
Initial Range from which the “Units of Measurement” is applicable for a Trade
7
UOM To
Integer
6
No
Final Range to which the “Units of Measurement” is applicable to a Trade
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
Trade Type Name (In either Language) should not contain any special characters
Small Bakery: [Allowed]
#Small_Bakery! : [Not allowed]
Sr. No | Usage Category Major Code* | Usage Category Major* (In English) | Usage Category Major* (In Local Language) |
1 | RESIDENTIAL | Residential | आवासीय |
2 | NONRESIDENTIAL | Non-residential | गैर आवासीय |
3 | MIXED | Mixed | मिश्रित |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Usage Category Major Code | Alphanumeric | 64 | Yes | This is a unique identifier being assigned to every major category. |
2 | Usage Category Major (In English) | Text | 256 | Yes | This is the description of the major category in the English Language. |
3 | Usage Category Major (In Local Language) | Text | 256 | Yes | This is the description of the major category in the Local Language e.g. Telugu, Hindi etc. |
Sr. No. | Checklist Parameter | Example |
Sr. No. | Checklist Parameter | Example |
1. | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Usage Category Sub Minor Code* | Usage Category Minor Code* | Usage Category Sub Minor* (In English) | Usage Category Sub Minor* (In Local Language) | Exemption Rate(In %) | Max Exemption Amount | Flat Exemption Amount | Effective From Date |
1 | RESIDENTIAL | RESIDENTIAL | Residential | निवास | 2 | 100 | 200 | 01-04-2020 |
2 | RETAIL | COMMERCIAL | Retail | खुदरा | 3 | 300 | 200 | 01-04-2020 |
3 | HOTELS | COMMERCIAL | Hotels | होटल | 5.1 | 200 | 300 | 01-04-2020 |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Usage Category Sub Minor Code | Alphanumeric | 64 | Yes | This is the unique code given to every category |
2 | Usage Category Minor Code | Alphanumeric | 64 | Yes |
3 | Usage Category Sub Minor (In English) | Text | 256 | Yes | This is the description of the sub minor category in English |
4 | Usage Category Sub Minor (In Local Language) | Text | 256 | Yes | This is the description of the sub minor category in Local Language |
5 | Exemption Rate (in % ) | Decimal | (5,2) | No | This column defines the % to which the property could be exempted |
6 | Max Exemption Amount | Decimal | (5,2) | No | This is the maximum amount which the property can be exempted from |
7 | Flat Exemption Amount | Decimal | (5,2) | No | This is the flat amount by which the property owner can be exempted |
8 | Effective From Date | Date | NA | Yes | This the date from which the exemption is applicable. |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No | Usage Category Minor Code* | Usage Category Minor* (In English)* | Usage Category Minor* (In Local Language) | Exemption Rate (In %)* | Max Exemption Amount | Flat Exemption Amount | Usage Category Major Code* |
1. | RESIDENTIAL | Residential | आवासीय | NA | 0 | 0 | RESIDENTIAL |
2. | COMMERCIAL | Commercial | व्यावसायिक | NA | 0 | 0 | NONRESIDENTIAL |
3. | INDUSTRIAL | Industrial | औद्योगिक | NA | 0 | 0 | NONRESIDENTIAL |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Usage Category Minor Code | Alphanumeric | 64 | Yes | This is the unique identifier that is given to every category. |
2 | Usage Category Minor (In English) | Text | 256 | Yes | This is the description of the Minor category in English. |
3 | Usage Category Minor (In Local Language) | Text | 256 | Yes | This is the description of the Minor Category in the Local Language. |
4 | Exemption Rate (in % ) | Decimal | (12,2) | No | This column defines the % to which the property could be exempted. |
5 | Max Exemption Amount | Decimal | (12,2) | No | This is the maximum amount which the property can be exempted from. |
6 | Flat Exemption Amount | Decimal | (12,2) | No | The amount that should be exempted for a particular category from the property tax. |
7 | Usage Category Major Code | Reference | 256 | Yes |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of. |
Sr. No. | Property Sub Type Code* | Property Sub Type* (In English) | Property Sub Type* (In Local Language) | Property Type Code* |
1 | SHAREDPROPERTY | Flat / Part of the building | फ्लैट / भवन का हिस्सा | BUILTUP |
2 | INDEPENDENTPROPERTY | Independent House / Whole Building | स्वतंत्र घर / पूरी इमारत | BUILTUP |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Property Sub Type Code | Alphanumeric | 64 | Yes | Unique Identifier for property sub type record |
2 | Property Sub Type (In English) | Text | 256 | Yes | Nomenclature of “Property Sub Type” in English |
3 | Property Sub Type (In Local Language) | Text | 256 | Yes | Nomenclature of “Property Sub Type” in local language e.g. Telugu, Hindi etc. |
4 | Property Type Code | Reference | 64 | Yes |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
The first level of classification of a property based on its construction is defined as Property Type. Generally, the property is divided into two types :
Built-up
Vacant Land
Mostly these property types are fixed and commonly used in all the ULBs across the country. Hence this data is not needed anymore in the template.
The data described in the above table is a sample.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify the “Property Types” that exists at a ULB/ State level.
Collect the above information and feed it below the “Property Type Description” column accordingly. The Description of Property Type must be provided as per the language specified in the respective column.
Add the “Property Type Code” respectively against the identified Property Type(s).
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
There is no separate checklist applicable to this entity.
The Usage category could be more detailed out on classifying them further and detailing more specifically on what kind of usage it is such as hotel, shops, community centre etc.
Below mentioned is the definition of the template which is used in data gathering:
Data given in the table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Gather all the details for this last classification of Usage Category Detail.
Figure out the codes, if not present abbreviate the description so that it creates relevancy between code and description.
Get the relations to the sub minor, minor and major.
Start filling the template with the codes and description of the usage Category detail and then followed by relative sub minor codes.
In the active column fill up weather the category is still active or not.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed on 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
In order to justify the Property Owner’s Special Category status, there are certain supporting documents that are required as the attachment of proof. These documents are crucial in terms of providing/ availing rebate on the property tax amount.
Data given in the table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify the “Owner Categories” that exists at a ULB/ State level.
Add the “Owner Type Code” respectively. The predefined format of the Owner Type Code only must be used from the “Owner Special Category” Master Sheet and not any random code. This will provide the base reference for the mapping of ownership type with the required documents.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Taxes are calculated based on the type of property and differ for each type.
For example, a residential property could have a different rate than a non-residential property, which could differ from year to year.
The tax could be a general property tax or a new type of tax introduced.
Data given in the table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Gather the details for all the types of properties and the type of taxes levied on them.
Start filling the type of tax and the property type from the first column and then start defining the rates and year of application.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
This is a further sub-classification of the ownership which details what is the ownership sub category, whether there is a single owner, multiple owner etc. . An example has been given in the attachments section of the page.
The data has to be collected for all the subcategories of ownership type present in the state. Below mentioned is the table of the template that is being used to gather data:
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts. First, get all the sub classifications for the listed category.
Get the codes and start filling the template.
Fill in the codes for the sub category in the 2nd column with there proper mapping of Ownership Type category(Parent level).
Repeat the steps for all the ownership type categories(Parent Level) .
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Unit rates are also an important part of property tax. The property tax for a property is counted on the are that the property is covering. These unit rates could differ from ULB to ULB, Ward to Ward, Mohalla to Mohalla and then can be based on different parameters such as Road Type, Property Construction Type etc.
Data given in the table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Figure out on what boundary types are the property tax unit rates being defined and start filling that with its code and its name in English in the boundary code and boundary code name column.
In case there are more parameters on which the unit rates are being classified such as road type, construction type is being classified, start making a different column for the same starting from parameter 1, parameter 2…
Make sure you replace the column name from parameter 1 to the classification on which it is being classified.
At the end fill up the unit rates column.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
The Owner’s Special Category represents those property owners whose property belongs to the “reserved” category as defined by the state. These special categories are entitled to a rebate in the property tax amount, as per the defined categories by a State/ ULB.
Data given in the table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify the “Owner Categories” that exists at a ULB/ State level.
Add the “Owner Type Code” respectively.
Add a description to the Owner Type Name, as per the required language.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Ownership is the state or fact of exclusive rights and control over property, which may be an asset, including an object, land or real estate, or intellectual property. Ownership involves multiple rights, collectively referred to as title, which may be separated and held by different parties. Further, the ownership can be categories based on the nature and type of the parties property is owned by e.g Property owned by an individual who is the resident of the city, by an institution etc.
Given below is the sample data table from the template in which the data has to be collected:
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Firstly Identify all the categories of the owners present in the state.
After which identify the codes of all the categories, if not present then form an abbreviated version of the code.
Start filling the template with the codes in the second column, its English name in 3rd and Local Language name in 4th.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
DIGIT Public Grievance Redressal system abbreviated as PGR is a mechanism commonly used to receive and act on complaints or grievances reported by residents of a city/ ULB enabling prompt actions on any issue raised by them and to avail services more effectively.
DIGIT PGR offers a variety of features to make complaint lodging and redressal easy for residents and employees of a ULB. List of standard features is given below.
Web and mobile interface to lodge, track, reopen, and update feedback on the complaint made by the citizen.
Web and mobile interface to comment, forward, and close the complaint by the ULB employees.
None
The request to change in owners associated with a property in municipal record is known as mutation or transfer of title. To process this request and make the necessary changes in the property records ULBs charge for a fee which is calculated based on the fee defined based on a few parameters.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify usage wise mutation fee amount and fill into the given template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
This checklist covers all the activities which are common across the entities.
Not Applicable
A grievance is a formal complaint submitted to a ULB. Something wrong or something believed to cause distress in services provided by the ULB is considered as grounds for complaint. Grievances which are closely associated with ULB’s functions classified into different buckets, that different sections of ULB deal with are known as grievance types.
Data given in the table is a sample 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 all different types of grievances on the basis of ULB’s functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Rebate is provided on early payments which are done in month April in every financial year at the rate of 5% when the property is paid fully up to prevailing financial year demand.`
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Get the rebate rate and the amount involved with it.
Get the year and the end date for the rebate period.
Start filling the template from the right which is the rebate percentage and end it with the rebate end date.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Not Applicable.
The penalty is defined as an amount which is charged to the citizen in violation of any rule. There would be multiple penalties defined associated with different rules and acts. Penalty rate decides on how and what amount to be calculated for a penalty.
Within DIGIT, the calculation of the penalty amount is configurable at both the State & ULB level.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify all the different types of penalty amounts (by percentage/ by a flat amount) etc and fill them in the provided columns respectively.
Fill in the details of the financial year/ date from which the type of defined penalties will be applicable.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
This is the amount which is calculated on percentage defined and collected from citizen if failed to pay the property tax demand on time. It is also called the late payment penalty.
Data given in the table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Get the interest rate that is being levied over a period of time.
Get the year as well as the date from which this was brought in place.
Start filling the data from the interest rate followed by the rest of the details.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
Buildings can be classified into various categories on the basis of their usage. Different fire stations can have different ontology for building usage type but in order to provide citizens and businesses a uniform experience, it is important that the building usage types ontology is standardized at the state level.
For this purpose, the states can also use the National Building Code of India (NBC), a comprehensive building code, which is a national instrument providing guidelines for regulating the building construction activities across the country.
Data given in the above table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify all the different types of buildings on the basis of their usage that are being catered by the fire station in their area and start filling them in the Building Usage Type column.
Next, give each building usage type a unique code and enter the code in the Building Usage Type Code column, next to the Building usage type.
Map the data filled in the building usage types column to the building usage type and building groups as per the national building code.
Record the appropriate group and building type from NBC in the Building Group (as per NBC) and Building Usage Type (as per NBC) respectively.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
This is the relationship between sub minor and
This is the mapping between the minor’s and major’s of the usage category which can be found
Property Type code referring to the
To see common checklist refer to the page consisting of all the activities which are to be followed to ensure completeness and quality of data.
Sr. No.
Property Type Code*
Property Type* (In English)
Property Type* (In Local Language)
1
BUILTUP
Built-Up
निर्माण
2
VACANT
Vacant Land
खाली जमीन
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Property Type Code
Alphanumeric
64
Yes
Unique Identifier for property type record
2
Property Type (In English)
Text
256
Yes
Nomenclature of “Property Type” in English
3
Property Type (In Local Language)
Text
256
Yes
Nomenclature of “Property Type” in local language e.g. Telugu, Hindi etc
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr.No.
Usage Category Detail Code*
Usage Category Sub Minor Code*
Usage Category Detail (In English)*
Usage Category Detail (In Local Language)*
Effective From Financial Year*
1.
RED
RESIDENTIAL
आवासीय
2019-20
2.
NONRED
HOTELS
होटल पेईग गेस्ट हाउस 10 कमरों तक(बेगैर वातानुकूलित)
2018-19
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Usage Category Detail Code
Alphanumeric
64
Yes
This column ideally contains the code for which the Usage Category Detail is being categorized
2
Usage Category Sub Minor Code
Alphanumeric
64
Yes
This is the mapping between detail and Sub Minor Code. Refer Sub Minor entity for more detail
3
Usage Category Detail Description (English)
Text
256
Yes
Description/ Detail of the detail code in which the category is being classified in the English Language
4
Usage Category Detail Description (Local Language)
Text
256
No
Description/ Detail of the detail code in which the category is being classified in Local Language. e.g. Hindi, Telugu etc.
5
Effective From Financial Year
Numeric
(12,2)
Yes
This is the year from which the category detail has come into effect for property tax
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Owner Type Code*
Ownership Documents Description (English)*
Ownership Documents Description (Local Language)*
1
FREEDOMFIGHTER
Certificate issued by DC/ Competent Authority
डीसी / सक्षम प्राधिकारी द्वारा जारी प्रमाण पत्र
2
WIDOW
Death Certificate + Spouse proof
डेथ सर्टिफ़िकेट + जीवनसाथी प्रमाण
3
HANDICAPPED
Certificate of Handicap by a competent authority
सक्षम प्राधिकारी द्वारा विकलांग का प्रमाण पत्र
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Owner Type Code
Reference
64
Yes
Unique Identifier assigned for the Owner Type. For example, Freedom Fighter is represented as FREEDOMFIGHTER
2
Ownership Documents Description (English)
Text
256
Yes
Nomenclature of “Owner Documents” in English. For ownership type Freedom Fighter, the document required is the certificate issued by DC/ Competent Authority
3
Ownership Documents Description (Local Language)*
Text
256
Yes
Nomenclature of “Owner Documents” in Hindi
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
The format of the Owner Type Code defined should be Text
War Widow is represented as WIDOW
2
Owner Type Code should not contain any special characters
WIDOW: [Allowed]
#WIDOW! : [Not allowed]
Sr. No.
Tax Head*
EffectiveFromFY*
Percentage*
1
General Tax (Residential)
2019-20
10
2
General Tax (Non-residential)
2019-20
9
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Tax Head
Alphanumeric
64
Yes
The type of tax and the property on which the tax is being levied
2
EffectiveFromFY
Numeric
(12,2)
Yes
The year from which the tax rate is being defined
3
Percentage
Numeric
(12,2)
Yes
The rate at which the tax is to be levied
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No
Ownership Sub Category Code*
Ownership Category Code*
Ownership Sub Category* (In English)
Ownership Sub Category* (In Local Language)
1.
SO
INDIVIDUAL
Single Owner
एकल स्वामी
2.
MO
INDIVIDUAL
Multiple Owner
मल्टीपल ओनर
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Ownership Sub Category Code
Alphanumeric
64
Yes
This is the code that is being used to categorize the sub type
2
Ownership Category Code
Alphanumeric
64
Yes
This is the mapping between the Ownership Category and Sub category
3
Ownership Sub Category (In English)
Text
256
Yes
Description of the ownership Sub type in the English Language
4
Ownership Sub Category (In Local Language)
Text
256
Yes
Description of the ownership Sub type in Native Language
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
There should be a mapping code between the sub category (child) and Property Tax: Ownership Category (parent level), no child can be left without a parent
-
2
Make sure that no code which is not mentioned in the ownership category classification (parent) can be used
-
Sr. No.
Boundary Code*
Boundary Name*
Parameter 1*
Parameter 2
Unit Rate*
1
M001
Haldwani Mandir
PUCCA
< 12 m
1.50
2
M001
Haldwani Mandir
SEMIPUCCA
>= 12 m and <= 24 m
1.75
3
M001
Haldwani Mandir
KUCCHA
> 24 m
2.00
4
M002
Kali Mata Mandir Road
SEMIPUCCA
< 12 m
3.00
5
M002
Kali Mata Mandir Road
SEMIPUCCA
>= 12 m and <= 24 m
10.00
6
M002
Kali Mata Mandir Road
SEMIPUCCA
> 24 m
20.00
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Boundary Code
Alphanumeric
64
Yes
The code of the boundary that is being used, depending upon the client's requirement it could be Mohalla or Ward but has to be from the data collected here
2
Boundary Name (In English)
Text
256
Yes
The name/description of the boundary that is being used for the classification. The names have to be from the data collected here
3
Parameter 1
Alphanumeric
64
Yes
This has to be the parameter 1 code on the basis of which the unit rates are being defined
4
Parameter 2
Alphanumeric
64
No
This is the second parameter(if available) on the basis of which the unit rates are being defined
5
Unit rates
Decimal
(5,2)
Yes
The unit rate
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Owner Type Code*
Owner Type Name (English)*
Owner Type Name (Local Language)*
1
FREEDOMFIGHTER
Freedom Fighter
स्वतंत्रता सेनानी
2
WIDOW
Widow
विधवा
3
HANDICAPPED
Handicapped Persons
विकलांग व्यक्ति
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Owner Type Code
Alphanumeric
64
Yes
Unique Identifier for Owner Type
2
Owner Type Name ( In English)
Text
256
Yes
Nomenclature of “Owner Type” in English
3
Owner Type Name (In Local Language)
Text
256
Yes
Nomenclature of “Owner Type” in the local language as Telugu, Hindi, etc.
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
The predefined format of the Owner Type Code only must be used and not any random code
-
Sr. No
Ownership Category Code*
Ownership Category* (In English)
Ownership Category* (In Local Language)
1
INDIVIDUAL
Individual
व्यक्तिगत
2
COMPANY
Company
कंपनिगत
3
SOCIETY
Society
सहकारी समिति
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Ownership Category Code
Alphanumeric
64
Yes
Code to uniquely identify the ownership category record
2
Ownership Category (In English)
Text
256
Yes
This is the name of the ownership category in the English language
3
Ownership Category (In Local Language)
Text
256
Yes
This is the name of the ownership category in the local language
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No. | Property Usage Code* | Flat Fee Amount* |
1 | RESD | 1000 |
2 | NONRESD | 5000 |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Property Usage Code | Alphanumeric | 64 | Yes | Property usage code - the fee depends upon the type of property usage |
2 | Flat Fee Amount | Decimal | (5,2) | Yes | Mutation fee flat amount |
Sr. No. | Grievance Type Code* | Grievance Type* (In English) | Grievance Type* (In Local Language) |
1 | SLS | Street Lights | स्ट्रीट लाइट |
2 | GBG | Garbage | कचरा |
3 | DRN | Drains | नाली |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Grievance Type Code* | Alphanumeric | 64 | Yes | Unique code is given to the grievance type. This code is used to uniquely identify the complaint type and as a reference in the child record. E.g. SLS given above in data table to identify Street Lights complaint type |
2 | Grievance Type* (In English) | Text | 256 | Yes | This is the text or string stating grievance type in English |
3 | Grievance Type* (In Local Language) | Text | 256 | Yes | This the text or string stating the grievance type in local language like Hindi, Telugu etc. whatever is applicable |
Sr. No. | Activity | Example |
1 | Grievance type code should not have any special characters other than ‘-', and '_’ | SLS - [Allowed] SLS1 - [Allowed] SL#1 - [Not Allowed] |
2 | Grievance type should be text and should not contain special characters other than ‘-', '_', SPACE | Street Light - [Allowed] Street_Light# -[Not allowed] |
RebateRate(In %)* | MaxRebateAmount* | FlatAmount* | FromFY* | RebateEndDate (DD/MM)* |
-10% | 300 | 200 | 2018-19 | 01/10 |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | RebateRate(In %) | Numeric | (12,2) | Yes | The percentage at which the rebate has to be provided |
2 | MaxRebateAmount | Numeric | (12,2) | Yes | The maximum amount of rebate that can be given |
3 | FlatAmount | Numeric | (12,2) | Yes | The flat amount which is levied |
4 | FromFY | Numeric | (12,2) | Yes | The year for which the rebate is being given |
5 | RebateEndDate (DD/MM) | Numeric | (12,2) | Yes | The date at which the rebate period ends |
Sr. No. | Penalty Head | *Penalty Rate (In % ) | Minimum Penalty Amount | *Flat Amount | *From Financial Year | *Start Date |
1 | Late assessment | 12.5 | 1000 | 500 | 2019-20 | 01-04-2019 |
2 | Unauthorized Construction | 100 | 5000 | 5000 | 2019-20 | 01-04-2019 |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Penalty Rate | Decimal | (12,2) | Yes | The Penalty charged by percentage |
2 | Min Penalty Amount | Decimal | (12,2) | No | The Minimum amount charged as penalty |
3 | Flat Amount | Decimal | (12,2) | Yes | The pre-decided amount that must be charged as penalty on the amount |
4 | From Financial Year | Decimal | (12,2) | Yes | The year from which the penalty rate begins |
5 | Penalty Start Date | Decimal | (12,2) | Yes | The Date from which the penalty amount will be applicable within a financial year |
Rate | Minimum Amount | Flat Amount | Maximum Amount | From FY* | Start Date* |
18% | 200 | 120 | 20000 | 2014-15 | 01/01/2019 |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Rate | Decimal | (12,2) | Yes | The interest rate percentage. |
2 | Minimum Amount | Decimal | (12,2) | No | Min amount of interest penalty levied. |
3 | Flat Amount | Decimal | (12,2) | No | The flat amount which is levied. |
4 | Maximum Amount | Decimal | (12,2) | No | The maximum amount which could be levied. |
5 | From FY | Decimal | (12,2) | Yes | The year from which the interest rate begins. |
6 | Start Date | Decimal | (12,2) | Yes | The date from which this penalty has to start. |
Sr. No. | *Building Usage Type Code | *Building Usage Type | *Building Group (as per NBC) | *Building Usage Type (as per NBC) |
1 | BU01 | Residential | Group A | Residential |
2 | BU02 | Educational Institute | Group B | Educational |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | Building Usage Type Code | Alphameric | 64 | Yes | The code is given to the building usage type by the Fire Station. Eg: BU01 for Residential, BU02 for educational institute |
2 | Building Usage Type | Text | 256 | Yes | Name of building usage type by the Fire Station. Eg: Residential, Educational Institute |
3 | Building Group (as per NBC) | Text | 256 | Yes | The code is given to the building usage type as per NBC. Eg: Group A, Group B |
4 | Building Usage Type (as per NBC) | Text | 256 | Yes | Name of building usage type as per NBC. Eg: Residential, Educational |
Sr. No. | Checklist Parameter | Example |
1 | Building Usage Type Codes that are defined by the Fire Station should be alphanumeric and Unique | BU01: Residential BU02: Educational Institute |
2 | Building Usage Type should not contain any special characters | Residential : [Allowed] #Residential! : [Not allowed] |
The Fire No-Objection Certificate (NOC) application, developed on the eGov-DIGIT platform, makes the process of obtaining a Fire NOC easy, smooth, and transparent. It eliminates the current manual process by automating and streamlining it, thus providing a better citizen service experience with the Urban Local Body (ULB) and Fire station employees.
Features offered to the citizens-
Apply for provisional or new fire NOC or renew existing Fire NOC.
Upload all the relevant documents required for the certificate.
Make payment for the Fire NOC using the online payment gateway.
Receive notifications and alerts by SMS, whenever the status of the application changes.
Download Fire NOC
Features offered to the Employees-
Flexible role-based workflow.
Configurable fee calculation mechanism.
Dashboard with application statistics.
Search applications using configurable parameters.
Receipt Register
Application Status
Escalation of a grievance is about updating the non-redressal of grievance to next level officer in the escalation level while the responsibility of resolving the grievance lies with the last mile employee who has received the grievance at first. Escalation matrix is defined based on the levels of escalations and the SLAs defined at each and every level.
This feature is in the development plan bucket.
This feature is in the development plan bucket.
This feature is in the development plan bucket.
This feature is in the development plan bucket.
Routing of the grievance is defined as assigning the grievance to the last mile employee from a ULB who has been designated with the responsibility to address it within the stipulated time frame. Assigning a grievance to an employee is role-based.
No data is required here to configure the routing matrix. It is simple UI based user-role mapping in the system.
Not applicable.
Not applicable.
Not applicable.
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of. |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
The first step is to identify all the fire stations within the state. It is important to note that all the ULBs may not have a fire department. Generally, the bigger ULBs of the state have a fire department that caters to that ULB at the same time to all the surrounding smaller ULBs and rural areas as well.
Data given in the above table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify all the fire stations operating in the state and enter their names in the Fire Station Name column
Next, give each fire station a unique code and enter that code in the Fire Station Code column.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Grievance sub-type defines the second level of classification of grievances which are related to ULB’s functions and adds detail to a grievance type.
The data table below represents the structure of the template and given here to explain the template in detail.
Data given in the table is a sample 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 all different subtypes of grievances on the basis of ULB’s functions and grievance types.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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.
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.
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.
This checklist covers the activities which are specific to the entity.
After the building usage types are identified, the next activity is to identify the building sub usage types.
Buildings types can be further classified into various subcategories to go into the granular level of their usage details. The National Building Code of India (NBC) also classifies the building's usage type into the sub usage types which can be seen in the attachment.
Data given in the above table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify and add all the different sub usage types for each building group that are being catered by the fire station in the Building Sub Usage Type column.
Next, give each building Sub Usage type a unique code and enter the code in the Sub Usage Type Code column, next to the Building Sub Usage type.
Map the data filled in the building sub usage type column to the building sub usage type and Subdivision as per the national building code.
Record the appropriate subdivision and building sub usage type from NBC in the Subdivision (as per NBC) and Building Sub Usage Type (as per NBC) respectively.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
The Service Subcategory refers to the secondary level of services. For instance, Sanitation Tax service describes the specific tax collection service existing at the ULB level.
Before creating the Service Subcategory make sure you have created the list. Map the Service Subcategory to the corresponding Service Category.
Data given in the table is a sample 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 all different types of service subcategory on the basis of ULB’s functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
The mCollect module is designed to facilitate the ULBs process miscellaneous types of payments. Miscellaneous payments may include parking fees, advertising fees, etc. The module objective is to process and record payment collections on account of miscellaneous heads within the ULBs. This makes it easy to track payment receipts and generate reports for administrative purpose.
Capture details of payment collection
Generate and print the collection receipt
Access to dashboard analytics
Generate reports for administration
None
Receipt Register
Cancelled Receipt Register
In all most all the states fire stations serve both the urban as well as the rural areas, therefore we need to prepare the masters for both urban areas as well as the rural areas being served in the state.
Data given in the above table is a sample data.
Urban Area
Rural Area
Urban Areas
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify the districts where fire services are provided and enter their names in the District Name column.
Give each district a unique code and enter the code in the District Code column, next to the District Name.
Identify all the ULBs within each district where fire services are provided and enter their name in the ULB Name column next to it's District Name.
Give each ULB a unique code and enter the code in the ULB Code column.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
Rural Areas
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify the districts where fire services are provided and enter their names in the District Name column.
Give each district a unique code and enter the code in the District Code column, next to the District Name.
Identify all the Sub District within each district where fire services are provided and enter their name in the Sub District Name column next to it's District Name.
Give each Sub District a unique code and enter the code in the Sub District Code column.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
After the building usage and sub usage ontology has been defined for all the Firestations, the next step is to collect the Fire NOC fee that the citizens have to pay to obtain the certificate.
The Fire NOC fee is dependent on the following parameters:
Fire Station
Building Usage type
Building Sub usage type
Fire NOC type
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter the Fire station codes of all the fire stations that are there in the Fire Station master, in the ‘Fire Station Code Column’.
Next, enter the Building usage types codes and building sub usage type codes that being catered by the fire station, next to the Fire Station Code.
Identify the fees that the fire stations are charging to issuing a new, provisional, or renewed Fire NOC for every building usage and sub usage combination.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
After we have created the fire station master, the next step would be to map the Districts, Sub-Districts, and ULBs with the fire stations. The two points that are very important to note here are:
All the ULBs in the state may not have a fire department.
Usually, only the larger ULBs in the state have a fire department that caters to that ULB at the same time to all the surrounding smaller ULBs and rural areas as well.
Note: Data given in the above table is a sample data.
Urban Area
Rural Area
Urban Area - Fire Mapping
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter the district codes of all the districts where fire services are provided, in the ‘District Code Column’.
Next, enter the ULB codes of all the ULBs within a particular district where the fire services are provided in the 'ULB Code Column'.
Identify the fire stations that are serving each District - ULB combination and enter their name in the Fire Station column along with its code in the Fire Station Code.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
Rural Area - Fire Mapping
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter the district codes of all the districts where fire services are provided, in the ‘District Code Column’.
Next, enter the sub-district codes of all the sub-district within a particular district where the fire services are provided in the 'Sub District Code Column'.
Identify the fire stations that are serving each District - Sub District combination and enter their name in the Fire Station column along with its code in the Fire Station Code.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Service Category is a comprehensive list of services existing for the specific State/ULB. Service Category basically defines the miscellaneous revenue collection heads. Example - Rental, Entry Fees, User Charges etc.
Service categories are defined at a global level for different types of revenues. Payment collection and processing for certain services like property tax and trade licenses are done through the individual modules. The mCollect module processes payments for other miscellaneous services.
The Service Category masters list allows States/ULBs to identify the miscellaneous services for which payments and collections can be processed.
Data given in the table is a sample 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 all different types of service categories on the basis of ULB’s functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Verify the data once again by going through theand taking care of each and every point mentioned in the checklist.
Sr. No.
*Fire Station Code
*Fire Station Name
1
FS01
Patiala
2
FS02
Amritsar
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Fire Station Code
Alphameric
64
Yes
The code is given to the fire station by the state team. Eg: FS01 For Patiala Fire station, FS02 for Amritsar Fire station
2
Fire Station Name
Text
256
Yes
Name of the fire station. Eg: Patiala, Amritsar
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
Fire Station Codes that are defined by the state team should be alphanumeric and Unique
FS01: Amritsar
FS02: Jalandhar
2
Fire station Name should not contain any special characters
Amritsar : [Allowed]
#Amritsar! : [Not allowed]
Sr. No.
Grievance Subtype Code*
Grievance Subtype * (In English)
Grievance Subtype* (In Local Language)
Grievance Type Code*
Department Code*
SLA* (In Hours)
1
SLS01
No Street Light
कोई स्ट्रीट लाइट नहीं है
SLS
TP
48
2
SLS02
Street Light Not Working
स्ट्रीट लाइट काम नहीं कर रही है
SLS
TP
48
3
WNS01
Illegal Discharge of Sewage
सीवेज का अवैध निपटान
WNS
PHS
48
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Grievance Subtype Code
Alphanumeric
64
Yes
Unique code is given to the grievance subtype and is used to uniquely identify the complaint subtype. E.g. SLS01 given above in data table to identify Street Lights complaint subtype
2
Grievance Subtype (In English)
Text
256
Yes
This is the text or string stating grievance subtype in English
3
Grievance Subtype (In Local Language)
Text
256
Yes
This the text or string stating the grievance subtype in local language like Hindi, Telugu etc. whatever is applicable
4
Grievance Type Code
Reference
64
Yes
Reference to parent grievance type code from the Grievance Type entity
5
Department Code
Reference
64
Yes
Unique department code from the ULB's Departments entity
6
SLA (In Hours)
Decimal
(5,2)
Yes
This field defined the service level agreements in hours. This the time within which a complaint raised to be resolved
Sr. No.
Activity
Example
1
Grievance Subtype code should not have any special characters other than ‘-', and '_’
SLS01 - [Allowed]
SLSA - [Allowed]
SLS#1 - [Not Allowed]
2
Grievance Subtype should be text and should not contain special characters other than ‘-', '_', SPACE
No Street Light - [Allowed]
No Street Light# -[Not allowed]
Sr. No.
*Building Usage Type Code
*Sub Type Code
*Building Sub Usage Type
*Sub Divison (as per NBC)
*Building Sub Usage Type (as per NBC)
1
BU01
BSU01
Hotel
A4
Hotel
2
BU01
BSU02
Apartment
A5
Apartment House
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Building Usage Type Code
Reference
64
Yes
The codes are given to the building usage type in the building usage type master
2
Sub Type Code
Alphameric
64
Yes
The code is given to the building sub usage type by the Fire Station. Eg: BSU01 for Hotel, BSU02 for Apartment Houses
3
Building Sub Usage Type
Text
256
Yes
Name of subcategories within each building usage type as per the fire station. Eg: Hotel, Apartment Houses
4
Sub Divison (as per NBC)
Alphameric
64
Yes
The code is given to the building sub usage type as per NBC. Eg: Subdivision A4, A5
5
Building Sub Usage Type (as per NBC)
Text
256
Yes
Name of subcategories within each building usage type as per NBC. Eg: Hotel, Apartment House
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
The Building Usage Type Code should be similar to the ones defined in the building usage type master
BU01: Residential
BU02: Educational
2
Building Sub Usage Type Codes that are defined by the Fire Station should be alphanumeric and unique
BSU01: Hotel
BSU02: Apartment
3
Building Sub Usage Type should not contain any special characters
Hotel : [Allowed]
#Hotel! : [Not allowed]
Sr. No. | Checklist Parameter | Example |
1 | The Service Category & Subcategory Name should not contain any special characters | Other Fee and Fines : [Allowed] #Other Fee and Fines! : [Not allowed] |
Sr. No. | *District Code | *District Name | *ULB Code | *ULB Name |
1 | DC01 | Amritsar | ULB01 | Amritsar |
2 | DC01 | Amritsar | ULB02 | Ajnala |
Sr. No. | *District Code | *District Name | *Sub District Code | *Sub District Name |
1 | DC02 | Patiala | SDC01 | Jhabal |
2 | DC02 | Patiala | SDC02 | Patran |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | District Code | Alphameric | 64 | Yes | The code is given to the district by the state team. Eg: DC01 for Amritsar, DC02 Patiala. |
2 | District Name | Text | 256 | Yes | Name of the district Eg: Amritsar, Patiala |
3 | ULB Code | Text | 256 | Yes | The code is given to the district by the state team. Eg: ULB01 for Amritsar, ULB02 Ajnala |
4 | ULB Name | Alphameric | 64 | Yes | Name of the ULB Eg: Amritsar, Ajnala |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | District Code | Alphameric | 64 | Yes | The code is given to the district by the state team. Eg: DC01 for Amritsar, DC02 Patiala |
2 | District Name | Text | 256 | Yes | Name of the district Eg: Amritsar, Patiala |
3 | Sub-district Code | Text | 256 | Yes | The code is given to the subdistrict by the state team. Eg: SDC01 for Jhabal, SDC02 Patran |
4 | Sub-district Name | Alphameric | 64 | Yes | Name of the sub-district Eg: Jhabal, Patran |
Sr. No. | Checklist Parameter | Example |
1 | District Codes, Sub District Codes, and ULB Codes should be alphanumeric and Unique. | ULB01: Amritsar SDC01: Jhabal |
2 | District Name, Sub District Name, and ULB Name should not contain any special characters. | Amritsar : [Allowed] #Amritsar! : [Not allowed] |
Sr. No. | *Fire Station Code | *Building Usage Type Code | *Sub Type Code | *Fire NOC Fee |
New | Provisional | Renew |
1 | FS01 | BU01 | BSU01 | 1000 | 200 | 800 |
2 | FS02 | BU01 | BSU02 | 2000 | 1000 | 2000 |
Sr. No. | *District code | *ULB Code | *Fire Station code | *Fire Station Name |
1 | DC01 | ULB01 | FS02 | Amritsar |
2 | DC01 | ULB02 | FS02 | Amritsar |
Sr. No. | *District code | *Sub District code | *Fire Station Code | *Fire Station Name |
1 | DC02 | SDC01 | FS01 | Patiala |
2 | DC02 | SDC02 | FS01 | Patiala |
Sr. No. | Service Category Code* | Service Category (In English)* | Service Category (In Local Language)* |
1 | OFF00034 | Other Fee and Fines | अन्य शुल्क और जुर्माना |
2 | SAC00456 | Service and Administration Charges | सेवा और प्रशासन प्रभार |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Service Category Code | Alphanumeric | 50 | Yes | Unique Identifier for “Service Category” and also a reference for the child mapping |
2 | Service Category (English) | Text | 250 | Yes | Name of “Service Category” in English. This will help the user select the category name to process the payment collection |
3 | Service Category (Local Language) | Text | 250 | Yes | Name of “Service Category” in Local Language. This will help the user select the category name to process the payment collection |
Sr. No. | Checklist Parameter | Example |
1 | The Service Category should not contain any special characters | Other Fee and Fines : [Allowed] #Other Fee and Fines! : [Not allowed] |
Sr. No. | Service Subcategory Code* | Service Subcategory (In English)* | Service Subcategory (In Local Language)* | Service Category Code* | Service Category |
1 | SANT0045 | Sanitation Tax | स्वच्छता कर | TAX00147 | Taxes |
2 | PEF0478 | Parks Entry Fee | पार्क प्रवेश शुल्क | EFEE0785 | Entry Fee |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Service Subcategory Code | Alphanumeric | 50 | Yes | Unique Identifier for “Service Subcategory”. |
2 | Service Subcategory (English) | Text | 250 | Yes | Name of “Service Subcategory” in English. This will help the user to select the Subcategory name for processing the payment collection |
3 | Service Subcategory (Local Language) | Text | 250 | Yes | Name of “Service Subcategory” in Local Language. This will help the user to select the Subcategory name for processing the payment collection |
4 | Service Category Code | Alphanumeric | 50 | Yes | Unique Identifier for “Service Category” |
5 | Service Category | Text | 250 | No | The listed Service Subcategory is mapped to the appropriate Service Category |
Manual processes related to scrutiny, approval, or rejection of building construction or renovation plans is a time-consuming process for both citizens and employees. The DIGIT OBPAS module automates the entire building plan approval process right from enabling online submission of plans, documents to initiating verification and final approval of the plan. Citizens can now track their plan approval or inspection status, pay fees online, download and print the Permit Order and Occupancy Certificate online. The module streamlines the building plan approval system with configurable workflows for effective management through different phases of approval.
Centralized login page for citizen, officials and stakeholders
Citizen functionalities
Online application submission - New construction
Occupancy certificate request
Field Inspection Report Capture
Pay fee online and generate permit order online
Inspection of applications and online status
Configurable workflow
Auto fee calculation
Online and offline payment collection
Rejection process
Revocation process
Configurable functionalities
None as of now.
Sr. No | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of. |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | Fire Station Code | Reference | 64 | Yes |
2 | Building Usage Code | Reference | 64 | Yes |
3 | Building Sub Usage Code | Reference | 64 | Yes |
4 | Fire NOC Fee | Integer | 6 | Yes | The amount that will be charged for each Fire NOC type. For Eg: 2000 for new, 0 for Provisional and 1000 for renew |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | Fire station codes, Building Usage code, and Sub usage Codes have to be similar to the codes entered in their respective masters |
2 | The Fire NOC fee should be an integer, without having any alphabet or symbol preceding or succeeding it | 2000: [Allowed] Rs. 2000 : [Not allowed] 2000 Rs. : [Not allowed] |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | District Code | Reference | 64 | Yes |
2 | ULB Code | Reference | 64 | Yes |
3 | Fire Station Code | Reference | 64 | Yes |
4 | Fire Station Name | Reference | 256 | Yes |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | District Code | Reference | 64 | Yes |
2 | Sub District Code | Reference | 64 | Yes |
3 | Fire Station Code | Reference | 64 | Yes |
4 | Fire Station Name | Reference | 256 | Yes |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | District Codes, Sub-district Codes, and ULB codes have to be similar to the codes entered in the Area Master |
2 | The Fire Station Name and the Fire station Code should be similar to the name and codes entered in the Fire Station Master |
Sr. No | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
States and ULBs can configure their web portal to deploy the DIGIT portal effectively. State-level and ULB level web portal configuration details are covered in this section.
Service Subcategory is mapped to relevant GL code to help capture the accounting-related parameters for each service subcategory. The same is used to pass the accounting vouchers into accounting and finance system.
Data given in the table is a sample 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 all different types of service subcategory GL code on the basis of ULB’s functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity. There is no entity-specific checklist activity applicable.
State Portal is a website for the state. Any content or information which is displayed on this site needs to be provided by the State.
This document is to define a template to collect the portal content and information. And to help in filling up the content into the template.
This section talks about the template and the table given below represents the template. Full template to fill with the portal content is attached with this page at the last into attachments sections.
This section consists of the information about the meaning of each and every section in the template and then how to fill the templates in a few easy steps.
Below table consist of a standard section of any portal. The additional section as required will have to capture as part of customization.
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning given in this document under section 'Data Definition'.
Make sure all the headers, its data type, field size and its definition/ description are 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.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
The list of services in the OBPS module refers to the various types of services offered to citizens or end-users. The Data Table below contains an indicative list of services and details required to configure the building plan approval module.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify the services provided by DIGIT OBPAS system and enter then into the template with other configurable parameters given in the template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
A ULB portal is a specially designed website for a ULB that serves as the single point of access for information. It can also be considered a library of personalized and categorized content. A ULB web portal helps in search navigation, personalization, notification and information integration, and often provides features like task management, collaboration, and business intelligence and application integration.
This section tells about the template and table given below represents the template. Full template to fill with the portal content is attached with this page at the last into attachments sections.
Data given in the table is a sample data.
This section consists the information about the meaning of each and every section in the template and then how to fill the templates in a few easy steps.
Below table consist of a standard section of any portal. The additional section as required will have to capture as part of customization.
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning given in this document under section 'Data Definition'.
Make sure all the headers, its data type, field size and its definition/ description are 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.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
This checklist covers all the activities which are specific to the entity.
Building Occupancy classifications help in categorizing structures based on the proposed use of the building. Occupancy categories determine the required permits and approvals. The Building Occupancy types data is hence a vital parameter used to define approval workflows in the OBPS module. Refer to the to view the prescribed list of occupancy types.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
The Building Usage data allows States/ULBs to classify the buildings based on occupancy types, sub-types and its actual usage. Permits and approval process are dependent on the Usage type. The Data Table provides the details required to configure the Building Usage types. Refer to the to view the prescribed list of usage types.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify all the building usage and its mapping with sub occupancy and then fill into the template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
Inspection checklist contains the list of activities which a field inspector should consider and check while on the field. The checklist is configurable at the State/ULB level.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify all the checkpoints service wise and then fill into the given template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
Stakeholders refer to the technical persons and end-users of the OBPS system. The Stakeholders Type masters list allows the registration of stakeholders in the OBPS system. The list of stakeholders varies from one State/ULB to another.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
Service-wise documents list tells about the documents required for processing of listed services. Citizens can view the checklist based on the selected service. States/ULBs can configure the list of supporting documents required for each service.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify the documents which are needed to avail the services and fill into the given template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
Building Sub Occupancy details refer to sub-categorization of primary occupancy types. For instance, residential buildings can be further classified as apartments or old age homes depending on the specific usage of the buildings. Refer to the to view the prescribed list of sub-occupancy types.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
The code given to each Fire station in the
The code given to each Fire station in the
The code given to each Fire station in the
The code given to each district in the
The code given to each district in the
The code given to each Fire station in the
The Fire Stations listed in the
The code given to each district in the
The code given to each sub-district in the
The code is given to each Fire station in the
The Fire Stations listed in the
Identify the occupancy which is applicable. Refer to to learn more about occupancy types and names.
Identify the stakeholders and fill into the given template. Refer to the for more details on stakeholder types and defined limitations.
Identify the sub occupancy which is applicable. Refer to to learn more about occupancy types and names.
Sr.No
Service Subcategory Code*
Service Subcategory (English)*
Service Subcategory (Local Language)*
GLCODE*
ULB CODE
DEPT CODE
FUND Code
1
PEF0478
Parks Entry Fee
पार्क प्रवेश शुल्क
1404007
1001
DEPT_1
01
2
SANT0045
Sanitation Tax
स्वच्छता कर
1405010
1002
DEPT_2
01
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Service Category
Text
250
Yes
The type of category which is to be mapped with the relevant service subcategory. Click here for Service category reference
2
Service Subcategory (English)
Text
250
Yes
Name of “Service Sub-category” in English. This will help the user to select the Subcategory name while doing the collection. Click here for Service Subcategory reference
3
Service Subcategory (local Language)
Text
250
Yes
Name of “Service Sub-category” in Local Language. This will help the user to select the Subcategory name while doing the collection
4
GLCODE
Alphanumeric
50
Yes
General Ledger Code (GL Code) is a string of alphanumeric characters assigned to each Service. Click here for the General Ledger Code Reference
5
ULB CODE
Alphanumeric
50
No
The CODE which is specified and assigned to each ULB. It refers to the department
6
DEPT CODE
Alphanumeric
50
No
The Master Department Code linked to the“Service Category” at the State Level. The Department Code can be ascertained from the ULB Departments master. Click here to learn more about ULB Departments
7
FUND Code
Text
250
No
The type of fund allocated/associated with the respective service subcategory. Click here for Fund reference
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No
Section Name
Section Content
1
Government Logo
2
Chief Minister Message
.
.
.
.
20
About Website
Sr. No.
Section Name
Data Type
Data Size
Is Mandatory?
Description / Definition
1
Government Logo
Document
N/A
Yes
Resolution: 80 * 80 pixels
Logo of the state to be updated on the website
2
Governor’s Message
Template
N/A
Yes
Message from the governor of the state to the citizens needs to be updated under this section
3
Chief Minister Message
Template
N/A
Yes
Message from the chief minister needs to be updated under this section
4
State News
Template
N/A
Yes
Under this section we have will add current news about the state
5
State Events
Template
N/A
Yes
Under this section, we will add the Ongoing and Upcoming Events in the state
6
Recruitment Listing
Template
N/A
Yes
Recruitment listing/vacancies within the state need to be mentioned in this section
7
Tender Listing
Template
N/A
Yes
All the tender issued by the state government needs to be added under this section
8
Project Info
Template
N/A
Yes
All the Information of upcoming or ongoing project within the state should be added under this section
9
Recent Announcement
Template
N/A
Yes
Any kind of announcements by the state government with title and description which are in public interest needs to be uploaded under this section
10
Home Screen Flash Announcement
Template
N/A
Yes
Any kind of announcements by the state government with title and description and by highlighting link which are in public interests can bee added under this section
11
Public Notice
Template
N/A
Yes
The notices announced by the state government for the citizens with description, Rule and Regulation and timelines
12
Government Resolution
Template
N/A
Yes
Directions, resolutions, and other legal instruction and acts issued by the department should be captured here
13
RTI Listing
Template
N/A
Yes
All the RTI received by the state government shall be listed under this section
14
Help Document for Online services
Template
N/A
Yes
Under this section, we will add the Document or link with the title of online services for citizens
15
Required documents list for Online Services
Template
N/A
Yes
This section tells us about the list of required documents and data like old receipt or old transaction no for each service
16
Forms for services
Template
N/A
Yes
This section tells us about the services are not online, offline forms can be uploaded for the users to download
17
Contact Us
Template
N/A
Yes
All details of the contact person should be added under this section
18
List of ULBs (links to the ULB sites)
Template
N/A
Yes
All website Link of ULBs within the state should be added under this section
19
About Website
Template
N/A
Yes
This section talks about the all over details whatever is there on the state website
20
Tourist Places
Template
N/A
Yes
Under this section, we will add all the tourist place in the state with details and images
21
Slider Images
Document
N/A
Yes
Slider images of resolution 1280 * 450 pixels to be shown on the website
22
State Map
Document
N/A
Yes
This section will have a map for the State
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
All the sections with data type ‘Template’, data to be filled into the section-wise template provided as an attachment
NA
Sr. No.
Service Code*
Service Name* (In English)
Service Name (In Local Language)
Plan required for service *
Occupancy Certificate applicable for service
Plan Validity of this service (In Years)*
Renewal Validity of the service (in Years)
1
NC
New Construction
Yes
No
2
2
2
ADD
Addition
Yes
Yes
1
1
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Service Code
Alphanumeric
64
Yes
Unique Identifier for the listed services for reference
2
Service Name (In English)
Text
64
Yes
Names of applicable services such as Permit for New Construction, Reconstruction, Alteration, or Demolition
3
Service Name (In Local Language)
Text
64
No
Service names in Local language
4
The plan required for service
Text
3
Yes
Building drawing (Plan) required to submit for the listed services. The radio button for marking Yes or No
5
Occupancy Certificate applicable for service
Text
3
No
Whether Occupancy Certificate requires to be generated for this service. Radio button to mark Yes or No
6
Plan validity for this service (In Years)
Integer
2
Yes
Define the validity period of the permit order generated for the listed service
7
Renewal Validity of the service (in Years)
Integer
2
No
It can be 1 or 2 or 3 years based on the State/ULB needs
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Section Name
Section Content
1
City Introduction
Kesariya Stupa is a Buddhist stupa in Kesariya, located at a distance of 110 kilometres (68 mi) from Patna, in the Champaran (east) district of Bihar, India. Kesaria Stupa has a circumference of almost 1,400 feet (430 m) and raises to a height of about 104 feet (32 m).
2
Mayor’s Message
It is with immense gratitude to the citizens of Kesaria for reposing their faith in me to serve them as Chairman of Kesaria Nagar Panchayat that I write this message. I shall endeavour to prove that they have made the right choice.
.
.
.
.
22
Contact Us
All details of the contact person should be added under this section.
Sr. No.
Section Name
Data Type
Data Size
Is Mandatory?
Description/ Definition
1
ULB Logo
Document
N/A
Yes
Logo of resolution: 80 * 80 pixels of the ULB to be shown on the top of the website.
2
Slider Images
Document
N/A
Yes
Slider images of resolution 1280 * 450 pixels to be shown on the website.
3
City Introduction
Text
N/A
Yes
This section talks about the city hence introducing the city to be filled here to display it to the final audience/traffic onto the portal
4
City Map
Document
N/A
Yes
This section will have a map for the city mainly the area which the municipality/ panchayat takes care of and which indicates ULB boundary
5
Public Utility Services
Template
N/A
Yes
This section should include the infrastructure services provided to the citizen. E.g. Public Toilet, Govt School, Temples managed by Municipal Corporations/ Nagar Palika/ Panchayat etc.
6
Tourist Locations
Template
N/A
Yes
All tourist places in the city should be captured under this section. Tourist locations with pictures and other relevant information should be captured here
7
Mayor’s Message
Template
N/A
Yes
Message from the ULB chairman needs to be updated under this section
8
Commissioner’s Message
Template
N/A
Yes
Message from the ULB’s EO/commissioner needs to be updated under this section
9
ULB News
Template
N/A
Yes
Under this section we have will add current news about the ULB
10
ULB Events
Template
N/A
Yes
Under this section, we will add the Ongoing and Upcoming Events by the ULB
11
Recruitment Listing
Template
N/A
Yes
Recruitment listing/vacancies within the ULB needs to be mentioned in this section
12
Projects Info
Template
N/A
Yes
The description of the govt. Projects which ULBs take care of needs to be updated here with all other relevant details
13
Recent Announcements
Template
N/A
Yes
Any kind of announcements with title and description which are in public interest needs to be uploaded under this section
14
Home screen flash Announcement
Template
N/A
Yes
Any kind of announcements with title and description and by highlighting link which are in public interests can bee added under this section
15
Public Notice
Template
N/A
Yes
The notices announced by the ULB for the citizens with description, Rule and Regulation and timelines
16
Government Resolutions
Template
N/A
Yes
Directions, resolutions, and other legal instruction and acts issued by the department should be captured here
17
RTI listing
Template
N/A
Yes
All the RTI received by the ULBs shall be listed under this section
18
Help Documents for Online Services
Template
N/A
Yes
Under this section, we will add the Document or link with the title of online services for citizens
19
Required documents list for Online Services
Template
N/A
Yes
This section tells us about the list of required documents and data like old receipts or old transaction no for each service
20
Forms for services
Template
N/A
Yes
This section tells us about the services are not online, offline forms can be uploaded for the users to download
21
Tender Listing
Template
N/A
NO
All the tender issued by the ULB needs to be added under this section
22
Contact Us
Template
N/A
Yes
All details of the contact person should be added under this section
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of.
Sr. No.
Checklist Parameter
Example
1
All the sections with data type ‘Template’, data to be filled into the section-wise template provided as an attachment
NA
Sr. No. | Service Type* | Description* |
1 | New Construction | As per Site |
2 | New Construction | As per document |
3 | New Construction | Access to Plot As per site plan |
4 | New Construction | The height of building - Whether marked correct and the same value of height is given in PDF? |
5 | Occupancy Certificate Request | As per the site plan |
6 | Occupancy Certificate Request | As per Document |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Service Type | Text | 64 | Yes | Type of Permit allowed eg. New construction, reconstruction, alteration, and demolition. This is a mandatory field |
2 | Description | Text | 256 | Yes | This field provides the details that field inspectors must consider during field inspections. The field inspector can check and mark True or False as per their findings |
Sr. No. | Code* | Stakeholder Type Name* | Stakeholder Permit Validity (In Years) | Limitations on construction |
1 | BLD | Builders | 2 | N/A |
2 | ARC | Architect | 2 | N/A |
3 | TPR | Town Planner | 5 | Can construct 3 floors building, up to a height of 300 mts. |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Code | Alphameric | 3 | Yes | Unique Code provided with respect to Stakeholders type. It can be alphabetical, numeric, and alphanumeric as well |
2 | Stakeholder Type Name | Text | 64 | Yes | Name provided for stakeholder type which is ideally the technical qualification of the person registering |
3 | Stakeholder Permit Validity (In Years) | Numeric | 64 | No | All the permits (Permits to the stakeholders) have a validity period within which he/she is authorized |
4 | Limitations on construction | Text | 612 | No | Building Bye-laws defines and permits the limitations on the type of construction any technical person can take up to. This field captures such information |
Details coming soon!!
Human Resource Management System (HRMS) is a key module, a combination of systems and processes that connect human resource management and information technology through HR software. The HRMS module can be used for candidate recruiting, payroll management, leave approval, succession planning, attendance tracking, career progression, performance reviews, and the overall maintenance of employee information within an organization.
HRMS module enables users to -
Create User Roles
Create System Users
Employee Information Report
Financial Module (FM) is a key module that is built on coexistence with DIGIT which enables municipalities to create and manage financial transactions like budget, revenue demand, receipt, advances, deposits, bills, payments, asset creation (capitalization), fund transfer and also reconciliations and reporting.
FM enables municipalities to maintain financial records of ULBs following established procedures and practices. Financial Module is a fund based double-entry accrual accounting system designed in line with the National Municipal Accounting Manual.
The financial module enables users to -
Posting of General Ledger
Bill Processing: Generation of bills for varied items such as purchases, works, and salaries
Payment Processing: Payments are processed based on the type of expense type
Receipts Processing - from other DIGIT modules or from any other third party application
Service Wise, Bank account mapping - Configurable
Collection Remittances - Configurable mode of collection wise
Budgeting: Upload Budgets, Budgetary Controls, Budget Enforcement & Budget Re-appropriations
Asset Management: Asset Categorizations, Depreciation, Capitalization & Improvement, Revaluation, sale and disposal
Contra Entry, Bank-reconciliation, Deduction Management & period End Activities.
Deduction Management - processing statutory and non-statutory deductions and its remittances.
Financial Management
Budget Reports
Accounting Reports
Deduction Reports
Revenue Reports
MIS Reports
A Bank is a financial institution licensed to receive deposits and make loans. Bank Offers Internet Banking Services, Mobile Banking Services, Accounts, Loans, Financial Services such as currency exchange and safe deposit boxes.
There are several different kinds of banks including retail banks, commercial or corporate banks, and investment banks. In most countries, banks are regulated by the national government or central bank.
The list of banks in which the ULB would have an account in and a possible list of banks from which citizens would pay the taxes and other fees using cheque will have to be created here.
List of RBI published banks.
None
List of RBI published banks
Sr. No. | Occupancy Code* | Occupancy Name (In English)* | Occupancy Name (In Local Language) |
1 | R1 | Residential | आवासीय |
2 | E1 | Educational | शैक्षिक |
3 | I1 | Institutional | संस्थागत |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Occupancy Code | Alphameric | 2 | Yes | Unique Code provided with respect to occupancy name. It can be numeric and alphanumeric as well |
2 | Occupancy Name (In English) | Text | 64 | Yes |
3 | Occupancy Name (In Local Language) | Text | 64 | No | Occupancy Name in the local language. e.g. Hindi, Telugu, etc. |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Usage Code* | Usage Name* (In English) | Usage Name* (In Local Language) | Sub Occupancy Code* | Sub Occupancy Name |
1 | A-AF-AH | Apartment type | अपार्टमेंट प्रकार | AF | Apartment/Flat |
2 | A-AF-FR | Family residential | परिवार आवासीय | AF | Apartment/Flat |
3 | A-AF-RF | Residential flat | आवासीय फ्लैट | AF | Apartment/Flat |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Usage Code | Alphameric | 7 | Yes | Unique Code for listed Usage name. It can be a combination of alphabets and numbers |
2 | Usage Name (In English) | Text | 64 | Yes | Type of usage of the building to be mentioned here |
3 | Usage Name (In Local Language) | Text | 64 | Yes | Type of usage of the building to be mentioned here |
4 | Sub Occupancy Code | Alphameric | 7 | Yes |
5 | Sub Occupancy Name | Text | 64 | No |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Service Code* | Service Name | Document Name* | Is Mandatory?* |
1 | NC | New Construction | Aadhar Card | No |
2 | NC | New Construction | Fire NOC | Yes |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Service Code | Alphanumeric | 64 | Yes |
2 | Service Name | Text | 64 | No |
Document Name* | Text | 256 | Yes | Name of documents which are needed to avail the service |
3 | Is Mandatory? | Text | 3 | Yes | It indicates if the provided document is mandatory or not to avail the service |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Sub Occupancy Code* | Sub Occupancy Name* (In English) | Sub Occupancy Name* (In Local Language) | Occupancy Code* |
1 | OAH | Old Age Home | वृद्धाश्रम | R1 |
2 | AF | Apartment/Flat | अपार्टमेंट/ फ्लैट | R1 |
3 | FH | Farm House | फार्म हाउस | R1 |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Sub Occupancy code | Alphameric | 3 | Yes | A unique identifier for the given sub occupancy type |
2 | Sub Occupancy Name (In English) | Text | 64 | Yes | Names for sub occupancy types. For example - Old age home, apartments, farmhouse |
3 | Sub Occupancy Name (In Local Language) | Text | 64 | Yes | Names for sub occupancy types in local language e.g. in Hindi, Telugu etc. |
4 | Occupancy Code | Reference | 3 | Yes |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Fee Structure masters list contains the fee details applicable for processing specific services. All fee-related information collected by the authorities during the course of building plan approval is maintained in this masters.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify the combination of attributes for with the fee is defined and then fill into the given template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
No objection certificates (NOC) are certifications or permissions acquired from various bodies like Airport authority, monument authority, etc before any construction activities actually take place.
To acquire a building permit, an applicant needs to acquire NOC from the concerned authorities. Add the specific authorities at the State/ULB level in the NOC Departments master list for automated processing of NOCs. Refer to the National Bye-Laws for details on State/ULB specific NOC requirements.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify all the departments, services and the approach on integration and then fill into the given template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
A user role defines permissions for users to perform a group of tasks. In a default application installation, there are some predefined roles with a predefined set of permissions. Each role has a certain number set of tasks it is allowed to perform and these roles are Super Admin, Trade License Approver, Data Entry Admin and Trade License document verifier etc.
Data given in the table is sample data for reference.
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 all different types of user roles on the basis of ULB’s functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
A chart of Accounts (COA) is a listing of the Ledger codes that a State or ULB’s has identified and made available for recording transactions in its general ledger. COA is a standard data which need to be set up as per the National Municipal Accounting Manual or Respective State-wise manual. Click here for NMAM manual. The COA definition can consist of 3 or 4 levels of hierarchy. Ex: Major->Minor->Detailed (3 levels) or Major->Minor->Sub Minor->Detailed (4 Levels). It is up to the state to define the levels required depending on the reporting needs. Detailed code is the node or the level at which the transaction is done.
Data given in the table is a sample 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.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Functions shall represent the various functions or services carried out by the ULBs. Functions are provided through various responsibilities centres called Departments.
Functions of the ULB can have three levels within it.
The first level under this group represents various functions both obligatory and discretionary. Identified as 0 in the template.
The second Level in function would represent the particular type of service under a function, known as “Function Description”. Identified as 1 in the template
The third level will represent a particular cost centre, Known as “Cost Centre”, which provides the service. Identified as 2 in the template.
Data given in the table is a sample 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 all different types of Function in the ULB.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Town Planning Schemes masters list contains all building plan approval schemes and sub-schemes available for the benefits of the citizens. Create a list of the available schemes and map these schemes to specific Occupancy Types.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Identify all the scheme and sub-schemes and fill into the given template.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
There is no separate entity-specific checklist for this entity.
A Fund is used to capture activities/ group of activities for which separate books of accounts are required to be maintained. The concept of Funds brings accountability and better transparency
Various Funds are set up in ULB for meeting certain objectives. Income and expenditure under these funds are to be identified and disclosed separately.
Fund Accounting is a self-contained accounting with its own assets, liabilities, revenues, expenditures and fund balance.
Data given in the table is a sample 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 all different types of Funds on the basis of ULB’s functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
A system user is a person who uses the application service. A user often has a user account and is identified to the system by a username. A user is a person who accesses a particular application to perform a set of actions.
Each user has a certain number of set tasks, the user would be allowed to perform a task by assigning particular roles which are Super Admin, Trade License Approver, Data Entry Admin and Trade License document verifier etc.
Data given in the table is sample data for reference.
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.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
A supplier is a person or business that provides a product or service to another entity. The role of a supplier in business is to provide high-quality products.
A supplier may also be referred to as a vendor who supplies required materials or a product to the State or ULB for the works which need to be executed. (Example: materials for street light, cable wires for street light etc)
Data given in the table is a sample 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 all different types of suppliers.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
A contractor is a person or firm who undertakes a contract to provide materials or labour to perform a service or do a job.
Contractors are basically who takes up the works which are awarded by the State or a ULB for a set period. For Example Construction of New Roads/Bridges, Maintenance of Parks etc.
Data given in the table is a sample 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 all different types of contractors.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
A Bank branch, banking centre is a retail location where a bank offers a wide array of face-to-face and automated services to its customers.
The list of banks branches(under Bank list from master) in which the ULB would have an account in will have to be created here.
Data given in the table is a sample data.
Download the workflow 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 all bank branches in the state which holds the bank account.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Sub schemes are defined under the schemes by the Centre or state government to be associate with a fund and for a time. The Sub scheme shall be defined under a scheme.
Data given in the table is a sample data.
Download the workflow 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 all sub schemes with the State.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
The Center or State comes up with various government programs called schemes (Yojana) from time to time. These schemes could be either Central, state-specific or joint collaboration between the Centre and the states.
Schemes and sub-schemes defined by the Centre or state government to be associate with a fund and for a time. Similar Sub scheme shall be defined under a scheme.
Data given in the table is a sample 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 all different types of Schemes on the basis of ULB’s functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Name provided for occupancy name which is used to configure in the OBPAS module. Refer to for more details
code to be mentioned here. Maps the Building Usage details to specific sub occupancy type
Name to be mentioned here. Maps the Building Usage details to specific sub occupancy type
Code of service - Refer to the to understand in detail
Name of service - Refer to the to understand in detail
Corresponding for the given sub occupancy type
Sr No.
Service Type*
Application Type*
Application Subtype
Fee Subtype*
BPA Fees*
Amount*
Calculation Logic
1
new construction
PERMIT APPLICATION
application fee
Application Fees
50
2
new construction
PERMIT APPLICATION
Medium Risk
sanction fee
Additional Fees
0
3
new construction
PERMIT APPLICATION
Low Risk
application fee
Land Development Charges
50
4
new construction
OCCUPANCY CERTIFICATE
High Risk
sanction fee
Charges for Well
50
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Service type
Text
256
Yes
The type of OBPS service for which the fees is to be collected. Refer to the Data Table above for illustration
2
Application Type
Text
256
Yes
List of application types for which the fees are to be calculated. Refer to the Data Table above for illustration
3
Application Subtype
Text
56
No
Application subtype is mentioned here such as type of risk
4
Fee Subtype
Text
256
Yes
Type of fees so collected to be mentioned here. Refer to the Data Table above for illustration
5
BPA Fee
Text
56
Yes
The type of OBPS service for which the fees is to be collected. Refer to the Data Table above for illustration
6
Amount
Integer
6
Yes
Fee Amount collected is mentioned here. Refer to the Data Table above for illustration
7
Calculation Logic
Text
1024
No
Fees calculation logic if any is mentioned here
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Government Department*
Application type*
Integration Type*
SLA
1
Airport Authority of India (AAI)
Permit
Web API
15
2
National Monument Authority (NMA)
Occupancy certificate
Manual
15
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Government Department
Text
256
Yes
Name of the department from where a NOC has to be acquired. This needs to be provided and uploaded into the system
2
Application Type
Text
256
Yes
The type of applications for which NOC is required. Check the Data Table for illustration
3
Integration Type
Text
256
Yes
This is about the approach of integration to be adopted with government departments systems
4
SLA
Integer
2
No
Timelines required (if any) for the NOC to be acquired. This information needs to be updated in the SLA column
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Code*
Name*
Description
1
TL_APPROVER
TL Approver
Trade License Approver
2
GRO
Grievance Routing Officer
Grievance Routing Officer
3
CSR
Customer Support Representative
An employee who files and follows up complaints on behalf of the citizen
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Code
Alphanumeric
64
Yes
A unique code that identifies the user role name.
2
Name
Text
256
Yes
The Name indicates the User Role while creating an employee a role can be assigned to an individual employee
3
Description
Text
256
No
A short narration provided to the user role name
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Activity
Example
1
The Code should be alphanumeric and unique
TL_APPROVER, GRO
2
The Name should not contain any special characters
TL Approver : [Allowed]
#TL Approver! : [Not allowed]
Sr. No*
Major Code*
Major head Description*
Minor Code*
Minor Head Description*
SubMinor Code
SubMinor Head Description
Detailed Heads (Ledgers)*
Ledger Code*
Type
Account Detail Type
Function Required
Budget Required
1
110
Tax Revenue
110-01
Property Tax
110-01-01
Property Tax - General Tax
Property Tax - General Tax - Residential
110-01-01-01
Income
Yes/No
Yes/No
2
210
Establishment Expenses
210-10
Salaries and Wages
Basic Pay
210-10-01
Expenses
Yes/No
Yes/No
3
350
Other Liabilities
350-11
Employee Liabilities
Salaries Unpaid
350-11-01
Liabilities
Drawing Officer
Yes/No
Yes/No
4
410
Fixed Assets
410-20
Buildings
Office Building
410-20-02
Assets
Yes/No
Yes/No
Sr No
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Major Code
Alphanumeric
50
Yes
The Major Code can be any number of digits, (though NMAM suggest the first 3 digits) of the GL Code to be the Major code, this will help in collating the reports at the Nation level
2
Major head Description
Text
250
Yes
The short name given to the Major code to easily identify the Account Name for individual code
3
Minor Code
Alphanumeric
50
Yes
The Minor Code can be any number of digits, the digits are configurable. The Minor code will help in collating the reports at the State level. Also, the State has the flexibility to define the minor codes
4
Minor Head Description
Text
250
Yes
The short name given to the Minor code to easily identify the Account Name for individual code
5
SubMinor Code
Alphanumeric
50
No
The SubMinor Code can be optional, State/ULB can set up a sub minor level code based on their requirement, this would help in facilitating the additional level of reporting and also detail transaction-level information (The SubMinor code is not listed in NMAM manual)
6
SubMinor Head Description
Text
250
No
The short name given to the SubMinor code to easily identify the Account Name for individual code
7
Detailed Heads (Ledgers)
Text
250
Yes
The short name for the Ledger Code, wherein users use this account head name while posting the transactions into the system
8
Ledger Code
Alphanumeric
50
Yes
A General Ledger Code (GL Code) is a string of 7 to 9 digit numeric characters assigned to each financial entry in a State/ULB ledger. A GL Code can be assigned to different debit or credit entries to make accounting transactions
9
Type
Text
250
No
The Type indicates the Income, Expenses, Liabilities and Assets which are mapped to each individual GL code. User can easily identify the GL code by this mapping
10
Account Detail Type
Text
250
No
The account details type is the subsidiary ledger, The Suppliers, Contractors and Employees are standard subsidiary ledger. This will help the user to identify the subsidiary ledger details while processing any bill transaction in the system
11
Function Required
Text
250
No
A GL Code can be linked for the validation of the Function, the user while posting a transaction can select a particular function to which transaction will be linked and this will facilitate easy Function wise reporting
12
Budget Required
Text
250
No
A GL Code can be linked for the validation of a Budget. User can have a validation check while posting a transaction into the system, this will facilitate to track the amount usage
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
The Major, Minor and Sub minor Description Name should not contain any special characters
Tax Revenue : [Allowed]
#Tax Revenue! : [Not allowed]
2
The Ledger Codes that are defined by the state team should be alphanumeric and Unique
110-01-01-01
*Sr. No.
*Name
*Code
*Level
Parent Type
Parent Code
1
General Administration
10
0
Nil
Nil
2
GENERAL ADMINISTRATION: Administration
1011
1
General Administration
10
3
General Department
101100
2
GENERAL ADMINISTRATION: Administration
1011
4
Public Works
20
0
Nil
Nil
5
PUBLIC WORKS: Roads and Pavement
2021
1
Public Works
20
6
Roads and Building Maintenance
202101
2
PUBLIC WORKS: Roads and Pavement
2021
Sr No
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Name
Text
250
Yes
To indicate the Function name, User can select a particular function code while recording a transaction in the system. This will facilitate in generating a report at the function level
2
Code
Alphanumeric
50
Yes
The unique code is given to the individual function. Child functions have to follow number pattern starting with the parent code
3
Level
Numeric
50
Yes
As per NMAM, the Function can be defined in the tree structure, so the Level indicates the structure in which the function would be setup. Root nodes will be level 0 and the next level funds will have value as 1 and the next level as value 2
4
Parent Type
Text
250
No
If the ULB’s using multiple Functions then a Hierarchy of “Parent-Child “can be set up for the Function, so under each Parent Function a multiple child function can be set up
5
Parent Code
Alphanumeric
50
No
The unique code representing the parent type function
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of.
Sr. No.
Checklist Parameter
Example
1
The Function Name should not contain any special characters
General Administration : [Allowed]
#General Administration! : [Not allowed]
2
The Function Code that is defined by the state team should be alphanumeric and Unique.
10, 1011 or 101100
Sr. No.
Code
Sub Scheme*
Scheme*
Occupancy Code*
Occupancy Name
1
SCM1
Sub scheme 1 for Ward No. 1
DTP Scheme for Ward No. 1
R1
Residential
2
SCM2
Sub scheme 2 for Ward No. 1
DTP Scheme for Ward No. 1
C1
Commercial
3
SCM3
Sub scheme 1 for Ward No. 7
DTP Scheme for Ward No. 7
C1
Commercial
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Code
Alphanumeric
64
Yes
Unique code to record
2
Sub scheme
Text
256
Yes
Sub scheme name
3
Scheme
Text
256
Yes
Name of the schemes available at a ULB/state level
4
Occupancy Code
Alphanumeric
64
Yes
Occupancy code - Refer to Building Occupancy to know more on it
5
Occupancy Name
Text
64
No
Name provided for occupancy in Building Occupancy
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No*
Name*
Code*
Identifier
Level*
Parent Fund
1
Municipal Fund
01
1
0
Nil
2
Grant Fund
02
2
0
Nil
3
Public Fund
03
3
0
Nil
4
Pension Fund
04
4
0
Nil
Sr No
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Name
Text
50
Yes
To indicate the Fund name, if there are multiple funds and by following the Fund Accounting method to record the transaction user can select a particular Fund
2
Code
Numeric
50
Yes
The unique code gives to the individual fund
3
Identifier
Numeric
50
No
A single character or number which is used as a unique identification for the fund. This identifier is used in the voucher number format
4
Level
Numeric
50
Yes
The Funds can be defined in the tree structure, so the Level indicates the structure in which the funds would be set up. Root nodes will be level 0 and the next level funds will have value as 1 and the next level as value 2
5
Parent Fund
Text
50
No
If the ULB’s using multiple Funds then a Hierarchy of “Parent-Child “can be set up for the Fund, so under each Parent Fund multiple child funds can be set up
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Activity
Example
1
The Fund Code that is defined by the state team should be numeric and Unique.
01
2
The Fund Name should not contain any special characters
Municipal Fund : [Allowed]
#Municipal Fund! : [Not allowed]
Sl No.
Name*
Mobile No*
Father/Husband's Name *
Gender *
Date of Birth*
Correspondence Address *
ULB*
Role*
Employment Type *
Current Assignment
Status *
Hierarchy *
Boundary Type *
Boundary *
Assigned from Date*
Department*
Designation*
1
Pooja
9999999999
Mr.Bala Chandra
FEMALE
22/01/1987
Nagar Nigam Haldwani-PIN CODE-263139
Haldwani
Super User
PERMANENT
Yes
EMPLOYED
REVENUE
City
Haldwani
05/10/2019
Revenue
Tax Inspector
2
M.C. Joshi
9999999999
Late Jai Dutt Joshi
MALE
04/08/1965
Nagar Nigam Haldwani
Haridwar
TL Counter Employee
PERMANENT
Yes
EMPLOYED
REVENUE
City
Haldwani
30/10/2019
Revenue
Tax Collector
Sr No
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Name
Text
256
Yes
The Name of his/her to whom the access to the system is provided, so he/she can use the application to perform the role function assigned
2
Mobile Number
Alphanumeric
10
Yes
The Mobile number of his/her to whom the access to an application provided. The mobile number is relevant so in an emergency case the person can be contacted
3
Father/Husband's Name
Text
256
Yes
The Name of the Father/Husband of his/her to whom the access to an application provided. This information is for internal records
4
Gender
Text
64
Yes
The Gender of the individual person. This information is for internal records
5
Date of Birth
Date
10
Yes
The Date of birth of the individual person. This information is for internal records
6
Alphanumeric
256
No
The email id of his/her, this email id is linked to receiving all the official communication from the customers and other counterparts
7
Correspondence Address
Text
256
Yes
The address of his/her, this information is saved for internal records
8
ULB
Text
256
Yes
A ULB to be assigned against the individual employee, So that the assigned role can perform his/her duty within that assigned ULB
9
Role
Text
256
Yes
A Role is a permission for users to perform a group of tasks, a role is assigned to the user to perform a function within the application. A user can be assigned multiple roles. Click User Roles for the Role master Data
10
Employment Type
Text
256
Yes
The employment types indicate the type of contract which he/she hold with the organization. This indicates whether he/she is a permanent employee or a contract employee for short period. The employment type “Permanent”, “Temporary”, “DailyWages” and “Contract” either one should be selected
11
Current Assignment
Text
64
Yes
The current assignment type to indicate whether the employee is currently assigned to a particular department and designation. A user can be also be assigned multiple assignments to perform his/her function
12
Status
Text
256
Yes
The Status indicates the type of status which he/she hold, whether employed or not within the organization
13
Hierarchy
Text
256
Yes
The hierarchy indicates the hierarchy type for the Boundary to which he/she is assigned
14
Boundary Type
Text
256
Yes
The boundary type indicates assigning a city to his/her role within the organization. A user can be assigned multiple Boundary Type to perform in different function. (Example: City, Zone, Block and Locality)
15
Boundary
Text
256
Yes
The boundary indicates assigning a particular city to his/her role wherein they perform role function of the application for the particular city. A user can be assigned multiple Boundary to perform in a different location (Example: City Name and Tenant Zone)
16
Assigned from Date
Date
10
Yes
The assigned from date indicates the date from which his/her role is assigned to perform the role function assigned
17
Department
Text
256
Yes
The Department indicates the particular department to which his/her role is assigned
18
Designation
Text
256
Yes
The designation indicates a particular designation is assigned to his/her role
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Activity
Example
1
The Name should not have any special character
Pooja : [Allowed]
#Pooja! : [Not allowed]
2
The date should be in DD/MM/YYYY format
DD/MM/YYYY : [Allowed]
YYYY/DD/MM : [Not allowed]
3
The Email ID should be valid Id, email Id should contain the Company/Firm name or an individual personal name before the “@” and the “XXXXX.com” after the “@”
Sr. No* | Name* | Permanent Address* | Correspondence Address | Supplier Code* | Contact Person* | Email ID* | Mobile No.* | PAN No. | Registration No | GST/TIN No. | GST registered State/UT | Bank Name | Bank Account No. | IFSC Code |
1 | ABC Supplies | #5 6th main cross opp to ICICI bank Punjab | NIL | ABC134 | Ramesh | abcsupplies@gmail.com | 98XXXXXX21 | APRFN9561B | Nil | 22AAAAA0000A1Z5 | NIL | ICICI | 2XXXX1234XX4 | ICICI00XXXX7 |
2 | Suresh Traders | 10 main road Punjab | #62 5th main road ITPL Punjab | MB0099 | Rakesh | sureshtraders@xyz.com | 98XXXXXXX95 | ARIZG9874C | AYR145U | 22BBBBA0000A1Z5 | 22BBBBA0000A1Z5 | HDFC | 98XXXXX5X4 | HDFC00XXX51 |
Sr No | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Name | Text | 250 | Yes | The register Name of the Company or an Individual Person Name, this will help the user to easily identify the supplier to raise a Purchase Order and also while generating the bills. |
2 | Permanent Address | Text | 250 | Yes | Company permanent address or an Individual Person permanent address, this will help the user to send the hard copy of a Purchase order to the Supplier. |
3 | Correspondence Address | Text | 250 | No | Alternative address of a Company or an Individual Person |
4 | Supplier Code | Text | 50 | Yes | A unique code that identifies the supplier of the goods |
5 | Contact Person: | Text | 250 | Yes | Details of a contact person of an individual or a Company, the user can contact the supplier to get the information and status of the delivery of the goods ordered. |
6 | Email ID | Text | 250 | Yes | Company email Id or an individual person email Id, with the email Id the supplier can receive the notification related to purchase order and payments. |
7 | Mobile No | Alphanumeric | 12 | Yes | Company Mobile number or an individual person mobile number, the supplier can receive SMS alerts after the bills are processed. |
8 | PAN No | Alphanumeric | 10 | No | Company registered PAN number or an individual person PAN number |
9 | Registration No | Alphanumeric | 21 | No | Company/Firm registered number, it’s a unique number assigned by the Registrar of Companies. |
10 | GST/TIN No | Alphanumeric | 15 | Yes | Company registered GST/TIN number is a Tax Identification Number is a unique 15-digit number. |
11 | GST registered State/UT | Alphanumeric | 15 | Yes | The company/Firm has multiple businesses with the state or union territory a separate registered GST number is a Tax Identification Number. |
12 | Bank Name | Text | 50 | No | Company Bank Name in which they hold the account or an individual person Bank account name which he/she holds the account |
13 | Bank Account No | Alphanumeric | 25 | No | Company Bank Account number or an individual person Bank Account number. With the bank account number, the bill payment can be made to the correct account, also while doing the RTGS fund transfer the amount can be transferred to the respective firms or individual account. |
14 | IFSC Code | Alphanumeric | 11 | No | The Bank IFSC code pertaining to the bank account of the Company or an Individual person holding a bank account, the IFSC code will be a validation check for the bank account provided by the contractor and useful for the user while doing a bill payment via RTGS. |
Sr. No* | Name* | Contractor Code* | Permanent Address* | Correspondence Address | Registration No.* | Contact Person* | Email ID | Mobile No.* | PAN No. | GST/TIN No. | GST registered State/UT | Bank Name | Bank Account No. | IFSC Code |
1 | Rakesh | RAK00123 | #141/25 2nd Cross koramangala Bangalore | #62 5th main road ITPL Bangalore | NIL | Rakesh | Rakesh@gmail.com | 98XXXXXX45 | AFRXXXX64N | NIL | NIL | ICICI | 000XXXX1234 | ICICI0XXXX97 |
2 | ABC Constructions | ABC00143 | #1/1 8th Main JP Nagar Bangalore | NIL | Z12345KA2020PTC097654 | Mahesh | contact@abcconstruction.com | 987XXXXXX65 | PNBXXXX78U | 22AAAAA0000A1Z5 | 22AAAAA0000A1Z5 | HDFC | 987XXXXX64 | HDFC0XXXX51 |
Sr No | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Name | Text | 50 | Yes | The register Name of the Company/Firm or an Individual Person Name, this will help the user to easily identify the contract assigned and also while generating the bills |
2 | Contractor Code | Alphanumeric | 50 | Yes | A unique code that identifies the contractor of the works |
3 | Permanent Address | Alphanumeric | 250 | Yes | Company/Firm permanent address or an Individual Person permanent address, this will help the user to send the hard copy document to the contractor. Example, A signed hard copy of the contract |
4 | Correspondence Address | Alphanumeric | 250 | No | Alternative address of a Company/Firm or an Individual Person Alternative address |
5 | Registration No | Alphanumeric | 21 | Yes | Company/Firm registered number, it’s a unique number assigned by the Registrar of Companies |
6 | Contact Person | Text | 100 | Yes | Details of a contact person of an individual or a Company/Firm. This will help the user to contact a person in case of any information required |
7 | Email ID | Alphanumeric | 250 | No | Company/Firm email Id or an individual person email Id, with the email Id the contractor, can receive the notification related to works and payments |
8 | Mobile No | Alphanumeric | 12 | Yes | Company/Firm Mobile number or an individual person mobile number, the contractor can receive SMS alerts after the bills are processed |
9 | PAN No | Alphanumeric | 10 | No | Company/Firm registered PAN number or an individual person PAN number |
10 | GST/TIN No | Alphanumeric | 15 | Yes | GST/TIN No: Company/Firm registered GST/TIN number is a Tax Identification Number |
11 | GST registered State/UT | Alphanumeric | 15 | Yes | The company/Firm has multiple businesses with the state or union territory a separate registered GST number is a Tax Identification Number |
12 | Bank Name | Text | 50 | No | Company/Firm Bank Name in which they hold the account or an individual person Bank account name which he/she holds the account |
13 | Bank Account No | Alphanumeric | 25 | No | Company/Firm Bank Account number or an individual person Bank Account number. With the bank account number, the bill payment can be made to the correct account, also while doing the RTGS fund transfer the amount can be transferred to the respective firms or individual account |
14 | IFSC Code | Alphanumeric | 11 | No | The Bank IFSC code pertaining to the bank account of the Company/Firm or an Individual person holding a bank account, the IFSC code will be a validation check for the bank account provided by the contractor and useful for the user while doing a bill payment via RTGS |
Sr. No. | Activity | Example |
1 | The Contractors Code should be alphanumeric and unique | RAK00123 |
2 | The Email ID should be valid Id, email Id should contain the Company/Firm name or an individual personal name before the “@” and the “XXXXX.com” after the “@” | ABCLtd@xeror.com |
Sr. No. | Activity | Example |
1 | The Branch Code should be unique | 006305, 7849 |
Sr. No. | Activity | Example |
1 | The date format should be as per example and the Start date should be greater than the current date and end date. | DD/MM/YYYY : [Allowed] YYYY/DD/MM : [Not allowed] |
2 | The name should be unique and should not contain any special characters | AMRUT : [Allowed] #AMRUT! : [Not allowed] |
3 | The scheme name mapped should be as per the scheme master entity | AMRUT, SWM |
Sr. No. | Activity | Example |
1 | The date format should be as per example and the Start date should be greater than the current date and end date | DD/MM/YYYY : [Allowed] YYYY/DD/MM : [Not allowed] |
2 | The name should be unique and should not contain any special characters | AMRUT : [Allowed] #AMRUT! : [Not allowed] |
The Water Charges module offers a consolidated platform for managing new and existing water connections. The module eliminates the need for manual processing and streamlines the key water management functions for operational efficiency. DIGIT Water & Sewerage (W&S) module enables automated processing of new connection requests, generating water bills, and facilitating online payment of bills.
DIGIT Water Charges module enables citizens to -
Apply for new water connections.
Upload documents required for processing new connections.
Pay water connection charges and water bills using online payment gateway.
Receive SMS alerts on application status, bills generated, payment due date, and payment receipt confirmation.
Download water connection approval letter, payment receipts, and bills online.
DIGIT Water module enables employees at ULB and State level to -
Process applications using customizable workflows.
Configure water charges, interest, and penalty calculation logic.
View custom dashboards for module statistics.
Filter search results using advanced configurable search parameters.
None
None
Sr. No | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of. |
Sr. No. | Activity | Example |
1 | The Supplier Code should be alphanumeric and unique | ABC134 |
2 |
Sr. No | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Bank* | Bank Code* | Branch Name/Location* | Branch Code* | MICR | Address* | Contact Person | Phone Number | Narration |
1 | STATE BANK OF INDIA | SBI | SBI Treasury Branch, Kurnool | 006305 | 518002007 | COLLECTOR COMPLEX DISTT KURNOOL ANDHRA PRADESH | Branch Manager | 0408743462 | Operating Current Accounts |
2 | KOTAK MAHINDRA BANK | KKBK | Ucon Plaza Kurnool | 7849 | 518064002 | Ucon Plaza, Park Road Kurnool | Branch Manager | 0812756943 | Nationalized Bank |
3 | ANDHRA BANK | ANDB | KRISHNANAGAR (KURNOOL) | 001430 | 518011010 | 80/112 Aabbas Nagarabbasnagar,Kurnool 518002 | Branch Manager | 022-2261759 | Nationalized Bank |
Sr No | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Bank | Text | 100 | Yes |
2 | Bank Code | Alphanumeric | 50 | Yes | The Unique code which represents each bank |
3 | Branch Name/Location | Text | 50 | Yes | The Branch Name/Location is the name of the branch of the bank which is registered with Central Bank. It helps to identify any specific branch of the bank |
4 | Branch Code | Alphanumeric | 50 | Yes | A unique code that identifies the bank branch, this will help the user to easily identify the bank branch |
5 | MICR | Alphanumeric | 50 | No | The MICR Code is used in Local clearing (this will be in the bottom portion of the cheque). IFSC Code used for RTGS, IMPS and NEFT transactions in India |
6 | Address | Alphanumeric | 50 | Yes | It's the address of the bank where the account is held by the State, the address is likely printed on a bank statement or in the cheque book |
7 | Contact Person | Text | 100 | No | A contact person who acts as a channel of communication between the bank and the customer, a contact person is the one who provides relevant information as and when required by the customer |
8 | Phone Number | Alphanumeric | 12 | No | A phone number is the registered number of the bank, wherein a customer can contact a bank representative for any kind of banking-related information |
9 | Narration | Text | 250 | No | A short narration which represents the bank and branch |
Sr. No | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Scheme Code* | Sub Scheme Name * | Sub Scheme Code * | Valid From * | Valid To * | Department Code | Initial Estimate Amount |
1 | 10 | Storm Water Drains | 1003 | 01/05/2018 | 01/06/2021 | PHS | 2500000 |
2 | 20 | Solid Waste Management- SWM | SBM02 | 01/06/2017 | 01/07/2020 | TP | 1000000 |
3 | 30 | Street Lights | 5001 | 01/03/2016 | 30/04/2019 | TP | 2000000 |
Sr No | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Scheme Code | Alphanumeric | 50 | Yes |
2 | Sub Scheme Name | Text | 50 | Yes | The Sub Scheme Name will facilitate the user to record the transaction against the individual sub-scheme and also helps in tracking the utilization of the sub-scheme |
3 | Sub Scheme Code | Alphanumeric | 50 | Yes | A unique code assigned to individual Sub Scheme |
4 | Valid From | Date | N/A | Yes | The Date on which the Scheme Started, this will help to facilitate the receiving of funds from Central Sponsored Schemes and State-Sponsored Schemes |
5 | Valid To | Date | N/A | Yes | The Date on which the Scheme will End, this will help to facilitate the end date by when the funds from Central Sponsored Schemes and State-Sponsored Schemes need to be utilized |
6 | Department Code | Text | 250 | No |
7 | Initial Estimate Amount | Numeric | 50 | No | The initial Estimate Amount approved amount under the sub-scheme can be updated while creating the sub-scheme master record. This will facilitate the user in utilizing the amount within the estimated amount |
Sr. No | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No* | Scheme Code* | Scheme Name* | Fund* | Description | Start Date* | End Date* |
1 | 10 | AMRUT | Grant Fund | Amrut | 01/05/2018 | 01/06/2021 |
2 | 20 | Swachh Bharat Mission | Grant Fund | Swachh Bharat Mission | 01/06/2017 | 01/07/2020 |
3 | 30 | Finance Commission | Municipal Fund | Finance Commission | 01/03/2016 | 30/04/2019 |
4 | 40 | Housing for All | Municipal Fund | Municipal Fund | 01/04/2016 | 31/03/2021 |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Scheme Code | Numeric | 50 | Yes | A unique code assigned to individual Scheme |
2 | Scheme Name | Text | 250 | Yes | The indicate Name of the Scheme, this will facilitate the user to record the transaction against the individual scheme and also helps in tracking the utilization of the Scheme |
3 | Fund | Text | 250 | Yes |
4 | Description | Text | 250 | No | A Short description provided to individual schemes |
5 | Start Date | Date | N/A | Yes | The Date on which the Scheme Started, this will help to facilitate the receiving of funds from Central Sponsored Schemes and State-Sponsored Schemes |
6 | End Date | Date | N/A | Yes | The Date on which the Scheme will End, this will help to facilitate the end date by when the funds from Central Sponsored Schemes and State-Sponsored Schemes need to be utilized |
Sr. No | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
The Sub-ledger category provides details behind entries in the general ledger used in accounting, which is also called subsidiary ledgers. The total of the Sub-ledger would match the line item amount on the general ledger. This corresponding line item in the general ledger is referred to as the controlling account.
Any other type of Sub-ledgers other than standard Sub-ledgers available in the system is to be created here. Standard sub-ledger available in the system is Contractor, Supplier and Employee.
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 all different types of sub-ledger category.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
A bank account is a financial account maintained by a State in which the financial transactions between the bank and a customer are recorded. Each bank sets the terms and conditions for each type of account it offers, which are classified in commonly understood types, such as deposit accounts, credit card accounts, current accounts, loan accounts or many other types of account.
The list of banks account which the ULB holds an account in various banks will have to be created here.
Data given in the table is a sample data.
Download the workflow 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 all bank branch within the State.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Once the SubLedger Category is created the Subledger master need to be defined. The Subledger master will help to record the transaction at the most detailed level. Subledger category is referred to as “Account detail type” here.
With recording the transaction at the Subledger level, the detail reports can be generated.
Data given in the table is a sample data.
Download the workflow 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 all subledger master details.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
The debit or credit balance of a ledger account brought forward from the old accounting period to the new accounting period is called opening balance. This will be the first entry in a ledger account at the beginning of an accounting period. The opening balance is being captured based on Department, fund, function etc are based on how the system is configured.
If a ULB is using another accounting system, firstly ULB should close financial statements in that system. Then the closing balance of the accounts should be updated as an opening balance in the new application.
Data given in the table is a sample 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 all the Ledger Codes for which opening balance need to be entered.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
A deduction master is defined to create a reference between ledger codes and to the standard and statutory deductions that are deducted in various creditor bills. By defining this deduction master, accounts department can process the remittance of all the deductions done for a time period at once and keep track of the same.
An example of a deduction is what is deducted from salary bill as income taxes.
Data given in the table is a sample 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 all different types of deduction.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Water Charges are levied for metered connections based on consumption. The rate for calculation of water charges varies widely and is dependent upon various parameters. In DIGIT W&S module, water charges defined are based on actual consumption and property usage type.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Please reach out to the person who has shared this template with you to discuss and clear your doubts.
Select the property type from the drop-down list available in the Property Usage Type column.
Enter the Slab (water consumed) range details in the From and To Value for water consumed.
Enter the Rate for the specified slab range and property type.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Separate Entity Specific Checklist is not required for this module data.
Water Charges are recurring charges levied for a pre-defined billing period. The billing period is configurable as per the state or ULB requirement. The rate for calculation of water charges vary widely and is dependent upon various parameters. Charges for water are dependent upon either plot size slab or No. of taps combined with property usage type. In some cases, they can also be solely dependent upon the property usage type.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Please reach out to the person who has shared this template with you to discuss and clear your doubts.
Select the property type from the drop-down list available in the Property Usage Type column.
Enter the Slab (property size value) range details in the From and To Value for property size.
Enter the value for No. of Taps. The water charges will be calculated on the number of taps.
Enter the Rate or the per-unit water consumption charges that will be applicable for the listed parameters.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
Separate Entity Specific Checklist is not required for this module data.
There are two reasons for recording the water source. One is to measure availability vs consumption. And, the other is to monitor the water quality. Each ULB captures this information. Hence, the water source details are configurable at the ULB level. ULBs can configure water source data at two levels - water source and water sub source.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.
Contact the person who shared this template with you to discuss and clear your doubts.
Enter the relevant Water Source.
Enter the corresponding Water Sub Source. This will map the water sub source to the specified water source.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
A separate Entity Specific Checklist is not required for this module data.
Water pipes are available in different sizes. Pipe size is a common parameter used for calculating water charges. The allotted pipe size for new water connections depends on specific service requirements.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
Enter the Pipe Size details.
Enter the corresponding UOM for the specified Pipe Size.
Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
A separate entity-specific checklist is not needed for this module data.
Interest is levied from the consumer in case the consumer fails to make the payment of the bill before the specified due date. The consumer has to make the full payment before the due date to avoid interest charges. The number of days after which the interest is applicable is configurable at the ULB level. Interest Rates are calculated essentially on a daily percentage basis.
The interest rate on a daily basis can be levied on -
Entire bill amount
Balance pending when partial payments have been made
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter the Grace Period.
Select the relevant Interest-based On parameter.
Enter the Interest Rate.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
Separate Entity Specific Checklist is not required for this module data.
The Email ID should be valid Id, email Id should contain the Company/Firm name or an individual personal name before the “@” and the “” after the “@”
The Bank Name defines the name of the bank in which the individual or an organization hold the different type of accounts. Click for the list of RBI published banks
A unique code assigned to individual Scheme, this will facilitate the user to assign the sub-scheme under the individual scheme and also helps in tracking the utilization of the Scheme. Click on to view the scheme master data
The sub-scheme can be linked to the individual department, so user while recording the transaction can assign the department. Click for the master data
To indicate the Fund name against each scheme. This will facilitate in support to track the scheme funds, receipts and utilization by attaching scheme code to the financial transaction. Click on to view the Fund master data
Sr No.
Name*
Description*
1
Telephone
Telephone
2
Other Creditors
Other Creditors
3
ULB and Other Dept
ULB and Other Departments
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Name
Text
50
Yes
The Name indicates the sub-ledger category, this will facilitate the user to record the transaction at the Sub-ledger level. (Example: While creating a bill, user can select the Sub-ledger details as a contractor to whom the bill need to be paid and the same can be recorded under the sub-ledger GL code which is mapped to the contractor)
2
Description
Text
50
Yes
A short description provided to the name of the Sub-ledger
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Activity
Example
1
The name should be unique and should not contain any special characters
Contractor : [Allowed]
#Contractor! : [Not allowed]
Sr. No.*
Bank Branch*
Bank Branch Code*
Account number*
Fund*
Account Type (COA Grouping)*
Description
Usage Type*
Pay to
1
HDFC Bank - Main City
HDFC147
00063897421
Municipal Fund
45020 - Balance with Banks – Main Municipal Fund
45022 - Other Scheduled Banks
RECEIPTS_PAYMENTS
Commissioner
2
SBI Treasury Branch, Kurnool
SB0012
844102001001VN
Municipal Fund
45021 - Nationalised Banks
PD Account-001
RECEIPTS_PAYMENTS
Commissioner, KMC
3
ICICI Bank
ICIC550
02042417454076
Municipal Fund
45021 - Nationalised Banks
P.F. Secondary Edn.Staff
RECEIPTS_PAYMENTS
Commissioner
Sr No
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Bank Branch
Text
50
Yes
The Bank Branch location is the name of the branch of the bank which is registered with Central Bank. It helps to identify any specific branch of the bank
2
Bank Branch Code
Alphanumeric
50
Yes
A unique code that identifies the bank branch, this will help the user to easily identify the bank branch
3
Account number
Alphanumeric
20
Yes
The Account number is a Bank Account number in which State holds a bank account. With the bank account number, the bill payment can be made to the correct account, also while doing the RTGS fund transfer the amount can be transferred to the respective firms or individual account
4
Fund
Text
50
Yes
The Fund indicate the Fund name against each bank account. This will facilitate in support to track the fund amount, receipts and utilization by individual bank account. Click on Funds to view the Fund master data
5
Account Type (COA Grouping)
Alphanumeric
250
Yes
The Account Type indicates the type of account which the state hold an account in a particular branch of the bank. This is also selected from the list of minor or sub minor codes under “450” Major head
6
Description
Text
250
No
A short description is given to the account type
7
Usage Type
Text
250
Yes
The Usage type indicates a bank account is used for, whether a particular account is used to make payments or used for collection purpose and used for both receipt & payment purpose
8
Pay To
Text
100
No
The “Pay To” indicates payments to be made to a particular bill or paying the relevant government department all the statutory remittances like Provident fund, TDS, etc using the particular bank account
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Activity
Example
1
The Fund Name should not contain any special characters
Municipal Fund : [Allowed]
#Municipal Fund! : [Not allowed]
Sr. No
Account detail type*
Name*
Code*
Narration
1
Telephone
0999784563
001
Telephone Number
2
Other Creditors
Park Welfare Society
Park Welfare
Park Welfare
Sr No
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Account Detail Type
Text
100
Yes
The Account detail type indicates the name of the subledger category name, this will help the user to identify the subledger account while recording the transaction
2
Name
Alphanumeric
50
Yes
The name of the subledger master, wherein the user will record the transaction at the most details level
3
Code
Alphanumeric
50
Yes
The unique code gives to the Subledger master
4
Narration
Text
250
No
A short narration provided to the subledger master
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Activity
Example
1
The name should be unique and should not contain any special characters
Telephone : [Allowed]
#Telephone! : [Not allowed]
Sr No*
Financial Year*
Department*
Fund Code*
Function Code*
Account Code*
Subledger Category
Entity
Debit
Credit
1
2020-21
Account Branch
01
000300
4101010
NIL
NIL
1000000
2
2020-21
Street Light
01
202406
3301010
NIL
NIL
2000000
3
2020-21
Street Light
01
202406
3401002
Contractor
MH003
1000000
Sr No
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Financial Year
Number
10
Yes
The Financial year indicates the year for the which the opening balances will be entered for the GL accounts. This can be the opening balance of the year or the date from which the system is going live
2
Department
Text
250
Yes
A department indicates to which the GL code is linked, the user while entering the opening balance can select a particular department to which amount will be entered
3
Fund Code
Alphanumeric
50
Yes
A GL Code can be linked for the validation of the Fund Code, the user while entering the opening balance can select a particular fund code to which amount will be entered
4
Function Code
Alphanumeric
50
Yes
A GL Code can be linked for the validation of the Function Code, the user while entering the opening balance can select a particular function Code to which amount will be entered
5
Account Code
Alphanumeric
50
Yes
A General Ledger Code (GL Code) is a string of 7 to 9 digit numeric characters assigned to each financial entry in a State/ULB ledger. A GL Code can be assigned to different debit or credit entries to make opening balances. A detailed GL code to be provided to update the opening balance
6
Subledger Category
Text
250
No
The Sub Ledger type indicates if the GL code is linked to a sub-ledger account which is contractor, supplier and employee then the user can select the sub-ledger type while entering the opening balances. Click SubLedger Category for the master details
7
Entity
Alphanumeric
50
No
When the Sub Ledger is linked to the individual entity, the user can select an entity while entering the opening balances. So when a sub-ledger is “Contractor” then the value here will be “Contractor code”
8
Credit
Number
50
No
If the opening balance for a Financial year or a period of a particular GL account is a credit Balance then the user needs to update the amount under the Credit column
9
Debit
Number
50
No
If the opening balance for a Financial year or a period of a particular GL account is a Debit Balance then the user needs to update the amount under the Debit column
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Activity
Example
1
The Amount cannot be entered in both the Debit and Credit column for a particular GL code.
Debit:100000 [Allowed]
Debit:10000 Credit:10000 [Not Allowed]
2
If for a particular account code the data is captured at sub-ledger level then the Sub-ledger and entity should be selected,
Account Head: Security Deposit
Subledger Type: Contractor:
Entity: Cont003 (Test Contractor)
Sr. No*
Deduction Name*
Deduction Code*
Subledger Category
Account Code*
*Remitted To
IFSC Code
Account No
Description
1
CPF Deduction
CPF
Employee
3502003 - CPF Deduction
Central Provident Fund Board
UBIN0XXXX69
2XXXX1234XX4
CPF Deduction
2
TDS Deduction
TDS
Contractor
3502001 - TDS Deduction
Central Government
ICICI00XXXX7
6XXX97156XX5
TDS Deduction
3
TDS from Employees
TDS Employees
Employee
3502008 - TDS Employee
Central Government
HDFC00XXX51
9XXXX759691XX7
TDS from Employees
Sr No
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Deduction Name
Text
250
Yes
The name for the deduction head, wherein users use this deduction head name while posting the transactions into the system and also user can generate an individual report using the deduction name.
2
Deduction Code
Alphanumeric
20
Yes
A unique code that identifies the deduction name, this will help the user to easily identify the deduction type while doing a transaction.
3
Subledger Category
Text
250
No
The Subledger type is the value which will tell the party type associated with the deduction. This will be aligned with the standard set of sub-ledger types in DIGIT like - Contractor, Supplier and Employee. Example: When payment to be made for a contractor, TDS deduction is done and “Contractor” would be mapped to the sub-ledger type. Click SubLedger Category for the master details
4
Account Code
Alphanumeric
50
Yes
A particular GL code would be mapped for the deduction code, these accounts codes would be used in the transaction when a deduction needs to be made. If the sub-ledger type is present then the GL code has to be a control code of that sub-ledger. If sub-ledger type is blank, then the GL code mapped will be a non-control code
5
Remitted To
Text
250
Yes
The “Remitted To” represent the relevant government department to which all the statutory remittances like Provident fund, TDS, CPF and ESI etc are deducted and remitted as per the Act. So while making the payment the “Pay To” will be set to this value
6
IFSC Code
Alphanumeric
11
No
The Bank IFSC code pertaining to the bank branch to which the payment will be made for this particular deduction
7
Account No
Alphanumeric
25
No
The Bank account number represents the account number to which all the deduction which are made would be remitted
8
Description
Text
250
No
A short description shows the deduction details for which the remittance made to the relevant government department
Sr. No
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of.
Sr. No.
Activity
Example
1
Deduction Code should be unique and no special character is allowed.
CPF : [Allowed]
#CPF! : [Not allowed]
2
The format of the Account Code to be 7 to 9 digits numeric and unique no repetitive code should be entered. Only detailed account code should be listed here and this should be an active code in the COA master.
Click on Chart of Accounts for master details.
Sr. No. | *Water source | *Water sub source |
1 | Ground | Well |
2 | Ground | Hand-pump |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | Water source | Text | 64 | Yes | Water source major category |
2 | Water sub source | Text | 64 | Yes | Water source minor category |
Sr. No. | Pipe Size* | UOM* |
1 | 0.25 | Inches |
2 | 0.50 | Inches |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | Pipe size | Decimal | (2,2) | Mandatory | Value for Pipe size |
2 | UOM | Text | 256 | Mandatory | Unit of measurement for the pipe size value |
Sr. No. | *Interest based on (Bill amount/Balance pending) | *Grace Period (days) | *Interest rate (%) |
1 | Bill Amount | 15 | 5 |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | Grace period | Integer | 2 | Yes | After the bill is generated, certain days are provided to the citizen for making the payment |
2 | Interest-based on | Text | 64 | Yes | Interest can be levied on either bill amount or balance pending if partial payments are made against the bill. |
3 | Interest rate | Decimal | (3,2) | Yes | Time-based Interest percentage |
The Sewerage Charges module offers a consolidated platform for managing new and existing sewerage connections. The module eliminates the need for manual processing and streamlines the key sewerage management functions for operational efficiency. DIGIT Water & Sewerage (W&S) module enables automated processing of new connection requests, generating water bills, and facilitating online payment of bills.
DIGIT Sewerage Charges module enables citizens to -
Apply for new sewerage connections.
Upload documents required for processing new connections.
Pay sewerage connection charges and bills using online payment gateway.
Receive SMS alerts on application status, bills generated, payment due date, and payment receipt confirmation.
Download sewerage connection approval letter, payment receipts, and bills online.
DIGIT Sewerage module enables employees at ULB and State level to -
Process applications using customizable workflows.
Configure sewerage charges, interest, and penalty calculation logic.
View custom dashboards for module statistics.
Filter search results using advanced configurable search parameters.
None
None
The Billing and Payments module serves the billing requirements of various ULB departments. The module caters to fulfil the demands generated by the revenue collection needs of the business services.
The module enables ULBs to -
Generate bills
Search bills
Update bills
ULB Level
None
A workflow process is a series of sequential tasks that are carried out based on user-defined rules or conditions, to execute a business process. It is a collection of data, rules, and tasks that need to be completed to achieve a certain business outcome.
In DIGIT, workflow for a business process is divided into three units out of which two are completely configurable while the remaining is fixed and lays the foundation of the other two.
This is the first unit which defines the actions and its nature which are basically executed during the workflow process by the workflow actors. It plays the foundation and configurable in nature as per the ground needs.
This is the second unit which defines the number of steps a workflow process may have and then trigger the creation role for each and every step with appropriate rights to perform a set of actions at each step. It is completely configurable.
This is the third unit which defines the workflow process including the steps, roles with actions and the present, next and previous state of a step/level of the workflow process. It is completely configurable.
The Decision Support System in DIGIT platform can be configured to provide customized insights and statistics on the dashboard. This section offers information on how to configure the DSS parameters for maximized efficiency.
Details coming soon!!
Sr. No. | *Property Usage Type | *Water consumed value from (units) | *Water consumed value to (units) | *Rate (in Rs/ unit) |
1 | Residential | 1 | 150 | 3 |
2 | Residential | 151 | 300 | 4 |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | Property usage type | Alphanumeric | 64 | Yes |
2 | Water consumed value from | Decimal | (5,3) | Yes | From value for water consumed |
3 | Water consumed value to | Decimal | (5,3) | Yes | To value for water consumed |
4 | Rate | Decimal | (3,3) | Yes | Consumption charges per unit corresponding to the usage type |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Property Usage Type* | Property size value from (units) | Property size value to (units) | No. of taps | Rate |
1 | Residential | 1 | 150 | 1 | 200 |
2 | Residential | 151 | 200 | 1 | 300 |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | Property usage type | Alphanumeric | 64 | Yes |
2 | Slab (Property size value) | Decimal | (10,2) | Yes | From and to value for property size |
3 | No. of Taps | Integer | 2 | Yes | No. of Taps to be recorded for calculation of water charges |
4 | Rate | Decimal | (3,2) | Yes | Consumption charges per unit corresponding to the usage type |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
2 | UOM should same for all the values provided pipe size in the template | E.g. If it is given as Inches then it should be inches for all. |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
The penalty is levied on the consumer if the consumer fails to make the payment for the bill raised before a specified due date. The consumer has to make the full payment before the due date to avoid penalty charges. The number of days after which the penalty is applicable should be configurable at the ULB level.
The penalty can be -
Fixed amount; or
Percentage: In case of percentage, it can be levied on either
Entire bill amount; or
Balance pending when partial payments have been made
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter the applicable value for the Grace Period.
Enter the corresponding Penalty Flat Amount.
Select the relevant parameter for Penalty Based On to specify if the calculation of the penalty is based on the bill amount or the pending balance.
Enter the applicable percentage value for calculating the Penalty amount.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
Separate Entity Specific Checklist is not required for this module data.
Interest is levied on the consumer if the consumer fails to make the bill payment before a specified due date. The consumer has to make the full payment before the due date to avoid interest charges. The number of days after which the interest is applicable is configurable at the ULB level. The interest amount is charged to the consumer on a daily basis once the specified grace period is over and till the bill payment is done.
Interest rate: The interest rate on a daily basis can be levied on -
Entire bill amount
Balance pending when partial payments have been made
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter the applicable Grace Period for calculating interest.
Select the relevant parameter for Interest-Based On to specify if the interest is applied to the bill amount or pending balance.
Enter the applicable percentage value for Interest Rate that will be used to calculate the interest amount.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
Separate Entity Specific Checklist is not required for this module data.
Tax is levied by the government in certain brackets, i.e there are certain components of a tax which sum up and make the final trans-actionable amount. For example, a property tax could have swatch-ta tax, fire cess and certain other components which sum up and make a final amount.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Get all the tax heads for a particular module and then proceed to the next module.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed on 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
Sewerage Charges are recurring charges levied for a pre-defined billing period. The billing period is configurable as per the state or ULB requirement. The rate for calculation of sewerage charges can vary widely and is dependent upon various parameters. For instance, they can be dependent either upon plot size slab combined with property usage type or solely dependent upon property usage type. In some cases, sewerage charges can also be levied as a percentage of water charges.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Please reach out to the person who has shared this template with you to discuss and clear your doubts.
Select the relevant Property Usage Type from the available drop-down list.
Enter the From and To value for property size to specify the range applicable for the selected property.
Enter the Flat Fee applicable for the selected property and Slab.
Enter the applicable Percentage of Water Charges value. The sewerage charges will be calculated as a percentage of the water charges.
Enter the corresponding consumption Rate per unit.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
Separate Entity Specific Checklist is not required for this module data.
Tax is levied by the government in certain brackets, i.e there are certain components of a tax which sum up and make the final trans-actionable amount. For example, a property tax could have swatch-ta tax, fire cess and certain other components which sum up and make a final amount.
Data given in the table is sample data for reference.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Get all the tax heads for a particular module and then proceed to the next module.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed on 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.
This checklist covers all the activities which are common across the entities.
Not Applicable
Workflow action defined as an activity which is performed by a workflow user on a service request/ application during the workflow. All the workflow actions are predefined and performed a well-defined job once performed.
In its nature actions are not configurable, only the localization of actions is permissible as a configuration.
Actions are standard and are not configurable, hence the template, data definition and standard procedure to fill the template are not needed. This page is created to provide the information and helping the defined workflow process.
Not applicable
Not applicable
Not applicable
Not applicable
Bill format can be configured on a module level. Few components on the DIGIT sample bill can be configured on a state level and few at ULB level. Components that can be changed on a module level can be categorized as mentioned:
Important messages: Values can be configured on a module level - state level
Data given in the table is sample data for reference.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Get information about the bill format followed by state
Classify the components on the bill and place it under any category
Map the particulars under each category with DIGIT sample bill
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one 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.
This checklist covers all the activities which are common across the entities.
Entity Specific Checklist is not required separately.
The common configuration details required for all modules are available in this section. Refer to the required for processing applications across modules, learn which to which services, find the for filling master data templates, and get the answers to common .
Key Performance Indicators(KPI) are a way of showing certain insights from the data available which would help the key management authorities to take important business decisions in order to improve the business, enhance the business process and help the people improve the way of functioning. This exercise largely becomes dependent on the data.
The insight could be shown in various available forms such as line graph, bar graph or a tabular format.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Present the client with information about various available chart types.
Show the client how the various KPI’s will look on the web page by showing the reference page from the attachments.
After which the gather the information for various chart types and the information that the chart types have to display in the description column.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity:
Workflow levels are defined for a service with Rights/Role to perform a set of Workflow Actions. There would one or more than one levels involved in a workflow process. This page helps to understand and then define all the levels with its job description and fill in a standard template.
Data given in the above table is sample 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 all different types of services on the basis of ULB’s functions to create a workflow.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
Please discuss with a relevant department head before finalizing the workflow.
The workflow process is a set of steps through which information flows in sequence and the which derives the actors are assigned to a step to complete the work defined for that . The states of each level are derived based on the information received from the previous step.
Data given in the above table is sample 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.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 point mentioned in the checklist.
The checklist is a set of activities to be performed once 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.
This checklist covers all the activities which are common across the entities.
Please discuss with a relevant department head before finalizing the workflow.
Refer
Specifies the
Sr. No.
*Penalty based on (Bill amount/Balance pending)
*Grace period (days)
Penalty flat amount (Rs)
Penalty (%)
1
Balance Pending
15
40
10
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Grace period
Integer
2
Yes
After the bill is generated, certain days are provided to the citizen for making the payment
2
Penalty flat amount
Decimal
(3,2)
Yes
If the penalty is not levied on a percentage basis, it is generally a flat fee which is penalty charges amount
3
Penalty based on
Text
64
Yes
The penalty can be a certain percentage of the bill amount or balance pending if partial payments are made against the bill
4
Penalty (%)
Decimal
(3,2)
Yes
The penalty is calculated as a percentage amount based on either Bill amount or Balance pending
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
*Interest based on (Bill amount/Balance pending)
*Grace Period (days)
*Interest rate
1
Balance Pending
15
5
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Grace period
Integer
2
Yes
After the bill is generated, certain days are provided to the citizen for making the payment
2
Interest-based on
Text
64
Yes
Interest can be levied on either bill amount or balance pending if partial payments are made against the bill
3
Interest rate
Decimal
(3,2)
Yes
Time-based Interest percentage
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Code*
Service*
Category*
Name*
Is Debit*
Is Actual Demand*
Order*
1
PT_UNIT_PENALTY
PT
Penalty
PT Penalty
FALSE
FALSE
1
2
PT_UNIT_EXEMPTION
PT
Exemption
PT Exemption
TRUE
TRUE
2
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1.
Code
Alphanumeric
64
Yes
The code for the tax that is being levied
2.
Service
Text
256
Yes
This is the module or the name of the service for which the tax head is being mentioned
3.
Category
Text
256
Yes
The category to which the tax head belongs such as Penalty or exemption or cess
4.
Name
Text
256
Yes
This is the name/description of the tax head
5.
Is Debit
Text
NA
Yes
In case the tax head is an amount that needs to be added up to the property tax, then this needs to be TRUE else FALSE
6.
Is Actual Demand
Text
NA
Yes
In case the tax head is an amount that needs to be subtracted from the property tax, then this needs to be TRUE else FALSE
7
Order
Integer
5
Yes
The order in which the mentioned tax head should appear on the screen
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
*Property Usage Type
*Property size slab from (units)
*Property size slab to (units)
*Percentage of water charges (%)
*Flat fee (in Rs)
*Rate
1
Residential
1
150
30
200
5
2
Residential
151
300
40
500
10
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Property usage type
Text
64
Yes
Refer to property usage type
2
Slab (Property size value)
Decimal
(10,2)
Yes
From and to value for property size
3
Flat fee
Decimal
(3,2)
Yes
Flat sewerage charges collected based on property usage type
4
Percentage of water charges
Decimal
(3,2)
Yes
Percent value
5
Rate
Decimal
(3,2)
Yes
Consumption charges per unit corresponding to the usage type
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Code*
Service*
Category*
Name*
Is Debit*
Is Actual Demand*
Order*
1
PT_UNIT_PENALTY
PT
Penalty
PT Penalty
FALSE
FALSE
1
2
PT_UNIT_EXEMPTION
PT
Exemption
PT Exemption
TRUE
TRUE
2
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1.
Code
Alphanumeric
64
Yes
The code for the tax that is being levied
2.
Service
Text
256
Yes
This is the module or the name of the service for which the tax head is being mentioned
3.
Category
Text
256
Yes
The category to which the tax head belongs such as Penalty or exemption or cess
4.
Name
Text
256
Yes
This is the name/description of the tax head
5.
Is Debit
Text
NA
Yes
In case the tax head is an amount that needs to be added up to the property tax, then this needs to be TRUE else FALSE
6.
Is Actual Demand
Text
NA
Yes
In case the tax head is an amount that needs to be subtracted from the property tax, then this needs to be TRUE else FALSE
7
Order
Integer
5
Yes
The order in which the mentioned tax head should appear on the screen
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
S. No.
Action
Description
Module(s)
1
Initiate
The action will start the application for citizen and CEMP
Trade Licenses, Property Tax, Building Plan Approval
2
Edit
Using this action the application can be opened in editable form and any changes can be performed
Trade Licenses, Property Tax, Building Plan Approval
3
Submit
This action will freeze the application from citizen or CEMP and proceed further for workflow
Trade Licenses, Property Tax, Building Plan Approval
4
Verify and Forward
This action will proceed application to the next stage of the workflow process and also assigns tasks to the next user in the workflow (if needed)
Trade Licenses, Property Tax, Building Plan Approval
5
Pay
This action will help to pay application fees
Trade Licenses, Property Tax, Building Plan Approval
6
Approve
This action will be the last stage of application workflow which will grant permission for a specific application
Trade Licenses, Property Tax, Building Plan Approval
7
Activate connection
This action will create a consumer no. against the application and demand generation can start
Water and Sewerage Charges
8
Reject
This action will reject the application, the application rejected can’t be processed further or with the help of it, citizens can not re-apply. He has to start a new application next time.
Trade Licenses, Property Tax, Building Plan Approval
9
Send Back
An actor can assign back the application to the previous state if any edits/changes are required
Trade Licenses, Property Tax, Building Plan Approval
10
Send Back to Citizen
An actor can assign back the application to the citizen if any edits/changes are required
Trade Licenses, Property Tax, Building Plan Approval
11
View
Anyone in the workflow can view the application and task details
Trade Licenses, Property Tax, Building Plan Approval
12
Comment
Comments can be recorded before any action is taken which can change the state of the application
Trade Licenses, Property Tax, Building Plan Approval
13
Download/ Print
Download/Print of any artefacts can be configured as per the requirement for application processing
All Modules
14
Forward
This action will not create any bill but will be forwarded to the next level review and approve
Finance
15
Create and Approve
In this action, the user who initiates the action can create and approve the bill. (Here there should a threshold amount to be set up)
Finance
16
Save
In this action, the approver can Save the bill before it is approved or rejected
Finance
17
Verify and Approve
This action will help the approver to approve the bill if he/she feels all the information is updated correctly
Finance
18
Reject
This action will help the approver to reject the bill if he/she feels all the information is not correct and may need further clarification.
Finance
19
Send back to Assistant
This action will help to send back the notification on the bill is rejected from the approver
Finance
20
Cancel
This action will help the approver to cancel the bill if he/she feels that the bill need to be rejected
Finance
Sr. No.
Business
Category
Particulars
1
Water Charges
Important messages
5% rebate to be given on advance payment on the bills
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Category
Text
64
Yes
To list out the components on the bill, every particular can be grouped into a category
2
Particulars
Alphanumeric
256
Yes
Each category can have multiple entries under it, ie particulars
3
Business
Text
64
Yes
The business for which the Bill format is to be configured
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No | Module* | KPI Chart Type* | Description* |
PGR | Line Chart | Showing the status of closed complaints over a year month-wise |
Pie Chart | Showing the various type of complaints |
Metric | Showing the rate of different complaint status by percentage in a tabular format |
2. | Property Tax | Horizontal Bar Graph | Showing the various information about property application status month-wise over a year |
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
1 | Module Name | Text | 256 | Yes | The name of the module for which the KPI chart types have to be defined |
2 | KPI Chart Type | Text | 256 | Yes | The type of chart which has to display information |
3 | Description | Text | 256 | Yes | A brief description of the information that the chart has to display. Steps to fill Data |
Sr. No. | Checklist Parameter | Example |
Make sure that the chart types are chosen from the list of available chart types from the attachment section | - |
Sr. No. | Module | Service | Workflow Level | Task | Role |
1 | Finance | Bill Accounting | Level 1 | Create Bill | Accounts Clerk |
2 | Finance | Bill Accounting | Level 2 | Create and Approve | Accounts Clerk |
3 | Finance | Bill Accounting | Level 3 | Forward for Approval | Chief Accountant |
4 | Finance | Bill Accounting | Level 4 | Verify the Bill | Chief Accountant |
5 | Finance | Bill Accounting | Level 5 | Approval | Approver |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Module | Text | 64 | Yes | The module indicates for which the user would be mapped for a specific module to perform the action |
2 | Service | Text | 64 | Yes | The service indicates the type of process which the user performs in a particular module |
3 | Workflow Level | Integer | 2 | Yes | The workflow level indicates when a process has executed the level at which the flow of the process in progress |
4 | Task | Text | 64 | Yes | The task refers to which state the action is in progress during the workflow |
5 | Job Description | Text | 256 | Yes | A short description provided for the role (Example: Designation of the Role) |
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
1 | Current State | Text | 256 | Yes | The Current State indicates the stage at which the process of the workflow in progress |
2 | Action | Reference | 64 | Yes | The Action indicates the activity that can be performed at the respective stage in the workflow. This refers to Workflow Actions |
3 | Next State | Text | 256 | Yes | The Next State is the state in the workflow that gets updated to in the respective stage on performing the action. (Example: assigning the for approval from one person to next person) |
4 | Role Name | Reference | 64 | Yes | The role is the different hierarchy of people with designation who are authorized to initiate, approval or rejecting the process. It refers to Workflow Levels |
5 | SLA | Integer | 2 | No | The SLA indicates the time-frame within which the action to be completed |
Sr. No. | Current State | Workflow Actions | Next State | Role Name | SLA |
1 | Create and Approve | Approved | Assistant | NA |
2 | Forward | Pending for Approval | Assistant | NA |
3 | Pending for Approval | Verify and Approve | Approved | Supervisor | NA |
4 | Pending for Approval | Save | Pending for Approval | Supervisor | NA |
5 | Pending for Approval | Reject | Rejected | Supervisor | NA |
6 | Pending for Approval | Send Back to Assistant | Rejected for Review | Supervisor | NA |
7 | Rejected for Review | Forward | Pending for Approval | Assistant | NA |
8 | Rejected for Review | Cancel | Rejected | Assistant | NA |
Sr. No. | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
Sr. No | Checklist Parameter | Example |
1 | Make sure that each and every point in this reference list has been taken care of |
The penalty is levied on the consumer in case the consumer fails to make the payment for the bill raised before the specified due date. The consumer has to make the full payment before the due date to avoid penalty charges. The number of days after which the penalty is applicable is configurable at the ULB level. The penalty calculation logic may differ from one state or ULB to another.
The penalty can be -
Fixed amount
Percentage: When it is a percentage, it can be levied on
Entire bill amount
Balance pending when partial payments have been made
Data given in the table is sample data for reference.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter an appropriate value for Penalty Based On.
Enter a value for the Grace Period.
Enter the Penalty Flat Amount.
Enter the Penalty value in percent.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
Separate Entity Specific Checklist is not required for this module data.
Sr. No.
*Penalty based on (Bill amount/Balance pending)
*Grace period (days)
*Penalty flat amount (Rs)
*Penalty (%)
1
Balance Pending
15
40
10
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Grace period
Integer
2
Yes
After the bill is generated, certain days are provided to the citizen for making the payment
2
Penalty flat amount
Decimal
(3,2)
Yes
If the penalty is not levied on a percentage basis, it is generally a flat fee which is penalty charges amount
3
Penalty based on
Text
64
Yes
The penalty can be a certain percentage of the bill amount or balance pending if partial payments are made against the bill
4
Penalty (%)
Decimal
(3,2)
Yes
The penalty is calculated as a percentage amount based on either Bill amount or Balance pending
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of