> 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/project-and-bill-aggregation.md).

# Project & Bill Aggregation

## Overview

This is the initial screen where the user selects:

1. Project: The specific project they are managing.
2. Bill Aggregation Level: The boundary level at which the bill should be generated (Country, Province, or District).

Users cannot proceed without filling out these fields.

<figure><img src="https://content.gitbook.com/content/I0KFbSBTySIQ7TCOKnJF/blobs/Uu1k5AdQAv0gNE3FrWYh/image.png" alt=""><figcaption></figcaption></figure>

## **Interface Elements**

<table><thead><tr><th width="259">Element</th><th>Details</th></tr></thead><tbody><tr><td><strong>Project Selection</strong></td><td>Dropdown menu to select the project.</td></tr><tr><td><strong>Bill Aggregation Level</strong></td><td>Dropdown menu to select the aggregation level (Country, Province, District).</td></tr><tr><td><strong>Action Buttons</strong></td><td>- Back: Navigate to the previous screen.<br>- Next: Proceed to view registers mapped to the selected project.</td></tr></tbody></table>

## **User Actions Flow**

1. Use the dropdown menu to select the project.
2. Select one of the available aggregation levels (Country, Province, or District) from the dropdown.
3. Click the "Next" button to navigate to the register filtering screen.

***

## **Validations**

* Both fields are mandatory:
* If either the Project or Bill Aggregation Level is not selected, an error toast message is displayed if you try to proceed.


---

# 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/project-and-bill-aggregation.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.
