> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/configuration/package-payment-config.md).

# Package Payment Config

**Available on:** Desktop · Web · Phone

The **voucher settings and print options** used when you take a payment or give a refund against a client's package in **Customer Package Payment** (see [Customer Packages](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/packages/customer-packages.md)).

In Setup Appointments, open the menu and double-click **Configuration › Package Payment Config** (the **Configuration** menu shows only for users allowed to change the configuration), or click **Configuration** in the **Customer Package Payment** window. The screen is titled **CUSTOMER PAYMENT CONFIGURATION**.

| Setting                                    | What it is                                                                                                                                                   |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Cash Receipt**                           | The voucher setting used for **cash** payments                                                                                                               |
| **Bank Receipt**                           | The voucher setting used for **card and cheque** payments                                                                                                    |
| **Cash Payment**                           | The voucher setting used for **refunds**                                                                                                                     |
| **Default Cash Account**                   | Required — without it, payments and refunds stop with *"Default cash card account is not selected!"*                                                         |
| **Print On Payment** / **Print On Refund** | After a payment or refund, the receipt opens in print preview, using the **Package Payment Receipt** or **Package Refund Receipt** design (see **Printing**) |

All four of **Cash Receipt**, **Bank Receipt**, **Cash Payment** and **Default Cash Account** must be filled before **OK** saves — for example *"Please Select Cash Account First."*. Fill it in and click **OK** before taking the first package payment.

> **Example.** Pick your cash-receipt, bank-receipt and cash-payment voucher settings, pick *Cash in Hand* as **Default Cash Account**, tick **Print On Payment** and click **OK**. When Kavya pays ₹4,000 in cash for her package, a cash receipt is made with the **Cash Receipt** setting and her receipt opens in print preview.

## On the web

The screen works the same way on the web.


---

# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/configuration/package-payment-config.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.