> 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/platform/configure-digit/configuring-digit-services/mcs-service-configuration/current-bill-cancellation-ui-flow/bill-details-ui-flow.md).
# Bill Details UI Flow
## **Overview**
To provide users with the bill details and the options to cancel the bill.
## Workflow Details
.png?alt=media)
## **Implementation Details**
The screen development file is available in the egov-abg-dev folder within the below link:
[
frontend/viewBill.js at master · egovernments/frontend](https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-abg-dev/src/ui-config/screens/specs/bills/viewBill.js)
The details of the Bill are fetched by calling BillingService fetchBill API and the [Consumer.No](http://consumer.no/) is used in the query param.
FetchBill API returns the Bill Object which contains all the details about the bill including Billing Period, Due Amount, Due Date, and information about the Tax, Cess, Rebate, and Penalty applied to this bill.
NextStep - On clicking on the next step, the screen navigates to the cancel bill screen. The user must select the option that best states the reason for bill cancellation. More details for the cancel bill screen is available on this page -[ Cancel Bill](/local-governance/v2.8/platform/configure-digit/configuring-digit-services/mcs-service-configuration/current-bill-cancellation-ui-flow/cancel-bill-ui-flow.md)
The Next Step button file is available in the file path below: [frontend/viewBillFooter.js at master · egovernments/frontend](https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-abg-dev/src/ui-config/screens/specs/bills/viewBillResource/viewBillFooter.js)
.png?alt=media)
## **API Call Role Action Mapping**
| API | Action ID | Roles |
| ---------------------------------------- | --------- | --------------------- |
| `/ws-calculator/meterConnection/_search` | `1936` | `EMPLOYEE` |
| `/billing-service/bill/v2/_fetchbill` | `1862` | `EMPLOYEE` |
| `/ws-services/wc/_search` | `1900` | `SW_CEMP , WS_CEMP` |
| `/sw-services/swc/_search` | `1940` | `SW_CEMP , WS_CEMP` |
| `/property-services/property/_search` | `1897` | `SW_CEMP` , `WS_CEMP` |
---
# 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/platform/configure-digit/configuring-digit-services/mcs-service-configuration/current-bill-cancellation-ui-flow/bill-details-ui-flow.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.