> 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/masters/main-master-module/gst-india/purchase-billwise-summary.md).
# Purchase Billwise Summary
**Purchase Billwise Summary** is a report that provides a consolidated view of all purchase transactions, summarized **bill by bill**. It helps in tracking supplier invoices, monitoring purchase expenses, and reconciling purchase bills with payments for accurate accounting and financial reporting.
## Steps to View Purchase Billwise Summary
Step 1: Go to the main menu of the application and click on **Settings**.
1. From the Settings menu, select **GST India**.
2. Click on **Purchase Billwise Summary** to open the screen.
Step 2: Select the required **From Date** and **To Date** for which you want to generate the report.
Step 3: After selecting the date range, click on the **Display** button.
* The system will generate and display the bill-wise purchase summary on the screen.
Step 4: Export and Print Options.
1. Click on the **Excel** button to download the report in Excel format..png?alt=media)
2. Click on the **Print** button to generate the report in PDF format or open it in print view for printing..png?alt=media)
---
# 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/masters/main-master-module/gst-india/purchase-billwise-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.
