> 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-reports/recurring-charges-posted.md).
# Recurring Charges Posted
The **Recurring Charges Posted** report displays all recurring charges that have been automatically or periodically posted within a selected date range. These charges may represent recurring income, expenses, subscriptions, maintenance fees, rent, service charges, or other scheduled transactions configured in the system.
## Steps to Generate the Recurring Charges Posted Report
Step 1: Navigate to the **General Ledger** module.
1. Click **Reports** from the menu.
2. Select **Recurring Charges Posted** option.
* The recurring charges posted screen will be displayed.
Step 2: Select the **From Date** and **To Date**.
Step 3: After selecting the required date range, click the **Display** button.
* The system will generate and display the Recurring Charges Posted report for the selected period.
Step 4: After generating the report :
* Click the **Print** button  to generate the report in a printable document format.
* Click the **Excel** button  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-reports/recurring-charges-posted.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.
