> 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-reports1/fo-reports1-day-settlement.md).
# Day Settlement
Steps to view day settlement report
**Navigation Path:**
1. Navigate to the **Front Office** module.
2. Click the **Reports Menu**.
3. Select **Day Settlement**.
**Day Settlement**
Day Settlement shows the user the types of settlements such as cash, CC, Cheque, City Ledger etc. In this report the types of settlements are as columns against the bills which are in rows and you can add Misc. Payments/collections and Tips.
.png?alt=media)
It will also show zero amount billings if you click on the checkbox ‘Zero Amount Bill’.
.png?alt=media)
You can filter it ‘**User**’ wise with multiple user selection and/ or all users all together.
You have the option to group this report ‘User’ wise or ‘Bill Type’ ,or 'Bill No' wise.
There is an option in the report to see ‘**Day Settlement Type**’ wise report, which opens a different. format and features many other options.
.png?alt=media)
You can see a specific type of settlement only and/ or all.
.png?alt=media)
There are few other columns that you can add and also see ‘**POS Receipts**’ from the filter
---
# 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-reports1/fo-reports1-day-settlement.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.