> 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/expenditure-add-expense.md).

# Expenditure - Add Expense

The expense entry for the O\&M on regular basis is captured on this screen.

![](/files/-MjDab1lX_swKzt_85dL)

On selecting the option “Add Expense Record” from the list of tile/cards on the home page, the user is navigated to the expense entry screen. The screen displays the following fields.

| **Field Name**   | **Type**                         | **Mandatory Y/N** | **Description**                                                                                                                                     |
| ---------------- | -------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Vendor Name      | Text (With Suggestions dropdown) | Y                 | Name of the Vendor. The suggestion list is shown as the user entry is done for every character. The new Name will also create a Vendor Register.    |
| Type of Expense  | Drop Down                        | Y                 | Type of expense list From Master                                                                                                                    |
| Amount           | Numeric                          | Y                 | Expense amount for the Bill                                                                                                                         |
| Bill Date        | Date                             | Y                 | Date on which the bill is to be recorded in the registers. Validation - Before Current Date and after party Bill Date.                              |
| Party Bill Date  | Date                             | N                 | Date on which the Party/vendor bill was issued. Validation - Before the Bill Date.                                                                  |
| Bill Paid        | Radio Buttons                    | N                 | With option Yes/No. To update status if it is paid. If yes, “Paid Date” is captured.                                                                |
| Paid Date        | Date                             | N                 | Date on which the bill is paid. Displayed if the Bill paid option is selected as “Yes”. Validation - After Bill date and less than current Date.    |
| Attach Documents | Doc Attachments                  | N                 | Option to upload documents (Max of 5). Supported files - PDF, JPEG, PNG. Should show required validation for other types of files.                  |
| Submit           | Button                           | -                 | On click, the consumer master gets created with the detail entered above. The new connection id also should get generated as per the configuration. |

On Submitting, the Expense entry gets created with a Bill number assigned. The Bill number generated would be based on logic defined as - “EB-\<FY>-<4 digit running seq No>”

On Successful creation of expense entry, an acknowledgement screen is shown “Expense Entry successful” along with the Bill Number.&#x20;

![](/files/-MjDadZWTW7nlnwJzfq9)

| **Expenditure Entry** | **Expenditure entry Successful** |   |
| --------------------- | -------------------------------- | - |
|                       |                                  |   |

> [![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/expenditure-add-expense.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.