> 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/faq-on-transaction/how-to-create-a-new-sales-voucher.md).

# How to create a new Sales Voucher ?

To create an accounting voucher (such as a sales voucher or receipt transaction), you can follow the general process flow under GL Transaction:Steps to Create a Voucher:

1. Navigate to General Ledger > Transaction > GL Transaction.
2. Click on the New icon to begin a new transaction.
3. Select the required Transaction Type and Transaction Date.
4. Click and select the Customer, Party, or Account from the Chart of Accounts.
5. Enter the Amount and configure reference details (such as Ref. Type, Bill No., Bill Date, and Due Date) by selecting the bill option.
6. Add new rows to enter the appropriate CR / DR side details.
7. Save the entry. A Voucher No. will be automatically generated for that transaction type, which can be printed or referenced later.

***

Configuring a Sales Voucher Type (If Not Already Created):If you need to set up a specific Sales Voucher classification in the system first:

1. Go to Voucher Type.
2. Click the Add button.
3. Enter the Voucher Name, Voucher No Type, and discount details.
4. Click Save to create the new voucher type.


---

# 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/faq-on-transaction/how-to-create-a-new-sales-voucher.md?ask=<question>&goal=<user_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.
