> 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/material-management/material-management-module/mm-transactions/faq-on-material/how-can-i-view-a-stock-ledger.md).

# How can I view a Stock Ledger?

You can view your stock ledger in two ways depending on whether you need a detailed item-by-item movement record or an overall period summary:1. Item Stock Ledger (Detailed View)This report tracks all stock transactions (receipts, issues, adjustments, and balances) for an item in chronological order.

* Steps:
  1. Go to Reports > Item Stock Ledger.
  2. Click on the Advance filter option.
  3. Click the Display button to load the report.
  4. *(Optional)* Click the Print or Excel button to print or download the report.

***

2\. Stock Ledger Summary (Period Summary View)This report provides a summary showing the Opening Quantity, Received Quantity, and Issued Quantity for a selected period.

* Steps:
  1. Go to Reports > Stock Ledger Summary.
  2. Use the Funnel Filter, Store By, or Group By options to filter by specific products or stores.
  3. Select whether to display the report by Quantity, Value, or Both.
  4. Click the Display button


---

# 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/material-management/material-management-module/mm-transactions/faq-on-material/how-can-i-view-a-stock-ledger.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.