> 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/po-terms-and-conditions.md).
# PO Terms & Conditions
The **PO Terms & Conditions** master is used to define and manage standard purchase terms that apply to Purchase Orders (POs).
## **Steps to Create PO Terms & Conditions**
Step 1: Navigate to the **Purchase** main menu from the dashboard.
1. Click on **Masters**.
2. From the Masters menu, select **PO Terms & Conditions**.
* The **PO Terms & Conditions** screen will be displayed.
Step 2: Click on the **Open** button.
Step 3: Select the required **Purchase Terms,** From the available drop-down list.
* After selecting the purchase terms, the system will display the selected terms on the screen.
Step 4**:** Click on the **Add** button.
1. Enter the **Terms Name** in the provided field.
* Ensure the terms name is clear, meaningful, and relevant to the purchase condition.
Step 5: After entering the required details, click on the **Save** button.
* The system will successfully save the PO Terms & Conditions.
---
# 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/po-terms-and-conditions.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.
