DIGIT Urban Stack is a set of Open APIs, services, and reference implementations, setup as a public good, to allow government entities, businesses, startups, and civil society to use a unique digital Infrastructure and build solutions for urban India at a large scale. It provides a set of open standards, specifications and documentation to create a level playing field and enable ecosystem players to innovate on the stack. As a public good, the platform is provided without profit or restriction to all members of society.

• Open Source - DIGIT is Open Source and has been built using the best in class Open Source technology stacks powering the most advanced companies in the world. DIGIT is able to provide the lowest total cost of ownership and helps ensure that governments retain strategic control of their systems and data.

• Mobile-Enabled - DIGIT has adopted a mobile-first approach, with robust mobile applications enabling citizens to easily access government services through their phones. Government officials and field workers are also empowered with mobile applications that enable them to deliver 24×7 governance with ease.

• Real-time Dashboards - DIGIT’s real-time dashboards provide governments with actionable insights on demand. Administrators and department heads are empowered with verified data that enables them to manage their work and budgets better. Field level employee reports enable effective performance management and ensure efficient usage of government resources.

Our Core Principles

DIGIT focuses on inclusion and is designed on the principle of enhancing both platform openness and choice for citizens. The platform uses open APIs and standards, creating a powerful framework to drive convergence across the multiple systems currently in use and to lower the barrier to entry for locally-developed solutions. Keeping in mind that most Indians use the internet through their phones, we follow and advocate a “mobile-first” approach, while supporting multi-channel access to accommodate diverse needs and preferences.

Know more about our Ecosystem or Contact Us for more details.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Details coming soon..

Details coming soon..

Join the virtual DIGIT Technical Training sessions to learn in-depth about the DIGIT platform architecture, key capabilities, and applications. These sessions will help understand DIGIT products, platform configurations, customizations and extension possibilities.

Event registration links and session details are provided below. Click on the Register button to enrol for the sessions.

DIGIT-Public Grievance Redressal (PGR) is a self-serve web and mobile-based, easy-to-use and configurable product for submission of grievances by the citizens from anywhere, anytime. For the speedy and efficient resolution of civic related complaints, DIGIT-PGR enables the citizens to report the issues in real-time and enables municipal employees with easy identification of the issues and helps them to initiate corrective actions, without any delay.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

The citizen pays the fees for miscellaneous services through the CEs or FEs. Once the payment transaction is complete the citizen can access the payment receipts online.

Citizens can

• Search receipts

• Download receipts

• Print receipts

Search Download And Print Receipts

Citizens can search for payment receipts and download or print these online. To search for payment receipts navigate to the Collections option in the sidebar main menu.

Enter the relevant search parameter. The system enables you to search using payment Receipt No. or Service Category, or payee Mobile No. Click on the Search button.

The system will display the relevant search results in the panel below. Click on the relevant record to view the payment receipt.

The system will generate a pdf format of the payment receipt. Click on the download icon on the pdf page to download the receipt.

Click on the Print icon on the pdf page to print the receipt.

Click on the Reset button to renew your search with different parameters.

All content on this page by is licensed under a .

Details coming soon..

DIGIT offers several modules. Each module is designed to automate the manual workflows for various governance units.

Key Benefits

DIGIT enables ULBs to be more effective and accountable—and to make better, data-driven decisions. The platform ensures both interoperability among ULBs and rapid development of new modules by a wide array of software partners.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Objective

Welcome to the Public Grievances and Redressal or PGR product demo script. This document is meant to guide DIGIT implementation partners and demo planners through the module demo. The key objective of the demo is to walk users through the PGR module and the key features supported by the module.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

DIGIT-Property Tax (PT) is a self-serve web and mobile-based, easy-to-use and configurable product that addresses the objectives of municipal corporations and local government to automate all property tax operations, thus providing property tax assessment and payment services to citizens in real-time.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

About mCollect

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.

Key Features

1. Capture details of payment collection

2. Generate and print the collection receipt

3. Access to dashboard analytics

4. Generate reports for administration

Section Overview

This section contains all docs and information required to understand the MCS module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the MCS module.

• Functional Specifications

• MCS Roadmap

• MCS User Manual

• Product Brochure

• MCS Workflows

• Master Data Configuration Template

• MCS Service Configuration

• Implementation Handbook

• Demo Script

Navigation Tips

• Click on the embedded links within the content to browse topic details

• Use the Contents links available on the right side of the screen to move to a specific heading

• Find the list of Related Docs links at the bottom of each page to browse through additional product details.

Contact Us

Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on MCS module deployment.

#147/J, 1st floor, 10th Cross, 12th Main, 3rd Block, Koramangala, Bangalore 560034

• ​​

• +91 80 4125 5708

• [email protected]

​All content on this page by is licensed under a .

About PGR

DIGIT-Public Grievance & Redressal (PGR) is a web and mobile-enabled system designed to register and resolve public grievances. The seamless interface enables citizens to submit their grievances anytime and from anywhere. The complaints are routed to the concerned municipal departments and employees who work towards resolving the issues within a specified time limit. This digitized and easily configurable platform facilitates speedy and efficient resolution of civic complaints while providing the local urban bodies with an intuitive system that categorizes issues and helps them to initiate corrective actions, without any delay.

Key Features

• Efficient public grievance redressal mechanism

• Simple user registration and login system

• Simplified complaint and sub complaint selection options

• GIS location mapping

• Easy complaint status tracking options

• Interactive dashboards

• Auto-escalations and SLAs

Section Overview

This section contains all docs and information required to understand the PGR module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the PGR module.

• Functional Specifications

• PGR Roadmap

• PGR User Manual

• Product Brochure

• PGR Workflows

• Master Data Configuration Template

• PGR Service Configuration

• Implementation Handbook

• Demo Script

Contact Us

Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on PGR module deployment.

All content on this page by is licensed under a .

Introduction

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.

Module Features

DIGIT Sewerage Charges module enables citizens to -

1. Apply for new sewerage connections.

2. Upload documents required for processing new connections.

3. Pay sewerage connection charges and bills using online payment gateway.

4. Receive SMS alerts on application status, bills generated, payment due date, and payment receipt confirmation.

5. Download sewerage connection approval letter, payment receipts, and bills online.

DIGIT Sewerage module enables employees at ULB and State level to -

1. Process applications using customizable workflows.

2. Configure sewerage charges, interest, and penalty calculation logic.

3. View custom dashboards for module statistics.

4. Filter search results using advanced configurable search parameters.

Module Ontology

State Level

None

ULB Level

Module Reports

None

All content on this page by is licensed under a .

About Water & Sewerage

The Water & Sewerage module offers a consolidated platform for managing new and existing water and sewerage connections. The module eliminates the need for manual processing and streamlines the key water or 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.

Key Features

DIGIT W&S module enables citizens to -

1. Apply for new sewerage or water connections

2. Upload documents required for processing new connections

3. Pay water or sewerage connection charges and bills using an online payment gateway

4. Receive SMS alerts on application status, bills generated, payment due date, and payment receipt confirmation

5. Download water or sewerage connection approval letter, payment receipts, and bills online

DIGIT W&S module enables employees at ULB and State level to -

1. Process applications using customizable workflows

2. Configure water and sewerage charges, interest, and penalty calculation logic

3. View custom dashboards for module statistics

4. Filter search results using advanced configurable search parameters

Section Overview

This section contains all docs and information required to understand the W&S module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the W&S module.

• Functional Specifications

• W&S Roadmap

• W&S User Manual

• Product Brochure

• W&S Workflows

• Master Data Configuration Template

• W&S Service Configuration

• Implementation Handbook

• Demo Script

Contact Us

Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on W&S module deployment.

All content on this page by is licensed under a .

Introduction

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.

Module Features

DIGIT PGR offers a variety of features to make complaint lodging and redressal easy for residents and employees of a ULB. A list of standard features is given below.

1. Web and mobile interface to lodge, track, reopen, and update feedback on the complaint made by the citizen.

2. Web and mobile interface to comment, forward, and close the complaint by the ULB employees.

Module Ontology

State Level

1. ​

2. ​

ULB Level

1. ​​

Module Reports

None

All content on this page by is licensed under a .

About Property Tax

DIGIT-Property Tax (PT) is a self-serve web and mobile-based, easy-to-use and configurable product that addresses the objectives of municipal corporations and local government to automate all property tax operations, thus providing property tax assessment and payment services to citizens in real-time.

Key Features

• Manage property database

• Various payment options available to citizens to make payments from their convenient places

• Auto-generated defaulters’ list and real-time online tracking

Section Overview

This section contains all docs and information required to understand the PT module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the PT module.

• Functional Specifications

• PT Roadmap

• PT User Manual

• Product Brochure

• PT Workflows

• Master Data Configuration Template

• PT Service Configuration

• Implementation Handbook

• Demo Script

Contact Us

Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on PT module deployment.

All content on this page by is licensed under a .

All content on this page by is licensed under a .

Introduction

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.

Module Features

1. Capture details of payment collection

2. Generate and print the collection receipt

3. Access to dashboard analytics

4. Generate reports for administration

Module Ontology

State Level

ULB Level

None

Module Reports

1. Receipt Register

2. Cancelled Receipt Register

All content on this page by is licensed under a .

Overview

Bill Amendment is a platform-level feature that can be used to create credit/ debit notes against a consumer for a configured service. Demand revision required due to out of system calculations i.e. tax exemptions, court case settlements, one-time settlement schemes can be performed using this feature.

Release Highlights

1. Workflow-based application approval system for better accountability of demand revision.

2. Artifact generation in the form of credit/debit note for record purposes

3. Auto application of note amount into latest or upcoming bills

Release Features

Known Issues

Upcoming Release Features

1. New UI for better accessibility

2. Application initiation from the citizen side

3. Extending this feature to deal with the current year and previous year items

Reference Doc Links

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

About TL

DIGIT-Trade License (TL) enables local government to regulate the trade and protect the interest of the public at large against the health hazard and inconvenience which a business may cause. With DIGIT-TL traders can obtain the trade certificate in a simplified manner and ensure compliance with rules and safety guidelines issued by the government. The module offers the citizens and governance bodies a convenient and transparent means of processing trade licenses.

The Trade License application 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.

Key Features

DIGIT Trade License module enables citizens to -

1. Apply for new trade license or renew an existing trade license.

2. Upload all the relevant documents required for the license.

3. Make payment for the Trade License (New/Renewal) fee using the online payment gateway.

4. Receive notifications and alerts by emails or SMS for new application status updates and pending renewals.

5. Download Trade License, Payment & Acknowledgement Receipts online.

DIGIT Trade License module enables employees to -

1. Create flexible role-based workflows.

2. Configure license fees calculation logic.

3. View custom dashboards for module statistics.

4. Filter search results using advanced configurable search parameters.

Section Overview

This section contains all docs and information required to understand the TL module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the TL module.

• Functional Specifications

• TL Roadmap

• TL User Manual

• Product Brochure

• TL Workflows

• Master Data Configuration Template

• TL Service Configuration

• Implementation Handbook

• Demo Script

Contact Us

Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on TL module deployment.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

The DIGIT-Trade License application 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.

Module Features

DIGIT Trade License module enables citizens to -

1. Apply for new trade license or renew an existing trade license.

2. Upload all the relevant documents required for the license.

3. Make payment for the Trade License (New/Renewal) fee using the online payment gateway.

4. Receive notifications and alerts by emails or SMS for new application status updates and pending renewals.

5. Download Trade License, Payment & Acknowledgement Receipts online.

DIGIT Trade License module enables employees to -

1. Create flexible role-based workflows.

2. Configure license fees calculation logic.

3. View custom dashboards for module statistics.

4. Filter search results using advanced configurable search parameters.

Module Ontology

State Level

1. Trade Category

2. Trade Type

3. Trade Sub Type

4. Trade License Documents Attachment

5. Structure Type

6. Structure Subtype

ULB Level

1. Trade License Fee

Module Reports

1. Receipt Register

2. Application Status

3. Cancelled Receipt Register

4. ULBwise Collection Report

5. ULBwise Application Status

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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

Data Table

The data described in the above table is a sample.

Configuration Data Templateconfiguration-data-template-pt-master.xlsx - 10KB

Sample Dataconfiguration-sample-data-pt-master.xlsx - 15KB

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

The Public Grievance Redressal or the PGR is a standardized solution offering on the DIGIT platform to register and redress citizen grievances. It provides a transparent and trackable mechanism to solve public grievances by inducing responsive administration. PGR enables the citizens to file complaints using various channels and helps the municipal employees to resolve them timely.

Key Features

• Citizens can lodge complaints, track, reopen and rate complaints through the web portal or the mobile application.

• ULB employees too can use the web or mobile interface to comment, forward, assign, verify, share, and resolve citizen complaints.

User Roles

Refer to the table below to understand the different user roles and the scope of action linked to each role. The manual provides a detailed description of how to use the system for each role.

Using PGR

This section guides you through the details of using the PGR module for each role. Click on the relevant role below to learn more about how to use the PGR system.

• Citizens

• CSR

• GRO

• FME

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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.

Module Features

DIGIT Water Charges module enables citizens to -

1. Apply for new water connections.

2. Upload documents required for processing new connections.

3. Pay water connection charges and water bills using an online payment gateway.

4. Receive SMS alerts on application status, bills generated, payment due date, and payment receipt confirmation.

5. Download water connection approval letter, payment receipts, and bills online.

DIGIT Water module enables employees at ULB and State level to -

1. Process applications using customizable workflows.

2. Configure water charges, interest, and penalty calculation logic.

3. View custom dashboards for module statistics.

4. Filter search results using advanced configurable search parameters.

Module Ontology

State Level

None

ULB Level

1. Pipe Size Types

2. Water Source Types

3. Water Rates (metered)

4. Water Rates (non-metered)

5. Water Penalty Rates

6. Water Interest Rates

Module Reports

None

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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 the primary factor defining the unit rates and hence configuration is needed for the DIGIT module in order to describe the property and what are the taxes it could attract.

Data Table

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.

Configuration Data Templateproperty-tax-roadtype_template_v1.xlsx - 9KB

Sample Datasample_data_propety-tax_road_type.xlsx - 9KB

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Release Highlights

eDCR Service 1.1.0 is a baselined release that has got few enhancements to the existing features.

Release Features

Upgrade Instructions

• eDCR 1.1.0: The above feature is useful and required in other states.

  • The above features are configurable. Users can enable the features if required for the selected state.

• Impact: Functionally, the upgrade to eDCR 1.1.0 will not impact the existing environments.

All content on this page by is licensed under a .

All content on this page by is licensed under a .

Introduction

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.

Module Features

The main features of the product are as given below.

1. Completely automated assessment and re-assessment of property tax against a property.

   1. Online self-assessment process

   2. Integrated workflow for ULB staff to perform the check and approve.

2. Transfer of title (Mutation)

   1. Online application

   2. Integrated workflow for ULB staff to perform the check and approve.

3. Generating the demand

4. Collection of property tax through various modes (Cash, Cheque, POS (Credit/ Debit Card), NEFT/RTGS, Online - Through Payment Gateway)

5. Auto calculation of rebate, interest and penalty.

Module Ontology

State Level

ULB Level

Module Reports

1. Receipt Register

2. Cancelled Receipt Register

3. Demand Register

All content on this page by is licensed under a .

The W&S module allows citizens to apply for new connections and pay bills online. For employees, this module enables automated processing of new connection requests, editing existing connection details, generating water bills, and facilitating online collection of bill payments.

Features and applications

The module supports the following key functions -

1. Apply for new connections

2. Pay one-time connection charges for new water or sewerage connections

3. Pay recurring bills using online payment gateway

4. Download artefacts such as application details, connection details, bills, receipts, sanction letter and estimation notice

5. Process applications using configurable workflows

User roles

Refer to the table below to understand the different user roles and the scope of action linked to each role. The applicable user roles and action items can vary from one State to another. DIGIT customizes the workflows to suit the requirements defined at the State level.

Using W&S

This section guides you through the details of using the [module name] module for each role. Click on the relevant role below to learn more about how to use the module.

All content on this page by is licensed under a .

Overview

Emptying of septic tank / Pit (Desludging) request can be created by the citizen online which will be processed by the ULB. The processed request will then be assigned to a particular desludging operator post payment of desludging charges by the citizen.

The desludging operator then completes the emptying task on the ground and transports the faecal sludge to the designated septage treatment plant where a plan operator updates the vehicle log and septage dumped at the plant.

Release Highlights

1. Citizen

   1. Create Emptying of septic tank/pit application

   2. View status of the application

   3. Make payment for an application

   4. Rate the service

2. Employee

   1. Create Emptying of septic tank/pit application

   2. Update application

   3. Make payment for an application

   4. Assign/Re-assign DSO for an application

   5. Complete request on behalf of DSO

3. Desludging operator

   1. Assign vehicle to a request

   2. Decline a request

   3. Complete request

4. FSTP Operator

   1. Update vehicle log

Release Features

Known Issues

None

Upcoming Release Features

• Dashboard and Reports

Reference Doc Links

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

CE And FE

The counter employees or field employees collect and process the miscellaneous payments on behalf of the citizens.

The CE or FE role can -

• Collect payment

• Search payment receipts

• Print receipts

• Download payment receipts

Collect Payment

CE can process and collect payments for miscellaneous services through the DIGIT web portal or the DIGIT mobile app. To process a new payment navigate to the Universal Collections option in the sidebar main menu.

Click on the New Collection button on the screen. This will open a new collection form page.

Enter the Mobile No. and Consumer Name of the payee.

Select the applicable Service Category.

The system will prompt the input of Tax amount, CGST, SGST, Field Fee, or any other details depending on the selected Service Category.

Enter the From Date and To Date to identify the applicable payment period. **Enter any additional information in the Comments** field.

Click on the Next button to move to the payment section. The Payment Collection Details page displays the fee details and capture payment form. The Fee Details panel displays the fee breakup and Total Amount details.

The Capture Payment panel displays the available payment methods. Click on the preferred payment tab. The available payment tabs are Cash, Cheque, Credit/Debit Card.

Enter the Paid By and the Payee Name details.

Enter the Payer Mobile No.

Enter the Cheque No., Cheque Date, IFSC, Bank Name, and Bank Branch details in case of payment by cheque. Enter your credit card or debit card Last 4 digits, Transaction No., and Re-enter Transaction No. details if you have selected the Credit/Debit Card payment option.

Enter the Gen/G8 Receipt No. issued at the payment counter in case payments are made offline. Enter Gen/G8 Receipt Issue Date mentioned on the receipt.

Click on the Generate Receipt button once the payment is collected or processed. The system will display the payment success acknowledgement message.

Click on the Download button to download/view the receipt. Click on the Print button to print the receipt.

Search Receipts

To search for payment receipts navigate to the Universal Collections page in the sidebar main menu.

Enter the relevant search parameter. The system enables you to search using payment Receipt No. or Service Category, or payee Mobile No. Click on the Search button.

The system will display the relevant search results in the panel below. Click on the relevant record to view the payment receipt. The system will generate a pdf format of the payment receipt.

Click on the download icon on the pdf page to download the receipt. Click on the print icon on the pdf page to print the receipt.

Click on the Reset button to renew your search with different parameters.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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.

Data Table

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

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

4. Identify usage wise mutation fee amount and fill into the given template.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

Not Applicable

Attachments

Configuration Data Templateconfigurable-data-template-mutation-fee_v1.xlsx - 10KB

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction to PT

The Property Tax (PT) module offers the citizens and governance bodies a convenient and transparent means of processing property taxes. Local governing bodies identify the applicable tax slabs for different types of properties. The PT module assesses properties, calculates tax amount, processes tax payment and generates tax collection reports.

Key Features

The PT module enables citizens to pay property taxes online. It facilitates the governing bodies process property tax payments.

User roles

Refer to the table below to understand the different user roles and the scope of action linked to each role. The applicable user roles and action items can vary from one State to another. DIGIT customizes the workflows to suit the requirements defined at the State level.

Using PT

This section guides you through the details of using the PT module for each role. Click on the relevant role below to learn more about how to use the PT system.

1. Citizens

2. Counter Employee (CE)

3. Document Verifier (DV)

4. Field Inspector (FI)

5. Approver

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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 Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to 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.

4. Enter the Pipe Size details.

5. Enter the corresponding UOM for the specified Pipe Size.

6. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

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 specifications. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

A separate entity-specific checklist is not needed for this module data.

Attachments

All content on this page by is licensed under a .

Introduction

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.

Data Table

The table above contains sample Trade Category data.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.

3. Enter a unique Trade Category Code for each trade head.

4. Enter the Trade Category Name. Some trade categories are already defined in the master. Add new categories as required.

5. Enter the Trade Category Name (Local Language).

Checklist

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Attachments

Configuration Data Templateconfiguration-data-template-trade-master-2-.xlsx - 17KB

Sample Data Templatesample-configuration-data-template-trade-master-filled-2-.xlsx - 19KB

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Setup

The above build has to be deployed to perform the migration. The batch persister config has to be added in config Repo. After adding the file in the repo, update the persister path in environment yml file. Make sure the persister.bulk.enabled is set to true. Once done restart the persister pod.

To start the migration call the following API with tenantId as param it will migrate data belonging to that tenantId. The API does not have role action mapping and should be used by port forwarding rainmaker-pgr pod.

curl --location --request POST 'http://localhost:8083/rainmaker-pgr/v2/_migrate?tenantIds=pb.jalandhar' \
--header 'Content-Type: application/json' \
--data-raw '{
     "RequestInfo": {
        "apiId": "Rainmaker",
        "action": "",
        "did": 1,
        "key": "",
        "msgId": "20170310130900|en_IN",
        "requesterId": "",
        "ts": 1513579888683,
        "ver": ".01",
        "authToken": "6fc5bb66-f3f1-49fa-b750-34f7b33d80d4",
        "userInfo": {
        "id": 23287,
        "uuid": "4632c941-cb1e-4b83-b2d4-200022c1a137",
        "userName": "PalashS",
        "name": "Palash S",
        "mobileNumber": "9949032246",
        "emailId": null,
        "locale": null,
        "type": "EMPLOYEE",
        "roles": [
            {
                "name": "PGR Last Mile Employee",
                "code": "PGR_LME",
                "tenantId": "pb.amritsar"
            },
            {
                "name": "Employee",
                "code": "EMPLOYEE",
                "tenantId": "pb"
            },
            {
                "name": "Employee",
                "code": "EMPLOYEE",
                "tenantId": "pb.amritsar"
            }
        ],
        "active": true,
        "tenantId": "pb.amritsar"
    }
    }
}'

WSD

Validation Queries

select  distinct(action),count(*) from eg_pgr_action group by  action
select st.state,count(*) from eg_wf_processinstance_v2 pi INNER JOIN eg_wf_state_v2 st ON st.uuid = pi.status  where businessService ='PGR' group by st.state

select tenantId,count(*) from eg_pgr_service group by tenantId;
select tenantId,count(*) from eg_pgr_service_v2 group by tenantId;

select servicecode,count(*) from eg_pgr_service group by servicecode;
select servicecode,count(*) from eg_pgr_service_v2 group by servicecode;

select active,count(*) from eg_pgr_service group by active;
select active,count(*) from eg_pgr_service_v2 group by active;

select count(*) from eg_pgr_address
select count(*) from eg_pgr_address_v2

-- Assignee count match
select count(*) from eg_pgr_action where assignee is not null;
select count(*) from eg_wf_assignee_v2;

select count(*)  from eg_pgr_action  where media NOT in ('[]','null')
select count(*) from eg_wf_document_v2 where processinstanceid IN (select id from eg_wf_processinstance_v2 where businessService ='PGR')

*(Last query related to document might need little modification as values in NOT IN clause can be more than the 2 specified)

Prod Data Insights

1. null value is stored in action for adding comments in the old system it’s mapped to COMMENT in new system.

2. The Locality attribute in new eg_pgr_address_v2 table does not allow NULL values whereas the locality attribute in the old eg_pgr_address in Punjab prod data has NULL values. Those values are filled in migration with dummy value NOT_AVAILABLE.

3. For 128 records accountId is NULL and so they won’t be associated with any citizen login.

4. For some records in the media column corrupt data is present. For example, in one case instead of fileStore uuid some normal text describing the complaint is present. While some other records have values like no. For data with such text having a length greater than 64 are set to null, else DB validations are violated.

5. In the old system-id is stored for referencing user data. In new systems we use uuid to refer user, therefore all id is mapped to respective uuid which are then migrated to the new system. If some user has uuid as NULL default value NOT_SPECIFIED will be used.

6. Some 1104 complaints has value in the column named feedback which seems to be from some set of predefined values like "Resolution Time", "Quality of work", ”others” etc. The new structure does not have any such column so we will be storing this in additionalDetails.

7. Address and landmark column in eg_pgr_service has values in some column they are also stored in additionalDetails.

8. Phone column contains phone numbers, we are not migrating that column as it has PII data and will be already present in user service as well.

9. If sla is not found in the old config (will only happen if some complaint category is removed from MDMS and complaints are present in the system of that category) default SLA value will be used.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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.

Data Table

The table above contains sample data.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.

3. Contact the person who shared this template with you to discuss and clear your doubts.

4. Enter the relevant structure types.

5. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

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 specifications. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

A separate entity-specific checklist is not needed for this entity data template.

Attachments

Configuration Data Templateconfiguration-data-template-structure-type_v1-1- (1).xlsx - 10KB

Sample Datasample-configuraion-data-structure-type-and-subtype-1-.xlsx - 9KB

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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 -

1. Fixed amount; or

2. Percentage: In case of percentage, it can be levied on either

   1. Entire bill amount; or

   2. Balance pending when partial payments have been made

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.

3. Please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Enter the applicable value for the Grace Period.

5. Enter the corresponding Penalty Flat Amount.

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

7. Enter the applicable percentage value for calculating the Penalty amount.

8. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

Separate Entity Specific Checklist is not required for this module data.

Attachments

Configuration Data Templateconfiguration-data-template-penalty-rates (1).xlsx - 10KB

Sample Datasample-configuration-data-penalty-rates (1).xlsx - 9KB

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Citizens represent individuals or communities who are the system end-users. The PGR module provides the citizens with the scope to file their complaints or grievances to initiate necessary action.

The Citizen role can -

• File complaints

• Track complaints

• Rate complaints

• Reopen complaints

File Complaints

The File Complaints option allows citizens to register their complaints.

To file complaints navigate to Complaints Home page. Click on the File Complaints tab on the screen. This will open the complaint form page. Select the relevant Complaint Type and the subtype from the drop-down list of options. Refer to the list of complaint types available in PGR.

Enter any additional information in the Complaint Additional Details field. Click on the map icon to pinpoint the Complaint Location. The City field will display the city specified in your profile by default. You can change the city if required. Choose the applicable Locality/Mohalla from the drop-down list. Enter the House No. and Street Name. Enter any Landmark to identify the exact location for the listed complaint.

Click on the camera icon to upload any photos for the complaint. Click on the Submit Complaint button once you have finished filling in all the details.

The system will display the Complaint Registered Successfully message along with the Complaint No. Click on the Continue button. Your complaint details are available on the dashboard.

The bell icon on the top right corner of the complaint tab will display any notifications received for the complaint. Click on the bell icon to view the complaint details.

My Complaints

My Complaints tab enables citizens to track the status of their complaints.

To view or track complaints click on My Complaints tab. The system will display all complaints filed by you or from your account and the corresponding status. Click on the Open button corresponding to any complaint to view the complaint details.

The complaint summary view contains the Complaint Details, Complaint Timeline, and Comments text box. The complaint timeline indicates the action taken on the complaint and the current or pending action status of the complaint.

Enter any additional information about the complaint in the Comments section.

Rate Complaints

The PGR module enables the citizens to give their feedback on resolved complaints.

To rate resolved complaints navigate to the Complaints menu option in the sidebar. Click on the My Complaints tab. Scroll down to the complaint you want to rate. You can rate only complaints marked as Closed. Scroll down to the Complaint Timeline section.

Click on the Rate button on the timeline.

Click on the number of stars on the screen to rate the work on the complaint on five. Click on the most appropriate feedback statement to rate the work. Add any additional information in the Comments section. Click on the Submit button.

The system displays an acknowledgement for your ratings. Click on the Go To Home button to navigate back to the home page.

Reopen Complaints

To reopen the complaint navigate to Complaints > My Complaints menu option in the sidebar. Click on the closed complaint that you want to reopen. Scroll down to the Complaint Timeline section. Click on the Re-Open button on the timeline.

Select the appropriate reason for reopening the complaint. Click on the camera icon to upload any photos related to the complaint. Enter any additional information in the Comments section. Click on the Continue button once done. The system displays an acknowledgement message stating the complaint is reopened. Click on the Go To Home button to navigate back to the home page.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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 -

1. Entire bill amount

2. Balance pending when partial payments have been made

Data Table

Data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.

3. Please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Enter the applicable Grace Period for calculating interest.

5. Select the relevant parameter for Interest-Based On to specify if the interest is applied to the bill amount or pending balance.

6. Enter the applicable percentage value for Interest Rate that will be used to calculate the interest amount.

7. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

Separate Entity Specific Checklist is not required for this module data.

Attachments

Configuration Data Templateconfiguration-data-template-interest-rate (1).xlsx - 10KB

Sample Datasample-configuration-data-interest-rate (1).xlsx - 9KB

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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 Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.

3. Contact the person who shared this template with you to discuss and clear your doubts.

4. Enter the relevant Water Source.

5. Enter the corresponding Water Sub Source. This will map the water sub source to the specified water source.

6. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

A separate Entity Specific Checklist is not required for this module data.

Attachments

Configuration Data Templateconfiguration-data-template-water-source-types.xlsx - 10KB

Sample Datasample-configuration-data-water-source-types.xlsx - 11KB

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

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 -

1. Entire bill amount

2. Balance pending when partial payments have been made

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.

3. Please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Enter the Grace Period.

5. Select the relevant Interest-based On parameter.

6. Enter the Interest Rate.

7. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

Separate Entity Specific Checklist is not required for this module data.

Attachments

Configuration Data Templateconfiguration-data-template-interest-rate.xlsx - 10KB

Sample Datasample-configuration-data-interest-rate.xlsx - 9KB

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

The PGR module is an application that allows citizens to lodge complaints and track them. Employees track and address the grievances registered in the system to ensure speedy resolution. The platform is available for use in both mediums as a web and mobile app.

Functional Scope

The list below summarizes the key features supported by the PGR module -

1. Registration, Login and Creation of User Profile

2. Lodging a Complaint

3. Assigning a Complaint

4. Resolving a Complaint

5. Manage Complaints

6. Track Complaints

7. Dashboards and Reports

8. General Features

Registration, Login & Creation of User Profile

Lodging Complaint

The Citizen or Citizen Service Representative (CSR) on behalf of citizens can lodge, civic works related complaints in the PGR system. Users can also upload associated or relevant pictures with the complaint. For identifying the location of the complaint, the user can provide city, mohalla, house no. and other details or even select the location using maps. After filing the complaint a complaint number is generated.

Assigning Complaint

The assigning officer has a dashboard with unassigned complaints. Any complaint can be selected to view details and expected closure timelines. The assigning officer can select and assign complaints to appropriate Employee from a department-wise list. A complaint can also be re-assigned if it is assigned incorrectly or for any other reason.

Resolving Complaint

The Employee can view the complaints assigned to him on the dashboard with functionality to mark them for closure. An employee can view details and closure timelines of the complaints from a list. After resolving the complaint the Employee can upload pictures as evidence and also enter comments. With the help of the Share feature, complaints details can be shared via Whatsapp, SMS, email etc to contractors. If the citizen finds the resolution to be unsatisfactory, the complaint can be reopened. Citizens can also provide feedback and rate the resolution.

Managing Complaint

The employee has access to the dashboard of open complaints from which he can select a complaint to view details and closure timelines. An employee can also request to reassign the complaint by selecting a reason from the list. In that case, the request goes to assigning officer and the complaint can be reassigned to a different Employee. The system has different interfaces for Assigning officer, Employee and CSR. The assigning officer can view tabs that contain unassigned and assigned complaints which are received from the citizens. The assigning officer can also view open/ closed complaints and access PGR reports for all grievances. Employee’s interface contains open and closed complaints which are assigned to him. CSR can view/ search the list of all the complaints filed on citizen’s behalf. The system has the provision to search, sort and refresh the list of grievances.

Tracking Complaint

Dashboards & Reports

PGR Reports provide an operational bird’s eye view of the PGR system in the city. It enables city managers - commissioners, department heads, administrators at various levels to keep a track of the volume of complaints being received and the performance of the ULB and its employees in addressing them. Reports can be filtered based on date and also can be downloaded in pdf and xls formats.

General Features

All content on this page by is licensed under a .

Introduction

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 that are closely associated with ULB’s functions classified into different buckets, that different sections of ULB deal with are known as grievance types.

Data Table

The data given in the table is sample data.

Procedure

Data Definition

Step to fill data

1. Download the data template attached to this page.

2. Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.

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

4. Identify all different types of grievances on the basis of ULB’s functions.

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

6. Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

To see a common checklist refer to the page consisting of all the activities which are to be followed to ensure completeness and quality of data.

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Attachments

All content on this page by is licensed under a .

Introduction

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

Data Table

Given below is the sample data table from the template in which the data has to be collected:

Procedure

Data Definition

Steps to fill Data

1. Download the data template attached to this page.

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

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Firstly Identify all the categories of the owners present in the state.

5. After which identify the codes of all the categories, if not present then form an abbreviated version of the code.

6. Start filling the template with the codes in the second column, its English name in 3rd and Local Language name in 4th.

7. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

Not Applicable

Attachments

All content on this page by is licensed under a .

Introduction

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.

Data Table

The data provided in the above table is sample.

Procedure

Steps to fill data

1. Download the data template attached to this page.

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

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Identify the “Property Types” that exists at a ULB/ State level.

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

6. Add the “Property Type Code” respectively against the identified Property Type(s).

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate checklist applicable to this entity.

Attachments

All content on this page by is licensed under a .

Introduction

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.

Data Table

The data described in the above table is sample.

Procedure

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to 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.

4. Identify all the property sub types applicable and fill into the given template.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate checklist is applicable to this entity.

Attachments

All content on this page by is licensed under a .

Introduction

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

Data Table

Procedure

Data Definition

Steps to fill Data

1. Download the data template attached to this page.

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

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Get the rebate rate and the amount involved with it.

5. Get the year and the end date for the rebate period.

6. Start filling the template from the right which is the rebate percentage and end it with the rebate end date.

7. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

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.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

Not Applicable.

Attachments

All content on this page by is licensed under a .

Introduction

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 its usage. Ideally, property usage is categorized as residential, non-residential or a mix of both.

Data Table

The data described in the above table is sample.

Procedure

Data Definition

Steps to Fill Data