> 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/dineplan/backoffice/accounts/account-types.md).
# Account Types
### **Overview**
The Account Types feature allows administrators to create and manage categories used to classify accounts in the Back Office. Account types help organize accounts based on their purpose, such as Receivables, Purchase, Payable, Sales, Payment, Discount, Member, Income, and Expense.
Administrators can add new account types, edit existing ones, delete unnecessary account types, and change their display order to maintain an organized account structure.
### **Screen Elements**
| **Screen Element** | **Description** |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Account Type List | Displays the available account types, such as Receivables, Purchase, Payable, Sales, Payment, Discount, Member, Income, and Expense. |
| Search | Allows you to search for a specific account type. |
| Add Account Type | Opens the screen to create a new account type. |
| Edit Account Type | Allows you to modify the selected account type. |
| Delete Account Type | Allows you to delete the selected account type after confirmation. |
| Sort Account Types | Opens the sorting window where account types can be reordered by dragging them. |
| OK | Saves the new order of account types in the sorting window. |
| Cancel | Closes the sorting window without applying the changes. |
| Close | Closes the Account Types screen. |
### **Working**
#### **Add Account Type**
1. Open “Account Types” from the Back Office.
2. Select "Add Account Type”.
3. Enter the required account type “Name”.
4. Select the “Filter type” for the account type.
5. Select the “Rules”.
6. Add the tags, if any.
7. Select “Save” to add the account type to the list.
#### **Edit Account Type**
1. Select the account type you want to modify.
2. Select “Edit Account Type".
3. Update the account type details as required.
4. Save the changes.
#### **Delete Account Type**
1. Select the account type you want to remove.
2. Select "Delete Account Type”.
3. A confirmation message is displayed.
4. Select “Yes” to delete the account type or "No” to cancel.
#### **Sort Account Types**
1. Select “Sort Account Types”.
2. In the Sort Account Types window, drag the account types to the required order.
3. Select “OK” to apply the new order.
### **Use Case**
* Create new account categories when additional account classifications are required.
* Modify existing account types when their names need to be updated.
* Remove account types that are no longer required.
* Reorder account types to organize the list according to operational requirements.
### **Notes**
* Enter a name before saving a new account type.
* The Account Type field is required when creating an account type.
* Deleting an account type requires confirmation.
* Use Sort Account Types to change the display order of account types.
* Drag and drop the account types to arrange them in the required order.
* Select OK in the sorting window to apply the new order.
* Select Cancel if you do not want to apply the sorting changes.
* Use the Search field to quickly locate an account type.
* Existing account types can be edited or deleted from the Account Type List.
---
# 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/dineplan/backoffice/accounts/account-types.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)
