​
Optimal hierarchy of Organizations and Ledgers

​
Single vs. multiple Organizations

Banks operating as a single legal entity typically require one Organization in Midaz. However, for banking groups with subsidiaries, a hierarchical structure is recommended, with a parent organization overseeing multiple child organizations. This setup aligns with corporate governance and enables data segregation per entity.
NoteThe organization structure should reflect your corporate structure.

​
Using multiple Ledgers

Within an organization, determine the number of ledgers to use based on operational needs. A common approach is to maintain a primary ledger for customer transactions while using additional ledgers for specialized purposes, such as treasury operations or regulatory segmentation.
NoteUse multiple ledgers only when necessary to minimize complexity. Transfers between ledgers require external flow orchestration via APIs.

​
Efficient account structuring for retail and corporate banking

​
Retail customers – Portfolio per customer

For retail banking, best practice is to create a Portfolio for each customer, containing individual accounts for different asset types (e.g., checking, savings, credit card). This setup allows efficient balance retrieval and streamlined operations.
TipUse the CRM plugin to manage personal data such as tax IDs, addresses, and banking aliases — all in one place.

​
Corporate clients – hierarchical accounts

For corporate banking, utilize child accounts within portfolios to reflect internal structuring. A company might have a parent account for its main funds and child accounts for subdivisions like payroll or expense tracking.

​
Internal accounts

Establish internal accounts for revenue, expenses, and settlement flows. Dedicated accounts for “Fee Income – USD” or “Interest Expense – USD” ensure clear financial reporting.