Loading...
Loading...
Loading...
Loading...
Learn more about PT workflows and its configuration
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...
Online automated management of property tax revenues and collections
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.
Manage property database
Provides support for property registration, transfer, bifurcations, amalgamation
GIS embedded and integrated with eGov financials municipal accounting system
Various payment options available to citizens to make payments from their convenient places
Auto-generated defaulters’ list and real time online tracking
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.
PT Service Configuration
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
Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on PT module deployment.
#147/J, 1st floor, 10th Cross, 12th Main, 3rd Block, Koramangala, Bangalore 560034
+91 80 4125 5708
contact@digit.org
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.
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
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.
1
Make sure that each and every point in this reference list has been taken care of
Not Applicable
Configuration Data Templateconfigurable-data-template-mutation-fee_v1.xlsx - 10KB
Functional overview for stakeholders
The Property Tax System(PT) provides a digital interface to make property assessments, pay property tax, generate payment receipts and monitor tax collection. It can be used by the citizens, Urban Local Body (ULB) counter and field employees and ULB Administrators to accomplish their specific tasks. It is available as a mobile and web-based application.
The PT product features can be broadly classified as the following modules:
Registration, Login and Creation of User Profile
Filling an Assessment for a Property
Searching for a Property
Modifications to a Property
Generate Demand Notice
Payments collection and Receipts
Dashboards and Reports
General Features
OTP Based Login for Citizen via Web/Mobile App
OTP Based Login for Employee via Web/Mobile App
Provision for language selection during first time registration for both Employee and citizens
Provision of creating a personalized Profile for Citizens and employees on Web App
Login Credentials for the various hierarchy of employees
Role-based access for performing different actions relating to property tax modules
With this feature, a citizen and employee can perform a self-assessment of a new property for a financial year. This feature helps in registering the property in the system. The details of the property can be entered online and can be assessed for the calculation of the taxes.
The PT Product is designed in a user friendly manner and reduces chances of error. System calculates the tax automatically and creates the demand. If a user wants to reassess his property due to any reason (for eg, incorrect data, change in property etc), it can be done by editing details of the last assessment.
An employee can edit the details of the last assessment, on behalf of the citizen-based on the owner’s input. Citizen can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.
Citizen/CSC can Assess New Property (By Different Financial Years).
Citizen/CSC can Capture Address, Assessment Info, Owner Info.for all types of properties like residential houses, flats and commercial buildings.
o Sample Details captured:
Door Number,
Mutation number,
Number of floors,
Area covered,
Owner and co-owner,
Mailing & permanent address,
Built year
Individual room measurements
The system computes the property taxes automatically as per process and rules of the state.
The system has a facility to make entry in system by inspector after site visit and assessment of the same by the superintendent.
The system supports dynamic calculation for late fees, interest, rebates, etc. as on the day of demand generation.
The system fetches the data of previous year property data while e-filing for current year so that all the dues are calculated.
The system assigns a unique property ID based on the process defined in the ULBs.
Citizen/CSC : View/Print Summary of Filled Form
Assessment Form
Assessment Form is also sent by email to citizen
Upload Documents
Ownership/Title related
ID Proof
Any other statutory documents
Citizen or Employee can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.
Citizen/CSC can search for Property by
Mobile No,
City,
Property Tax Unique ID
Citizen/ CSC can view Incomplete Assessments
Citizen/CSC can reassess Searched Property
View Property details and pending dues
The PT system provides the ability to capture mutation and transfer of ownership. It reduces interfaces between the user and the State and thus promote greater transparency. It also helps in reducing the time taken for mutation after registration. The system provides the ability for alteration of assessment after verification and inspection. Any structural changes like addition/extension/reduction of existing built up area or construction type OR utility changes like usage or occupancy have an impact on the increase/decrease in property tax demand. These changes can be handled by the ‘Additional/Alteration of Assessment’ feature.
The System provides the ability for bifurcation/ amalgamation of property. The property bifurcation/ amalgamation undergoes an approval process. The parent property needs to be modified accordingly, which can be done in the system.
Mutation of property and change of ownership details
Capture Extension/ Addition and Alteration and reassessment based on changed property details
Bifurcation of property
Amalgamation of property
System has the capability to automatically generate demand notice for a financial year based on set triggers like time-based roll over on completion of a financial year. The system notifies the citizens about the demand through SMS/Email. The generated Bills can also be grouped and printed for physical distribution by the ULB employees. The system provides the capability to Employees to merge and download bills based on given parameters to plan their distribution drives.
Generate Demand Notice based on periodic basis
Group Demand Notices
Print Demand Notices
Cancel Demand Notices
Send notifications to citizens on demand generation- SMS, Whatsapp, Email, Physical bil
The citizen/ employee can view payment status of previous assessments from Assessment History section. Payment for any assessment with full or partially paid amount can be completed. Receipts for assessment can be downloaded in Assessment history section after searching for the property details.
Payment of Property Tax -Online, Cheque, Cash, DD, during assessment
Partial Payment of Property Tax -Online, Cheque, Cash, DD, during assessment
The system allows a citizen to pay for anyone's property without changing the demand
The system can also be integrated with PoS machines to enable doorstep collection of property tax and issual of receipt
PT reports provides facility to access receipt register, cancelled receipt register, account receipt register, ULB wise PT collection report, DCB Register. All reports can be downloaded in PDF/XLS format.State level administrator can monitor property tax collections, assessments and other information at a state level through dashboards.
State Dashboard : View Reports for Total Collections, Properties Assessed, ULBs on Prod, Usage Type, Payment Distribution
State Dashboard : PT Collection Timeline (Monthly,Weekly)
State Dashboard : ULB Wise (Collection, Assessments)
Cancelled Receipt Register Report
PT Collection Report (ULB/Date Wise)
Notifications - The system has the capability to send notifications to citizens. These notifications can be sent for various steps like - assessment completion, payment reminder, payment confirmation. These notifications can be sent in the language chosen by the ULB through all channels - SMS, Whatsapp, Email.
Legacy Data Migration - The system has the capability to migrate Demand and Collection. In most states, the preliminary step would be to migrate Legacy data of existing properties/connections along with the Demand and Collection details. This would ensure that subsequent demand generation happens through the system.
Configurable Masters - The system provides the following masters that can be configured as per the State’s
Requirements -
Charges & Calculation : Calculation Engine, Rebate, Penalty,
Rate Master
State Masters : Property Ontology, Documents List, Employee Data Mapping, Boundary Data Mapping
System specification in compliance with the Ease of Doing Business (EODB) BRAP 2019
7
Land administration and Transfer of Land and Property
3
Digitize land transaction deeds of last 10 years at all sub-registrar offices and make the same available on an online system to check for ownership details and history. The metadata should be searchable for each record and a soft copy of the registered deed should be available. The searchable metadata available should be:
i. Name of buyer
ii. Name of seller
iii. Survey no.
iv. Registration number
v. Registration date
The feature of ‘Property Registry’ in the product will enable this recommendation
8
Land administration and Transfer of Land and Property
3
Digitize and publish the updated Record of Rights (ROR) at all Revenue department offices online in public domain for all areas of the State/UT. The searchable metadata available should be:
i. Name of buyer
ii. Name of seller
iii. Date of mutation
iv. Survey no.
The Property tax system enables this capability
9
Land administration and Transfer of Land and Property
2
Digitize and publish data of Property Tax payment dues online in public domain for all the Urban Local Bodies (ULBs) in the State/UT. The searchable metadata available should be:
i. Name of the Property Tax payer
ii. Property Tax dues
iii. Survey no. of land / Unique Identification no. of property
This feature is enabled by the citizens itself
10
Land administration and Transfer of Land and Property
2
Digitize cadastral maps of all rural areas in the State/UT and make them available in public domain
This can be enabled and worked on by the state team
11
Land administration and Transfer of Land and Property
5
Integrate the below-mentioned records on one website:
i. Data of land transaction deeds for last 10 years at all sub-registrar offices (Name of buyer, Name of seller, Registration number, Registration date, Survey no.),
ii. Updated Record of Rights at all Revenue department offices (Date of mutation), and
iii. Data of Property Tax payment dues at all urban areas of the State/UT (Name of the Property Tax payer, Property Tax dues)
iv. Revenue Court case data (Court case number, Name of parties involved, Date of filing of court case, Status of case [Ongoing/Resolved])
v. Civil Court case data (Court case number, Name of parties involved, Date of filing of court case, Status of case [Ongoing/Resolved])
The website should be publicly accessible. It will help in establishing property ownership and identify tax encumbrances. The integration should be done for all areas of the State/UT.
The integration with external portals and systems of other departments can be enabled by state teams who can enhance the offered product to cater to this recommendation
12
Land administration and Transfer of Land and Property
2
Implement an online application system having the following features
i. Mandatory Online application submission including submission of draft deed and other documents
ii. Provision of online payment of Stamp duty and Registration fee
iii. Auto generation of appointment date and time on making the payment of Stamp duty and Registration fee
The system will provide these capabilities which can be customised as per the state specific rules and regulations
13
Land administration and Transfer of Land and Property
1
Provide model deed templates for sale, gift, lease, mortgage and rent in downloadable and editable format along with instructions to use them
This provision is made available through the ULB portal to make these features accessible to the citizens
14
Land administration and Transfer of Land and Property
2
Integrate the mutation process with the registration process and mandate initiation of mutation process (Revenue department and/ or ULB) as soon as the deed is registered. Ensure that:
i. Information to mutation authority to be automatically shared on completion of transaction (registration). This should be considered as initiation of mutation process.
ii. No separate application from transferee to be required.
iii. SMS/email should be sent to transferee/ transferor to inform about the initiation of mutation
The integration with external portals and systems of other departments can be enabled by state teams who can enhance the offered product to cater to this recommendation
List of Features- Property Tax
Registration, Login, Creation of User Profile
Provision for Language Selection during first time registration via Mobile/ Web App.
OTP Based Login for Citizen/ Employee via Mobile/ Web App
Login Credentials for various hierarchy of employees.
Provision of Personalized Profile for Citizen/ Employee on Web App
Filing an assessment for a property
Citizen/CSC : Assess New Property (By Different Financial Years).
Citizen/CSC : Capture Address, Assessment Info, Owner Info.
Citizen/CSC : View/Print Summary of Filled Form
Searching for a property
Citizen/CSC : Search Property (By Mobile No,City, Property Tax Unique ID, Existing ID).
Citizen/CSC : View the Searched Property
Citizen : View My Properties
Citizen : View Incomplete Assessments
Citizen/CSC : Edit the Searched Property
Citizen/CSC : Reassess Searched Property
Generate demand notice
Generate Demand Notice based on periodic basis
Group/ Print/ Cancel Demand Notices
Send notifications to citizens on demand generation- SMS, Whatsapp, Email, Physical bill
Modifications to a property
Mutation of property and change of ownership details
Capture Extension/ Addition and Alteration and reassessment based on changed property details
Bifurcation/ Amalgamation of property
Payment collection and receipts
Payment of TAX (Online,Cheque,Cash,DD) : During Assessment
Payment of TAX (Online,Cheque,Cash,DD) : Partial Payment
Citizen/CSC : Download Receipts for payments
Dashboards and reports
State Dashboard : View Reports for Total Collections, Properties Assessed, ULBs on Prod, Usage Type, Payment Distribution
State Dashboard : PT Collection Timeline (Monthly,Weekly)
State Dashboard : ULB Wise (Collection, Assessments)
Cancelled Receipt Register Report
PT Collection Report (ULB/Date Wise)
General features
Notification
Legacy data migration
System assigns a unique property ID based on the Process defined in the ULBs.
System has the facility to classify the property based on its type.
System allows changing the type of property.
Configuration masters
Configurable Rate Master (ULB Specific) : Fire Cess/ Building Height
Charges & Calculation : Calculation Engine, Rebate, Penalty
State Masters : Property Ontology, Documents List, Employee Data Mapping, Boundary Data Mapping
This page provides configuration details for PT master data templates
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
Download the brochure to view product features, capabilities, scope and application details
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.
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
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.
All content on this page by is licensed under a .
The computerized and automatic Property Tax system offered by eGov, facilitates citizens who seek to pay their Property Tax within any Urban Local Body with a transparent, speedy, hassle-free and user-friendly procedure. Property Tax (PT) is one of the components of a smart city that has the capability of providing the highest revenue of a state. Keeping in mind the benefits associated with the product offered, the proposed system is about to be implemented in 500+ ULBs across the country in 15 states. (For details on product features refer to Section-2)
For the offered product, the implementation process can be divided into seven major distinctive stages. Each stage has a predefined entry and exit criteria, roles & responsibilities to assure objective monitoring and decision making for the overall success of the engagement. The whole implementation lifecycle is typical of 38-42 weeks for the State, keeping in mind the entry, and exit criteria defined at the beginning and end of each stage are met on time recommended.
Stage Zero-program setup and onboarding is a pre-requisite for the initiative to kick-off and requires setup of the governance model, implementation Team and decision regarding other significant elements of the initiative like funding and procurement process. Stage One requires scoping of the initiative and decisions on the priorities for implementation by the State Implementation Team. In stage two, the State Team will work upon identifying and finding solutions to the significant gaps in the product offered with respect to the need of the State. Configuration and customization of the product offered is the primary objective of stage four. This involves working on various aspects of State-specific needs and incorporating them into the product offered. In stage five, post doing UAT and including all the necessary feedback on the product, the roll-out of the product is done at the State level (Go Live) from a couple of ULBs to pan State coverage in batches. Finally, in stage 6 sustenance and ongoing improvements are worked upon while the product is already functioning in the State. (For details on implementation plan refer to Section-3)
Implementation of Property Tax (PT) requires meticulous planning and close coordination between various stakeholders at the center and State level. The success of the initiative is dependent upon many factors like strong Program governance, availability of the trained resource, financial planning, targeted Implementation Team onboarding, focus on last-mile capacity building and ensuring necessary support to Urban center. Achievement of all these factors will provide the most effective and efficient roll-out and adoption of the Property Tax System in the State.
The Property Tax System(PT) provides a digital interface to make property assessments, pay property tax, generate payment receipts and monitor tax collection. It can be used by the citizens, Urban Local Body (ULB) counter and field employees, and ULB Administrators to accomplish their specific tasks. It is available as a mobile and web-based application. The PT product features can be broadly classified as the following modules:
Registration, Login and Creation of User Profile
Filling an Assessment for a Property
Searching for a Property
Modifications to a Property
Generate Demand Notice
Payments collection and Receipts
Dashboards and Reports
General Features
This module provides enables the following capabilities
OTP Based Login for Citizen via Web/Mobile App
OTP Based Login for Employee via Web/Mobile App
Provision for language selection during first time registration for both Employee and citizens
Provision of creating a personalized Profile for Citizens and employees on Web App
Login Credentials for various hierarchy of employees
Role based access for performing different actions relating to property tax modules
With this feature, a citizen and employee can perform self assessment of a new property for a financial year. This feature helps in registering the property in the system. The details of the property can be entered online and can be assessed for calculation of the taxes. The PT Product is designed in a user friendly manner and reduces chances of error. System calculates the tax automatically and creates the demand. If a user wants to reassess his property due to any reason (for eg, incorrect data, change in property etc), it can be done by editing details of last assessment. Employee can edit the details of the last assessment, on behalf of the citizen based on owner’s input. Citizen can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.
This module provides enables the following capabilities:
Citizen/CSC can Assess New Property (By Different Financial Years).
Citizen/CSC can Capture Address, Assessment Info, Owner Info.for all types of properties like residential houses, flats and commercial buildings.
Sample Details captured:
Door Number,
Mutation number,
Number of floors,
Area covered,
Owner and co-owner,
Mailing & permanent address,
Built year
Individual room measurements
The system computes the property taxes automatically as per process and rules of the state.
The system has a facility to make entry in system by inspector after site visit and assessment of the same by the superintendent.
The system supports dynamic calculation for late fees, interest, rebates, etc. as on the day of demand generation.
The system fetches the data of previous year property data while e-filing for current year so that all the dues are calculated.
The system assigns a unique property ID based on the process defined in the ULBs.
Citizen/CSC : View/Print Summary of Filled Form
Assessment Form
Assessment Form is also sent by email to citizen
Upload Documents
Ownership/Title related
ID Proof
Any other statutory documents
Citizen or Employee can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.
This module provides the following capabilities:
Citizen/CSC can search for Property by
Mobile No,
City,
Property Tax Unique ID
Citizen/ CSC can view Incomplete Assessments
Citizen/CSC can reassess Searched Property
View Property details and pending dues
The PT system provides the ability to capture mutation and transfer of ownership. It reduces interfaces between the user and the State and thus promote greater transparency. It also helps in reducing the time taken for mutation after registration. The system provides the ability for alteration of assessment after verification and inspection. Any structural changes like addition/extension/reduction of existing built up area or construction type OR utility changes like usage or occupancy have an impact on the increase/decrease in property tax demand. These changes can be handled by the ‘Additional/Alteration of Assessment’ feature. The System provides the ability for bifurcation/ amalgamation of property. The property bifurcation/ amalgamation undergoes an approval process. The parent property needs to be modified accordingly, which can be done in the system.
This module provides the following capabilities:
Mutation of property and change of ownership details
Capture Extension/ Addition and Alteration and reassessment based on changed property details
Bifurcation of property
Amalgamation of property
System has the capability to automatically generate demand notice for a financial year based on set triggers like time-based roll over on completion of a financial year. The system notifies the citizens about the demand through SMS/Email. The generated Bills can also be grouped and printed for physical distribution by the ULB employees. The system provides the capability to Employees to merge and download bills based on given parameters to plan their distribution drives.
This module provides the following capabilities:
Generate Demand Notice based on periodic basis
Group Demand Notices
Print Demand Notices
Cancel Demand Notices
Send notifications to citizens on demand generation- SMS, Whatsapp, Email, Physical bill
The citizen/ employee can view payment status of previous assessments from Assessment History section. Payment for any assessment with full or partially paid amount can be completed. Receipts for assessment can be downloaded in Assessment history section after searching for the property details.
This module provides the following capabilities:
Payment of Property Tax -Online, Cheque, Cash, DD, during assessment
Partial Payment of Property Tax -Online, Cheque, Cash, DD, during assessment
The system allows a citizen to pay for anyone's property without changing the demand
The system can also be integrated with PoS machines to enable doorstep collection of property tax and issue of receipt.
PT reports provides facility to access receipt register, cancelled receipt register, account receipt register, ULB wise PT collection report, DCB Register. All reports can be downloaded in PDF/XLS format. State level administrator can monitor property tax collections, assessments and other information at a state level through dashboards.
This module provides the following capabilities:
State Dashboard : View Reports for Total Collections, Properties Assessed, ULBs on Prod, Usage Type, Payment Distribution
State Dashboard : PT Collection Timeline (Monthly,Weekly)
State Dashboard : ULB Wise (Collection, Assessments)
Cancelled Receipt Register Report
PT Collection Report (ULB/Date Wise)
The system has the capability to send notifications to citizens. These notifications can be sent for various steps like - assessment completion, payment reminder, payment confirmation. These notifications can be sent in the language chosen by the ULB through all channels - SMS, Whatsapp, Email.
The system has the capability to migrate Demand and Collection. In most states, the preliminary step would be to migrate Legacy data of existing properties/connections along with the Demand and Collection details. This would ensure that subsequent demand generation happens through the system.
The system provides the following masters that can be configured as per the State’s requirements:
Charges & Calculation : Calculation Engine, Rebate, Penalty,
Rate Master
State Masters : Property Ontology, Documents List, Employee Data Mapping, Boundary Data Mapping
This section provides an overview of the methodology for State-wide implementation of PT. The Implementation of PT is distributed across seven distinct stages. Each stage has a predefined entry & exit criteria and roles & responsibilities. This is to ensure objective monitoring and decision making for the overall success of the program. Details of each stage are defined in this section.
Note: This document is specific for States that have more than 30 ULBs
PT implementation program is expected to be completed approximately between 38- 42 weeks depending on the variety in Processes, Integration and the Disparate legacy data systems involved. This is done with the resource deployment by the State and System Integrator (SI) Team. However, it is critical that activities and exit criteria set for each stage are achieved to adhere to this timeline.
This is a set of initial critical activities undertaken on receiving a letter of Enrollment or MOU from the State. Successful completion of these activities assures that the program is started with crucial personnel, System Integrator(SI) Teams, and funds.
*Details of PT cell is mentioned in section 4 of the handbook
System Integrator and state will agree on program scope, program timelines, and budgeting & resourcing.
This stage envisages in-person interaction of crucial State officials and implementation System Integrator(SI) Teams to kick-start the program. This stage may require multiple interactions/meetings with different interest groups. The principal objective of these interactions is to identify and agree on the scope and exclusions of Pilot ULBs, create an active collaboration & Governance approach and agree on a high-level timeline for the engagement.
*Details of PT cell is mentioned in section 4 of the handbook
During the Solution design stage, key State officials and members, who are subject matter experts, are expected to share their inputs, discuss the process and help understand how to bring in compliance around the system design for the System Integrator(SI) Team. This stage baselines the State-specific product features in the Product Configuration report.
This stage consists of a series of developments in accordance with the detailed project plan to ensure smooth functioning of the customised product. Master Data Collection & Environment Setup will be achieved in this phase. Further monitoring and maintenance strategies are put in place.
During this stage, demonstration of the product followed by a hands on session is conducted for the ULB officials. Necessary training of ULB officials and resources required for UAT is conducted and identified respectively. The establishment of the State support Team and required processes are initiated in this stage.
On successful Go-Live in the Pilot ULBs, and further fine tuning to stabilize the product, the solution will be rolled out to the rest of the ULBs in phases. Guidance and support from the State Team will be required to create the rollout plans and assure the necessary infrastructure for training and deployment is available at each ULB.
Note: The rollout phase needs to be detailed out for iterative activities of onboarding ULBs in batches.
Note: Only once all the stages are complete in one batch of rollout of around 30 ULBs, the next batch begins. There are multiple phases of rollout. The second batch begins after the first batch has successfully fulfilled all the criteria of the Rollout Phase. Typical timeline for closure of rollout in each batch is 5-6 weeks (in a batch of 30 ULBs)
The final stage consists of strategies to ensure the sustenance of the program in the State. Systems are put in place to ensure the continuous tracking of data and provisions are made to improve the product if new data suggests.
This section outlines the activities involved in each stage of the implementation along with responsibility and accountability of critical stakeholders - State, eGov Team and System Integrator Team onboard.
PT Cell: PT Cell is the government-appointed body chaired by the Principal Secretary/Secretary, Urban Development Department with members from Urban Development Department etc.
Resource requirements for the PT cell required to be formed by the State
Note:
Designations mentioned above are in accordance with those already driving PT implementation at the State level.
The description of each designation is explained below.
Project Head: Is the Head of the PT Cell who will drive the project from the State’s Side
Domain Expert: Person who is well aware of the on ground scenario, well versed with the act, GOs passed, Prevalent Business processes, Deviations from the acts, PT Rates/ slabs applicable. In addition, provisions may be made to include External Domain Consultants/Advisors.
Nodal officer (EO/Commissioner/ Senior Official): the product coordinator to drive the project centrally. Monitor usage post Go Live- point of escalation for Implementation Team, Seasoned and worked in Multiple ULBs on various modules and has a good understanding of PT, Facilitate and Track data collection Post Go Live, Monitors and facilitates adoption of application. Point of contact for Management team, SI and at the HQ level.
MIS Expert: Data Preparation for ULBs,Day to day tracking of the data specific to ULBs, data collection/validation for correctness and comprehesiness, reporting and review to senior officials
eGOv Team: eGov Team is the technical partner of the project which will provide all necessary support to the State/UT concerning the implementation, Program Designing etc.
System Integrator (SI)Team: SI Team will be responsible for consulting, program management and the implementation of the state specific customized and configured products in the ULBs in close collaboration with the PT cell, technical partner (eGov) and various other stakeholders.
Execute - One who owns the accountability to complete the activity
Consult - One who may initiate, guide and in the process, handhold the execution of the activity
Note: Stage 0 is where the PT cell and SI team is formed, hence there are only two entities playing a role which is that of eGov and the state leadership. Once the PT cell and SI team is finalised, their role begins in the following stages.
Vision:
Defining the time frame to go live, the time frame to scale it pan state, the value proposition of the programme for the state and year-on-year financial targets and adoption targets
Project Plan:
A detailed plan of Program schedule/timelines, implementation phases, team structure and ongoing support and maintenance required.
System Integrator:
The Entity/Company which collates all the subsystem required for the project and integrates them to achieve the program objective
Program Charter:
Outline of implementation plan agreement with priority applications and broad timelines, program governance model, program success metrics and capacity building.
Acceptance Letter/MOU:
Formal Acceptance/Sign Off of the Client State with a clear mandate of the Program
Program Success Metrics:
Defining the parameters (which are measurable) prior to the program, on which the success of the program is to be measured on the completion of the program
Project steering committee:
The key body within the governance structure which is responsible for the business issues associated with the project that are essential in ensuring the delivery of the project outputs and the attainment of project outcomes.
Project governance:
Set of policies, regulations, functions, processes, procedures and responsibilities that define the establishment, management and control of projects, programmes and portfolios.
Scoping:
List of activities measured against time taken to complete them in accordance with the project goals
Baseline data:
Set of information that serves as a foundation to compare other data acquired afterwards
Project Kick off meeting:
Meeting with the project team and the client of the project. This meeting would follow definition of the base elements for the project and other project planning activities
Fitment Study:
GAP Study of the Existing/Required Field Process Vs Product
Data migration:
Existing Records of the functional activities need to be moved into the Database of the newly released Application
Data collection:
Required data for the roll-out of the applications, which needs to be collected from the existing functional process
Data validation approach:
This approach enables the sanctity of the Data with built-in validation by Design
Data synchronization:
The process of establishing consistency among data from a source to a target data storage and vice versa and the continuous harmonization of the data over time.
Pilot Implementation:
Any new process is tested out as pilot in one or two instances before pan implementation
Pilot ULB:
The ULB's Selected for the pilot implementation are called pilot ULB’s.
Roll out:
On successful clearance of the Pilot, the Process/Application/Services are implemented across all Offices/ULB's
Deployment:
Deployment defines the complete package of Software components set up in a particular environment
Customisation:
Details of changes to be made in the Product to comply with the needed field process
Configuration:
Defining existing content such as Options and Variables based on the requirements on the ground
Product walkthrough:
Explaining the users step-by-step through a set of actions that they need to take to achieve a specific outcome
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.
The data given in the table is 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 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.
Not Applicable
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by is licensed under a .
All content on this page by is licensed under a .
All content on this page by is licensed under a .
All content on this page by is licensed under a .
All content on this page by is licensed under a .
1
Late assessment
12.5
1000
500
2019-20
01-04-2019
2
Unauthorized Construction
100
5000
5000
2019-20
01-04-2019
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
1
Make sure that each and every point in this reference list has been taken care of
-10%
300
200
2018-19
01/10
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
1
Make sure that each and every point in this reference list has been taken care of
7
Land administration and Transfer of Land and Property
3
Digitize land transaction deeds of last 10 years at all sub-registrar offices and make the same available on an online system to check for ownership details and history. The metadata should be searchable for each record and a soft copy of the registered deed should be available. The searchable metadata available should be:
i. Name of buyer
ii. Name of seller
iii. Survey no.
iv. Registration number
v. Registration date
The feature of ‘Property Registry’ in the product will enable this recommendation
8
Land administration and Transfer of Land and Property
3
Digitize and publish the updated Record of Rights (ROR) at all Revenue department offices online in public domain for all areas of the State/UT. The searchable metadata available should be:
i. Name of buyer
ii. Name of seller
iii. Date of mutation
iv. Survey no.
The Property tax system enables this capability
9
Land administration and Transfer of Land and Property
2
Digitize and publish data of Property Tax payment dues online in public domain for all the Urban Local Bodies (ULBs) in the State/UT. The searchable metadata available should be:
i. Name of the Property Tax payer
ii. Property Tax dues
iii. Survey no. of land / Unique Identification no. of property
This feature is enabled by the citizens itself
10
Land administration and Transfer of Land and Property
2
Digitize cadastral maps of all rural areas in the State/UT and make them available in public domain
This can be enabled and worked on by the state team
11
Land administration and Transfer of Land and Property
5
Integrate the below-mentioned records on one website:
i. Data of land transaction deeds for last 10 years at all sub-registrar offices (Name of buyer, Name of seller, Registration number, Registration date, Survey no.),
ii. Updated Record of Rights at all Revenue department offices (Date of mutation), and
iii. Data of Property Tax payment dues at all urban areas of the State/UT (Name of the Property Tax payer, Property Tax dues)
iv. Revenue Court case data (Court case number, Name of parties involved, Date of filing of court case, Status of case [Ongoing/Resolved])
v. Civil Court case data (Court case number, Name of parties involved, Date of filing of court case, Status of case [Ongoing/Resolved])
The website should be publicly accessible. It will help in establishing property ownership and identify tax encumbrances. The integration should be done for all areas of the State/UT.
The integration with external portals and systems of other departments can be enabled by state teams who can enhance the offered product to cater to this recommendation
12
Land administration and Transfer of Land and Property
2
Implement an online application system having the following features
i. Mandatory Online application submission including submission of draft deed and other documents
ii. Provision of online payment of Stamp duty and Registration fee
iii. Auto generation of appointment date and time on making the payment of Stamp duty and Registration fee
The system will provide these capabilities which can be customized as per the state specific rules and regulations
13
Land administration and Transfer of Land and Property
1
Provide model deed templates for sale, gift, lease, mortgage and rent in downloadable and editable format along with instructions to use them
This provision is made available through the ULB portal to make these features accessible to the citizens
14
Land administration and Transfer of Land and Property
2
Integrate the mutation process with the registration process and mandate initiation of mutation process (Revenue department and/ or ULB) as soon as the deed is registered. Ensure that:
i. Information to mutation authority to be automatically shared on completion of transaction (registration). This should be considered as initiation of mutation process.
ii. No separate application from transferee to be required.
iii. SMS/email should be sent to transferee/ transferor to inform about the initiation of mutation
The integration with external portals and systems of other departments can be enabled by state teams who can enhance the offered product to cater to this recommendation
Stage 0 - Program Setup/ On-Boarding
Duration
4-6 weeks
Entry Criteria
Acceptance Letter/MoU by State
Exit Criteria
Finalize Property Tax Program Vision
Finalize funding for the program
Define State- specific procurement process
Property Tax Cell appointment (*). Consisting of :
Domain expert
Nodal officer (EO/ Commissioner/ Senior Official)
Program Head
System Integrator(SI) Team sign-up/onboarding
Duration
4-6 weeks
Entry Criteria
Program setup (Stage 0) is complete
SI Team onboarded
Key Activities
Identify & agree on scope and exclusions
Identify pilot ULBs
Project Kickoff - Implementation Methodology Presentation
Product Walkthroughs
Define Project Steering Committee Structure and Project Governance process
Define phases of rollout/ deployment
Agreement on Deployment Priorities and high-level delivery timelines
Assessment of all current PT processes along
(1) Citizen services/channels around it
(2) Integration with other Department process
Finalise Program Success Metrics for Rollout, Adoption and Governance, adhering to the vision of the program
Internal Capacity Building, program logistics at State and ULBs, as per the current scenario
Collection of baseline data to measure endline target for the product (Revenue generated, total properties in ULBs etc.)
Exit Criteria
Publish the program charter
Implementation plan agreement with priority applications and broad timelines
Program Governance Model and processes
Program Success Metrics
Capacity Building
PT Cell formation and appointment (*)
Data preparation/collection kickoff from Pilot ULBs
Cloud Infrastructure procured
Project Office Space allocated
Program Branding (name, logo, tagline etc.)
Stage 2 - Solution Design
Duration
4-6 weeks
Entry Criteria
Program Charter
PT Cell appointment
Key Activities
Standardisation of all PT processes
Initiate policy change if needed, based on the Processes defined
Conduct Product familiarisation workshop
Initiate collection of master data from pilot ULBs
Finalise data migration/collection/sync-up approach
Finalise data validation approach
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc.
Dashboard design finalisation for Program Tracking
Exit Criteria
Publish the PT processes, data template/workflows
Finalisation of Roll-out plan (in different phases)
Solution agreement for required State- specific customisations
Program tracking mechanism (Dashboard design finalisation)
Sign-off on approach to work with legacy or manual data (Data collection/migration/correction/ sync-up/validation)
Detailed project plan
Stage 3 – Configuration & Customization
Duration
6-8 weeks
Entry Criteria
Product Configuration Report has been signed off by the state
Detailed Project Plan set up in accordance with master data collection and environment setup
Key Activities
Setting up development environments
Development/customisation of reports and dashboards
Development/ integration of portal
Third-Party integrations (payment gateway, handheld/pos device)
Updation of user manuals and other key documents
Preparation & execution of Test Cases
Setup monitoring, support & maintenance processes, tools and dashboards
PT legacy data collection from Pilot ULBs(at least). No historical transaction will be considered. Only outstanding and property details shall be migrated
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc.
Identify ULB level Nodal officers for day to day support
Migration and verification of Pilot ULB data
Exit Criteria
Configured/Customized product that is ready for UAT
Monitoring, support & maintenance of Dashboards
Finalization of Initial Reporting and Dashboard KPIs
Identification of participants for UAT session
Training for System Content related Capacity Building finalised
Stage 4 – UAT & Go Live
Duration
2-3 weeks
Entry Criteria
Configured/Customized product ready for UAT
Pilot ULB Officials associated with TL are available for UAT & Training
Key Activities
UAT Environment Setup
Regression UAT and sign off from Pilot ULBs/ State
Issues/bug resolution
Setting up the Production environment
Setting up Support Center & processes (Help Desk)
Training (Users, trainer)
master trainers identified from ground for simultaneous training
Training the support resources
Marketing & promotion activities
Go Live & launch event
Setup of review and monitoring cadence/team
Usage/review/Dashboard/Field Visits
Exit Criteria
UAT Sign-off & Go Live for Pilot ULBs
Setup of review and monitoring cadence
Stage 5 – Rollout
Duration
5-6 weeks
Entry Criteria
Pilot has been successful in the State
there are less than 3 open critical incidents (issues) with respect to product, implementation and data
Key Activities
ULB configurations phase wise as per the Project Plan
Migration and verification of ULB data
Logistics planning for training
Establishment of bug ticketing tool for resolving ground level issues by the state team
Training the Users at the district level
Pan State Roll Out - Phase wise
Stabilise product
Exit Criteria
State-wide Rollout in batches:
Adoption tracking & Review Cadence operational
Help Desk Effectiveness assured
Critical Bugs fixed
Program Success Metrics Tracking Kick-started
Stage 6- Sustenance and Ongoing Improvement
Duration
Ongoing process
Entry Criteria
Rollout Phase 1 (First set of 30 ULBs where rollout will happen after all ULBs are live)
Key Ongoing Activities
Adoption Review Meetings as per the vision defined for the program
Plans for Execution of Core Team to ensure Sustenance of the initiative in the areas of:
Funding
IT support (infra, helpdesk, ongoing enhancements)
Process Effectiveness and Improvements
PT Cell Focuses on Using data for:
tracking field issues and performance data to identify improvements
identify additional Integrations around PT to make processes more robust towards enhancing PT revenues (e.g Upstream and downstream Processes)
Project Head
1
Domain Expert
1 Representation from Corporations/Council/Panchayat etc.
District Nodal Officer
1 per district
MIS Expert
1 per district
Task/Activity
eGov
State Leadership
Appoint PT Cell
Consult
Execute
Finalise funding for the program
Consult
Execute
Define state -specific procurement process
Consult
Execute
System Integrator(SI) Team sign-up/onboarding
Consult
Execute
Finalise Property Tax Program Vision
Consult
Execute
Task/Activity
eGov
PT Cell
SI Team
Identify & agree on scope and exclusions
Consult
Consult
Execute
Identify pilot ULBs
Execute
Consult
Project Kickoff - Implementation Methodology Presentation
Consult
Consult
Execute
Product Walkthroughs
Consult
Execute
Define Project Steering Committee structure and Project Governance process
Consult
Consult
Execute
Define phases of deployment/ rollout
Consult
Execute
Agreement on Deployment Priorities and high-level delivery timelines
Consult
Execute
Assessment of all PT process along
(1) citizen services/channels around it
(2) Integration with other department process
Consult
Execute
Finalize Program Success Metrics for Adoption and Governance adhering to the vision of the program
Consult
Consult
Execute
Internal Capacity Building, program logistics at State and ULBs, as per the current scenario
Execute
Consult
Collection of baseline data to measure endline target for the product (Revenue generated, total properties in ULBs etc.)
Consult
Execute
Consult
Task/Activity
eGov
PT Cell
SI Team
Standardisation of all PT processes, if needed
Consult
Execute
Initiate policy change, if needed based on identified improvements
Consult
Execute
Consult
Conduct Product familiarisation workshop
Consult
Execute
Initiate collection of master data from pilot ULBs
Consult
Execute
Finalise data migration/collection/sync-up approach
Consult
Execute
Finalise data validation approach
Execute
Consult
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc.
Execute
Consult
Task/Activity
eGov
PT Cell
SI Team
Setting up development environments
Consult
Execute
Development/customisation of reports and dashboards
Consult
Execute
Development/Integration of portal
Consult
Execute
Third-Party Integrations (Payment gateway, Handheld/pos device)
Consult
Execute
Updation of user manuals and other key documents
Consult
Execute
Preparation & execution of Test Cases
Consult
Execute
Setup monitoring, support & maintenance processes, tools and dashboards
Consult
Execute
PT legacy data collection from Pilot ULBs(at least)
Consult
Execute
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc.
Execute
Consult
Migration and verification of Pilot ULB data
Consult
Execute
Task/Activity
eGov
PT Cell
SI Team
UAT Environment Setup
Consult
Consult
Execute
Identification of participants for UAT session
Consult
Execute
Issues/bug resolution
Consult
Execute
Regression UAT and sign off from Pilot ULBs/ State
Execute
Consult
Setting up the Production environment
Consult
Execute
Setting up Support Center & processes (Help Desk)
Execute
Consult
Training user
Execute
Consult
Training Trainer
Consult
Execute
Training the Support Resources
Consult
Execute
Marketing & promotion activities
Execute
Consult
Go Live & launch event
Consult
Execute
Execute
Setup of review and monitoring cadence/team
Execute
Consult
Task/Activity
eGov
PT Cell
SI Team
ULB configurations phase wise as per the Project Plan
Consult
Execute
Migration and verification of ULB data
Execute
Consult
Logistics planning for training
Execute
Consult
Establishment of bug ticketing tool for resolving ground level issues by the state team
Consult
Execute
Training the Users at the district level
Execute
Consult
Pan State Roll Out - All Locations
Consult
Execute
Execute
Stabilise product
Consult
Execute
Task/Activity
eGov
PT Cell
SI Team
Adoption Review Meetings as per the vision defined for the program
Consult
Execute
Consult
PT Cell Focuses on Using data for:
tracking field issues and performance data to identify improvements
identify additional Integrations around PT to make processes more robust towards enhancing PT revenues (e.g Upstream and downstream Processes)
Execute
Consult
Plans of ongoing Sustenance in Place with respect to :
Funding
IT support (infra, helpdesk, ongoing enhancements)
Process Effectiveness and Improvements
Consult
Execute
Consult
Infrastructure
The actual Infra will be provided based on the questionnaire inputs received from the state
The state will take care of providing necessary project infrastructure and office facilities during the program for all on-site project Team members, which will be confirmed during the initiation phase. This includes workspace, office equipment (e.g., telephone with STD, fax machine, photocopy machine, etc.), stationery, PC/workstation, project LAN and internet access, etc.
The state will provide the necessary administrative support staff to carry out day-to-day project administration tasks, e.g., meeting rooms, Videoconferencing, etc.
The state should provide a Project Office and at least one conference room with speakerphone throughout the Project Duration.
Project Scope
Any new requirements received from State during the implementation phase will be handled through a change management process
State Team
The state will nominate a reasonably sized multifunctional Team from various departments of the State to be responsible for the implementation. The state Team would be required for information, validation, and execution through the implementation cycle and the Team members should be reasonably empowered to take decisions. Any delay in the decision-making process and the non-availability of the State Team may have an impact on the schedule.
The participants from State are expected to have a thorough understanding of the State’s internal processes.
The state will engage internal and external stakeholders required for this engagement and ensure their availability whenever needed.
Documentation
The Tech Implementation Partner will ensure provision of the following:
User education and training documentation delivery as per the default product documentation of the identified product versions.
Product manuals are expected to be shared with the State as part of the user manual.
All documentation in English and the language requirement of the state.
Training
Training to the end-users will be driven by the state Team.
The state will be responsible for providing the necessary infrastructure required for the Training, which includes the following readiness.
Training Rooms (Parallel Training Sessions) with Projector, White Board, Markers, Internet Connection, sufficient seating capacity, Desktop/Laptop for each participant and availability of Network for Trainees to connect to the server.
Implementation
The scope of the implementation will be limited to the services mentioned in Section 2.
State Team will have an identified SPOC for handling the first level of eGov communication with the client unless discussed and agreed.
eGov Team will not be involved in defining the test cases or executing the test cases.
Necessary signoff would be provided by the state upon completion of the defined milestones.
PROGRAM
18%
200
120
20000
2014-15
01/01/2019
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.
1
Make sure that each and every point in this reference list has been taken care of.
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.
1
General Tax (Residential)
2019-20
10
2
General Tax (Non-residential)
2019-20
9
The data given in the table is sample data.
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
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 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.
1
Make sure that each and every point in this reference list has been taken care of
Not Applicable
Configuration Data Templateconfigurable-data-template-tax-rate-v1.xlsx - 9KB
Sample Dataconfigurable-sample-data-tax-rate-v1.xlsx - 10KB
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:
1.
SO
INDIVIDUAL
Single Owner
एकल स्वामी
2.
MO
INDIVIDUAL
Multiple Owner
मल्टीपल ओनर
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
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
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 the 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 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.
1
Make sure that each and every point in this reference list has been taken care of
This checklist covers the activities which are specific to the entity.
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
-
Configuration Data Templateconfigurable-data-template-pt-ownership-sub-type.xlsx - 9KB
Sample Dataconfigurable-sample-data-ownership-sub-category.xlsx - 11KB
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.
1
FREEDOMFIGHTER
Certificate issued by DC/ Competent Authority
डीसी / सक्षम प्राधिकारी द्वारा जारी प्रमाण पत्र
2
WIDOW
Death Certificate + Spouse proof
डेथ सर्टिफ़िकेट + जीवनसाथी प्रमाण
3
HANDICAPPED
Certificate of Handicap by a competent authority
सक्षम प्राधिकारी द्वारा विकलांग का प्रमाण पत्र
The data given in the table is sample data.
1
Owner Type Code
Reference
64
Yes
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
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 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.
1
Make sure that each and every point in this reference list has been taken care of
This checklist covers the activities which are specific to the entity.
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]
Configuration Data Templateconfiguration-data-template-pt-master-3- (1).xlsx - 10KB
Sample Dataconfiguration-sample-data-pt-master-3-.xlsx - 15KB
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.
Given below is the sample data table from the template in which the data has to be collected:
1
INDIVIDUAL
Individual
व्यक्तिगत
2
COMPANY
Company
कंपनिगत
3
SOCIETY
Society
सहकारी समिति
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
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 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.
1
Make sure that each and every point in this reference list has been taken care of
Not Applicable
Configuration Data Templateconfiigurable-template-pt-ownershiptype.xlsx - 8KB
Sample Datasample-configurable-data-pt-ownership-category.xlsx - 9KB
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.
1
FREEDOMFIGHTER
Freedom Fighter
स्वतंत्रता सेनानी
2
WIDOW
Widow
विधवा
3
HANDICAPPED
Handicapped Persons
विकलांग व्यक्ति
The data given in the table is sample data.
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.
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.
1
Make sure that each and every point in this reference list has been taken care of
This checklist covers the activities which are specific to the entity.
1
The predefined format of the Owner Type Code only must be used and not any random code
-
Configuration Data Templateconfiguration-data-template-pt-master-3-.xlsx - 10KB
Sample Dataconfiguration-sample-data-pt-master-3- (1).xlsx - 15KB
Unit rates are also an important part of property tax. The property tax for a property is calculated on the area covered by the property. 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.
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
The data given in the table is sample data.
1
Boundary Code
Alphanumeric
64
Yes
2
Boundary Name (In English)
Text
256
Yes
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
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 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.
1
Make sure that each and every point in this reference list has been taken care of
Not Applicable
Configuration Data Templateconfigurable-data-template-property-tax-unit-rate-v1.xlsx - 9KB
Sample Dataconfigurable-sample-data-property-tax-unit-rate-v1.xlsx - 10KB
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.
1
RESIDENTIAL
Residential
आवासीय
2
NONRESIDENTIAL
Non-residential
गैर आवासीय
3
MIXED
Mixed
मिश्रित
The data described in the above table is sample.
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.
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 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.
Identify all the property usages categorized at the 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 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.
1.
Make sure that each and every point in this reference list has been taken care of
Not Applicable
Configuration Data Templateconfigurable-template-pt-usage-typemajor.xlsx - 10KB
Sample Dataconfigurable-sample-data-usage-category-major.xlsx - 10KB
The Property Sub Type represents 2nd level classification to the Property Type 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.
1
SHAREDPROPERTY
Flat / Part of the building
फ्लैट / भवन का हिस्सा
BUILTUP
2
INDEPENDENTPROPERTY
Independent House / Whole Building
स्वतंत्र घर / पूरी इमारत
BUILTUP
The data described in the above table is sample.
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
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 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.
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 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.
1
Make sure that each and every point in this reference list has been taken care of
There is no separate checklist is applicable to this entity.
Configuration Data Templateconfiguration-data-template-pt-master-2-.xlsx - 10KB
Sample Dataconfiguration-sample-data-pt-master-2-.xlsx - 15KB
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:
1.
RED
RESIDENTIAL
आवासीय
2019-20
2.
NONRED
HOTELS
होटल पेईग गेस्ट हाउस 10 कमरों तक(बेगैर वातानुकूलित)
2018-19
The data given in the table is sample data.
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
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
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 whether 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 that 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.
1
Make sure that each and every point in this reference list has been taken care of
This checklist covers the activities which are specific to the entity.
Configuration Data Templateconfigurable-data-template-usagetypedetail-v1.xlsx - 10KB
Sample Dataconfigurable-sample-data-usagetypedetail-v1.xlsx - 10KB
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.
1
BUILTUP
Built-Up
निर्माण
2
VACANT
Vacant Land
खाली जमीन
The data provided in the above table is sample.
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
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.
1
Make sure that each and every point in this reference list has been taken care of
There is no separate checklist applicable to this entity.
Configuration Data Templateconfiguration-data-template-pt-master-1-.xlsx - 10KB
Sample Dataconfiguration-sample-data-pt-master-1-.xlsx - 15KB
Ownership Transfer Technical documentation
The mutation service provides a facility to change ownership of a property in relation to sales, inheritance of property. it helps by providing a workflow on config and allows the municipality to collect payment with ease on approval of the process. The mutation flows ad APIs exist within the property-services code base and makes use of all the mentioned external services and configured values, in addition to those the rest can be used to control mutation flow.
Prior Knowledge of Java/J2EE.
Prior Knowledge of Spring Boot.
Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON etc.
Prior knowledge of Git
Prior knowledge of the demand-based systems.
Following services should be up and running:
user
MDMS
Persister
Location
Localization
Id-Gen
Billing-service
URL-shortener
Enables the user to create a mutation and transfer the ownership to the new owner.
Workflow config:
In Addition to property information and the extra owner information being added, some other information is required for workflow
The Creation Reason in the property should be sent as MUTATION for the request to be considered as a mutation request.
Along with the workflow name for mutation, a few extra details have to be provided in the additional details field of the property. Also either a new owner has to be added or an existing one has to be set to inactive for a valid mutation request.
The business workflow config follows the structure given for property workflow with respective name changes.
Workflow sample config for Mutation.
The property services will make a call to the mutation calculator at the required interval during the mutation flow.
The mutation service belongs to the property service itself and provides the same ease of access for the functionality.
Pick a property id that is already created in the system.
call the property/update API by changing the owner information or adding new owner information.
workflow information must be added mandatorily before submitting the request.
The calculation logic for mutation fee depends on the usage type of property (RESIDENTIAL, NON-RESIDENTIAL, etc ) and the current market value of the property.
If the current market value (CMV) of the property comes in between the minimum and maximum market value range of billing slab and the usage type of property match with the usage type for that billing slab then the mutation fees for that property is the amount mentioned in that particular billing slab.
Further, there are two calculation types which are FLAT and RATE which have to set by state/ULB for their billing slab for property mutation. If the calculation type is set as FLAT then mutation fee is the fixed amount mentioned in the billing slab which is used for the property.
If the calculation type is set as RATE the Mutation fee is X% of the current market value, where X is the percentage rate mentioned in the billing slab which is used for the property.
Other factors influencing calculation can be :
Ownership type
Property type
Locality
When the property is registered for mutation/transfer of ownership and all the document is submitted, then the mutation fees have to pay within a specified period of time of property mutation registration date. If a person fails to pay the amount of the fee before the deadline date, then some penalty charges have to pay. The penalty charge is Y% of the tax amount. The penalty percentage is set by the state/ULB. If a person pays the amount of the fees within the specified month of the property mutation registration date, then a certain amount is rebated from the tax amount. The rebate charge is Z% of the tax amount. The rebate percentage is set by state/ULB.
Note: For mutation fees calculation, document date value (means the date at which property is registered for mutation), market value of property, usage type value of the property is essential.
PT-Calculator Service is used for creating demands based on property assessments, mutations, and updating demands with the penalty, interest in case of payment delay.
Before you proceed with the documentation, make sure the following pre-requisites are met -
Java 8
Kafka server is up and running
PSQL server is running and a database is created to store property/application data
Following services should be up and running:
MDMS
property-services
billing-service
Calculate property tax, mutation fee based on billing slab.
create and update demand.
Deploy the latest version of property service and pt-calculator
Criteria:
Property Type
Property Subtype
Usage Category Major
Usage Category Minor
Usage Category Subminor
Usage Category Detail
Ownership Category
Sub Ownership Category
Plot Size
Floor Number
Area Type
The combination of the above variables can be used to define a billing slab. The billing slabs are stored in db in the table named “eg_pt_billingslab_v2”. To perform CRUD operations on the billing slabs API’s are provided in the module. Following is a sample create request:
The ‘ALL' keyword can be used if the slab is independent of that particular variable. If ‘fromPlotSize’ or ‘toPlotSize’ values are null they will set to positive infinity and negative infinity, a similar process will be for ‘fromFloor’ and 'toFloor’ values.
The estimation service class loops through all the units and calculates the tax based on the applicable billing slab. The exemptions are calculated using master data in MDMS Service. Each tax or exemption is added to the tax head estimate. Following are the exemptions and taxes that are calculated:
Property Base Tax
Owner Exemption
Unit Exemption
Penalty
Rebate
Interest
Fire Cess
Cancer Cess
From the above charges and exemptions penalty, interest and rebate are time-based. Rebate is given if the payment is done before the rebate deadline date specified in Rebate master data. Similarly, the penalty is charged if payment is not done before the deadline to pay tax. After the deadline to pay tax is passed daily interest is charged according to the rate defined in the master.
Property tax is calculated by adding the tax for each unit calculated using the billing slab for that unit. The formula for calculating tax for the unit is:
In case the unit is commercial and rented the formula is as follows:
ARV stands for Annual rent value.
If the property contains ground units (i.e unit with floor number = 0) then tax is also calculated for the unbuilt area. The formula for calculating the tax on the unbuilt area is as follows:
Below is a sample of master data JSON for interest :
If the given year rate is not defined the service will recursively fall back on the previous year until it finds a defined rate slab. The time for which interest is applicable is calculated by subtracting the epoch value of starting day (At 00:00 AM) from the end of the day (23:59 PM) epoch value of the current date. In the case of partial payment, the interest is calculated for each interval between payments and summed as the applicable amount for interest won’t be constant throughout.
If the fraction is greater than equal to 0.5 the number is round up else it’s round down. eg: 100.4 will be rounded to 100 while 100.6 will be rounded to 101
The following is the format of penalty master data:
If the time during the demand creation date is greater than the penalty starting day, a penalty of x% will be applied. The x% is defined in the rate field. The penalty also provides a fallback for master data i.e if for a particular year entry is not present it will recursively search for the previous year and apply that rate.
Depending on the owner type of user flat amount or percentage of tax amount is given as exemption. In the case of multiple owners, the exemption is calculated for each owner and summed. Following is a sample master data:
Once the property is sent to the calculator its tax estimates are calculated. Using these tax head estimates demand details are created. For every tax head, the estimate-demand function will create a corresponding demand detail.
Whenever _calculate API is called demand is first searched based on the property id and the demand from and to period. If demand already exists the same demand is updated else new demand is generated with consumer code as property and demand from and to a period equal to financial year start and end period. In the case of Reassessment, the demand is always updated for the given year.
In case of update, if the tax head estimates changes, the difference in amount for that tax head is added as new demand detail. For example, if the initial demand has one demand detail with PT_TAX equal to 100
After updating if the PT_TAX increases to 150 we add one more demand detail to account for the increased amount. The demand detail will be updated to:
RoundOff is bill-based i.e every time bill is generated round-off is adjusted so that the payable amount is the whole number. Individual PT_ROUNDOFF in demand detail can be greater than 0.5 but the sum of all PT_ROUNDOFF will always be less than 0.5.
If demand is created and the total tax is supposed 100.40, then a negative round-off amount of -0.40 is added so that the tax becomes 100. If during reassessment the tax changes and becomes 111.70, to round it off estimate will give tax head estimate of +0.3. The demand generation logic will add a new demand detail by taking the difference in the old and new tax amount for that tax head. Therefore a new demand detail of 0.3-(-0.4)=0.7 will be added. There will be now two PT_ROUNDOFF tax heads one with an amount -0.4 and the other with 0.7 making the total round-off amount (-0.4+0.7)= 0.3 which with the tax amount of 111.70 will give a bill amount of 111.70+0.3=112.
PT-calculator should be integrated with property-services which internally invokes the calculator service to calculate and generate demand for the charges.
Carries out the process of creating demand and updating them on a need basis as per the requirement of assessment and mutation.
/_caluclate should be exposed internally for property-services integration.
/_estimate API should be exposed for UI integration, which enables users to view the estimate before proceeding.
/demand/_update API should be configured in billing service for demand update function on bill expiry.
Service configuration details
One of the major applications of the eGov stack which helps municipal and citizens to handle property tax payments and other related functions on the property such as assessments, mutation, and so on.
Prior Knowledge of Java/J2EE.
Prior Knowledge of Spring Boot.
Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON etc.
Prior knowledge of Git
Prior knowledge of the demand-based systems.
Following services should be up and running:
user
MDMS
Persister
Location
Localization
Id-Gen
Billing-service
URL-shortener
The Property Service provides multiple functionalities starting from serving as a central repository where property information is registered for reference of citizens and other municipality-provided services such as water connection and sewerage management. An assessment can be done so as to calculate and pay tax on the property. The different services provided by the property services are
Property Registry
Assessment
Mutation
Bifurcation
Consolidation
Registry Explanation
The registry flow helps the citizen/Employee to create a property in the system with the minimal information required.
Other workflows such as assessment or mutation can be triggered on the existing ACTIVE Property in the registry.
The property can be created, updated, cancelled, searched, Followed by the process of Mutation and Assessment.
The same entry in the registry can be referred by other modules for their business purposes(Water charges).
Persister File Config
Workflow-configs
Each flow in property has a workflow associated with it, which can be controlled by the following configs
The Boolean field which can enable/disable Workflow - same field controls the update and create the workflow
Workflow Config for property create if the source is from WATER CONNECTION module
For use case 1 which says, The property which is creating from Water and sewerage module should have one step workflow. for this requirement in the above MDMS file businessService with PT.CREATEWITHWNS object must have enabled the field to set as true. Then for all the property creation from Water and Sewerage module would have one step workflow and property would be created with an ACTIVE state.
Fields in the above MDMS file
Sample workflow config for use case 1 where property creation is from water and sewerage module with one step workflow
Sample workflow config - (The same PT.CREATE can be used for update workflow also since both involve the same functionality)
PT.LEGACY workflow config
Notifications :
To enable or disable notifcation notif.sms.enabled=true
#notif urls - makes use of the UI app host in notification service egov.notif.commonpay = citizen/egov-common/pay?consumerCode={CONSUMERCODE}&tenantId={TENANTID} egov.notif.view.property = citizen/property-tax/my-properties/property/{PROPERTYID}/{TENANTID} egov.notif.view.mutation = citizen/pt-mutation/search-preview?applicationNumber={APPID}&tenantId={TENANTID}
The Current localization messages for notification
Configs in App.props
Property service can be integrated with any organization or system that wants to maintain a record of the property and collect taxes with ease.
Easy to create and simple process of self-assessment to avoid the hassle.
Helps maintain property data which can be used in the integration of other essential services like asset management, water connection and so on.
provides additional functionalities like mutation, assessment of properties.
Customer can create a property using the /property/_create
Search the property using /property/_searchendpoint
/property/_update endpoint to update the property demand as per need.
Mutation can be carried out with the help of /property/_update itself, no extra API is needed.
Doc Links
API LIST:
Theme
Q1
Q2
Q3
Q4
Enhance functional Coverage
Open dashboards for citizens - To view defaulters - ULB collection performance - Document required in PT UX Revamp - Citizen & Employee - Mutation - Bill Genie & other functions - Receipt Cancellation
Capital rules based assessments supporting the product
- Amalgamation of a property - Bifurcation of a property
Increase adoption
- Product dashboard to measure adoption on field
- Completing the product dashboard documentation & Testing - Deploy updated UX to the existing clients - Data Uploader for improving data migration activities
- A/B testing on features based on the usage and adoption patterns - Data uploader using excel files - POC with impel
- A/B testing on features based on the usage and adoption patterns - Explore interoperability with other govt. functions like registry deptt. etc.
Product innovation
Implementing registry principle in the property tax product
POC - Revenue enhancement tool to plug revenue leakages using GIS, image processing, etc.
Ease of deployment & Partner Enablement
- Centralized Demo environment with completed demo scripts and videos - Standardized reports and dashboard for PT
- Internalizing the BBPS protocols & integration (as done in UK)
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
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)
कच्चा भवन अर्थात समस्त अन्य भवन जो (एक) और (दो) में अच्छादित नही है
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.
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.
Given below is the sample data table from the template in which the data has to be collected:
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 मीटर से अधिक की चौड़ाई वाले मार्ग पर
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.
Usage Category Minor is nothing but a further classification of , 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 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.
Not Applicable
Procedure to integrate elastic search for Fuzzy search with any of the eGov modules.
Creating the index as per the requirement
The elastic index has to be used for fuzzy search due to performance enhancement and when PII fields are involved which cannot be accessed in DB directly to apply fuzzy logic.
When PII data are involved those fields shouldn’t be returned by the elastic search but only can be used to apply the filter. To enable this that particular field should be indexed but not stored.
eg -
In the above example, when data is posted, all the fields will be stored, but the index will never return the excluded source fields when searched.
Querying an index
Elastic Integration with code
Add the elasticsearch host from the eGov cluster.
Divide the search params between the ones that will be sent to elastic and others to DB (search to elastic should be made only if the fuzzy fields are present in search request)
The result of the elastic search should be only the required primary-Id of the entity(property-id, trade license-id, etc..)
Then the resulting ids should be used in the normal search as it is.
Application Properties
Properties need to add for integration
The indices need to be reindexed for the fuzzy search to work if changes are done in the index. particularly in the case of protected fields being indexed but not to be returned in the search.
This is a further or third level sub-classification of the property 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:
The data given in the table is 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 that 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
For overview Please refer to the parent file -
The assessment set of services inside the property module is used for assessing the value of a property in a given time frame and collect taxes for the same. Assessment is a snapshot of Property for a given transaction on that Property. These APIs provide functionalities to create/update/search the assessments. An assessment cannot exist without property.
MDMS CONFIG:To show a preview of this link, connect your Github account.GithubConnect
Configs
Assessment shares most of the configs with Property as mentioned above, only exclusive properties are mentioned in this section.
PERSISTER CONFIG: ``
Workflow Config
Sample businessService create API body for Assessment workflow:
Other system-level configs are the same as PT-Registry as mentioned above.
Notification Configs
Payment Notification
For adding localization for any status append ASMT_ prefix to the status and for adding a message for any status add ASMT_MSG_ before the status.
Assessment ****(Property Calculator) -
The calculator service Prepares and property tax and files the demand in the billing service for payment. It has the ‘estimate’ API to give the estimated property tax without persisting data and a calculated API to create demand for payments.
Assessment integration helps citizens to assess their property with ease and helps them verify their tax values by themselves which gives more control to the citizens and hep the municipality collect taxes with ease.
Easy to create and simple process of self-assessment to avoid the hassle.
Integrated payment for multiple years enables by digit platform.
Customer can create an assessment on a given property using the /assessment/_create
Search the assessment and its workflow status by using /assessment/_searchendpoint
/assessment/_update endpoint to update the assessment and its workflow states as per need.
API LIST
Users can look for the list of the properties registered under their mobile number in My Properties Tab. Each Property for the initial view will display Property Id, Owner Name, Address and status, with view details option, through which User can look up more details about the property registered. If users do not find the property looking for, new property can be registered using the below link “Click here to register new Property”.
Once the user clicks on View Details, the Property Information Page is displayed with all the necessary information about the property.
The template for My properties and Property Information page is present inside pt/pages/citizen/MyProperties. The list of properties is retrieved by calling the search API "/property-services/property/_search".
This API is called using the React hook present inside the index of My Properties and Property information page, a single property is being loaded, bypassing the unique Property Id in the search API.
If search API result is successful, Assessment Search API is called to know the assessment status i.e /property-services/assessment/_search.
If the assessment object returned fetches assessment array details then the fetch bill API is called in order to retrieve the payment details for the particular property. API is /billing-service/bill/v2/_fetchbill
Following is the hook used for the property search API, assessment search and fetch bill.
No MDMS data is used here, all the data is loaded from Search API.
For My Properties also the Localization keys are added to the ‘rainmaker-pt’ locale module. To change, update or add, any new localization key is done in the same locale module only.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
This is the mapping between the and Sub category
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Unique Identifier assigned for the . For example, Freedom Fighter is represented as FREEDOMFIGHTER
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
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
The name/description of the boundary that is being used for the classification. The names have to be from the data collected
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Property Type code referring to the
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
This is the mapping between detail and Sub Minor Code. Refer entity for more detail
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Please refer to the parent for external services:
All content on this page by is licensed under a .
Property-services
API Collection -
All content on this page by is licensed under a .
MDMS CONFIG:
The persister File config for property services can be found in the Config repo of eGov Git, which needs to be added in the persister service -
For the creation of property from the water and sewerage module, as per the use case mentioned in this , a different workflow config is used. For each use case, to identify which workflow to use can be identified from this .
Note: The above objects indicate each use case mentioned in this , so at a time only one object (use case) enable field must set as true
All content on this page by is licensed under a .
All content on this page by is licensed under a .
This is a simple request, there are that can be used to enhance the fuzzy search.
Please refer to the following for the integration
Reindexing for PT:
All content on this page by is licensed under a .
The first property switches workflow on or off, while the second property provides a way to control which field change can trigger the workflow. A businessService needs to be created using the workflow API.
The calculator service
please refer to the property document
All content on this page by is licensed under a .
for the My Properties and Property Details common Index.
All content on this page by is licensed under a
name
value
description
is.mutation.workflow.enabled
true/false
enables/disbales the workflow
PT.MUTATION
workfow config name
Residential
0
X lacs
A% of CMV
INR G
FLAT
Non -Residential
0
X lacs
E% of CMV
INR Q
RATE
Residential
X+1 Lacs
Y Lacs
B% of CMV
INR H
FLAT
Non -Residential
X+1 Lacs
Y Lacs
B% of CMV
INR H
RATE
Residential
Y+1 Lacs
>Y+1Lacs
D% of CMV
INR L
FLAT
Non -Residential
Y+1 Lacs
>Y+1Lacs
C% of CMV
INR I
RATE
Title
Link
API contract for MT calculator
API list to create Mutation Slabs mutation/_create, _search, _update
API list for MT-Calculator mutation/_calculate
1
Make sure that each and every point in this reference list has been taken care of.
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
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
This is the relationship between sub minor and minor usage categories.
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.
1
Make sure that each and every point in this reference list has been taken care of
Title
Link
/assessment/_create
/assessment/_update
/assessment/_search
name
value
description
is.workflow.enabled
true/false
enable disbale workflow
PT.CREATE
the name should match the config name in the workflow businessservice JSON
PT.LEGACY
PT.UPDATE
MDMS Fields
Description
businessService
Name of workflow config
initialAction
Indicate the start(initial) action of the particular workflow mention in businessService.
inWorkflowStatusAllowed
This field indicate whether the property with application status as “inWorkflow” can be use with water and sewerage connection creation. If this field is true then for that particular use case, the property with “inWorkflow” status can be use with water and sewerage connection creation and vice versa
enable
If this filed is set as true, then the other fields associate with the particular object is use for property creation.
name
value
egov.idgen.ack.format
PB-AC-[cy:yyyy-MM-dd]-[SEQ_EG_PT_ACK]
egov.idgen.mutation.format
PB-MT-[CITY]-[SEQ_EG_PT_MUTATION]
egov.idgen.assm.format
PB-AS-[cy:yyyy-MM-dd]-[SEQ_EG_PT_ASSM]
egov.idgen.ptid.format
PB-PT-[cy:yyyy-MM-dd]-[SEQ_EG_PT_PTID]
citizen.allowed.search.params
accountId,ids,propertyDetailids,mobileNumber,oldpropertyids
employee.allowed.search.params
accountId,ids,propertyDetailids,mobileNumber,oldpropertyids
Title
Link
USER Service
url-shortening
MDMS
Billing-service
Location
Workflow
Persister
****
Localization
Id-Gen service
Title
Link
/Property/_create
/Property/_update
/property/_search
1.
RESIDENTIAL
Residential
आवासीय
NA
0
0
RESIDENTIAL
2.
COMMERCIAL
Commercial
व्यावसायिक
NA
0
0
NONRESIDENTIAL
3.
INDUSTRIAL
Industrial
औद्योगिक
NA
0
0
NONRESIDENTIAL
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
This is the mapping between the minor’s and major’s of the usage category which can be found in Usage Category Major
Step 1
Get the current mapping of the pt index using the _mapping API
Step 2
Add the following json mappings in the existing mappings (parallel to properties key):
Sample QA final mapping for reference is attached at the end.
Step 3
Recreate property-services-enriched with the new mapping.
Step 4
Update the indexer configuration, add the following 3 fields ownerNames
, doorNo
, street
in custom mapping as added below in sample configuration:
https://github.com/egovernments/configs/blob/qa/egov-indexer/property-services.yml
** If search has to be enabled only on names of only ACTIVE user, configure indexer jsonPath accordingly. Use $.owners[*][?(@.status=='ACTIVE')].name
instead in the config
Step 5
Restart indexer
Step 6
Trigger reindexing
Recreated property-services-enriched index with the new mapping
Created kafka connector
Hit the legacy index api
Once data is indexed in property-services-enriched, verify that all the data is indexed
After validating the data, drop the property-services index and use alias to point property-services
to property-services-enriched
Sample mappings from QA env:
Migrating legacy data
This section covers the principles eGov will be following for migrating legacy property registry along with demand and collection balances to the DIGIT system (currently in Uttarakhand but can be used for other clients in future). eGov has been successful in implementing property tax applications in states of Andhra Pradesh, Punjab and various other Municipal Corporations like Greater Chennai, Nagpur and so on using best practices defined here.
The state team is supposed to take care of the below activities before property data is shared to eGov for data migration:
State team to share all master data and its localization that are part of the property tax. For example masters like - city, boundary, usage type, property type and so on
State team to do the data gathering and prepare the property tax data in the predefined template shared by eGov
Data prepared needs to be scrutinised by the data owner from the State’s team. Following data validations to be considered in particular:
Validate if all sheets have accurate records (owner details, property details and DCB details, Floor details) in terms of what is expected
DCB details can be more than the number of records in the property sheet
There can be multiple owners for a single property. But there needs to be an owner and DCB for each of the properties
Have a check on all mandatory data present
All sheets to be aligned with the unique id field
The state has to share the complete set of property data for a city in a single go. They can also give one set for residential properties and another for commercial properties, but cannot give multiple sets for the same.
Data owner to give a sign off on data before handing over to eGov team
State team to be aware of assumptions and default values that will be applied as part of the data migration process. This will be shared by the eGov team
UAT and production environment where the data is to be loaded to be provisioned and set up
Data received from the State team will be cleansed by eGov with default values
Mandatory fields that have no financial impact on citizens can be filled with default values in the absence of values specified by the State team. Few examples are listed below -
Covered areas can be updated as 0
Road type as 12 meters
The number of floors can be updated as 1
Certain fields that have a financial impact can also have default values like tax amount in the absence of values specified by the State team. (It can be updated as Rs.1)
If the mobile number is blank, a dummy mobile number will be updated. Care will be taken to ensure that this is not an actual mobile number and this number will be removed from notifications. Dummy numbers can be something like 99999xxxxx where the first few dummy numbers in a state will be 9999900001, 9999900002, 9999900003 so on.
Follow the below assumptions to do data cleaning
If the mobile number and user name combinations are duplicating we will consider these properties belong to the same owner. This means one user will be created in the system which will have a link to two properties.
Have a marker if any assumptions and default values are applied on a record
Certain data are currently not assumed or defaulted. Below listed are a few cases -
Owner details completely not available for a property - If complete owner details are missing, these records to be kept in the not to be migrated list.
If DCB is not there or given for a range of years - since there are a lot of use cases here, we can keep this record in the not to be migrated list
Duplicate old property id - leave the data as it is and then edit it later using the data entry screen
If boundary data is not present or data not aligned with the master data shared - update to a default mohalla which the state agrees to
Door number is not present - update the value as “door number”
Owner Name blank in the owner details sheet - update the value as “owner”.
Load the records using property migration kit to UAT server
Prepare a list of all passed and failed property records and share them back with the State team. Passed records along with values defaulted will be shared.
If the State team wants eGov to retry all failed records they are expected to come back with the revised data within one week.
Repeat Step 1 for revised records received from the State team.
The final status of the data load will be shared with the State team.
State team to verify data loaded on UAT server and provide a sign off for each of the ULBs within 1 week
On getting sign-off of UAT data, eGov will load that data to production using the migration kit used for loading to UAT instances. This can be done only if the production infrastructure is ready.
Get sign off on the production data before the application can be made live.
Roorkee
16363
500
97%
3%
Rishikesh
2877
356 in the first sheet
261 in the second pass
88%
91%
12%
9%
Communication for data migration exercise can be split into the following stages:
There will be a SPOC from the State team who is the data owner who will share data with the eGov team. Excel sheet data will be put on google drive and shared with the project manager from eGov. Similarly, all communications from the eGov side to State will be routed through the project manager.
Pre-migration
A demo of how PT module works - State + ULBs
Product fitment discussion, configurable data finalization and sign off - State
An overview of how data migration works - State + ULBs
Sharing the template (along with checklists and FAQs) in which we will collect data and type of data required against each field along with training - State + ULBs
Sharing assumptions which will be followed while migrating data - State + ULBs
During migration
Data inconsistencies observed in Data cleaning stage - State
Gaps needed to complete data migration (like mohalla mapping) - State
List of records which will be migrated as-is and the ones which will be migrated with assumptions - State
Post-migration
List of properties migrated without error - State
List of properties migrated with error for ULBs manual entry - State
UAT Sign-off document - State + ULB
Final confirmation post migration on Production - State + ULB
All failed records from the second pass will be manually entered into the system using data entry screens
The state has to make a mandate to collect property tax only using DIGIT.
All records with assumption markers or incorrect data can be updated by counter employees when citizens come for payment. Maybe this option can be given to the citizen when coming for online payment.
When a citizen is coming for making his payment, the counter operator can check if their property exists in the system using propertyid or mobile number. If it is found to be missing, it can be captured afresh in the system using the data entry option. All required information can be obtained from the citizen, either from previous year receipts that they carry or directly asking them.
With this approach, a ULB can go live with 90% of property data within a short time.
Data Migration Checklist
Data provided in the standard template attached only will be accepted for further analysis and process.
Data provided into the template is loaded into staging tables and then validation and data clean-up is done.
Properties with current Tax 0. (2020-21)
Properties with advance collection
Properties with current tax partially payment
Properties with Mohalla not configured in master
Masters mapping with the configured masters data in the system.
All the findings of data are reported to the onsite team and sought clarification.
Once all the queries/ findings are cleared/addressed data is moved into UAT.
Data is verified into UAT with sampling by the state team. Go ahead.
Preparing some basic checkpoints before moving into production.
Move the data into production and verify the checkpoints.
An illustrative guide to using the property tax module
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.
The PT module enables citizens to pay property taxes online. It facilitates the governing bodies process property tax payments.
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.
Citizen
Add Property
Search Property
Edit Property
Assess Property
Re-Assess Property
Pay Property Tax
Transfer Property Ownership
Download Receipts/Applications
Individuals and Community groups
Counter Employee (CE)
Add Property
Search Property
Edit Property
Assess Property
Re-Assess Property
Pay Property Tax
Transfer Property Ownership
Download Receipts/Applications
Counter employees who assist citizens register new property details, transfer ownership of property, pay property tax on their behalf
Document Verifier (DV)
Verify and forward
Send Back
Edit Application
Employees responsible for verifying the supporting documents submitted by citizens for a new property or transfer of ownership of property
Field Inspector (FI)
Verify and forward
Send Back
Reject
Edit
Employees who go on to the field (i.e. location of property) and physically verifies the information provided by the applicant is correct
Approver
Approve
Send Back
Reject
Cancel
An employee who has the final authority to approve or reject the property registration
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.
name
value
description
assessment id format
PB-AS-[cy:yyyy-MM-dd]-[SEQ_EG_PT_ASSM]
kafka create assessment topic
save-pt-assessment
kafka update assesmsent topic
update-pt-assessment
assessment.workflow.enabled
true/false
Workflow integration can be controlled by the following two properties
assessment.workflow.trigger.param
usageCategory,occupancyType,occupancyDate
This page provides the user interface and API details for My Applications feature in the PT module. Users can review the list of applications and their status registered under their mobile number in the My Applications tab. Initially, only four application will load at once. If the user wants to look for more, the “Load More” option needs to be clicked. Each Application for the initial view will display Application No, Service Category, Property Id, Application Type and status, with Track option, that enables the user to look up more details about the Application. If a user is unable to find their property details on the system, a new Application can be raised using the link provided at the bottom of the page.
Once the user clicks on the Track Button, the Application Details Page is displayed with all the necessary information about the application.
Timeline component: The timeline component is present at the end of the application details which tells about the current status and history of the application passing through various workflows and actions taken.
Click here to fetch the working code details for My Applications and Application Details common Index.
The template for My Application is present under pt/pages/citizen/PTMyApplications and the Application Details page is present inside pt/pages/citizen named as PTApplicationDetails. The list of Applications is retrieved by calling the search API "/property-services/property/_search"
This API is called using the React hook present inside the index of PTMyapplication and PTApplicationDetails page, a single application is being loaded, bypassing the unique Property Id in the search API.
Following is the hook used for the property search API.
Create and Update Util Function
The two main util function and the objective of it are given below:
Create Util Function: While going through the Create flow, all the inputs that the user has entered are stored in a different structure. Since the units are not separated in the flow but incorporated according to each ground, the storing structure is different from the request body of Create API. This function transforms the flow of stored data into the requested body format.
Click here to fetch the code.
Update Util Function: Click here to find detailed information about this function.
No MDMS data is used here, all the data is being loaded from Search API.
For My Applications also the Localization keys are added in the ‘rainmaker-pt’ locale module same as My properties and create. To change, update or add any new localization key is done in the same locale module only.
Objective: To provide employees with the ability to Edit property Details (except Owner Details).
The Edit form can be used to update the details of an approved property, or whenever an application is in a workflow state that allows/require employees to make changes.
All the updatable Input fields are enabled, and all the fields related to owner details are disabled.
After editing and clicking submit when the user is successful the user is redirected to a success screen similar to that in Employee Create.
The implementation of the Edit Form can be found in:
The document details are implemented similar to the create application and uses the same MDMS configurations.
APIs Called:1property-services/property/_update
** The Update API is supplied with updated property values from the form, and also all the units that were added at the time of creation are set with active
: false
, while the new units are set to be active
: true
even if no change is made to the units.
Acknowledgement Screen
If the Property Update is successful. then the employee is directed to this screen that shows the Acknowledgement Id and option to download a pdf of the acknowledgement containing property details.
Url
Roles
Action Id
property-services/property/_update
PT-CEMP
1896
Objective: To provide the employees involved in PT workflow, the functionalities to create a property Application in create workflow.
A counter employee can use create an application form, to register a citizen’s property.
The file for create Application form for PT can be found in:-
for creating an application employee enters all the details of the form manually, and Documents are uploaded based on the MDMS configuration found in the file:
https://github.com/egovernments/egov-mdms-data/blob/DEV/data/pb/PropertyTax/Documents.json
MDMS Data
The MDMS data for documents is similar to that found in :
**with the noted addition of formDataPath, formArrayAttrPath
, in filterCondition
and dropdownFilter
.
formDataPath
path is the form path in form of an array of keys that requires to be followed to a new UI form to check the entered value. similar to jsonPath
and parentJsonpath
in old UI, While the formArrayAttrPath
replaces the arrayAttribute
.
The use of the MDMS data within the component can be found in :
After adding all the valid documents and form values in the form, the user is allowed to submit the form
which calls the property create API:1property-services/property/_create
Acknowledgement Screen
If the Property creation is successful. then the employee is directed to this screen that shows Acknowledgement Id and the option to download a hardcopy of the acknowledgement containing property details.
Url
ROLE
Action ID
property-services/property/_create
PT-CEMP
1895
Objective: To provide citizens with the functionality to apply for Ownership Transfer for an active property.
The Transfer of Ownership Option is provided to citizens on the home screen in the citizen App, under property Tax card.
Upon clicking on “Transfer Property Ownership/Mutation” link, users are taken to property search page just like in case of “search & Pay” option, where he can search for the property he wants to search the property for.
After searching the property the user is shown the property details for the properties based on the search criteria. With Total Dues on top of the card.
If there are dues owed on the property (unpaid taxes), then users are shown a popup stating that the citizen has to clear his dues first. with a proceed to pay button that takes citizens to the common pay page, just like in the case of Search & Pay.
In case of dues cleared the citizen is taken to the Docs required Page, just like in the case of Employee Mutation, where he is shown the list of docs he is supposed to have in order to be able to transfer the property.
on this page after clicking on Transfer of Ownership, the citizen is made to go through the Ownership Transfer flow where he fills in the Ownership details and Mutation Details. After completing the flow citizen is shown with the success screen with his application number and the option to download his acknowledgement as a pdf.
The code for citizen mutation can be found in the link:
MDMS data
The MDMS data is the same as in the case of employee Mutation Screen.
API used
The citizen mutation calls the property-services/property/_update
API to update the property status after that the application is gone through the Employee workflow to complete the transfer.
**When Update API is called the documents are updated for the property according to the following snippet:-
Here originalProperty
is the property data before mutation, and mutationDocs
is the MDMS response for Mutation Docs.
Url
Roles
Action Id
property-services/property/_update
CITIZEN
1896
The Quick Pay feature allows a citizen to quickly view or pay all his pending bills for Property Tax (or any other supported business Service) by clicking links directly from the Digit-UI home screen.
Clicking on the Property Tax link in the Quick Pay section, a user is logged in and redirected to the My Bills Screen. Else, the user has to log in using his mobile number and the OTP sent to the number. The user is redirected to the My Bills screen.
On the My Bills screen, the user finds his pending property Tax bills (displayed as cards) for registered properties. The user can click on the View Details button of the corresponding card to check the detailed bill summary which takes him to the bill details page. There is also a link for the case when the user is unable to find the property tax bills.
The Bill Details screen shows a list of various categories of taxes that are present. After checking the user can select to pay either the full amount or custom amount, which cannot be less than ₹100 and not more than the total tax. These restrictions, however, are customizable as per ULB requirement and can be changed through MDMS.
Click on the Proceed To Pay button redirects the user to the Pay screen. The user is asked to select the payment gateway from a bunch of radio buttons, and then after clicking pay, the user is redirected to the bank payment gateway.
After making a successful payment through the bank gateway, the user is redirected to the response screen which shows the details of the payment and other bill details.
In case the payment fails for any reason the response screen shows the message, that the payment transaction has failed.
Use Case: when user wants to pay for Property for a different mobile number:
My Bills page only displays the properties with pending Taxes, which are associated with the mobile number which is logged in. But if a user wants to search for any other property, then he can click on the link below the My Bills screen which will take the user to the search screen.
On the Search screen, the user can search a property by mobile Number, a unique property ID, or an existing property ID. After mentioning the parameters the search takes the user to the search results screen. Where user can see all the properties with the matching criteria, whether or not they have pending taxes.
From Here on clicking view Details a user is redirected to the bill-details Screen, for the property, just as in the case of My Bills Screen.
My Bills Screen
Click here to fetch the My Bills screen starting file
An MDMS call is made to this page to fetch details based on the defined restrictions such as partial payment is allowed or not, advance payment allowed or not, minimum payable amount etc. for the particular business Service which is supplied into URL.
The MDMS criteria used here for fetching MDMS details are:
Also, the pending bills are fetched for the citizen for the specific business service using the custom hook, that fetches bill for logged-in mobile number.
The bill is rendered using a keynoteConfig file which can be located here.
On this page, for each business service, there is a configuration stored to define what part of the bill is to be displayed.
The configuration returns an object of structure.
Here my-bill key has config for the my-bills screen, this configuration decides what details to show on the card for each service from the bill object returned through fetchBill API.
It is an array of objects, where each object puts the bill detail on the My-Bills bill card.
Each object contains 4 properties ie keyValue, keyPath, fallback, noteStyle
. The keynote config is added into the Digit component Registry as getBillDetailsConfigWithBusinessService
The implementation of the config can be found here.
Bill Details Screen
The bill details screen can be found here.
It checks for various payment restrictions which are fetched from the MDMS on above mentioned MY Bills description, and also all the tax heads that are to be displayed in the summary are also fetched from the same MDMS.
The structure for payment rule response from the MDMS are -
partPaymentAllowed
key when true allows payment less than bill details to be paid otherwise the user can pay only the bill Amount.
minAmountPayable
is the minimum bill amount a user can pay.
isAdvanceAllowed
if the true user can enter the amount more than the specified.
The link for the MDMS can be found here.
Payment Screen
The payment screen fetches the payment gateways from an MDMS call.
The code can be found here.
Response Screen
The response page code can be found here.
Search Screen
The search screen is a part of PT module and its code can be found here.
Search Result Screen
The Search Result screen code can be referred to here.
The keynote config is responsible for adding the new bill UI for adding a new Bill for a business Service.
The whole function is exposed within the component Registry as getBillDetailsConfigWithBusinessService
and can be redefined from here.
S. No.
API
Action id
Roles
1
/access/v1/actions/mdms/_get
870
CITIZEN
3
/egov-mdms-service/v1/_search
954
CITIZEN
4
/localization/messages/v1/_search
1531
CITIZEN
5
/billing-service/bill/v2/_fetchbill
1862
CITIZEN,
6
/pg-service/transaction/v1/_create
1571
CITIZEN
7
/collection-services/payments/_search
1864
CITIZEN
8
/pg-service/transaction/v1/_update
1572
CITIZEN
9
collection-services/payments/PT/_search
2029
PTCEMP, CITIZEN
This page provides information and details for edit and updates property feature in the PT module. This feature allows the user to edit the application already created or update the property already registered with their mobile number. After verification, the employee can send the application back to the citizen with remarks on any required changes. The edit and update feature allows the users to make these changes. It also allows the user to update the details of the property details online if there are any such upgrades or changes.
On the Application details page, on the employee side, if the property is marked with “Send Back to Citizen”, the edit option will appear dynamically at the end of the page and will be static in nature.
On clicking the Update button, users can edit/update the property details by going through the Create flow again. The only exception here is the values will be pre-populated from the Property object received from Property Search API. On completing the flow the Update API is called and the property is updated successfully.
Acknowledgement screen
Click here to access the Edit/Update property main index.
The main code contains the functions that transform the property object received in Search API to the object. This includes primarily the Assessment flow units suitable for the Create flow since the user has to go through Create flow again with pre-populated details and update the value of the data accordingly. It also contains the routing details for the pages in the Create flow.
Update Util function: this function does the exact opposite of the Create util function (refer Property Tax - My Applications ). The property object which is received from the Property Search API is converted to the Create flow relevant structure so that the values can be pre-populated for the user convenience, on completing the flow, the application is updated. The link for the same is available here.
MDMS data used here is the same as the Create flow since the flow structure used for edit/update property is the same as the create property flow. Please refer to the link here for detailed MDMS information.
For Edit/Update Property also, the Localization keys are being added in the ‘rainmaker-pt’ locale module. To change, update or adding of any new localization key will be done in the same locale module only.
This page provides detailed UI information on the Create Property feature available in the Property Tax module.
The objective is to provide user facilities to add a new property, view the property details and the application currently on their number. The feature allows users to update the property or edit the application.
Users can add new property using the Create Property button, and while going through the workflow, can add all the valid information, according to the question asked. At the end of the flow, a Check page will be displayed on which the user can cross verify the information entered. On submitting, the application is created.
Create Property Flow
Property Tax information screen will be displayed after login, which helps the user to understand the necessary documents needed to complete the new registration for the property.
Property Details Flow
The user needs to enter the details about the property first. Below is the flow chart for the property details flow**.**
Assessment Details Flow
Then the user will be asked about the assessment details, which contains information about each floor and basement.
Address Details Flow
After entering the details of the property, the user needs to enter the address of the property, where it is located. The flow is straightforward, without any conditional routing.
Users can pinpoint the location in the Geo-location map, according to which pin code and city, as well as locality, is auto-populated.
Owner Details Flow
Finally, the user needs to enter the details, about the property owner, it can be institutional - (Government/ Private) or Single/Multiple Owner. According to which the details will be filled.
Check Page and Acknowledgement Screen
Users can cross-verify the data entered throughout the flows in the Check page. Click on the change button adjacent to the relevant data allows users to change/update the entered data. The user is redirected to the relevant page where data needs to be changed. Repeat the successive flows to submit the application.
For Registration of property, Create API is called. Following is the snippet of the Create API used:1create: "/property-services/property/_create"
If the API response is successful, then the Acknowledgement Screen is displayed, otherwise Failed Acknowledgement Screen is displayed.
All the screens have been developed using the new-UI structure followed previously in FSM and PGR.
The link for the Create Property Main Index is given below, it can be used to understand the starting point of the flow:
PT (Property Tax) Module has been segregated into a specified structure. All the screen configuration is inside PageComponent Folder, and the configuration for routing of the pages are mentioned in the config folder which is common for both Citizen as well as Employee. The snippet for folder structure and routing configuration is given below.
Pages Folder is where the high-level configuration for controlling the whole flow is mentioned, for citizens and employees. Citizen flows include Create, Edit, My Properties, My Application and Search Property. The search property flow carries the index (the main starting point of the whole flow).
After completing the flow the user can download the acknowledgement PDF form of the property created. Click here to find the config for the PDF generation.
Utils Folder basically contains all the methods which are being used throughout the PT module. In case any common method needs to be declared here, it can be imported into other files.
For creating an Application the Create API from Property Tax is being called using the React hooks, which has been declared under hooks/elements/PT as PTService.
Throughout the flows, data across a few pages are imported from MDMS. Following is the list of pages that are using MDMS data. These pages .js files can be found under page components.
1
PropertyTax
List of documents required for each category
PropertyTax
Documents
2
PropertyUsageType
Four category imported - (Commercial, industrial, institutional & others)
PropertyTax
UsageCategory
3
PropertyType
three major categories - (Independent, Flat & Part of the building & Vacant)
PropertyTax
PropertyType
4
SubUsageType
List of sub-usage category according to the property usage selected before
PropertyTax
UsageCategory
5
SubUsageTypeOfRentedArea
List of sub-usage category according to the property usage category selected before, same as sub-usage type
PropertyTax
UsageCategory
6
PTSelectAddress
List of Cities (Amritsar, Jalandhar and Nawanshahr) and List of localities according to the city selected
PropertyTax
tenants
7
OwnershipDetails
Four categories imported - (Institutional - private, Institutional - Government, Single Owner and multiple Owner)
PropertyTax
OwnerShipCategory
8
SpecialOwnerCategory
List of special category imported eg Freedomfighter, handicap etc
PropertyTax
OwnerType
9
PTGeolocation
Default value for location i.e Pratap Nagar Latitude and longitude
PropertyTax
MapConfig
10
RentalDetails
Rentaldetails information regarding tax percentage is taken from MDMS
PropertyTax
RentalDetails
Data React Hooks are used for calling MDMS, so that it could be shared throughout the modules.
Below is the little code snippet for the call used for MDMS.
Localization keys are added under the ‘rainmaker-pt’ locale module. In future, if any new labels are implemented in the Property Tax (Citizen) they should also be pushed in the locale DB under rainmaker-pt locale module. Below is an example of few locale labels.
S.No.
API
Action Id
Roles
1
/access/v1/actions/mdms/_get
870
CITIZEN
2
/egov-mdms-service/v1/_search
954
CITIZEN
3
/localization/messages/v1/_search
1531
CITIZEN
4
/property-services/property/_create
1895
CITIZEN
5
/property-services/property/_search
1897
CITIZEN
6
/property-services/property/_update
1896
CITIZEN
7
/property-services/assessment/_search
CITIZEN
8
/billing-service/bill/v2/_fetchbill
CITIZEN
Property applications
Registered properties
Application details
Property information
Edit or update property details
Make payment or search property details
Objective: To Provide employees with functionality to transfer Ownership of an active property.
When a property is in Active status and has no dues to pay then Employee is given an option on the property details page to mutate a property.
The doc required page is shown if the property is paid for otherwise it is taken to the payment details page. It shows the employee the list of documents required in order to proceed with the form.
After clicking on the “Transfer of Ownership” button on the required page, the employee is redirected to the Transfer of Ownership or Mutation form. Here the Transferor details are displayed and Employee can fill the transferee details form.
The file for mutation can be found on:
MDMS Data Used
Similar to that in employee Property create along with Mutation Documents. Which can be found in:-
APIs Called: 1property-services/property/_update
**When update API is called the documents are updated according to the snippet :-
Here data.originalData
is the property before the update, while data.documents
is the documents that were uploaded in the form, and mutationDocs
is the MDMS response for Mutation Docs.
Acknowledgement Screen
If the Property Mutation is successful. then the employee is directed to this screen that shows the Acknowledgement Id and the option to download a pdf of the acknowledgement containing property details.
Url
Roles
Action Id
property-services/property/_update
PT-CEMP
1896
Objective: To provide the employee with the functionality to search the created Applications.
The employee inbox screen shows all the created applications which are in the workflow and requires action from that particular employee.
The employee has the ability to search any application based on Application no, Property Id, or mobile number, or he can apply filters, based on the business service (create, edit, or update), application status, locality, and application assigned specifically to him.
By clicking on the /application no in the inbox user goes to the application details page. where he can take action on the application to push it forward or backwards in the workflow.
The file path for inbox can be found in:
digit-ui-internals/Inbox.js at main · egovernments/digit-ui-internals
API Used
The API used for searching the Inbox is
The above API is used to fetch the Inbox results based on filters and search criteria.
Inbox Screen offers customization for the fields in the inbox table. The fields inside the inbox table are exposed in the component registry service as in the file:
digit-ui-internals/inbox-table-config.js at main · egovernments/digit-ui-internals
It is exposed as PTInboxTableConfig
key in component registry service, and can be redefined to reset the columns.
the function returns an object of the following structure:-
the object.PT
contains 2 keys inboxCloumns
and searchColumns
, which are yet again functions.
These functions are provided with props
as an argument, which are props supplied to the component called DesktopInbox
as can be seen in the following file:-
inboxCloumns
and searchColumns
functions return an array of objects, each object represents a column.
The inboxCloumns
is used for setting columns in the Inbox, while searchColumns
is used for setting columns
every column has the following properties:-
Header
is the head that is used in thead
of the column (basically name of the column).
accessor
is .
separated string value that specifies the path within each row to be followed in order to display the value of the column. The structure of the row object is similar to row.original
explained below.
Cell
is function returning a valid JSX, in case some complex component is needed to be rendered. The function is supplied an object with row
property, each row containing property details , with row.original
being the actual data for the property row which is of the form. The searchData
contains search related result associated with the property, while workflowData
contains workflow related data associated with property
This page is where the Employee visits after clicking on desired Application No. in the inbox. The user can find a “take action” button at the bottom of the screen and can perform actions, based on the role the employee profile has and the state of the application in the workflow. He can also view the timeline in which he can see which employee made what update in the workflow.
The employee can see details like owner details, address etc, along with the documents attached at the time of creation, and while action performing by any other employee in the workflow. In the case of mutation Application, the employee can see transferer and transferee details.
While performing the action user can upload docs, comments for the next employee in workflow, or they can assign them to a specific employee in the action resultant workflow.
The code for the application details can be found in
APIs Called
The application details page calls the following APIs.
the 1st API is called to fetch the timeline, through which the Process Instance has gone through.
The 2nd API is called to fetch address, owner-details, and document fileStoreId
for all the documents associated with the property.
The 3rd API is called to get current performable actions based on the current state of the process Instance, which is then filtered through according to actions performable by the employee’s role.
The 4th API is called to fetch all the documents for the file store ids.
Url
Roles
Action Id
egov-workflow-v2/egov-wf/process/_search
All Roles
1730
/property-services/property/_search
All Roles
1897
/egov-workflow-v2/egov-wf/businessservice/_search
All Roles
1743
/filestore/v1/files/url
All Roles
1528
Objective: To provide employees with the functionality to search property (whether Active or in workflow). based on locality, owner mobile, or unique Property Id.
The employee also can see the dues for property within the search results and can choose to pay the dues if any, by clicking on collect tax.
Users can also view the current property Details page, to view Property Details, where employees can perform actions like assessment, Updation and Mutation, on an approved active Property.
The file for search can be found in:
APIs
The 1st API is used to fetch all the localities, based on the logged**-**in tenant.
The 2nd API is used to fetch the search Table data.
The 3rd API is used to fetch the bills for showing the due taxes present in search results.
Property Details Page
This page is visible to the employee when he clicks the property Id of property in search.
Here employees can see the latest approved Property Details. The employee also has the option to start property assessment, transfer ownership, and Edit Property details flow.
The employee also has the option to view history - this enables the users to view the owner details within the history of the property.
The code details can be found in:
APIs
Same as in the case of Application details, But here, The latest approved data is shown and any data which is not in the workflow is filtered out.
Assessment Popup
When an employee selects the action to assess property from the property details page of active property,
A popup is shown having a list of Financial Years:-
A financial Year is selected for the assessment of the property.
Technical Details
The Financial Years are fetched from the MDMS:
Assessment Screen
When selected and clicked on Assess Property the Property Assessment Screen is displayed.
This screen gives the assessment details of the selected financial year from the popup. After clicking on Assess Property, the button changes to “Proceed To Pay” which takes the employee to the common pay screen for employees.
Technical Details
The file for the assessment Details page can be found at the following link :
API Used
The 1st API is provided with financial Year and property Id as parameters to get the payment estimations for the Property.
The 2nd API is used to fetch Property Details.
The 3rd API is used to create an Assessment of the property. Which marks property with the estimated tax.
Url
Role
Action Id
/egov-location/location/v11/boundarys/_search
All Roles
1429
/property-services/property/_search
All Roles
1897
/billing-service/bill/v2/_fetchbill
All Roles
1862
/pt-calculator-v2/propertytax/v2/_estimate
PT-CEMP
1962
/property-services/property/_search
PT-CEMP
1897
/property-services/assessment/_create
PT-CEMP
1933
This section illustrates the steps for different employee user roles at the ULB level
DV is responsible for verifying the supporting documents uploaded by the property applicants or the counter employee on behalf of the applicants.
The DV can
Property applications are rejected if the supporting documents uploaded by the applicant fails to comply with the property regulatory requirements or the details provided in the form are incorrect.
To reject applications navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The DV verifies and forwards the property applications to the Field Inspector if the DV finds all information and documents provided by the applicant correct.
To verify and forward the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Verify and Forward button. Select the relevant Assignee Name from the list of available employees for subsequent processing.
Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Verify and Forward button.
The property application is assigned to the selected assignee for subsequent processing.
To edit applications navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Edit button. Change any details in the form as required.
The FI can
FI sends back the applications to the citizens if some vital information is missing in the application or there is a mistake in the information provided.
To send applications back to the citizen navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Send Back to Citizen button. Enter any Comments stating why the application is sent back.
Click on the Upload Files button to upload any files or images in context to the application. Click on the Send Back to Citizen button.
The system displays a success acknowledgement message stating that the application is sent back to the initiator.
The FI can send back the PT application to the DV if there is any mistake or lapses in the document verification process.
To send back applications to the DV navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Send Back button.
Select the Assignee Name who will be responsible for verifying the application. Enter any Comments stating why the application is sent back. Click on the Upload Files button to upload any files or images in context. Click on the Send Back button.
The application is assigned back to the selected assignee for verification of documents.
Property tax applications are rejected if the supporting documents uploaded by the applicant fails to comply with the license requirements or the details provided in the form are incorrect.
To reject applications navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The FI verifies and forwards the property applications to the Approver if the information and documents provided by the applicant are correct.
To verify and forward the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Verify and Forward button. Select the relevant Assignee Name from the list of available employees for subsequent processing.
Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Verify and Forward button.
The property application is assigned to the selected assignee for subsequent processing.
The Approver can
The Approver can send back the property applications to the FI or DV if there is any mistake or lapses in the document verification process.
To send back applications to the DV or FI navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Send Back button.
Select the Assignee Name who will be responsible for verifying the application. Enter any Comments stating why the application is sent back. Click on the Upload Files button to upload any files or images in context. Click on the Send Back button.
The application is assigned back to the selected assignee for verification of application.
Property applications are rejected if the supporting documents uploaded by the applicant fails to comply with the regulatory requirements or the details provided in the form are incorrect.
To reject applications navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The Approver signs off the PT application once the information and documents provided by the applicant are found correct.
To approve the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Take Action button available at the bottom of the page. Click on the Approve button.
Select the relevant Assignee Name from the list of available employees for subsequent processing. Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Approve button.
The property application is approved.
Learn how to add new property, assess or transfer property and pay property tax
Citizens represent individuals, communities, or business entities who are the system end-users. The PT module allows property owners to register their property details online. These details are then used for various property-related transactions.
The citizen can also approach the Counter Employee (CE) to register new property, assess property or pay property tax.
The Citizen or CE role can -
Citizens or CE can add new property details through the DIGIT web portal or the DIGIT mobile app.
To add a new property click on the Property Tax card available in the Citizen Services section of the Home page.
Click on the Add New Property button on the screen. This will open a new form page.
The system will display the Required Documents - Property Tax list. Note the list of documents valid for address, identity, registration, usage, special category, and occupancy proofs.
Click on the Print button to get a hard copy of the documents list for reference. Click on the Apply button to proceed with adding your property. The form sections are available on the top of the page.
Add Property Form Sections
The add property form page contains various sections that include
Property Address
Property Details
Owner Details
Document Info
Summary
Enter the following information in the Property Address section.
The City field displays the registered city by default. Click on the drop-down list to select a different city. Enter the House/Shop No., Building/Colony Name, Street Name, Locality/Mohalla, and the Pincode. Enter the Existing Property ID in case there is a legacy property ID available for the listed property.
Click on the Next button to move to the next section.
Enter the following details in the Property Details section
Select the applicable Property Usage Type and the Property Type from the drop-down list available.
Check Yes or No to indicate Whether rainwater harvesting structure provided on the property? Enter Vasika No. and Vasika Date if applicable. Enter Allotment Letter No. and Allotment Date if applicable.
Enter Firm/Business Name if the property is listed as commercial or institutional. Enter any information in the Remarks field. Check the box Do you have any inflammable material stored on your property? if it is true. Check the box adjacent to Height of property more than 36 feet? if it is true. Fill in the Unit details if the selected property usage type is Commercial, Institutional, Other Non-Residential, or Residential.
The Unit Usage Type by default accepts the Property Usage Type value. Select the applicable Sub Usage Type for the listed property in case of Commercial or Institutional properties. Select the most applicable option for the type of Occupancy. Enter the Built-up-area (sq ft) value of the property. Select Floor to identify the relevant floor of the property. Click on +Add One More Unit button to add more units.
Click on the Next button to proceed to enter the Owner Details.
Enter the following information in the Owner Details section. Select the relevant Type of Ownership. Enter the Owner’s Name.
Check the applicable Gender of the owner. Enter the owner’s Mobile No. and Guardian’s Name. Select Relationship of the owner with the guardian. Enter the applicable Special Category. Enter the owner’s Email Id and the Correspondence Address. Check the Same as property address box if the correspondence address is the same as the address of the listed property. The Correspondence Address field is auto-populated in that case.
Click on the Next button to move to the Documents section.
Upload the required documents in the Documents section of the application form. In the Select Document field, select the type of document you are uploading for Address Proof, Identity Proof, Registration Proof, Usage Proof, and Construction Proof.
Click on the Upload File button to upload the documents.
Click on the Next button to proceed to the next section.
Click on the Add Property button once the details are reviewed and corrected. The system displays the New Property Successfully Added acknowledgement message.
The Property ID is available along with this message.
Click on the Download button on top of the message box to download the application. Click on the Print button to print the application.
To search for a submitted application or track the status of submitted applications navigate to the Property Tax home page. There are two search options available. Users can search by property or application.
To Search by Property click on the Search Property tab. Enter the ULB. The system displays the registered City or ULB details by default. Enter any of the following search parameters or combinations to refine the search for property. Enter the Owner Mobile No. or the Unique Property ID allotted by the system. Enter the Existing Property ID if there is any legacy ID linked to the property.
Click on the Search button to view the results. Click on the Reset button to renew search with different parameters.
To Search by Application click on the Search Application tab.
Enter any of the following search parameters or combinations to refine the search for property. Enter the Application No. or the Owner Mobile No. or the Unique Property ID.
Click on the Search button to view the search results. Click on the Reset button to renew search with different parameters.
The search results show the filtered list of property entries along with the application Status.
An Active Status means the listed property is pending for further action. Inworkflow status means there is some action going on for the listed property and hence it is not accessible for any other action. Once the action is complete the status will change to Active.
Click on the Unique Property ID or Application No. hyperlink to access the property details.
Listed properties are assessed every financial year to calculate the property tax amount.
To assess property navigate to the Property Tax >> Assess & Search menu option on the sidebar. Alternatively, click on the Property Tax card on the Home page. Enter the required search parameter to refine your search for properties.
Click on the Search button to view the results. Click on the relevant Unique Property ID.
Scroll down the Property Information page to view the property details. Expand the Assessment History panel to view the previous assessment details.
Click on the Re-Assess button if you want to reassess the property. Expand the Payment History panel to view earlier payments made for the listed property.
Click on the Download Receipt button to get a soft copy of the listed payment. Expand the Application History panel to view the property application details.
Click on the View Details button to fetch application details. Click on the Assess Property button.
Select the relevant Financial Year.
The panel will display the Property Tax Amount details.
Click on the Add Rebate button to apply any rebates or discounts on the tax amount. This feature is not available for the citizens.
Enter any Additional Charges amount, if applicable. Select the appropriate Reason for Charges. Enter any Additional Rebate amount, if applicable. Select the appropriate Reason for Rebate.
Click on the Submit button to apply the rebate or charges to the tax amount. Click on the Calculation Details button to view the calculation logic applied for calculating the tax amount.
Click on the OK button to move back to the Assessment page.
Click on Assess Property once you complete reviewing all details. The system will display the assessment success acknowledgement message.
Click on the Proceed to Payment button to pay the property tax. Else click on the Home button to navigate back to the home page.
Applicants have to pay the property tax once the property is assessed for the specified financial year.
To make payment for property tax click on the Proceed to Payment button after the property assessment is complete. The Payment Collection Details panel displays the tax Fee Details.
Enter the payment details. The system allows you to pay by cash, cheque, or credit/debit card. Click on the Cash, Cheque, Credit/Debit Card tab depending on the preferred payment method.
Enter payment details as requested on the screen. Click on the Generate Receipt button to confirm the payment. The screen displays the success acknowledgement message along with the Payment Receipt No.
Once the payment is complete the Property Tax Receipt is issued. Click on the Download or Print button to download or print the tax Payment Receipt.
The PT module allows users to transfer the ownership of property.
To transfer the ownership of property search for the property by entering the Unique Property ID or any other search parameter. Click on the Unique Property ID to open the application. Scroll down the Property Information page. Click on the Transfer Ownership button available in the Owner Details panel.
The system will display the list of Required Documents - Transfer to Ownership.
Click on the Print button to print the list of documents. Click on the Transfer Ownership button to proceed with the mutation process. The Transfer of Ownership form page is displayed.
The application timeline shows three sections -
Transfer Details
Document Upload
Summary
The Transfer Details page includes three panels -
Transferor Details - This panel displays the current owner details.
Transferee Details - This panel requires the user to input the details of the individual to whom the property is to be transferred.
Enter the following details in the form -
Select applicable Ownership Type. Enter the Name, Gender, and Mobile No. of the transferee. Enter Guardian’s Name of the transferee and the Relationship with Guardian. Enter the Email address of the transferee. Select the relevant Special Applicant Category. Enter the Correspondence Address of the transferee.
Registration Details - This panel requires the user to input the registration details in context to the transfer of the property ownership.
Enter the following details in the form.
Select Reason for Property Transfer. Enter Property Market Value, the Registration Document No. and the Registration Document Issue Date. Enter the Registration Document Value. Enter any Remarks.
Click on the Next Step button to move to the Document Upload section.
Select Document you want to upload for Address Proof, Identity Proof, and Registration Proof. Click on the Upload File button to upload the copy of scanned documents.
Click on the Next Step button to move to the Summary section.
The Summary page will display the filled-in application details. Scroll down the page to review the information entered. Click on the Previous Step button to go back and make any changes in the form.
Click on the Submit button once all details are reviewed. The screen will display the application success message. Click on the Download button on top of the message box to download the application. Click on the Print button to print the application.
To make any changes in the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.
Click on the Edit Property button available at the bottom of the page. Change any details in the form as required. Click on the Update Property button once all changes are complete.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
__All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
On the Property details page, on the employee side, if the property is marked with Verify → forward → approved, the Update option will appear dynamically at the end of the page and will be static in nature.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
In the case of Institutional, the following data will be asked in the first screen, and the following screen will remain the same.
In the case of a single/Multiple Owner following screen will be displayed, rest flow will remain the same.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
For further enquiry on how to set columns, you can check __out the link:- Getting Started: Overview
If a particular workflow is completed then, the application is said to be completed and the status of property changes to ACTIVE
.
FI is responsible for inspecting and verifying the field details of the property in the application.
The Approver is responsible for the final approval of the PT application.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
The system will display the New Property form page.
The Application Summary page provides all the information filled in by the applicant. Click on the Edit icon to make any changes to the application.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.