> 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-party-outstanding/bills-aging-summary-monthwise.md).
# Bills Aging Summary-Monthwise
The **Bills Aging Summary – Monthwise** report provides a consolidated month-wise summary of outstanding bills based on their aging. This report helps users track unpaid amounts, understand overdue status, and analyse payment patterns over different months.
## Steps to Generate the Bills Aging Summary – Monthwise Report
Step 1: Navigate to the **General Ledger** module.
1. Click **Party Outstanding** from the menu.
2. Select **Bills Aging Summary – Monthwise** option.
* The bills aging summary – Monthwise screen will be displayed.
Step 2: Click the **Group** drop-down.
1. Select the required group from the available list.
Step 3: Click the **Party** selection field.
1. Select the required party from the list.
Step 4: Click the **Advance Filter** option.
1. Select the required filter options.
Step 5: Verify all selected filters, click the **Display** button.
* The system will generate and display the Bills Aging Summary – Monthwise report.
Step 6: 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-party-outstanding/bills-aging-summary-monthwise.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.
