> 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/difference-between-amount-split-and-bill-split.md).

# Difference between Amount Split and Bill Split

## **What Is the Difference Between Amount Split and Bill Split?**

The **primary difference between an Amount Split and a Bill Split** is whether you are **dividing the cost of a single transaction** or **organizing multiple transactions into separate bill documents**.

## **Amount Split**

* **Purpose:**\
  Used to **divide the specific amount of a single revenue item**.
* **Functionality:**\
  The amount can be split:
  * **Percentage-wise**
  * By a **specific amount**
* **Use Case:**\
  Ideal when guests want to **share the cost of a specific charge equally**.
* **Process:**\
  Once the amount is divided, the user can proceed with a **Bill Split** if required.

## **Bill Split**

* **Purpose:**\
  Used to **generate multiple separate bill documents**.
* **Functionality:**\
  The system allows up to **9 different bill splits**.\
  A **bill number** (for example, **"1" or "2"**) is assigned to each revenue item listed on the guest's account.
* **Result:**\
  The system creates **separate bills** based on the assigned numbers:
  * Items marked as **"1"** appear on the **first bill**.
  * Items marked as **"2"** appear on the **second bill**.

## **Location**

Both **Amount Split** and **Bill Split** options are available in:

**Cashier > Check Out > Bill Summary Screen**


---

# 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/difference-between-amount-split-and-bill-split.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.