Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Key Principles

Principle

Decision / Discussion

Portfolio Level

  • All relevant master data for a portfolio can be fetched in a single call

Mandate/Client Level

  • If a mandate or a client is implemented via multiple (custody) portfolios and the reporting should be provided on the mandate/client level, the master data call should also deliver information on mandate level in the same format

Consolidation Level

  • If a reporting should be producing a consolidated view over multiple mandates, the master data call should also deliver information on the consolidation level in the same format

  • Additionally the structure of the consolidation (list of portfolios / mandates) should be contained in the data

Interface "PortfolioMasterData"

Usage

Query portfolio master data to provide input for

  • Report covers (client name), headers/footers

  • Portfolio information blocks (e.g. PI001)

  • Performance charts (determination of performance periods, see below)

  • Footers/Header of report

Data Contents

  • performanceMeasurementStartDate

  • portfolio strategies (different types, including target weight, bandwiths, index/benchmark)

  • reporting legal entity -> controls disclaimer-text

  • Portfolio contacts for pm (portfolio manager), cpm, rm (including pictures)

  • Information about sub-portfolios (for consolidation of mandates or mandates implemented by multiple custody portfolios)

  • etc.

Parameters

  • portfolioId

  • reportingDate

Reporting Business Logic

  • determination of periods to report portfolio performance as well as benchmark performance (e.g. performanceMeasurementStartDate)

Schema

Example



  • No labels