Skip to main content

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.

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

Create your Organization

Start with the legal and operational owner of the environment.Use Midaz Module onboarding if this is your first setup, or go directly to Creating an Organization if the organization already exists and you are adding another one.
2

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

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

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

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.
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 supporting structures. They help classify or identify accounts, but they are not the first thing to configure unless your workflow depends on them.Use:
8

Create Accounting Routes

Routes define which accounts can participate in an operation and how entries are recorded.Go to Creating an Accounting Route.
9

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

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.

​
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

Every Account must be linked to an Asset. If the Asset does not exist yet, account creation stalls immediately.
This makes the type field mandatory, but the dropdown remains empty. Create the Account Types first or disable validation until they are ready.
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.
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.
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.