> 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-cashier/faq-on-cashier/how-do-i-track-voided-guest-charges.md).
# How do I track voided guest charges?
To track voided or cancelled guest charges, you can utilize specific audit reports designed to provide transparency into modifications and deletions within the system:
* **Void Bills Report:** This report is specifically used to see all bills that have been cancelled in the Front Office after a checkout bill or final bill was generated.
* **Cashier Transaction Audit:** This is a comprehensive tool for monitoring any changes made by a cashier. It shows all instances where a cashier has cancelled, modified, or transferred charges. To isolate voided items, you can select the specific checkbox to see only **"Cancelled"** or **"Amended"** transactions.
* **Verification Prior to Night Audit:** As part of the daily closing process, all settled and voided bill copies from all outlets and modules must be verified against system reports. You can use the "void bill report option" provided in the Front Office module for this purpose.
* **Audit Logs and Reasons:** When a guest charge is deleted through the Guest Charges menu **(Cashier > Guest Charges > Delete)**, the system requires the user to provide a mandatory reason for deleting the record. This reason, along with the identity of the staff member who performed the action, is stored in the logs and reflected in the relevant audit reports.
---
# 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-cashier/faq-on-cashier/how-do-i-track-voided-guest-charges.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.
