> 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-to-void-a-guest-charge-if-i-made-a-mistake.md). # How to void a guest charge if I made a mistake ## **How Do I Void a Guest Charge if I Made a Mistake?** To **void a guest charge** that was posted incorrectly, you must use the **Guest Charges Deletion process** within the **Cashier module**. ## **Steps to Void a Guest Charge** ### **1. Navigate to the Menu** * Go to **Cashier Main Menu > Cashier > Guest Charges**. ### **2. View Posted Charges** * Click the **View button** located in the **toolbar** to display all **guest charges that have already been posted**. ### **3. Select the Record** * From the displayed list, select the **specific guest and charge** that you want to remove. ### **4. Execute Deletion** * Click the **Delete button**. ### **5. Provide a Reason** * When prompted, enter a **valid reason for deleting the record**. * Click **OK** to finalize the **void process**. ## **Modifying vs. Voiding** If you do not want to **delete the charge completely** and only need to **correct an error**, you can modify the bill instead: * Click the **Refresh button** in the **Guest Charges window** to enter **Open mode**. * Select the **bill**, make the required **adjustments**, and click the **Save button**. ## **Important Constraints** * **Current Date Only:** You can only **post, modify, or delete guest charges** based on the **current accounting date**. The system does not allow selecting or changing charges from **previous days**. * **Audit Trail:** All **amendments and deletions** are saved in a **log** and will be 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-to-void-a-guest-charge-if-i-made-a-mistake.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.