> 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/faq-on-queries/verify-posting-in-the-guest-folio.md).

# Verify Posting In The Guest Folio

**How do I verify postings in the Current Guest Ledger?**

To verify postings in the **Current Guest Ledger** (also referred to as the **Guest Folio**), follow these steps:

#### **1. Navigate to the Report**

Go to:

**FRONT OFFICE → QUERIES → GUEST FOLIO**

Alternatively, you can access the **CURRENT GUEST LEDGER** report under **QUERIES 1**.

#### **2. Select the Room**

Choose the required **Room Number** to view the ledger details for the current in-house guest.

#### **3. Review Transactions**

* **Default View:**\
  By default, the report displays the **current day's postings**, while transactions from previous days are shown as an **opening balance**.
* **Full Transaction History:**\
  Select the **Arrival** checkbox to display all transactions recorded from the guest's **check-in date**.

#### **4. Use Filters to Verify Specific Data**

* **PM Button:** Displays only **Pay Master (PM)** rooms.
* **All Guest Button:** Shows the names of **all guests** assigned to the room instead of only the primary guest.
* **Search/Advance:** Use the search fields or the **Advance** option to filter records by specific information, such as **mobile number**.

#### **5. Verify Split Postings**

If **billing routing** or **split billing** has been configured for the reservation, review the transactions **split-wise** to ensure all charges have been allocated correctly.

**Recommendation:**\
Verify the **Current Guest Ledger** before posting additional charges (such as **Post Plan – Single**) to help prevent duplicate postings.


---

# 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/faq-on-queries/verify-posting-in-the-guest-folio.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.