> 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/design/architecture/low-level-design/services/health-services/generate-bill.md).

# Generate Bill

## Overview

The **Campaign Supervisor Flow** is designed to streamline the management of attendance registers and bill generation processes for supervisors overseeing specific projects and boundaries. This flow ensures efficient selection, filtering, and approval of registers and simplifies the generation and tracking of bills. It focuses on clear workflows, actionable feedback, and validation mechanisms to enhance usability and accuracy.

## **Features**

* **Project and Bill Aggregation Selection**: Supervisors select a project and boundary aggregation level to narrow down the scope for attendance registers and billing.
* **Registers Filtering and Bill Generation**: Enables supervisors to filter registers based on boundaries, view attendance data, and generate bills only when all registers are approved.
* **Bill Management (My Bills)**: Provides a centralised view of all generated bills, with tools for searching, filtering, and downloading them in preferred formats.

<table><thead><tr><th width="223.68359375">Role</th><th>Responsibility</th></tr></thead><tbody><tr><td>CAMPAIGN_SUPERVISOR</td><td>aggregate the bill generation, based on district, province or country and download it for further processing</td></tr></tbody></table>

This structured approach empowers supervisors to manage attendance registers and related billing tasks with ease while adhering to necessary validations and role-based permissions.

## **Sequence Diagram**

<figure><img src="https://content.gitbook.com/content/I0KFbSBTySIQ7TCOKnJF/blobs/4lhjaVcXDKtbLfJMPdZx/bills.png" alt=""><figcaption></figcaption></figure>


---

# 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/design/architecture/low-level-design/services/health-services/generate-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.
