Introduction
Unit rates are also an important part of used in calculation property tax . The property tax for a property are counted on the are that the property is covering. These unit rates could differ from ULB to ULB, Ward to Ward, Mohalla to Mohalla and then can be based on different parameters such as Road Type, Property Construction Type etcfor Unit Area Value System . This rate is fixed (e.g. per square foot per month) based on the expected returns of the property as per its location, land price, construction, and usage.
Data Table
Sr. No. | Boundary Code* | Boundary Name* | Parameter 1Boundary Type* | Construction Type* | Parameter 2Road Type* | Unit Rate* |
1 | M001 | Haldwani Mandir | Ward | PUCCA | < 12 m | 1.50 |
2 | M001 | Haldwani Mandir | Ward | SEMIPUCCA | >= 12 m and <= 24 m | 1.75 |
3 | M001 | Haldwani Mandir | Ward | KUCCHA | > 24 m | 2.00 |
4 | M002 | Kali Mata Mandir Road | Ward | SEMIPUCCA | < 12 m | 3.00 |
5 | M002 | Kali Mata Mandir Road | Ward | SEMIPUCCA | >= 12 m and <= 24 m | 10.00 |
6 | M002 | Kali Mata Mandir Road | Ward | SEMIPUCCA | > 24 m | 20.00 |
Note: The data provided here is sample data.
Procedure
Data Definition
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
1 | Boundary Code | Alphanumeric | 64 | Yes | The code of the boundary that is being used, depending upon the client's requirement it could be Mohalla or Ward but has to be from the data collected here. |
2 | Boundary Name (In English) | Text | 256 | Yes | The name/description of the boundary that is being used for the classification. The names have to be from the data collected here. |
3 | Boundary Type | Text | 256 | Yes | Name of boundary type for which rates are defined. |
3Parameter | 1Construction Type | Alphanumeric | 64 | Yes | This has to be the parameter 1 the construction type code on the basis of which the unit rates are being defined. |
4Parameter | 2Road Type | Alphanumeric | 64 | NoYes | This is the second parameter(if available) to be road type code on the basis of which the unit rates are being defined |
5 | Unit rates | Decimal | (5,2) | Yes | The unit rate |
Steps to fill the data
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Figure out on what boundary types are the property tax unit rates being defined and start filling that with its code and its name in English in the boundary code and boundary code name column.
In case there are more parameters on which the unit rates are being classified such as road type, construction type are being classified, start making 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.
Checklist
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
Common Checklist
This checklist covers all the activities which are common across the entities.
Sr. No. | Checklist Parameter | Example |
|---|---|---|
1 | Make sure that each and every point in this reference list has been taken care of. |
Entity Specific Checklist
Not ApplicableTwo separate files to be prepared for built-up and vacant land unit rates.