> 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-reports-2/settlement-pos.md).
# Settlement POS
The **Settlement (POS) Report** is used to view settlement transaction details generated through the POS system. This report provides settlement information outlet-wise and user-wise, helping users monitor payment collections and settlement summaries.
## Steps to Open the Settlement (POS) Report
Step 1: Navigate to the **Point of Sale** module and click the **Reports** menu.
1. Select **Settlement (POS)**.
* The Settlement (POS) Report screen will appear.
Step 2: Select Required Filters
1. Outlet-wise Settlement Report
* If you want to generate an outlet-wise settlement report, select the required **Outlet** from the filter options.
2. User-wise Settlement Report
* If you want to generate a user-wise settlement report, select the required **User** from the available options.
* These filters help users generate customised settlement reports based on their requirements.
Step 3: Click on the **Advanced Filter** option.
* The Advanced Filter screen will appear, where additional sorting and filtering options can be selected to generate more detailed reports.
Step 4: After selecting all the required filters, click on the **Display** button.
* The report will load and display the different types of settlements along with their corresponding amounts.
* If you want to export the report to Excel format, click on the **Excel Export Icon** available on the screen.
---
# 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-reports-2/settlement-pos.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)