> 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/front-office-module/fo-reports1/fo-reports1-void-bill.md).
# Void Bills
Steps to view void bills and pending bills report
**Navigation Path:**
1. Navigate to the **Front Office** module.
2. Click the **Reports Menu**.
3. Select **Void Bills**.
**Void Bills**
This report is to see all the Bills that have been cancelled in the Front Office after making a Check out Bill or Final Bill within a selected period.
**Pending Bills**
This report shows the Bills you have generated while checking out the guest, but have not settled them yet. So if this report shows data, it means the Bill is printed but the payment has not been made. Usually this report must be empty within 5-10 minutes to have an optimal practice of the check out process.
---
# 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/front-office-module/fo-reports1/fo-reports1-void-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.
