> ## 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 order to configure the Midaz Module so each screen has the prerequisites it expects.

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/lerian-console/midaz-console/midaz-console-onboarding) if this is your first setup, or go directly to [Creating an Organization](/en/lerian-console/midaz-console/creating-an-organization) if the organization already exists and you are adding another one.
  </Step>

  <Step title="Create your first Ledger">
    The Ledger is the workspace where balances, accounts, and transactions live. Nothing downstream works without it.

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

  <Step title="Review Ledger settings">
    Decide whether the ledger will enforce account type validation and other structural rules before users start creating accounts.

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

  <Step title="Create Assets">
    Assets define what unit of value the ledger can move, such as `BRL`, `USD`, or a custom token.

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

  <Step title="Create Account Types">
    If your ledger uses type validation, define the account classes that can be selected later in account creation and routing.

    Go to [Creating an Account Type](/en/lerian-console/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/lerian-console/midaz-console/creating-an-account).
  </Step>

  <Step title="Add Portfolios, Segments, Holders, and Aliases when needed">
    These are supporting structures. They help classify or identify accounts, but they are not the first thing to configure unless your workflow depends on them.

    Use:

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

  <Step title="Create Accounting Routes">
    Routes define which accounts can participate in an operation and how entries are recorded.

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

  <Step title="Create Transactions">
    Only create transactions after the ledger has at least one asset, the required accounts, and a route model that matches the intended movement.

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

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

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

## Fast path by goal

***

<CardGroup cols={2}>
  <Card title="I need my first working ledger" icon="play" href="/en/lerian-console/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/lerian-console/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/lerian-console/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/lerian-console/midaz-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">
    Every Account must be linked 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>
  If you are documenting or training a client team, teach the setup in this order first. The CRUD pages become much easier once the dependency chain is explicit.
</Note>