> 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/revenue-collection-offline.md). # Revenue Collection - Offline ![](/files/-MjDb4t7S9aPBwSO6Jvb) After the demand is generated for Metered and non-metered connections Revenue collectors come to this screen to collect payments. 1. Users can see the consumer billing information on the screen 2. Clicking on View Details expands the card and shows more details. Clicking on the Hide Details collapses the card to show only connection ID, Consumer Name & Total Due Amount. 3. Payment amount - can either pay 1. The full amount, or 2. Custom amount - Users can enter the custom amount in the input field - this cannot be zero or greater than the total due amount. 4. Payment methods 1. Cash - select cash and proceed to payment takes the user to the successful collection screen 2. Online - The online payment option displays a Q/R code on the user screen that can be scanned by another phone to pay the due. 3. Post payment via any mode - payment success screen is shown 4. Receipt ID format - RB-dd/mm/yyyy-yy/running\_sequence\_number 5. User Actions 1. Download receipt - download PDF version of receipt with receipt ID as the name of PDF while downloading 2. Share receipt via WhatsApp - opens the Phone OS sharing options 3. back to home - takes the user back to the home screen 6. SMS to HH 1. As soon as the amount is paid and the Revenue collector reaches the Payment success screen SMS is sent to HH. 1. SMS 1 - Dear ‘Username’, Paid Rs.X for water charges for bill period \. Download receipt \ 2. SMS 2 - Dear ‘Username’, Please leave a review on water supply at \ at \ 3. HH is able to leave a review for water charges. Refer [Feedback - Post Payments](/public-finance/v2.3/exemplar/mgramseva/features/feedback-post-payment.md). Details on the card | **Detail** | **Comments** | | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | Connection ID | New Connection ID will be displayed here | | | Consumer Name | Consumer Name (Should take updated consumer name) | | | Bill ID number | ID of the Bill | | | Bill period |

for non-metered connections

  1. This is the latest billing cycle for which demand is generated

For metered connections

  1. This is the new bill generated from the meter reading between the 2 most recent billing dates
|

Format

  1. Month \ Financial Year
  2. Previous meter reading date - New meter reading date
| | Water charges | Amount for the latest billing cycle | For metered, calculate charges as per rate master between the latest 2 billing dates | | Arrears | All old arrears accumulated for HH | Expansion should breakup of arrears by individual billing cycles/bill generation dates | | Total Due amount | Net amount consumer has to pay | | ![](/files/-MjDbMsgMkbLl_XkqKJC) ![](/files/-MjDbQygLo3C_mnBcvwB) 1. When online is selected for payment method, the “Collect Payment” option is disabled. Since HH scans the QR, the Revenue collector does not have control over the online process. 2. A partial amount can’t be greater than the full amount. > [![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/revenue-collection-offline.md?ask=&goal= ``` `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.