> 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/provisional-bill-cancellation.md).
# Provisional Bill Cancellation
**Provisional Bill Cancellation** is used to cancel a provisional bill that was generated for a guest or reservation. A provisional bill is usually a temporary or interim bill created before the final billing process. If the bill was created incorrectly or is no longer required, it can be cancelled using this option.
## Steps to Cancel a Provisional Bill
Step 1: Navigate to the **Banquet** module and select the **Cashier** menu.
1. From the available options, select **Provisional Bill Cancellation**.
* The Provisional Bill Cancellation screen will appear.
Step 2: Choose the provisional bill that needs to be cancelled.
* Identify the correct bill using the bill number, guest name, reservation number, or other available details.
* Click on the **Select** button to confirm the chosen provisional bill.
Make sure the correct bill is selected before proceeding with the cancellation.
Step 3: After selecting the provisional bill, click on the **Cancel** button.
* The selected provisional bill will be cancelled successfully.
---
# 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/provisional-bill-cancellation.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.
