> 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/mcollect-mcs/mcollect-service-configuration/current-bill-cancellation-ui-flow/cancel-bill-ui-flow.md).

# Cancel Bill UI Flow

## **Overview**

To provide users with the option to select cancel reasons and the options to cancel the bill.

## Workflow Details

![](/files/-MgiGgcr0X7-pWdAbFw6)

## **Implementation Details**

The screen development files are available in the egov-abg-dev folder within the below-mentioned link.

[<img src="https://github.com/fluidicon.png" alt="" data-size="line">frontend/cancelBill.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/cancelBill.js)

The reasons for bill cancellation options are fetched from the MDMS service.

[<img src="https://github.com/fluidicon.png" alt="" data-size="line">egov-mdms-data/CancelCurrentBillReasons.json at QA · egovernments/egov-mdms-data](https://github.com/egovernments/egov-mdms-data/blob/QA/data/pb/common-masters/CancelCurrentBillReasons.json)

**PREVIOUS STEP:** Clicking on the Previous Step option redirects users to the bill details screen.

![](/files/-MgiGgcupFIaKQHoGfBA)

## **Cancel Bill**

<div align="left"><img src="/files/-MgiGgcxmxhU3wcbwJHq" alt=""></div>

Clicking on the cancel bill option triggers the cancel bill API (`billing-service/bill/v2/_cancelbill` ). Once the API call is successful it routes to the acknowledgement screen.

The Next Step button file is available in the below-mentioned file path.

[<img src="https://github.com/fluidicon.png" alt="" data-size="line">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)

![](/files/m7r1kZTfKxElZMVxW59l)

**Acknowledgement Screen**

file path: [<img src="https://github.com/fluidicon.png" alt="" data-size="line">frontend/acknowledgement.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/acknowledgement.js)

![](/files/-MgiGgd0wiwzPvSgoqDF)

## **Localisation**

For localisation, the “rainmaker-ws” and “rainmaker-abg” modules are re-used. In case they are any new keys, these are added under “rainmaker-abg”.

## **API Call Role Action Mapping**

| API                                   | Action ID | Roles                             |
| ------------------------------------- | --------- | --------------------------------- |
| `billing-service/bill/v2/_cancelbill` | `1936`    | `SUPERUSER`, `SW_CEMP`, `WS_CEMP` |
| `egov-mdms-service/v1/_search`        | `954`     |                                   |


---

# 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/mcollect-mcs/mcollect-service-configuration/current-bill-cancellation-ui-flow/cancel-bill-ui-flow.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.