> 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/tabular-dashboard-expense.md).

# Tabular Dashboard - Expense

Clicking on the Dashboard on the home screen takes the user directly to the revenue dashboard of the current month. From here, the user can switch to the expenditure tab to get a view of expenses. This provides a tabular view of all expenses incurred in that month.

![](https://2287351256-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Mfb8ehcimjt6ER7QOME%2F-MjDUbePQJ7qAqKML_Gs%2F-MjDUs4oKwXacNx2qnnj%2Fimage.png?alt=media\&token=aa872ecf-92e9-48f2-a6b1-2ec0f4e2155c)

Following are the data points/actions needed on the screen

| [**S.No**](http://S.No) | **Item**             | **Explanation**                                                                                                                                                                                                                                                                                                                                                                                         |
| ----------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1                       | Search Expense Bills | <ul><li>Search by Bill ID or Vendor</li><li>The Vendor Name should be a partial match. As the user starts typing a consumer name, respective vendors get filtered in the table displayed below</li><li>Bill ID should be a partial match. As the user starts typing a New Bill ID, respective Bills should get filtered in the table displayed below</li></ul>                                          |
| 1.1                     | Filters              | <ul><li>Default is “All” View. Switching to Paid or Pending filters the table accordingly. Alongside the filter, how many Bills fall into that filter is shown in numbers</li><li>The table also has sort options for each column (ascending, descending)</li></ul>                                                                                                                                     |
| 1.2                     | Columns              | <ul><li><p>Bill ID - Vendor Name</p><ul><li>Bill ID is assigned to each bill while creating an expense entry record</li><li>Sort happens on the Bill ID</li></ul></li><li><p>Expense Type</p><ul><li>Under which expense head the bill is tagged to</li></ul></li><li>Amount</li><li>Bill Date</li><li><p>Paid Date</p><ul><li>If Bill is not paid, this should show pending in RED</li></ul></li></ul> |

The table on the screen is a horizontal scrollable one with the left-most column fixed.

> [![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 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/public-finance/v2.3/exemplar/mgramseva/features/tabular-dashboard-expense.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.