> 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/fo-cashier-bill-split.md).
# Bill Split
Steps to split the bill
### **Bill Split**
This option is used to split the bills. By using this option, the user can make upto 9 bill splits as required.
#### **Steps to Bill Split**
1. Go to **Front Office>> Cashier>>Checkout>> Bill Split**
2. Then, select the guest either from the guest list or through the Calendar view.
1. Click on the room number field to open the guest list.
2. Select the guest.
3. Or Select the guest from the Calendar View.
4. Select the guest from the list.
5. Click on the Bill Split button from the bottom of the screen to display the bill charged to the guest.
6. If the user is allowed to split the amount using the [amount split](/front-office-module/fo-cashier/fo-cashier-amountsplit.md) functionality and save.
7. Click next to go to bill settlement.
8. Click on the Provisional button to create a [provisional bill](/front-office-module/fo-cashier/provisional-bill.md)
9. Click on the Bill & Settle button [to settle bills](/front-office-module/fo-cashier/fo-cashier-bill-settle-cancel.md).
10. Click on the Print Bill button to print bills.
---
# 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/fo-cashier-bill-split.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)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)