> 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-masters/faq-on-masters/how-do-i-define-a-paymaster-room-type.md).
# How do I define a Paymaster room type?
To define a **Paymaster room type**, you must configure it within the Room Type master under the Front Office module.
**Steps to Define a Paymaster Room Type**
1. **Navigate to the Menu:** Go to the **FRONT OFFICE** module, select **MASTERS**, then **ROOMS**, and click on **ROOM TYPE**.
2. **Create New Record:** Click on the **NEW** button to begin defining the category.
3. **Enter Category Details:** Provide a **room type ID and name** for the category.
4. **Enable Paymaster Type:** Locate the **"Paymaster type" checkbox** and **enable it**. This identifies the room type as being for internal, temporary folio, or clearing purposes rather than for standard guest accommodation.
5. **Finalize:** Click the **Save** icon to update the system with the new room type.
**Context and Use Cases**
* **Internal Accounting:** Paymaster (PM) rooms are often used to manage **temporary folios**, which record charges against a reservation before check-in or accommodate split billing and third-party service charges.
* **Monitoring:** You can specifically filter for Paymaster rooms in various reports, such as the **High Balance Report**, to monitor outstanding balances in these internal accounts.
* **In-House Tracking:** In the **Guest Folio query**, there is a dedicated **PM button** that allows users to view only the ledger details for Paymaster rooms.
---
# 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-masters/faq-on-masters/how-do-i-define-a-paymaster-room-type.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.
.png?alt=media)