Portfolio Type

Table of Contents

• Description
• Examples
• Cookbook
• F.A.Q.
• API Documentation

Description

Financial meaning

Portfolio Type has no specific financial meaning, it's a logical configure-defined classification of the portfolios, help to differentiate manual portfolios from transaction and position based portfolios.

Platform abstraction

Portfolio Type is an entity designed as a criterion for comparing portfolios against each other, defining configured-defined groups with the Portfolio Classes. Portfolio Classes represents the primary attribute, with pre-defined classes for reconciliation calculation and filtering purposes in the reports, entity viewers:

• General Portfolio: Consists of banking transactions and/or a combination of initial positions and banking transactions.
• Manual Managed Portfolio: Managed through manual transaction booking within the system or imported from the client's internal manual tracking systems for bank verification purposes.
• Position Only Portfolio: Focuses on importing balance states for a specific day using Daily Positions/Cash transaction types.

It's used in:

• reconciliation using portfolio and portfolio reconcile group. 

Examples

• User code: workspace-unique identifier of the portfolio type with source prefix 

• Portfolio class: classification used to define general behavior or usage category of the portfolio (e.g., General, Manual Managed)

• Short name: compact label shown in lists and relations for easier navigation

• Name: full descriptive name of the portfolio type

• Public name: label shown to users without configuration access; often used in reports

• Notes: optional custom description or comment field for internal purposes

• Configuration code: reference to the configuration source that governs the behavior of this portfolio type

Cookbook

CRUD

• Create: A new portfolio type can be created using the "+" button in the upper-right corner of the page. Users must provide the configuration code, user code, portfolio class, short name, name, public name, and optional notes.
• Read: The same page provides a list of all existing portfolio types. Users can search, filter, and review attributes such as class, names, and configuration references.
• Update: To edit a portfolio type, users can click on an existing entry to open the edit form. All fields—except those constrained by platform rules—can be modified, including the classification and public-facing labels.
• Delete: Portfolio types can be deleted directly from the management page.

Use Cases

• Portfolio Types help categorize portfolios by behavior, such as whether they are general-purpose, manually managed, or used solely for reconciliation. These classifications are leveraged in reporting filters and entity viewers.
• Fields like Short Name and Public Name allow different representations for internal use and external presentation. This is useful in environments where access permissions differ across user roles.

F.A.Q.

Frequently asked questions.

API documentation

Link to API documentation.