> 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/health/access/public-health-product-suite/health-campaign-management-hcm/attendance-and-payments-user-manual/payment-editor.md).

# Payment Editor

Verify worker details

## Overview

Verifies and corrects the payment details for each worker in the bill (payee name, bank account, bank code, and beneficiary code), then individually approves each worker's record.

The Payment Editor is the first role in the Payments portal. They receive the generated bill, check that every worker's payee details are correct, fix any errors, and approve each record. Only fully verified workers can proceed to payment.

## Steps

{% stepper %}
{% step %}

### Open the Payments portal 

Navigate to Manage Bills. Log in to the Payments URL. Click Payments in the left menu. You will see three options: Inbox, My Bills, and Manage Bills. Click Manage Bills.
{% endstep %}

{% step %}

### Find the Bill Verification in Progress tab

The Manage Bills screen has tabs: Not Verified, Verification in Progress, Partially Verified, Verified, and Sent for Review. Open the Verification in Progress tab to find bills that need your attention.
{% endstep %}

{% step %}

### Open the bill

Click the Bill ID link to open the bill. You will see a summary (Bill Amount, No. of Workers, No. of Registers) and a worker list showing Worker ID, Worker Name, Mobile Number, Payee Name, Payment Provider, Bank Account, Bank Code, Beneficiary Code, Role, Wage Rate, Allowances, and No. of Days.
{% endstep %}

{% step %}

### Edit a worker's payment details

If a worker's payee details are incorrect, click on the Worker ID to open the Edit Worker's Details modal. Update Payee Name, Payment Provider, Bank Account, Bank Code, and/or Beneficiary Code. Click Approve in the modal to save and verify the worker.

<figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FnZkOuBIS41VqBSoXX9Fl%2Fimage.png?alt=media&amp;token=651acbb1-85f7-4f2c-bce6-932744b53ee5" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="170.7421875"></th><th></th></tr></thead><tbody><tr><td>Payee Name</td><td>The name registered with the bank for this worker's account. Must match the bank's records.</td></tr><tr><td>Payment Provider</td><td>Set to BANK for bank transfers in this release.</td></tr><tr><td>Bank Account</td><td>The worker's bank account number.</td></tr><tr><td>Bank Code</td><td>The bank's routing or sort code.</td></tr><tr><td>Beneficiary Code</td><td>An alphanumeric code up to 35 characters. Required by the payment provider for routing. Must not contain special characters.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Handle verification failures

If a worker has a Verification Failed status, the system was unable to validate their bank details with the payment provider. Open their modal, correct the details, and re-verify. Check the Beneficiary Code field carefully; it must be alphanumeric and up to 35 characters.
{% endstep %}

{% step %}

### Verify all workers

Browse through all workers. Continue verifying workers until the bill moves to the Verified tab. You can also use the Edit in Excel option to download the bill as a spreadsheet, edit multiple workers at once, and upload it back.
{% endstep %}
{% endstepper %}


---

# 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/health/access/public-health-product-suite/health-campaign-management-hcm/attendance-and-payments-user-manual/payment-editor.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.