> 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/point-of-sale/point-of-sale-module/pos-transactions/pos-advance.md).
# POS Advance
The **POS Advance** feature is used to collect advance payments from guests before billing or service completion. This helps maintain advance payment records for future transactions.
## Steps to Create POS Advance
Step 1: Go to the **Point of Sale** module and select the **Transaction** menu.
1. Click on **POS Advance**.
* The POS Advance screen will open.
Step 2: Click on the **New** button.
1. Select the required **Outlet Name** from the list.
* This ensures the advance is recorded for the correct outlet.
Step 3: Click on the **Guest Search** button.
1. Select the required **Guest Name** from the list.
* This links the advance payment to a specific guest.
Step 4: Enter the **Advance Amount** to be collected.
1. Select the **Settlement Mode** (such as cash, card, or other available payment methods).
* Ensure all details are entered correctly before saving.
Step 5: After entering all required details, click on the **Save** button.
1. The POS Advance entry will be successfully recorded in the system.
---
# 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/point-of-sale/point-of-sale-module/pos-transactions/pos-advance.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)