> 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/sales-day-book.md).
# Sales Day Book
The **Sales Day Book Report** is used to view all sales transactions recorded for customers on a particular day. This report provides a complete overview of daily sales activities in a single report format.
## Steps to View the Sales Day Book Report
Step 1: Navigate to the **Point of Sale** module and click the **Reports** menu.
1. Select **Sales Day Book**.
* The Sales Day Book screen will open.
Step 2: In the Sales Day Book screen, choose the required **Advanced Filter** options.
1. Select the necessary criteria based on your reporting requirement.
* The filter options help users generate the report according to specific conditions.
Step 3: Select the required **Date**.
1. Click on the **Display** button.
* The Sales Day Book Report will be generated and displayed on the screen.
**Important Note:**
* This report can be generated **only on a day-wise basis**.
If you want to export the report to Excel:
1. Click on the **Excel Export Icon** available on the report screen.
2. The report will be downloaded in Excel format for further use and analysis.
---
# 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/sales-day-book.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)