> 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-general-ledger.md).
# General Ledger
The **General Ledger Report** provides a detailed view of all transactions recorded for a selected ledger. It displays complete transaction history, including debit and credit entries, within a chosen period.
## Steps to Access the General Ledger Report
Step 1: Go to the **General Ledger** module.
1. Click **Analysis** from the menu.
2. Select **General Ledger**.
* The **General Ledger Report** screen will be displayed.
Step 2: Click the **Search** icon.
1. Choose the required date range or reporting period from the available options.
Step 3: Click on the **Advanced Filter** option.
1. Select the required filter criteria from the available options.
Step 4: Click on the **Three-Dot option** available on the screen.
1. Select the available options as per your requirement.
Step 5: Click the **Display** button.
* The **General Ledger Report** will be generated and displayed on the screen.
---
# 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-general-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.
