> 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/setups/configurations/sale-voucher-configuration/other-settings-1/do-not-allow-multiple-payment-modes-tenders-in-case-of-sale-return.md).

# Do Not Allow Multiple Payment Modes/Tenders in case of Sale Return

**YouTube:** [How to Disable Multiple Payment Modes in Sales Return ?](https://www.youtube.com/watch?v=loNIKRWSYe0)

## How to Disable Multiple Payment Modes in Sales Return?

In this tutorial, we will guide you through the process of **restricting the use of multiple payment modes (tenders)** during a **sale return transaction** in Logic ERP.

### Open Sales Voucher Configuration

* Navigate to Sales Voucher Configuration.
* Select the relevant billing series.
* Locate the option “Do not allow multiple payment modes/tenders in case of sale return.”
* Let’s first keep this option disabled and see how it behaves.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FhaDShE26jXqK9zmkmJOa%2FDo%20Not%20Allow%20Multiple%20Payment%20ModesTenders%20in%20case%20of%20Sale%20Return%20-%20Configuration.png?alt=media&amp;token=725bc023-7443-429e-8073-32f66013cd94" alt=""><figcaption><p>Let's keep this feature Disabled and Observe its Impact</p></figcaption></figure>

### Process a Sale Return (With the Feature Disabled)

* Navigate to the Sale Voucher and create a new bill.
* Initiate a return/exchange transaction for an existing customer.
* At the payment stage, select multiple tenders or payment modes.
* Proceed to save the bill.
* Result: Since the restriction is disabled, the system allows saving the bill using multiple payment methods.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FPk5521PEI9dREtvxoWE6%2FAllow%20Multiple%20payment%20mode.png?alt=media&amp;token=a9c5d68a-9c23-4fdb-bf63-c84a6200450c" alt=""><figcaption><p>As you can see in the Picture, we have selected multiple payment modes here.</p></figcaption></figure>

### Enable the Restriction

* Return to Sales Voucher Configuration.
* Enable the feature: “Do not allow multiple payment modes/tenders in case of sale return.”
* Save the configuration.

### Re-process a Sale Return (With the Feature Enabled)

* Again, start a return/exchange transaction.
* Attempt to use multiple payment modes during billing.
* Result: The system displays an error message:
* “Multiple payment modes/tenders are not allowed in case of sale return.”
* In this case, only a single payment mode must be selected.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FCiAfAjJ9FIRPCCv3otA2%2FPrompt%20for%20Multiple%20payment%20mode.png?alt=media&amp;token=d8f97192-90a6-471a-8dee-090f3208ada1" alt=""><figcaption><p>As you can see in this image, the software has not allowed multiple payments.</p></figcaption></figure>

### Conclusion

* This feature helps enforce stricter payment policies during sale returns by:
  * Preventing confusion caused by multiple payment modes.
  * Ensuring streamlined and secure payment reconciliation.&#x20;


---

# 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/setups/configurations/sale-voucher-configuration/other-settings-1/do-not-allow-multiple-payment-modes-tenders-in-case-of-sale-return.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.
