> 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/purchase-voucher-configurations/other-settings-1/pick-party+company+group-wise-markdown-po-as-td.md).

# Pick Party+Company+Group Wise Markdown (PO) as TD

YouTube: [How to Retrieve Party + Company/Group wise Markdowns defined for PO as TD Purchase?](https://www.youtube.com/watch?v=uiJdZcbWXxA)

## How to Retrieve Party + Company/Group wise Markdowns defined for PO as TD Purchase?

In this tutorial, we will explore a feature that enables the automatic application of party, company, and group-wise markdowns in purchase vouchers when retrieving purchase orders as TD. First, we will demonstrate how to activate this setting within the purchase configuration.

### **Enable the Feature:**

* Navigate to the "**Purchase Voucher Configuration"**.
* Locate the option and enable **"**&#x50;ick Party + Company + Group Wise Markdown (PO) as T&#x44;**"**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FBm1CeFPeR1lCMsONORtM%2FPick%20Party%2BCompany%2BGroup%20Wise%20Markdown%20(PO)%20as%20TD-Configuration.png?alt=media&amp;token=d4e1c7df-b325-4203-a1d8-e7f3bb0c01e9" alt=""><figcaption><p>Let's keep this feature enable and observe it's impact.</p></figcaption></figure>

### **Define Markdown Percentage:**

* Navigate to the Setups/Party Wise Settings and the click on "Setup Supplier + Company + Group/Item Wise Markdowns for PO"
* Define the details accordingly.
  * To Learn more about this option [<mark style="color:green;">CLICK HERE.</mark>](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/setups/party-wise-settings/setup-supplier-+-company-+-group-item-wise-markdowns-for-po.md)

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F28sGvPSQgyao7raG0fsx%2FMarkdown%20details.png?alt=media&amp;token=fd671e0c-c0fe-43c9-bbec-c1a19cbee95f" alt=""><figcaption><p>This is how you will define the details.</p></figcaption></figure>

### **Observe Impact in Purchase:**

* Click on **Retrieve Purchase Order**.
* The **Markdown as TD** is automatically fetched.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F1VxtDg934aCHH1NrePpA%2FTD%20Retirved.png?alt=media&amp;token=673de004-021a-46c5-b452-00a9f52e80bd" alt=""><figcaption><p>As you can see, the markdown percentage has been successfully retrieved in TD.</p></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-learning-hub-tutorials-and-best-practices/setups/configurations/purchase-voucher-configurations/other-settings-1/pick-party+company+group-wise-markdown-po-as-td.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.
