> 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-queries1/fo-queries1-high-balance-report.md).

# High Balance Report

Steps to view high balance report

**Navigation Path:**

1. Navigate to the **Front Office** module.
2. Click **Queries menu**.
3. Select **High Balance Report.**

**High Balance Report**

This report shows you the balance amount for in house guests and their credit limits (if set). The report is to alert you if the outstanding amount is greater than their allowed limits.

![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-7c1155da275230cfebb9b2ccab91b1187ea04077%2FScreenshot%202023-07-31%20114257.png?alt=media)

Check boxes are provided to see the specific info. And/ or to add the info. In report:

**Guest Balance** is to see the current Balance pending from guest.

**Cut off Limit** is to see the cut off based on the amount you enter in the corresponding field of **Cut off Amount**.

**Credit Limit** is to see the Credit Limit given to the Guest

**CC Preauthorization** where guest has given Credit Card details and has authorized to use it up to a certain amount.

**PM** is to see Pay Master Rooms.

![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-48157edab3a4ed0260f9f9dca14e648c3d98530e%2F1%20\(170\).png?alt=media)

To see Company Guests with **Company** Name or Individuals and **Credit Card Details**.

![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-9d3c1f7cb179d3053a8a847f627b9e32a74c977f%2F2%20\(110\).png?alt=media)

**Funnel Filter** is provided to search for specific **Company, Group and Agent**. **Sorting Button** is provided to sort and sequence the report based on the requirement

![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-09e3cc143b93dcf1ac80fe77db54514cdc6f62ff%2FScreenshot%202023-07-31%20114359.png?alt=media)

**Options button** is provided to add the information as columns as shown below.

![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-9e3ad41e3149f64466b0eb1092f188d6a6287360%2F5%20\(24\).png?alt=media)

.

Report will be generated as on date and will reflect the information based on your selection of filters.

![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-93267d0e56896417f276fb4dd087481aa1525521%2FScreenshot%202023-07-31%20114928.png?alt=media)


---

# 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-queries1/fo-queries1-high-balance-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.