> 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/employee-user-manual.md).

# Property Tax System Employee User Manual

This section illustrates the steps for different employee user roles at the ULB level

## **Counter Employee (CE)** <a href="#document-verifier-dv" id="document-verifier-dv"></a>

The citizen can approach the Counter Employee (CE) to register new properties, update property details, apply for title transfer or pay property tax.

The CE can&#x20;

* [Search Properties](#search-property)&#x20;
* [Collect property tax ](#collect-property-tax)
* [View property details](#view-property-details)
* [Payment history](#payment-history)
* [Register property](#register-property)
* [Edit property](#edit-property)
* [Assess property](#assess-property)
* [Transfer property ownership](#document-verifier-dv-2)
* [Edit application](#edit-application)
* [Reopen application ](#document-verifier-dv-3)

## **Document Verifier (DV)** <a href="#document-verifier-dv-3" id="document-verifier-dv-3"></a>

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**

* [Send back applications​](https://urban.digit.org/products/modules/property-tax/pt-user-manual/employee-user-manual#reject-applications)
* [Reject applications](https://docs.digit.org/v/v2.2/modules/user-manuals/pt-manual/pt-employee-manual#reject-applications)​
* ​[Verify and forward applications](https://docs.digit.org/v/v2.2/modules/user-manuals/pt-manual/pt-employee-manual#verify-and-forward)​​

## **Field Inspector (FI)** <a href="#field-inspector-fi" id="field-inspector-fi"></a>

FI is responsible for inspecting and verifying the field details of the property in the application.

**The FI can**

* ​[Send applications back to citizens](https://docs.digit.org/v/v2.2/modules/user-manuals/pt-manual/pt-employee-manual#send-back-to-citizen)​
* ​[Send back](https://docs.digit.org/v/v2.2/modules/user-manuals/pt-manual/pt-employee-manual#send-back)​
* ​[Reject applications](https://docs.digit.org/v/v2.2/modules/user-manuals/pt-manual/pt-employee-manual#reject-applications-1)​
* ​[Verify and forward applications](https://docs.digit.org/v/v2.2/modules/user-manuals/pt-manual/pt-employee-manual#verify-and-forward-1)​​

## **Approver** <a href="#approver" id="approver"></a>

The Approver is responsible for the final approval of the PT application.

**The Approver can**

* [​Send applications back to citizen](#send-back-1)
* [Send back applications​](#send-back-2)
* ​[Reject applications](https://docs.digit.org/v/v2.2/modules/user-manuals/pt-manual/pt-employee-manual#reject-applications-2)​
* ​[Approve applications](https://docs.digit.org/v/v2.2/modules/user-manuals/pt-manual/pt-employee-manual#approve-applications)​


---

# 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-user-manual/employee-user-manual.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.