> 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/front-office-module/fo-masters/faq-on-masters/how-do-i-create-a-new-company-profile.md).
# How do I create a new Company Profile?
To create a new Company Profile, also known as a **Company Master**, follow these steps:
1. **Navigate to the Company Master:** Go to the **Front Office** module, select **Masters**, then **Company Profile**, and click **New**.
2. **Fill in Address Details:** Under the **Address tab**, enter the company's location and contact details.
3. **Enter Account and GST Information:** Switch to the **Accounts tab** to fill in the **GST details** for the company.
4. **Select Company Type:** It is critical to select the **correct company type** so that settlements reflect accurately under that company.
5. **Enable Approval Status:** By default, a new company is marked as "unapproved." You must manually **change the status to "approved,"** or the system will not allow settlements to be taken for that company, even if it appears in the list.
6. **Save:** Click the save button to finalize the profile.
If you need to **deactivate** a company later, you can do so by opening the company record, selecting the company name, and disabling the active tick-box.
---
# 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/front-office-module/fo-masters/faq-on-masters/how-do-i-create-a-new-company-profile.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)