> For the complete documentation index, see [llms.txt](https://docs.simptel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simptel.com/tf-platform/administration/organizations/billing/disable-a-billing-account.md).

# Disable a Billing account

This article provides an overview to disable a billing account.

### Steps to Disable a Billing Account

1. **Sign In to Your Account:**\
   Log in to your account on the TF Platform.
2. **Select Your Organization:**\
   If you belong to multiple organizations, choose the appropriate organization from the list.
3. **Navigate to Billing Settings:**\
   Go to the settings menu and select **Billing Accounts** under the **Billing** section.
4. **Select Your Billing Account:**\
   Choose the billing account you wish to disable.
5. **Initiate Closure:**\
   Look for the option to **Disable Billing Account** and follow the on-screen prompts.
6. **Confirm Closure:**\
   Review the consequences of closing your account and confirm your decision.
7. **Check for Confirmation:**\
   Ensure you receive a confirmation message or email verifying that your billing account has been successfully closed.

{% hint style="danger" %}
If you disable your active billing account, all services for linked projects will stop, and your data will be retained for **30 days**. After this period, the data cannot be recovered.
{% endhint %}

<br>


---

# 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://docs.simptel.com/tf-platform/administration/organizations/billing/disable-a-billing-account.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.