> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/stock-reports/stock-ledger.md). # Stock Ledger Logic ERP has added a **Branch Group** filter to the **Stock Ledger**. You can now run the report for all the branches of one or more branch groups without picking each branch by hand. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Stock Reports**. * Open the **Stock Ledger**. *** ### **Step 2: Branch Group filter** * In the report's selections, choose **Branch Group**. It appears just after **Branch**. * Pick the branch group level and then the groups you want. The report then includes only the branches that belong to the chosen groups. * The filter applies to every part of the report: purchases and purchase returns, sales and sale returns, issues and receipts, production receipts, challans and challan returns, purchase challans and their returns, godown transfers, and the opening stock. * **Branch Group** is a filter only. It does not add a branch group column or a branch group break to the report. * You can use it together with **Branch**. The report then shows only the chosen branches that also belong to the chosen groups. * With **Show Data For Current Branch Only** ticked in the configuration, the report shows the current branch only if it belongs to the chosen groups. --- # 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://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/stock-reports/stock-ledger.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.