> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/purchase/purchase-module/masters/supplier-terms-and-condition.md).
# Supplier Terms and Condition
The **Supplier Terms and Condition** feature is used to define and maintain specific terms and conditions for suppliers. These terms can be applied during Purchase Order processing and supplier transactions.
## Steps to Create Supplier Terms and Condition
Step 1: Navigate to the **Purchase** main menu from the dashboard.
1. In the **Purchase** menu, click on **Masters**.
2. Select **Supplier Terms and Condition** from the sub-menu.
* The Supplier Terms and Condition entry screen will appear.
Step 2: Click on the **Open** button.
Step 3: Select the required **Type** from the available list.
1. Select the appropriate **Supplier Name**.
* These details determine the supplier and category for which the terms and conditions will be applied.
Step 4: After selecting the supplier, enter the required **Terms and Conditions** in the provided text area.
1. Review the entered details carefully to ensure accuracy.
Step 5: Click on the **Save** button.
* The Supplier Terms and Condition details will be saved successfully.
---
# 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://help.rbsgo.com/purchase/purchase-module/masters/supplier-terms-and-condition.md?ask=&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.
