> 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/point-of-sale/point-of-sale-module/advanced-reports/faq-on-advanced-reports/what-information-is-in-the-bill-split-audit.md).

# What information is in the Bill Split Audit?

The Bill Split Audit report is designed to track and review transactions specifically for bills that have been split within the system. It provides a detailed view of several key data points:

* **Identification:** Bill numbers and the name of the assigned steward.
* **Order Details:** The type of Kitchen Order Ticket (KOT) and the specific items billed.
* **Financials:** The total bill amount.
* **Timings:** The exact bill generation time and the settlement time.
* **Cancellations:** Details regarding any settlement cancellations.

To access this report, navigate to **Advance Reports > Bill Split Audit.** You can sort the data as needed before clicking Display to generate the report. Additionally, the system allows you to convert and save this audit in an Excel format.


---

# 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/point-of-sale/point-of-sale-module/advanced-reports/faq-on-advanced-reports/what-information-is-in-the-bill-split-audit.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.