> 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/user-access/logic-global-admin/sale/sale-settings-2/do-not-allow-multiple-taxes-in-a-single-sale-bill-return.md).

# Do Not Allow Multiple Taxes in a Single Sale Bill/Return

**YouTube:** [How to Restrict the Use of Multiple Taxes in a Single Sale Bill ?](https://www.youtube.com/watch?v=EA6zA5Vj5nQ)

## How to Restrict the Use of Multiple Taxes in a Single Sale Bill ?

By default, the system allows adding items with different tax rates in a single sale or sale return voucher. This tutorial will guide you on how to restrict that functionality.

***

### **Steps to Enable Tax Restriction in Sale Vouchers**

* Open the **Logic** folder and launch **Logic Admin**.
* Click on **Global Settings**.
* Navigate to the **Sales Settings - 2** tab.
* Locate and enable the option: **"Do Not Allow Multiple Taxes in a Single Sale Bill/Return"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FKN6wo5ZeEZJf2ZId0dDJ%2FAdmin%20Setup%20-%20Do%20Not%20Allow%20Multiple%20Taxes%20in%20a%20Single%20Sale%20BillReturn.png?alt=media&amp;token=15c4050e-6e11-4a85-9123-0de3b5ff8683" alt=""><figcaption><p>Let's keep this feature enable to observe its impact in Billing.</p></figcaption></figure>

* Click **Save** to apply the changes.
* **Restart the software** to activate the setting.

***

### **Verify the Configuration**

* Create a new **Sale** or **Sale Return** voucher.
* Add an item with a specific tax rate.
* Attempt to add another item with a **different tax rate**.
* The system will display a message stating that **multiple taxes are not allowed in the same bill**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FPMh8D9tZd5w0YWpCzk6p%2FPrompt%20for%20Multiple%20Taxes.png?alt=media&amp;token=da538973-933b-42f7-9819-ca3f60be2fef" alt=""><figcaption><p>This picture shows that the software is prompting you that multiple taxes cannot be selected.</p></figcaption></figure>

***

### **Benefits of Enabling This Setting**

* **Ensures Tax Uniformity** – Keeps tax rates consistent within each voucher.
* **Reduces Calculation Errors** – Prevents mistakes in tax summaries and totals.
* **Improves Compliance** – Helps maintain alignment with tax reporting standards.
* **Simplifies Accounting** – Makes reconciliation and audit processes easier.
* **Enhances Billing Accuracy** – Ensures each invoice adheres to a single tax structure.


---

# 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/user-access/logic-global-admin/sale/sale-settings-2/do-not-allow-multiple-taxes-in-a-single-sale-bill-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.
