> 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-queries2/faq-on-advanced-queries/what-is-the-purpose-of-business-of-books-report.md).

# What is the purpose of "Business of Books" report ?

**Purpose and Overview**

The Business on Books report shows the revenue amount collected (when "Past Days" is selected) and the business expected to be generated from future reservations. It provides a real-time view from the current moment up to a selected month in the future.By default, the report uses a month-wise date format, displaying months in columns and dates in rows.

**Revenue Considerations**

To calculate the revenue for a given month, the report takes three primary factors into consideration:

* Total Nights.
* Revenue Generated (or expected to be generated) from bookings.
* ADR (Average Daily Rate).

**Report Filters and Customization**

The report includes multiple filters to refine the data based on operational needs:

* **Room Type Wise:** Displays the report based on specific room types, allowing for single, multiple, or all types to be selected.
* **With Compl/HU:** Includes rooms for complimentary bookings, house use, or management bookings in the totals.
* **With Day Use:** Includes bookings for day-use guests.
* **Exclude Tentative:** Removes all tentative bookings to show only confirmed business.
* **Occ%:** Adds a column for each selected month to show the percentage of occupancy on that day.
* **RevPAR:** Adds a column showing the average revenue generated (and to be generated) across all available rooms within the selected period.
* **Funnel Filter:** Allows users to sort the report by specific market segments or date-wise criteria


---

# 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-queries2/faq-on-advanced-queries/what-is-the-purpose-of-business-of-books-report.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.