> 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-reports1/fo-reports1-guest-ledger.md).
# Guest Ledger
Steps to view guest ledger report
**Navigation Path:**
1. Navigate to the **Front Office** module.
2. Click the **Reports Menu**.
3. Select **Guest Ledger**.
**Guest Ledger**
The Guest Ledger report shows, by default, the current day’s Ledger of all the guests processed today (includes in house and checked out guests both).
You will have options to check both **Current Guest and Checked out Guest** separately and/ or together in the report.
.png?alt=media)
If you want to see the **Arrival and Departure Date** of the Guests there is a provided checkbox to add that to the report as well. Choose it from the options as shown below
.
---
# 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-reports1/fo-reports1-guest-ledger.md?ask=&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.