> 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-summary.md).
# Settlement POS Summary
The **Settlement (POS) Summary Report** provides a summary of all settled transactions processed through the POS system. This report helps users analyze settlement information in a summarized format, including outlet-wise and user-wise settlement details.
## Steps to Open the Settlement (POS) Summary Report
Step 1: Navigate to the **Point of Sale** module and click the **Reports** menu.
1. Select **Settlement (POS) Summary**.
* The Settlement (POS) Summary Report screen will appear.
Step 2: Select the required **Outlet** for which the settlement summary report needs to be generated.
* This option allows users to generate outlet-specific settlement summaries.
Step 3: Click on the **Advanced Filter** option.
* The Advanced Filter screen will appear, allowing users to apply additional sorting and filtering options for more detailed report analysis.
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 the summary details.
* 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-summary.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.
