> 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/process-for-deactivating-a-company-profile.md).

# Process for deactivating a company profile

**What is the process for deactivating a company profile?**

To deactivate a **Company Profile**, follow these steps:

#### **Steps to Deactivate a Company Profile**

1. **Navigate to the Company Master:**\
   Go to **Front Office → Masters → Company Profile**.
2. **Select the Company:**\
   Click the **search** icon next to **Company Name** and select the company you want to deactivate.
3. **Disable Active Status:**\
   Clear the **Active** checkbox to deactivate the company profile.
4. **Save the Changes:**\
   Click **Save** to apply the changes.

#### **Important Considerations**

* **Approval Status:**\
  Deactivating a company makes it unavailable for active use. In addition, a company must be marked as **Approved** to be available for settlements. By default, newly created company profiles are **Unapproved** and cannot be used for settlements until they are approved.
* **Company Type:**\
  Ensure the correct **Company Type** (such as **Corporate**, **Travel Agent**, or **Credit Card**) is selected, as it affects billing, settlements, and reporting.
* **Sales Executive Linking:**\
  Company profiles can be linked to **Sales Executives** to help track corporate accounts, performance, and revenue contributions.


---

# 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/process-for-deactivating-a-company-profile.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.