> 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/access/local-governance-stack/property-tax/pt-master-data-templates/mutation-fee.md).

# Mutation Fee

## Introduction <a href="#introduction" id="introduction"></a>

The request to change in owners associated with a property in municipal record is known as mutation or transfer of title. To process this request and make the necessary changes in the property records ULBs charge for a fee which is calculated based on the fee defined based on a few parameters.

## Data Table <a href="#data-table" id="data-table"></a>

<table><thead><tr><th width="103.66666666666666">Sr. No.</th><th width="247">Property Usage Code*</th><th>Flat Fee Amount*</th></tr></thead><tbody><tr><td>1</td><td>RESD</td><td>1000</td></tr><tr><td>2</td><td>NONRESD</td><td>5000</td></tr></tbody></table>

## Procedure <a href="#procedure" id="procedure"></a>

### Data Definition <a href="#data-definition" id="data-definition"></a>

<table><thead><tr><th width="96">Sr. No.</th><th>Column Name</th><th>Data Type</th><th>Data Size</th><th>Is Mandatory?</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>Property Usage Code</td><td>Alphanumeric</td><td>64</td><td>Yes</td><td>Property usage code - the fee depends upon the type of property usage</td></tr><tr><td>2</td><td>Flat Fee Amount</td><td>Decimal</td><td>(5,2)</td><td>Yes</td><td>Mutation fee flat amount</td></tr></tbody></table>

### Fill Data - Steps <a href="#steps-to-fill-data" id="steps-to-fill-data"></a>

1. Download the data template attached to this page.
2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
4. Identify usage-wise mutation fee amount and fill it into the given template.
5. Go through the checklist to verify the data. Make sure that each point mentioned in the checklist is covered.

## Checklist <a href="#checklist" id="checklist"></a>

### Common Checklist <a href="#common-checklist" id="common-checklist"></a>

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

<table><thead><tr><th width="109.66666666666666">Sr. No.</th><th width="363">Checklist Parameter</th><th>Example</th></tr></thead><tbody><tr><td>1</td><td>Make sure that each and every point in this reference list has been taken care of</td><td>​<a href="https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist">Checklist</a>​</td></tr></tbody></table>

### Entity Specific Checklist <a href="#entity-specific-checklist" id="entity-specific-checklist"></a>

Not Applicable

## Attachments <a href="#attachments" id="attachments"></a>

{% file src="/files/yyIMkcJBi2kcbgG3GoCH" %}


---

# 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/access/local-governance-stack/property-tax/pt-master-data-templates/mutation-fee.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.