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
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: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
Customer account grouping
Customer account grouping
Create portfolios to group all accounts belonging to a single customer:
- Portfolio:
Customer-12345with Entity ID linking to your CRM - Contains: Checking account, savings account, investment accounts
- Use metadata for customer tier, relationship manager, onboarding date
Product-based organization
Product-based organization
Organize accounts by financial product:
Checking Accounts Portfolio- All customer checking accountsSavings Accounts Portfolio- All customer savings accountsBusiness Accounts Portfolio- All commercial/business accountsInvestment Accounts Portfolio- All investment-related accounts
Institutional portfolios
Institutional portfolios
Group accounts by institution or partner:
Partner Bank A- Accounts related to Partner Bank A operationsPartner Bank B- Accounts for Partner Bank B integration- Use Entity ID to link to partner identifiers in your system
Operational grouping
Operational grouping
Create portfolios for operational purposes:
Treasury Operations- Internal treasury and liquidity accountsSettlement Accounts- Accounts used for settlement operationsSuspense Accounts- Temporary holding accounts for reconciliationFee Collection- Accounts for collecting and managing fees
Best practices
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.
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.
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.
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.
Portfolios vs Segments
Both Portfolios and Segments help organize accounts, but they serve different purposes:
| Feature | Portfolio | Segment |
|---|---|---|
| Purpose | Group related accounts as a unit | Classify accounts by category |
| Entity ID | Yes - links to external entities | No |
| Use Case | Customer accounts, product grouping | Departmental, regional classification |
| Relationship | One-to-many (portfolio contains accounts) | Many-to-many (accounts tagged with segments) |

