> 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/public-finance/v2.3/exemplar/mgramseva/features/billing-bulk-demand-generation.md).

# Billing - Bulk Demand Generation

All GPs have a monthly billing cycle for water charges.  The Scheduler automatically triggers on “X” date of every month to generate demand and raise bills for non metered connections.

* Metered connections do not fall under bulk demand generation

1. For the first month of go live, it is only the arrears and no demand is generated and hence no bill to collect payments
2. From the second month (X date of Month 2) onwards, demand is generated.
3. Once the demand is generated, a notification is triggered to all mGramSeva users.
   1. Details of Notification
      1. “Demand for water charges has been raised for \<GP>. New Bill Amount is Rs. Xyz. Overall pending amount is Rs.AbcD”
4. Each non metered household also get notifications
   1. SMS Notification with Bill PDF
      1. Dear “username”, A new water bill has been generated against \<connection ID>. Please download the bill using \<link>
   2. &#x20;SMS notification with a payment link
      1. Dear “username”, A new water bill has been generated against \<connection ID>. Please pay the bill online to avoid late payment charges\<link>
5. Revenue collector when on HH Details screen sees a new card (Updated card from month 2 onwards) with information related to demand and payment collection.
6. There is also a demand collection Tile/Card on the home screen.
   1. This is used in cases when the scheduler is not run (due to technical errors) and GP wants to run it manually.
7. If the manual demand generation is done in the middle of the billing cycle for which demand has already been generated this will do nothing.
   1. Only when the scheduler has not generated a demand for a billing cycle, manual demand generation helps.

For Demand Generation Logic refer to [Bulk Demand Generation for Non-Metered](/public-finance/v2.3/exemplar/mgramseva/features/bulk-demand-generation-for-non-metered.md)

In the Bulk Demand screen -

**Service Category:** Defaulted to Water Charges (Module)

**Service Type:** Defaulted to “Non-Metered”

**Billing Year:** Dropdown with the list of the financial years from the master.

**Billing Cycle:** Dropdown with the list of billing cycles for the selected financial year.

On Click of Generate Demand, demand for the given billing cycle gets generated based on the logic defined above.

![](/files/-MjDgZCOtBPRYqZn2-2h)

> [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)*​*](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*


---

# 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/public-finance/v2.3/exemplar/mgramseva/features/billing-bulk-demand-generation.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.