> 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-bill-covering-letter-print.md).
# Bill Covering Letter Print
The **Bill Covering Letter – Print** feature allows users to print previously generated covering letters for **Receivable (Accounts)** transactions. Users can search for covering letters based on a specific party, date, or pending bill status and print the required covering letter whenever needed.
## Steps to Print a Bill Covering Letter
Step 1: Navigate to the General Ledger module.
1. Click Party Outstanding from the menu.
2. Select **Bill Covering Letter – Print** option.
* The **Bill Covering Letter – Print** screen will be displayed.
Step 2: Click the **Group** drop - down.
1. Select the required group from the available list.
2. The system will display the parties associated with the selected group.
Step 3: Click the **Party** selection field.
1. Select the required party from the list.
* The system will retrieve the covering letters previously generated for the selected party.
Step 4: Select the required date range.
1. Click **Display** to view covering letters generated within the selected period.
* If you want to print covering letters only for outstanding bills:
1. Enable or click the **Pending Bills** option.
2. The system will display covering letters associated only with pending bills.
Step 5: To print a covering letter:
1. Select the required covering letter from the displayed list.
2. Verify the covering letter details.
3. Click the **Print** button.
---
# 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-bill-covering-letter-print.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.
