> 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/mcollect-mcs/mcollect-user-manual/mcs-employee-user-manual.md).
# MCS Employee User Manual
This section illustrates the steps for different employee user roles at the ULB level
## **CE And FE**
The counter employees or field employees collect and process the miscellaneous payments on behalf of the citizens.
**The CE or FE role can -**
* [Generate challan](#collect-payment)
* [Make payment](#make-payment)
* [Search challan](#search-challan)
### **Generate Challan**
CE can process and collect payments for miscellaneous services through the DIGIT web portal or the DIGIT mobile app. To process a new payment, click the **mCollect** card on the employee home screen. Click on **Generate New Challan** button.
On the **New Challan** page, enter the **Consumer Details** and **Service Details**.
Click on **Submit** button at the bottom of the page. The success message screen pops with the **Challan No.** Click on the **Print Challan** option to print the challan.
Click on **Proceed to Payment** button to make the payment.
## Make Payment
The **Generate Receipt** page displays the payment information details. Enter the **Payer Details**. Select the **Payment Mode**.
Enter the **Gen/G8 Receipt Details**, in case the receipt is generated manually. Click on the **Collect Payment** button at the bottom of the screen to register payment details.
The success message is displayed. Click on **Print Receipt** to print the receipt.
### Search Challan
Click on **Search Challan** option on the employee home page.
Select the required filters and click on the **Search** button. The results will be displayed on the page.
---
# 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/mcollect-mcs/mcollect-user-manual/mcs-employee-user-manual.md?ask=&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.
.png?alt=media&token=6efe61ef-7dd8-41c2-b30d-ee9697d3cc0f)
.png?alt=media&token=abfc64b2-9d53-453f-b514-fef3a10b90f2)
.png?alt=media&token=26219754-47cd-4630-847e-6c417352e46d)
.png?alt=media&token=157d3b9b-869b-449e-afe4-2a8b100d2b42)
.png?alt=media&token=01b6c4af-66b3-4885-910e-564a50443927)
.png?alt=media&token=cee1c1ea-2e83-4def-914d-4d26876efe84)