---
title: Account Hierarchy
slug: account-hierarchy
docTags: 
createdAt: 2026-09-18T04:03:34.748Z
---

Monoova lets you create different hierarchies within your account.

- **mAccount: **The main central repository of funds. It stores configuration, permissions, authentication tokens, and the main balance.
- **Ledger Accounts**: Sub-accounts that store and segregate customer funds independently, with their own BSB and account number.
- **Virtual Account Numbers / PayIDs: **Unique identifiers and payment methods linked to your mAccount or ledger accounts to receive real-time payments from customers.

## How it works

The diagram below shows how the structure nests inside Monoova: 
Company → mAccount → (optionally Ledgers) → Virtual accounts → PayIDs

![](https://api.archbee.com/api/optimize/Bdjf3QgVQAMLM5ajfBYwb/KGE-hRn0HWMuBDe6EQM8V_screenshot-2026-09-18-135644.png)

## Layer by layer

::::WorkflowBlock
:::WorkflowBlockItem
**Your company (Monoova Portal sign in) **— the top-level customer entity. Access at this level is via Portal login.
:::

:::WorkflowBlockItem
**mAccount** — the funded account. Two things are attached to it in both branches:

- Available funds balance.
- API Key — access is scoped per mAccount, not per company. Portal login is company-wide, but each mAccount carries its own API Key, so integrations are isolated per mAccount.
:::

:::WorkflowBlockItem
**Ledger** — an mAccount can have *1\:N* to Ledgers. Each ledger holds its own balance, and the ledger balance is separate to the parent mAccount balance.
:::

:::WorkflowBlockItem
**Virtual Accounts** — the addressable receiving identity (BSB and account number). These addresses do not hold balances unless linked to a ledger.

- **Ledger-based setup**: Ledger *1:1* to Virtual Account — exactly one Virtual Account per ledger. In this set up the ledger effectively tracks the balance and transaction history for the virtual account.
- **Virtual Account-only setup**: mAccount *1\:N *to Virtual Accounts — many Virtual Accounts can connect straight off the mAccount, and none of them holds a balance. All inbound funds will settle to the mAccount balance in this case.
:::

:::WorkflowBlockItem
**PayID **— each Virtual Account can have *1\:N* to PayIDs. A single Virtual Account can have multiple PayIDs aliases. 
:::
::::

****