# Expense ### Overview The expense module implements the functionality of bills and payments. A bill or a group of bills can be aggregated together as payments. Payment advice can be submitted through integration with IFMS (Integrated Financial Management Systems) or any other third-party payment provider. The expense module always works in combination with a calculator service. The calculator service is implementation-specific and provides business logic to compute bills. The calculator calls into the expense service to create bills. In general, the expense create/update APIs are not called by any other module other than the calculator. [Click here ](/works/reference-implementations/muktasoft-v2.2/deployment/muktasoft-services/expense-calculator.md)to browse for more information on the sample calculator provided with the Works platform. ### Pre-requisites * DIGIT backbone services * Persister * Indexer * IDGen * MDMS * Workflow * Notification ### Functionalities * Create/update/search functionality for bills * Ability to create different bill types according to configuration. * The workflow is integrated and needs to be configured for usage. * Works with an expense calculator that contains the business logic to compute bills. **Code** [Expense Module](https://github.com/egovernments/DIGIT-Works/tree/master/backend/expense) ### Deployment Details [Helm Chart](https://github.com/egovernments/DIGIT-DevOps/tree/digit-works/deploy-as-code/helm/charts/digit-works/backend/expense) ### Configuration Details ### Integration Details [API spec](/works/platform/architecture/low-level-design/services/expense.md#api-specifications) --- # Agent Instructions: 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: ``` GET https://docs.digit.org/works/setup/configure-works/service-configuration/expense.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.