> 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-tariff-all-function.md).

# How do I perform a Post Tariff All function?

To perform the **Post Tariff All** function, navigate to the **Front Desk Main Menu**. From there, select **Front Desk > Post Tariff - All**. Once the Post Tariff - All screen appears, click the **Post button** to charge the room rates to all guest rooms simultaneously.

This function is a mandatory requirement that must be completed before the **Night Audit** process can be executed. It is important to note that the system only allows you to perform this action after **10:00 PM**. If this step is missed, the **Night Audit Checklist** will flag "Tariff not posted" as a pending job, and the system will block the transition to the new accounting date until the tariffs for all in-house guests are finalized.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-db926156b1d6a081552283ea99cb9df37cbff2ce%2Fimage%20(1122).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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-tariff-all-function.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.
