> For the complete documentation index, see [llms.txt](https://pivot-payment.gitbook.io/pivot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pivot-payment.gitbook.io/pivot-docs/account-and-balance-management/account-management.md).

# Account management

## Sub-account management

When you sign up for Pivot, you will receive a main account. A merchant that utilizes the Account and Balance management can manage multiple sub-account accounts to be managed. You can register your user and/or your customer's user as your sub-account.

A sub-account has a separate financial account that you can use to manage various transaction activities, from payments to pay out funds. For transactions that happened on the sub-account (for example: receiving payments or sending money out), will be recorded on their balance & ledger which is separated from the main accounts.&#x20;

## Account structure

<figure><img src="/files/SznjNVw5iK2xsekpyQ2Y" alt=""><figcaption><p>Your Business structure</p></figcaption></figure>

Your account acts as the main account. A main account is tied to Pivot through the business terms and agreement. All transaction fees of sub-account or Account and Balance management usage will be billed to the main account.

While your sub-account account — they are your user. You can manage and treat the sub-account account according to your preferences and business scenario, on top of some rules that were established by Pivot.

## Assign admin user for Sub-Account

After sub-account creation, you have the option whether to assign a user account related to your sub-account as admin and give them access to the Pivot Dashboard to manage their account or not. If you decide to give them access, the sub-account registered email will receive an email invitation and can use it to set up their Pivot account access.

## Account status

| Status      | Definition                                                                                                               |
| ----------- | ------------------------------------------------------------------------------------------------------------------------ |
| Created     | Sub-account has just been created and has not been activated yet. This will be applicable for KYC Sub-account Type only. |
| Active      | Sub-account account is ready to be used for transaction activity                                                         |
| Deactivated | Sub-account account is deactivated by main account / your request                                                        |
| Blocked     | Sub-account account is blocked due to various reasons                                                                    |
| Dormant     | Sub-account account is dormant and does not have any payment/payout activity in the past 90 days                         |
| Closed      | <p>Sub-account account is closed by main account<br><br>\*Note: Closed account can't be restored</p>                     |

<br>

<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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pivot-payment.gitbook.io/pivot-docs/account-and-balance-management/account-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
