Skip to main content
Use Midaz Module to manage Portfolios that group and organize your accounts. Portfolios provide a higher-level organizational structure for accounts, enabling you to manage collections 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, meaning each ledger can have its own set of portfolios tailored to your organizational 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 listing all Portfolios in your Ledger.
If you do not have any Portfolios, the list will appear empty with a prompt to create your first portfolio.

Available actions---

From the Portfolios page, you can:

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 hierarchy before creating accounts. Consider how accounts will be grouped and what Entity IDs you’ll use for external integration.
2

Use Entity ID for integration

When portfolios need to link to external systems (CRM, core banking, etc.), set the Entity ID during creation to enable seamless data synchronization.
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

Leverage metadata for context

Use the Metadata tab to store additional information like business unit codes, cost centers, or integration references that don’t fit in standard fields.
5

Keep portfolios focused

Each portfolio should have a clear purpose. Avoid creating catch-all portfolios; instead, create specific portfolios for different use cases.

Portfolios vs Segments


Both Portfolios and Segments help organize accounts, but they serve different purposes:
FeaturePortfolioSegment
PurposeGroup related accounts as a unitClassify accounts by category
Entity IDYes - links to external entitiesNo
Use CaseCustomer accounts, product groupingDepartmental, regional classification
RelationshipOne-to-many (portfolio contains accounts)Many-to-many (accounts tagged with segments)
You can use both portfolios and segments together for comprehensive account organization. For example, a customer portfolio might contain accounts that are also classified by segments (checking, savings, investment).