> 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-cashier/faq-on-cashier/how-do-i-perform-a-post-plan-single-function.md). # How do I perform a Post Plan Single function? To perform the **Post Plan-Single** function, which allows you to post plan charges for a specific guest separately from room tariffs, follow these steps: 1. **Navigate to the Menu:** Go to the **FRONT OFFICE** module and select **CASHIER > POST PLAN - SINGLE**. 2. **Select the Room:** Click the **room selection icon** to choose the specific room number where the plan amount should be posted. 3. **Verify Guest Details:** Select the **guest name** and carefully check the **amount** to be posted. 4. **Check Child Plans:** If a **child plan** is being charged, verify that specific amount as well. 5. **Complete the Posting:** Once all details are confirmed, click the **post icon** to finalize the transaction. #### **Important Precautions** * **Avoid Double Postings:** Before performing this action, it is highly recommended to check the **"CURRENT GUEST LEDGER"** report (located under QUERIES 1 in the Front Office module) to ensure the charges haven't already been applied. * **Night Audit Preparation:** While plan charges can be posted along with the room tariff, this dedicated option is used if those charges were missed earlier in the day. If left unposted, this will appear as a **"Plan not posted"** error on your Night Audit Checklist.
--- # 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-cashier/faq-on-cashier/how-do-i-perform-a-post-plan-single-function.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.