> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/tour/customer-management/account-hierarchies.md). # Account hierarchies Bunny allows you to organize accounts into hierarchies. The illustration below shows how Acme has two child accounts, one of which also has two child accounts.
In this example, all child accounts propagate their invoices to the root account, Acme. ### Building a hierarchy Use the `...` menu on the account form to either create a child account or assign a parent account.
**Assign parent account** opens the modal below.
Once an account is part of a hierarchy, a **Hierarchy** tab will appear on the account form, which shows en entire hierarchy as a tree. Here you can also specify which account receives the invoice or whether the account is using an ancestor account's payment method for its own invoices.
### Delegating invoicing Accounts in a hierarchy can have different billing days. When an account delegates its invoicing to another account, the invoice is forwarded immediately upon generation. If the target account doesn't have consolidated billing enabled, it's also emailed immediately. If consolidated billing is enabled, the invoice is held and included in the target account's next invoice on its billing day. ### Using parent account's payment method Instead of delegting invoicing to another account, you can choose to let a child account use the payment method of another account in the direct path up the hierarchy. ### Restrictions Certain restrictions apply in an account hierarchy. * All accounts must belong to the same entity * All accounts must have the same billling currency * Invoice delegation can only go up in the hierarchy to a direct ancestor * No cyclical references are allowed --- # 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://docs.bunny.com/guide/tour/customer-management/account-hierarchies.md?ask=&goal= ``` `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.