Portfolio

A financial portfolio made up of multiple positions (holdings) in several instruments. Contrast this with e.g. the InstrumentList type, which is just a list of instruments.

This is a good example of how types can be composed and extended with extra properties to define more complex types.

The Portfolio type consists of an array of Position types, each of which refers to a single Instrument and a holding amount for that instrument.

The portfolio schema does not explicitly include identifiers in the id section, as there bis not a common standard for such identifiers. Applications can, however, populate this part of the contract with custom identifiers if so desired.

Schema

https://fdc3.finos.org/schemas/next/context/portfolio.schema.json (github)

Type

fdc3.portfolio

Properties

positions (required)

type: array

Items

type: Position

The List of Positions which make up the Portfolio

id

type: object

Additional Properties

type: string

One or more identifiers that refer to the portfolio in an OMS, EMS or related system. Specific key names for systems are expected to be standardized in future.

name

type: string

An optional human-readable name for the portfolio

Example

{
  "type": "fdc3.portfolio",
  "positions": [
    {
      "type": "fdc3.position",
      "instrument": {
        "type": "fdc3.instrument",
        "id": {
          "ticker": "AAPL"
        }
      },
      "holding": 2000000
    },
    {
      "type": "fdc3.position",
      "instrument": {
        "type": "fdc3.instrument",
        "id": {
          "ticker": "MSFT"
        }
      },
      "holding": 1500000
    },
    {
      "type": "fdc3.position",
      "instrument": {
        "type": "fdc3.instrument",
        "id": {
          "ticker": "IBM"
        }
      },
      "holding": 3000000
    }
  ]
}