> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/banquet/banquet-module/reports/banquet-settlement.md).
# Banquet Settlement
**Banquet Settlement** is a report feature used to view and manage settlement details related to banquet bookings. It helps in tracking financial transactions and can be filtered based on users or advanced search options for better analysis.
## Steps to View Banquet Settlement
Step 1: Go to the **Reports** menu in the **Banquet** module.
1. Click on **Banquet Settlement**.
Step 2: After opening the Banquet Settlement page, you will see the list of all settlement records.
* This page displays settlement details such as bookings, amounts, and related information.
Step 3: To filter records based on a specific user:
1. Click on the **User** filter option.
2. Select the required user from the drop down list.
3. The system will display only the settlement records associated with the selected user.
Step 4: Click on the **Advanced Search** option available on the screen.
1. Select the required filter criteria as needed.
Step 5: After applying filters in Advanced Search, click on the **Display** button.
* The system will display Banquet Settlement report on the screen.
---
# 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://help.rbsgo.com/banquet/banquet-module/reports/banquet-settlement.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
