> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup path

> Follow the recommended setup order for the Midaz Module so each Console screen has the Organization, Ledger, Assets, and Accounts it depends on.

The Midaz Module is easier to configure when you follow the dependency order the product expects. Most user confusion comes from trying to create Accounts, Routes, or Transactions before the structural pieces already exist.

## Recommended order

***

<Steps>
  <Step title="Create your Organization">
    Start with the legal and operational owner of the environment.

    Use [Midaz Module onboarding](/en/midaz/console/midaz-console-onboarding) if this is your first setup. If the organization already exists and you want to add another, go directly to [Creating an Organization](/en/midaz/console/creating-an-organization).
  </Step>

  <Step title="Create your first Ledger">
    The Ledger is the workspace where balances, Accounts, and Transactions are scoped.

    Go to [Creating a new Ledger](/en/midaz/console/creating-a-new-ledger).
  </Step>

  <Step title="Review Ledger settings">
    Decide whether to enable Accounting Route validation before users start creating Transactions. This setting is optional and defaults to `false`.

    You can configure these settings while creating the Ledger in [Creating a new Ledger](/en/midaz/console/creating-a-new-ledger#ledger-settings), or update them later from [Managing Ledgers](/en/midaz/console/managing-ledgers-via-console#ledger-settings).
  </Step>

  <Step title="Create Assets">
    Assets define a unit of value for the Organization, such as `BRL`, `USD`, or a custom token. Accounts reference an Asset when you create them.

    Go to [Creating an Asset](/en/midaz/console/creating-an-asset).
  </Step>

  <Step title="Create Account Types">
    Define Account Types when your configured Account or Route rules need those classifications.

    Go to [Creating an Account Type](/en/midaz/console/creating-an-account-type).
  </Step>

  <Step title="Create Accounts">
    Accounts hold balances and are the source or destination of transactions.

    Go to [Creating an Account](/en/midaz/console/creating-an-account).
  </Step>

  <Step title="Add Portfolios, Segments, Holders, and Aliases when needed">
    These are persisted support structures. Configure them when your workflow needs ownership context, grouping, fee resolution, or scoped rules.

    Use:

    * [Creating a Portfolio](/en/midaz/console/creating-a-portfolio)
    * [Creating a Segment](/en/midaz/console/creating-a-segment)
    * [Creating a Holder](/en/midaz/console/crm-creating-a-holder)
    * [Creating an Alias Account](/en/midaz/console/crm-creating-alias-account)
  </Step>

  <Step title="Create Accounting Routes">
    Accounting Routes define optional participant and posting rules. Midaz applies them when route validation is enabled.

    Go to [Creating an Accounting Route](/en/midaz/console/creating-an-accounting-route).
  </Step>

  <Step title="Create Transactions">
    Create Transactions after the Organization has an Asset and the Ledger has the required Accounts. A matching Accounting Route is required only when route validation is enabled.

    Go to [Creating a Transaction](/en/midaz/console/creating-a-transaction).
  </Step>

  <Step title="Enable plugins after core setup is stable">
    Capabilities such as Fees Engine extend behavior. Turn them on after the base ledger model is already clear.

    Go to [Midaz module settings](/en/platform/console/plugin-settings).
  </Step>
</Steps>

## Fast path by goal

***

<CardGroup cols={2}>
  <Card title="I need my first working ledger" icon="play" href="/en/midaz/console/midaz-console-onboarding">
    Use onboarding, then create at least one Asset and one Account.
  </Card>

  <Card title="I need to model account structure" icon="layer-group" href="/en/midaz/console/creating-an-account-type">
    Start with Ledger settings, Account Types, Accounts, and Segments.
  </Card>

  <Card title="I need to control how money moves" icon="route" href="/en/midaz/console/creating-an-accounting-route">
    Create the accounts first, then define Accounting Routes and test with a transaction.
  </Card>

  <Card title="I need to estimate fees" icon="calculator" href="/en/midaz/fees/console/managing-fee-calculations">
    Enable Fees Engine only after the core ledger structure is already in place.
  </Card>
</CardGroup>

## Common sequencing mistakes

***

<AccordionGroup>
  <Accordion title="Creating an Account before creating an Asset">
    You must link every Account to an Asset. If the Asset does not exist yet, account creation stalls immediately.
  </Accordion>

  <Accordion title="Enabling Account Type validation before defining Account Types">
    This makes the type field mandatory, but the dropdown remains empty. Create the Account Types first or disable validation until they are ready.
  </Accordion>

  <Accordion title="Designing Accounting Routes before knowing the real accounts">
    Users often try to model routes too early. In practice, route rules are easier to define after the treasury, customer, fee, and settlement accounts already exist.
  </Accordion>

  <Accordion title="Trying to create Transactions before aliases or accounts are ready">
    Transaction creation depends on accounts being searchable and structurally valid. If operators cannot identify the source and destination accounts quickly, stop and fix the account model first.
  </Accordion>
</AccordionGroup>

<Note>
  When you document the setup or train a client team, teach this order first. The CRUD pages become much easier once the dependency chain is explicit.
</Note>