Position Limits Aggregation Logic

Overview

In this article, we will discuss the aggregation logic for the Position Limits rules and the exceptions FundApps covers.

FundApps uses information available from exchange rulebooks to determine aggregation requirements because this data is not provided by FIA Tech. 

The default aggregation type is Legal, and the default aggregation level is Top unless there are exceptions. These exceptions are further explained below. 

The Legal structure serves as:

  1. A concept covering the different “roles” in which an entity/person may have an obligation. For example, beneficial owners.
  2. A superset of the Management and Voting structures

See this article for more information about how the Legal aggregation tree is used in Shareholding Disclosure. 

The aggregation level defines wherein the aggregation structure of the rule will potentially trigger disclosures. The Top-level will only trigger one disclosure, which will be an aggregation across all portfolios in a given aggregation structure (i.e., a disclosure will only trigger on the ultimate parent of the structure). 

This article contains more information about the different types of aggregation levels. 

Exceptions

As mentioned above, there are a few exceptions that FundApps covers:

  1. MiFID II
  2. Relationships the Manager has with an Exchange
  3. The Korea Exchange (XKRX)

MiFID II aggregation rules state that aggregation must occur at a portfolio level for certain:

  1. Organizations that meet the eligibility requirements
  2. Some or all portfolios that meet the eligibility requirements
  3. Some or all umbrellas that meet the eligibility requirements

The identification of these eligibility requirements lies with the client. By default, contracts are aggregated to the Top Entity. To implement these exceptions, FundApps will create a new aggregation structure and create an aggregation tree specifically for these rules. To learn more, you can contact FundApps Support.

For certain exchanges, there can be different limits on the same contract depending on the relationship the manager has with the exchange or the reasons they may be trading a contract. This is covered by the portfolio property ExchangeAccountType, which should be set at the Top-level Entity. See this Article for the different exceptions supported. Please note that depending on the above exceptions, ExchangeAccountType may need to be populated on different levels. 

The Korea Exchange aggregation rules state that aggregation must occur at the portfolio level. Specifically, the limits apply to individual client accounts and not the aggregated position they hold for multiple clients. In order to have results aggregate to each individual client account, FundApps will create client accounts represented as portfolios or umbrellas. To manage this exception, FundApps has Position Limits rules which aggregate at the portfolio level for assets listed on the Korea Exchange. To learn more, contact FundApps Support.

Was this article helpful?
0 out of 0 found this helpful
Share article