> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/v2.8/products/modules/property-tax.md).

# Property Tax (PT)

Online automated management of property tax revenues and collections

## About Property Tax

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

## Key Features

* Manage property database
* Property registration feature and title transfer 
* Various payment options available to citizens to make payments from their convenient places
* Auto-generated defaulters’ list and real-time online tracking

## Section Overview

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

* [Functional Specifications](/local-governance/v2.8/products/modules/property-tax/pt-module-functional-specifications.md)
* [PT Roadmap](broken://pages/-MgiGQwpX4EVuKnSmdp9)
* [PT User Manual](/local-governance/v2.8/products/modules/property-tax/pt-user-manual.md)
* [Product Brochure](/local-governance/v2.8/products/modules/property-tax/pt-brochure.md)
* [PT Workflows](broken://pages/-MgiGQwrHxwfj3XCtCQT)
* [Master Data Configuration Template](/local-governance/v2.8/products/modules/property-tax/pt-master-data-templates.md)
* PT Service Configuration
* [Implementation Handbook](/local-governance/v2.8/products/modules/property-tax/pt-implementation-guide.md)
* Demo Script

{% hint style="warning" %}
**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
  {% endhint %}

## Contact Us

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

{% hint style="danger" %}
\#147/J, 1st floor, 10th Cross,\
12th Main, 3rd Block,\
Koramangala, Bangalore 560034

* [Find us on map](https://goo.gl/maps/pYCFMhHWW7r)
* +91 80 4125 5708
* <contact@digit.org>
  {% endhint %}

> [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation* ](https://egov.org.in/)*is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/local-governance/v2.8/products/modules/property-tax.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.