Skip to main content

Portfolio Type

Table of Contents

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:

Examples

User code Portfolio class Short name Name Public name  Notes  Configuration code
com.finmars.standard-other:portfolios.portfoliotype:general General Portfolio General Portfolio General Portfolio

com.finmars.standard-other

  • 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

Operations within platform.

Use Cases

What for it's used.

F.A.Q.

API documentation

Back to top