> 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-version-release-notes/november-2019/user-access/clear-all-discounts-before-implementing-schemes.md).

# Clear All Discounts Before Implementing Schemes

In the Setup User/Company Wise Global Settings of Logic Admin, a new option i.e. ‘**Clear all discounts before Scheme implementation at Bill End is** added. When you enable this option, it will clear all existing discounts before implementing schemes. Please note that, all manual discounts given and discounts picked from defaults will also be cleared. This option is only useful for the customers who are not giving any manual discounts.

**Problem Details:**

***If all schemes are applied but user press cancel from payment window and then changes some items in the bill, sometimes existing discount values remains there even if there is no scheme applicable on the bill. This option ensures all discounts gets cleared before re-implementing schemes***

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F9h7ZQqN9OJa2xjkdX8Nx%2Fimage.png?alt=media&amp;token=aeebac5e-0fb3-4b50-ad65-3e658672d239" alt=""><figcaption></figcaption></figure>


---

# 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-version-release-notes/november-2019/user-access/clear-all-discounts-before-implementing-schemes.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.
