> 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-user-manual/citizen-user-manual/amalgamate-property.md).

# Amalgamate Property

The amalgamation process is a service requiring the owner(s) to apply. A single application should include the details of all the properties and the necessary supporting documents. No application or processing fee is required for the amalgamation of properties.

{% hint style="info" %}
Conditions for property amalgamation -

* There should not be any dues on the property.&#x20;
* The property should be active and **there should not be any application in flow for an integrated module associated with the property.**&#x20;
* The property should belong to the same locality as the retaining property.
  {% endhint %}

| <img src="/files/hezLR1nluGkBsLc5Vaz5" alt="" data-size="original">                              | <img src="/files/IK8eLs8Rtv1kesPwRgRy" alt="" data-size="original">                                                                               |
| ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Step 1:** Select the **Amalgamate Property** option.                                           | **Step 2:** Select a property to merge.                                                                                                           |
| <img src="/files/SYPMJg8vzbTKHw7SmaQw" alt="" data-size="original">                              | <img src="/files/qsa6dcivCa4dlsxFUhSH" alt="" data-size="original">                                                                               |
| **Step 3:** Check the property registration documents list.                                      | **Step 4:** The retaining property address and ownership details are displayed on the application.                                                |
| <img src="/files/IKut2v8qa9Fw2Jfd2Pag" alt="" data-size="original">                              | <img src="/files/f0zy4YLoHUrGI4snVHIE" alt="" data-size="original">                                                                               |
|                                                                                                  | **Step 5:** Select the property to be merged.                                                                                                     |
| <p><img src="/files/OtjeKmBmfAFhymeijUxe" alt="" data-size="original"></p><p></p>                | <img src="/files/qTZad8B3Lo1h2UWLAZ2Y" alt="" data-size="original">                                                                               |
| **Step 6:** Review the two selected property details                                             | **Step 7:** Upload the required documents to process the merge application.                                                                       |
| <img src="/files/OsDeXwiY0EZXlcGHlxv5" alt="" data-size="original">                              | <img src="/files/zdMd1mbDXsuCo5WEgcXC" alt="" data-size="original">                                                                               |
| **Step 8:** Review the application details before clicking on the **Submit Application** button. | **Step 9:** The application is submitted successfully. Note the acknowledgement reference number. You can also **Download Acknowledgement Form**. |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/local-governance/access/local-governance-stack/property-tax/pt-user-manual/citizen-user-manual/amalgamate-property.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
