> 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-analysis/faq-on-analysis/can-i-view-month-wise-sales-summary.md).

# Can I view month-wise sales summary?

Yes, you can view month-wise sales summaries using specific reports and analysis tools within the system:

**1. Sales Day Book Month Wise Report**

This specialized report allows you to view transaction details on a monthly basis.

* Details Provided: It shows a day-wise summary of sales, including product group-wise data and GST details.
* How to Access:
  1. Navigate to **Reports > Sales Day Book Month Wise.**
  2. Select the specific outlet for which you want to generate the report.
  3. Use the Advance Filter options if you need to sort the data further.
  4. Click Display to generate the report.

**2. Cover Analysis**

If you need to analyze sales volume in terms of "covers" (guest packs) over time, this report provides both month-wise and day-wise views.

* **Details Provided:** It allows you to check how many packs were sold per day or per month, and includes session-wise and outlet-wise details.
* **How to Access:**
  1. Navigate to **Analysis > Cover Analysis.**
  2. Choose any additional options for the report, such as selecting MTD/YTD to generate a yearly view,.
  3. Click Display to load the data.

**3. Sales Analysis**

For a broader overview of sales trends, you can also use the general Sales Analysis tool located under the Analysis main menu.Both the Sales Day Book Month Wise and Cover Analysis reports can be converted and saved into Excel format by clicking the corresponding icon,.


---

# 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-analysis/faq-on-analysis/can-i-view-month-wise-sales-summary.md?ask=<question>&goal=<user_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.
