> 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-1.md).

# How do I define a Paymaster room type

**How do I define a Paymaster room type?**

To define a **Paymaster (PM) room type**, configure it in the **Room Type Master** under the **Front Office** module.

#### **Steps to Define a Paymaster Room Type**

1. **Navigate to the Menu:**\
   Go to **FRONT OFFICE → MASTERS → ROOMS → ROOM TYPE**.
2. **Create a New Record:**\
   Click the **New** button to create a new room type category.
3. **Enter Category Details:**\
   Provide the required:
   * **Room Type ID**
   * **Room Type Name**
4. **Enable Paymaster Type:**\
   Select the **Paymaster Type** checkbox.\
   This identifies the room type as a Paymaster account used for internal, temporary folio, or clearing purposes rather than standard guest accommodation.
5. **Save the Configuration:**\
   Click the **Save** icon to add the new Paymaster room type.

#### **Context and Use Cases**

* **Internal Accounting:**\
  Paymaster rooms are commonly used for:
  * Temporary folios
  * Recording charges before check-in
  * Split billing
  * Third-party service charges
* **Monitoring:**\
  Paymaster rooms can be filtered in reports such as the **High Balance Report** to monitor outstanding balances in internal accounts.
* **In-House Tracking:**\
  In the **Guest Folio** query, the dedicated **PM** button allows users to view ledger details specifically 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-1.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.