> 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/point-of-sale/point-of-sale-module/pos-reports-2/void-bill.md).
# Void Bill
The **Void Bills Report** is used to view details of cancelled or voided bills. This report helps users track cancelled transactions and review important information related to void bills.
## Steps to Open the Void Bills Report
Step 1: Navigate to the **Point of Sale** module and click the **Reports** menu.
1. Select **Void Bills Report**.
* The Void Bills Report screen will appear.
Step 2: Select Required Filters
1. Outlet-wise Filter
* If you want to view void bill details for a specific outlet, select the required **Outlet** from the outlet filter option.
2. Bill Details Option
* If you want to view detailed information for a particular void bill, select the **Details** checkbox as shown on the screen.
This option allows users to view complete cancellation details, including items, users, and reasons for cancellation.
Step 3: After selecting all the required fields and filters, click on the **Display** button.
* The Void Bills Report will load and display the selected cancelled bill details on the screen.
* If you want to export the report to Excel format, click on the **Excel Export Icon** available 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/point-of-sale/point-of-sale-module/pos-reports-2/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.
.png?alt=media)
