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

# Campaign Supervisor

Generate a bill

## Overview

Generates the payment bill from approved attendance registers. The Campaign Supervisor is the same person who manages the campaign; they carry the Bill Generator role in the payments workflow.

The Campaign Supervisor acts as the Bill Generator (BG). They create a bill by selecting approved attendance registers for a given LGA and billing period. The bill is then passed to the Payment Editor. The Campaign Supervisor logs in to the Attendance module to generate bills, not the Payments portal.

## Steps

{% stepper %}
{% step %}

### Navigate to Generate Bill

From HCM, go to Attendance Registers, then Generate Bill (the Bill Inbox section). This shows all registers grouped by billing period.
{% endstep %}

{% step %}

### Select the LGA and billing period

In the left panel, select the LGA and the Billing Period from the dropdowns. The Approved Registers tab shows registers ready for billing. The Pending Registers tab shows registers not yet approved.
{% endstep %}

{% step %}

### Check the approved registers

You will see each register listed with its Attendance ID, Boundary, the Proximity Supervisor who approved it, and the number of attendees. Review these before generating.
{% endstep %}

{% step %}

### Click Apply to generate the bill

Click the Apply button. A confirmation toast appears, letting you know the bill is generating and will appear under My Bills.
{% endstep %}

{% step %}

### Check My Bills

Click My Bills in the left navigation. The new bill appears with a Bill ID, Bill Type (Intermediate), Bill Date, Billing Period, No. of Registers, No. of Workers, Boundary, and Project Name. Status shows report generation in progress while processing.
{% 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 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/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/attendance-and-payments-user-manual/campaign-supervisor.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.
