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

---

1. Create your Organization

   Start with the legal and operational owner of the environment.

   Use Midaz Module onboarding if this is your first setup. If the organization already exists and you want to add another, go directly to Creating an Organization.

2. Create your first Ledger

   The Ledger is the workspace where balances, Accounts, and Transactions are scoped.

   Go to Creating a new Ledger.

3. 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, or update them later from Managing Ledgers.

4. 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.

5. Create Account Types

   Define Account Types when your configured Account or Route rules need those classifications.

   Go to Creating an Account Type.

6. Create Accounts

   Accounts hold balances and are the source or destination of transactions.

   Go to Creating an Account.

7. 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
   • Creating a Segment
   • Creating a Holder
   • Creating an Alias Account
8. 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.

9. 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.

10. 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.

Fast path by goal

---

I need my first working ledger

Use onboarding, then create at least one Asset and one Account.

I need to model account structure

Start with Ledger settings, Account Types, Accounts, and Segments.

I need to control how money moves

Create the accounts first, then define Accounting Routes and test with a transaction.

I need to estimate fees

Enable Fees Engine only after the core ledger structure is already in place.

Common sequencing mistakes

---

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.

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.

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.

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.

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.