> 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/cashier/bill.md).
# Bill
A **Bill** is a document generated for a guest or customer that contains the details of the services used, charges applied, taxes, and the total amount to be paid. It helps the cashier maintain accurate payment records and complete the guest checkout process smoothly.
## Steps to Create a Bill
Step 1: Navigate to the **Banquet** module and select the **Cashier** menu.
1. Click on **Bill**.
* This will open the Bill creation screen.
Step 2: Click on the **Reservation No Search** option.
1. Select the required reservation number from the list.
2. Click **OK** to confirm the reservation selection.
* This step links the bill to the correct guest reservation.
Step 3: After selecting the reservation number, verify the guest details displayed on the screen.
1. Ensure that all charges and booking information are correct before proceeding.
* This helps avoid billing errors.
Step 4: Click the **Save** button.
1. The system will generate and create the bill successfully.
* Once saved, the bill will be available for payment processing and printing.
---
# 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/cashier/bill.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.
