> 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/works/reference-implementations/muktasoft-v2.2/deployment/sms-adapter-services/expense-notification-service.md).

# Expense Notification Service

* Package: org.egov.works.service
* Source File: ExpenseNotificationService.java

## Overview

The ExpenseNotificationService class is responsible for processing notifications related to expenses within the eGov Works module. It handles the generation and sending of notifications for both purchase bills and supervision bills.

## Attributes

1. producer: Kafka producer for sending notifications.
2. config: Configuration settings for notification services.
3. hrmsUtils: Utility class for interacting with the HRMS (Human Resource Management System).
4. projectServiceUtil: Utility class for project-related operations.
5. locationServiceUtil: Utility class for location-related operations.
6. mapper: Object mapper for JSON serialization/deserialization.
7. repository: Repository for service requests.
8. notificationUtil: Utility class for notification-related operations.
9. localizationUtil: Utility class for localization operations.

## Methods

* process(final String record, @Header(KafkaHeaders.RECEIVED\_TOPIC) String topic): Processes the incoming Kafka message, determining whether it pertains to a purchase bill or a supervision bill, and sends the appropriate notification accordingly.
* sendNotificationForPurchaseBill(BillRequest billRequest): Sends notifications for purchase bills, handling approval and rejection actions.
* sendNotificationForSupervisionBill(BillRequest billRequest): Sends notifications for supervision bills.
* getMessage(RequestInfo requestInfo, String tenantId, String msgCode, Map\<String,Object> additionalFields): Retrieves the localized message for a given code and locale, optionally adding additional fields if required.
* buildMessageReplaceVariables(String message, String billNumber, String amount): Replaces variables in a message template with actual values.
* setAdditionalFields(RequestInfo requestInfo,String tenantId, String localizationCode, Map\<String,Object> additionalFields): Sets additional fields for the notification if required.
* checkAdditionalFieldAndPushONSmsTopic(String customizedMessage, Map\<String, Object> additionalFields, String mobileNumber): Checks if additional fields are present and sends the SMS request accordingly.

## Usage

Instantiate and configure the ExpenseNotificationService class within the application context to handle notifications related to expenses. Ensure that dependencies such as Kafka producer, configuration settings, and utility classes are properly injected.


---

# 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/works/reference-implementations/muktasoft-v2.2/deployment/sms-adapter-services/expense-notification-service.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.