> 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/masters/main-master-module/master/party-sub-type-master.md).
# Party Sub Type Master
The **Party Sub Type** is a detailed classification under a Party Type that allows finer categorisation of business partners such as customers, suppliers, or vendors. It helps in accurate transaction handling, reporting, and accounting by distinguishing parties based on specific characteristics or business rules.
## Steps to Create a Party Sub Type
Step 1: Log in to the application.
1. Go to the **Settings** section from the main menu.
2. Under **Masters**, click on **Party Sub Type**.
* The Party Sub Type screen will open.
Step 2: Click on the **Add** button available on the screen.
* A new Party Sub Type entry form will open.
Step 3: Enter the required details in the respective fields.
1. Select the appropriate **Party Type**.
2. Enter the **Party Sub Type** name and other necessary information as required by the system.
* Ensure that all mandatory fields are filled correctly.
Step 4: Once all details are entered, click on the **Save** button.
1. The system will save the Party Sub Type 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/masters/main-master-module/master/party-sub-type-master.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.
.png?alt=media)
