> 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/manage-group-billing-and-split-bill-routing.md).

# Manage group billing and split bill routing

**Explain how to manage group billing and split-billing routing**

Managing **group billing** and **split-billing routing** involves using the **Group Master** for centralized control and the **Routing** feature for automatic distribution of charges.

### **1. Centralized Group Billing**

To manage billing for an entire group:

* First, create a **Group Master** record.
* The Group Master acts as the main record that consolidates all individual reservations under one group.
* It allows centralized:
  * Billing management
  * Reporting
  * Tracking of group-related transactions

### **2. Split-Billing Routing**

The **Routing** feature automatically divides charges among guests or companies, reducing the need for manual bill splitting.

Routing can be applied at four stages:

* During **reservation creation**
* During **check-in**
* After **check-in**
* During **check-out**

#### **Steps to Create a Routing**

1. **Initiate Routing:**
   * Click the **Routing** button after completing guest and room creation.
2. **Assign Splits:**
   * Use the **Assign To** field to define the number of splits required for the reservation.
3. **Specify Recipients:**
   * In the **Edit Split** option, enter:
     * Guest Name or Company Name
     * Payment details
     * Collection details
     * Tip details (if applicable)
4. **Select Revenues:**
   * Click the **Group/Revenue** field.
   * Select the required revenue groups and specific charges to be routed, such as:
     * Room charges
     * Telephone charges
     * Laundry charges
5. **Save Routing Preferences:**
   * Save the configuration so charges are automatically posted to the correct folio.

### **3. Manual Billing Splits at Checkout**

If splitting is required manually during checkout, the system provides two options:

#### **Amount Split**

* Allows splitting a revenue amount:
  * By percentage
  * By fixed amount
* Example: Dividing one charge equally between two guests.

#### **Bill Split**

* Allows creation of up to **9 separate bill splits**.
* Specific revenue items can be assigned to different bill numbers:
  * **Bill 1:** Room charges
  * **Bill 2:** Incidental charges

### **4. Additional Billing Tools**

#### **Temporary Folios**

Used for:

* Recording charges before guest check-in.
* Handling third-party service charges.
* Managing complex split-billing requirements.

#### **Link/De-link Rooms**

* Allows multiple rooms to be connected:
  * **Parent Room:** Main billing room.
  * **Child Rooms:** Linked rooms included under the same bill.
* Child rooms cannot be checked out individually and must be checked out through the parent room.

These features help ensure accurate charge allocation, simplify group billing, and improve control over complex payment arrangements.


---

# 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/manage-group-billing-and-split-bill-routing.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.