> 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/gl-party-outstanding-outstanding-bill-ageing-summary.md).
# Bill Aging (Summary)
The **Bill Aging (Summary) Report** provides a summarized view of outstanding dues in ledger accounts on a group-wise and account-wise basis. This report helps users analyze pending receivables and payables according to their aging period without displaying detailed bill-level information.
## Steps to Generate the Bill Aging (Summary) Report
Step 1: Navigate to the **General Ledger** module.
1. Click **Party Outstanding** from the menu.
2. Select **Bill Aging (Summary)** option.
* The Bill Aging (Summary) Report screen will be displayed.
Step 2: Locate the **Group** field.
1. Select the required group from the list.
Step 3: Click the **Parties Search** option.
1. Search for and select the required account name or party from the available list.
Step 4: Click the **Advanced Filter** option.
1. Apply the required filters to refine the report data.
Step 5: Review all selected groups, accounts, and filters.
1. Click the **Display** button.
* The Bill Aging (Summary) Report is generated and displayed on the screen.
Step 6: After generating the Bill Aging 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-party-outstanding/gl-party-outstanding-outstanding-bill-ageing-summary.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.
