> 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-reserv/faq-on-reservations/explain-how-to-manage-group-billing-and-split-billing-routing.md).
# Explain how to manage group billing and split-billing routing?
Managing group billing and split-billing routing involves using the Group Master record for centralised control and the routing tool for automated charge distribution.
**Centralised Group Billing**
To manage billing for an entire group, you must first create a Group Master record. This serves as the primary record that consolidates all individual reservations, allowing for centralised billing and reporting for the entire group.
**Split-Billing Routing**
The Routing feature is used to automatically split bills among guests, which saves the effort of manual splitting. Routing can be applied at four different stages:
* While creating the reservation.
* While checking in.
* After check-in.
* While checking out.
**Steps to Create a Routing:**
* **Initiate:** Click the Routing button after the guest and room creation is complete.
* **Assign Splits:** Use the Assign to field to specify the number of splits required for the reservation.
* **Specify Recipients:** In the Edit Split button, specify the Guest name or Company Name, as well as details for payments, collections, and tips.
* **Select Revenues:** Click on the **Group/Revenue** field to select the specific group and the particular revenues (such as room charges, telephone, or laundry) that need to be split.
* **Save:** Save these preferences to ensure charges are automatically directed to the correct folio.
**Manual Billing Splits at Checkout**
If billing needs to be handled manually during the checkout process, the system offers two additional options:
* **Amount Split:** This allows you to split the amount of any revenue either percentage-wise or by a specific amount (e.g., splitting a single charge equally between two guests).
* **Bill Split:** This option allows you to create up to 9 different bill splits. You can assign specific revenue items to different bill numbers (e.g., Bill 1 for room charges and Bill 2 for incidental charges).
**Additional Billing Tools**
* **Temporary Folios:** These are used to record charges before a guest officially checks in or to accommodate third-party service charges and complex split-billing scenarios.
* **Link/De-link Rooms:** You can link **"child rooms"** to a **"parent room"** so they have a single bill during checkout. In this setup, the system will not allow child rooms to be checked out individually; they must be checked out through the parent room.
---
# 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-reserv/faq-on-reservations/explain-how-to-manage-group-billing-and-split-billing-routing.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.
