> 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/fo-cashier-post-tariff-all.md).
# Post Tariff – All
Steps to post tariff all
If the final day's tariff has not yet been posted, the Post Tariff-All option in the Cashier menu can be used to update the ledgers all at a go.
### **Post Tariff – All**
This option allows the user to post tariffs for all rooms simultaneously. It is typically used before the Night Audit process to ensure that tariffs are posted for all occupied rooms.
#### **Steps to Post Tariff-All**
1.Go to **Front Office>>** **Cashier >>Post Tariff - All.**
4. Click the “Specific” checkbox. Once selected, the system prompts the user to choose a specific company or group.
5. Once the Group or Company option is selected, the system displays the corresponding selection field, allowing the user to choose the specific company or group.
5. Select the company/group. Here in the example, a company is chosen, and hence the list of companies are displayed.
6. Once the user clicks on the Post button, a confirmation pop-up is displayed, and the Tariff will be posted to all the rooms. This option can be used before the night audit process to post tariffs to all the rooms.
.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/fo-cashier-post-tariff-all.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)