> 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/post-plan-single.md).
# Post Plan-Single
Steps to post plan single
### **POST PLAN – SINGLE**
**Post Plan – Single** allows the user to post all plan charges to a specific guest, separate from tariff postings. This option also enables the user to post child plan charges, if applicable at the property. Although plan charges can be posted along with the tariff posting, this dedicated option can be used to post the plan separately if it was missed earlier.
**NOTE:** Before posting any charges, ensure that you check the “Current Guest Ledger” report under “Queries 1” in the Front Office module to prevent duplicate postings.
1. To post plan - single, go to **FRONT OFFICE>>CASHIER**>>**POST PLAN - SINGLE**
2. Click on the magnifier icon in the 'Room no' field to select the guest’s room number to which the plan amount is to be posted.
3.
```
```
4. Select the guest name and check the amount that is to be posted
4. If a child's plan is charged, check the amount of the plan .png?alt=media)
5. After confirming the details, proceed with posting by clicking the post button. .png?alt=media)
.png?alt=media)
---
# 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/post-plan-single.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)
.png?alt=media)