Skip to main content
Use Midaz Module to manage Portfolios that group your accounts. A Portfolio gives your accounts a higher-level structure. You manage a set of accounts as a single unit.

What are Portfolios?


A Portfolio is a container that groups related accounts within a ledger. In Midaz Module, portfolios enable you to:
  • Group related accounts - Organize accounts that belong together logically or operationally
  • Associate with external entities - Link portfolios to external system identifiers via Entity ID
  • Simplify account management - Manage multiple accounts as a cohesive unit
  • Add custom context - Store additional information through metadata for integration and reporting
Portfolios are ledger-specific. Each ledger has its own set of portfolios for your needs. For technical details about portfolios in Midaz, refer to the Portfolios documentation.

Accessing the Portfolios page


To open the Portfolios page, select the Portfolios option from the Accounts section of the left-side menu. The Portfolios page displays a table of all Portfolios in your Ledger.
If you have no Portfolios, the list is empty and shows a prompt to create your first Portfolio.

Available actions

From the Portfolios page, you can:

Create a Portfolio

Add a new portfolio to group your accounts

Edit a Portfolio

Update portfolio name and metadata

Delete a Portfolio

Remove a portfolio from your ledger

Common use cases


Create portfolios to group all accounts belonging to a single customer:
  • Portfolio: Customer-12345 with Entity ID linking to your CRM
  • Contains: Checking account, savings account, investment accounts
  • Use metadata for customer tier, relationship manager, onboarding date
Organize accounts by financial product:
  • Checking Accounts Portfolio - All customer checking accounts
  • Savings Accounts Portfolio - All customer savings accounts
  • Business Accounts Portfolio - All commercial/business accounts
  • Investment Accounts Portfolio - All investment-related accounts
Group accounts by institution or partner:
  • Partner Bank A - Accounts related to Partner Bank A operations
  • Partner Bank B - Accounts for Partner Bank B integration
  • Use Entity ID to link to partner identifiers in your system
Create portfolios for operational purposes:
  • Treasury Operations - Internal treasury and liquidity accounts
  • Settlement Accounts - Accounts used for settlement operations
  • Suspense Accounts - Temporary holding accounts for reconciliation
  • Fee Collection - Accounts for collecting and managing fees

Best practices


1

Plan your portfolio structure

Design your portfolio structure before you create accounts. Decide how to group the accounts and which Entity IDs to use for external systems.
2

Use Entity ID for integration

Set the Entity ID during creation when a portfolio links to an external system (CRM, core banking). External systems can then match the portfolio to their own records.
3

Choose meaningful names

Use portfolio names that clearly indicate the purpose or contents of the portfolio. This helps team members quickly understand the account organization.
4

Use metadata for context

Use the Metadata tab to store extra details. Add business unit codes, cost centers, or integration references that do not fit in the standard fields.
5

Keep portfolios focused

Each portfolio should have a clear purpose. Do not create catch-all portfolios. Instead, create a specific portfolio for each use case.

Portfolios vs Segments


Both Portfolios and Segments help organize accounts, but they serve different purposes: You can use portfolios and segments together to organize accounts. For example, accounts in a customer portfolio can also belong to a segment (checking, savings, investment).