> 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-frontdesk/fo-frontdesk-bar-posting.md).
# Bar Posting
Steps to Bar post the rooms
### **What is Bar Posting?**
Bar Posting is a feature that allows the front office team to block any charges or credits from being posted to a guest’s room. Once a room is bar-posted during the guest’s stay, any services used or items consumed must be paid for immediately and cannot be charged to the room.
### **Steps to enable Bar Posting:**
1. Go to **Front Office>>Front Desk >>In-House Guest Amend**
3. Click on the **Room No.** and select the particular guest that needs to be Bar Posted.
4\. Double-click the selected guest to display the guest's details on the screen. From the ellipsis (three vertical dots), select “Bar Post.”
5. Once the user has clicked on **Bar Post,** he will get a pop-up of the **Bar Posting** Screen where he can select the particular transaction for which he needs to prohibit posting to the room and then click save.
6\. If the user wants to Bar Post a Specific outlet from Guest Charges or POS, click specific as shown below
7\. Select the particular **Outlet** which the user needs to **Bar Post** and click **OK**
8\. Click on save to save the amendments.
---
# 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-frontdesk/fo-frontdesk-bar-posting.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)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)