> 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/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/data-protection-and-privacy/display-bank-account-details-on-wage-bill.md).

# Display Bank Account Details On Wage Bill

## Scope

Data Privacy: Bank account details will be removed from the wage bill.

## Details

1. The wage bill is generated automatically by the system on approval of the muster roll.
2. As of now in the view wage bill details page, bank account details are displayed.
3. Bank account details are to be removed from the View Wage Bill page.
4. Muster Roll ID should be a **hyperlink**, on clicking it, opens into the View Muster Roll page.
5. The wage seeker ID should be a **hyperlink**, clicking it, opens the view wage seeker’s details.
6. Based on the role user can view the wage seeker’s details masked/unmasked.

## User Interface

{% embed url="<https://www.figma.com/design/M2P3O9WlKtxuLCjQKxLLDg/DIGIT-Works>" %}

## Acceptance Criteria

1. Sensitive information account - IFSC to be removed from the view bill.
2. Muster roll ID and Wage seeker ID will be available as hyperlinks.
3. Wage seekers' details are displayed masked/unmasked based on the role of the logged-in user.


---

# 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/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/data-protection-and-privacy/display-bank-account-details-on-wage-bill.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.