> 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/general-ledger/general-ledger-module/gl-analysis/gl-analysis-ledger-analysis-report.md).
# Analysis Ledger Summary
The **Ledger Summary Report** under Analysis is used to view ledger-wise financial data based on **Analysis Levels**. These analysis levels are created to bifurcate ledger amounts across different **Cost Centers**, enabling structured financial tracking.
This report provides a summarized view of transactions by cost center and ledger, making it useful for detailed financial analysis and reporting.
## Steps to Access the Anaalysis Ledger Summary Report
Step 1: Go to the **General Ledger** module.
1. Click **Analysis** from the menu.
2. Select **Ledger Summary**.
* The **Ledger Summary Report** screen will be displayed.
Step 2: Click on the **Group** option.
1. Choose the required ledger group from the available list.
Step 3: Click on the **Ledger** option.
1. Select the required ledger name from the list.
Step 4: Click on the **Advanced Search Filter** option.
1. Choose the required filter criteria.
Step 5: Click on the **Three-Dot menu**.
1. Select the available options as per your requirement.
Step 6: After selecting the required group, ledger, or filters, click **Display**.
1. If no specific ledger is selected, the report will display data for **all cost centers** by default.
Step 7: After generating the report :
* Click the **Print** button .png?alt=media)to generate the report in a printable document format.
* Click the **Excel** button .png?alt=media) to export the report to Microsoft Excel format for further analysis and reporting.
---
# 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/general-ledger/general-ledger-module/gl-analysis/gl-analysis-ledger-analysis-report.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.
