> 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-check-out-and-cashier-menu.md).

# How to check out & Cashier Menu

### **How to do Check-out in WINCLOUD?**

Checkout in the WinCloud system must be completed through the Cashier module by following a structured process to ensure all outstanding charges are properly settled.

1\. **Initiating the Checkout**

* Navigate to the **Front desk >>Cashier >> Check Out**.
* Select the specific room number from the list to begin the process.
* If the user attempts to check out a guest before their scheduled departure date, the system will display a warning message; click Yes to proceed.
* Alternatively, the user can perform an **instant checkout using the Due Out** button on the Calendar screen.

2\. **Managing Charges and Splits**

Before finalizing the bill, the system provides several options to accommodate guest requests:

* **Amount Split**: This option is used to split a specific revenue amount either by percentage or by a specified dollar value.
* **Bill Split:** The user can create up to nine separate bill splits by assigning different revenues to specific bill numbers.
* **Post Tariff**: If the final day's tariff has not yet been posted, the user can use the Post Tariff-Single option in the Cashier menu to update the ledger.
* **Bar Posting**: Use this feature to prevent additional charges from being applied to the room bill. Once activated, the guest must settle any further services at the time of consumption.

3\. **Finalizing and Settlement**

* Click Next to **advance to the bill summary** screen.
* Review the charges and select either **Bill Print to preview/print the guest bill** or **Bill & Settle** to finalize the payment.
* You have the option to send the **bill via emai**l and either **print a physical copy** or **skip** the printing process.
* Choose the **appropriate settlement mode** (such as cash, credit card, or city ledger) and click Save to complete the checkout.

4\. **Post-Checkout Considerations**

* **Pending Bills:** If a bill is printed but the payment is not immediately processed, it will appear in the Pending Bills report; these should ideally be cleared within 5–10 minutes for optimal practice.
* **Reinstate Checkout**: If a checkout was performed in error, you can use the Reinstate Checkout option in the Front Desk menu to undo it. Note that this is only possible if the room is still vacant.
* **Bill Resettlement**: If the payment mode needs to be changed after the bill is settled, you can use the Bill Resettlement option to update the transaction


---

# 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-check-out-and-cashier-menu.md?ask=<question>&goal=<user_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.