> 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-transaction/gl-transaction-reprint-voucher.md).
# Reprint Voucher
**Reprint Voucher** is a feature that allows users to print a copy of an existing voucher that has already been generated and saved in the system. This option can be used to obtain duplicate copies of vouchers for reference, record-keeping, auditing, verification, or customer requirements.
## Steps for Reprinting a Voucher
Step 1: Navigate to the **General Ledger** module.
1. Click Transaction from the menu.
2. Select **Reprint Voucher** option.
* The Reprint Voucher screen will be displayed.
Step 2: Locate the **Voucher Type** field.
1. Select the required voucher type from the available list.
Step 3: Use the available search filters to locate the required voucher.
1. Enter the **From Date** and **To Date** to specify the period during which the voucher was generated.
Step 4: Select the required voucher from the list.
Step 5: Click the **Print** button.
* The system generates a printable version of the selected voucher.
---
# 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-transaction/gl-transaction-reprint-voucher.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.
