> 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/gstr-1-nil-rated-supplies.md).
# GSTR-1 Nil Rated Supplies
**GSTR-1 Nil Rated Supplies** refers to the reporting of outward supplies of goods or services that are taxed at **0% GST or are fully exempt from GST**. Even though no tax is charged on these supplies, they must still be properly reported in the GSTR-1 return.
## Steps to View GSTR-1 Nil Rated Supplies
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 **GSTR-1 Nil Rated Supplies** to open the screen.
Step 2: Select the required **From Date** and **To Date** to define the reporting period.
Step 3: After selecting the date range, click on the **Display** button.
* The system will generate and show the list of Nil Rated Supplies for the selected period on the screen.
Step 4: Export and Print Options.
1. Click on the **Excel** button to download the report in Excel format.
2. Click on the **Print** button to generate the report in PDF format or open it in print view for printing.
---
# 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/gstr-1-nil-rated-supplies.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.
