Skip to main content

Major: Japan Rule Explained

Updated today

Overview

The Major: Japan rules include functionality for the Special Reporting System (SRS), co-holders, base dates, and stock lending. Additionally, we have established a link between the top entity and sub-entities acting as co-holders, allowing FundApps to anchor shareholding levels whenever a disclosure is made.

This article provides a plainspoken explanation of the nuances of the Major: Japan rules, including swinging thresholds, aggregation exemptions, and diluted denominators.

If you require further clarification, please contact your Client Success Manager or FundApps Support.

Key Terminology

  • Special Reporting System (SRS) - Applies to certain institutional investors who trade securities without the intention of materially affecting changes in the business activities of the issuer. SRS investors are only obligated to report their holdings on base dates, which can be 2 to 3 times a month. It is also important to note that SRS is applicable only when holdings are between 5% and 10%.

  • Base Dates - SRS investors can choose to report on either (i) the second and fourth Mondays of every month (in a month that has a fifth Monday, the second, fourth, and fifth Mondays) or (ii) the 15th day and the last day of every month.

  • Co-holders - Co-holders or joint holders are entities with a relationship in which they are likely to jointly exercise the voting rights of a company. Within FundApps, co-holders are recognised as entities with portfolios holding the securities. As illustrated below, in a multi-layered aggregation tree, the middle entities do not need to disclose.

    Multi-layered aggregation tree diagram showing how orange-shaded entities are considered co-holders while middle entities do not require disclosure.
  • Swinging Thresholds - Major: Japan rules use swinging thresholds. Meaning that a disclosure is made when there is a >1% movement from the last disclosure. For example, the first disclosure is made at 5.1%, which means that another disclosure will be made only if your holdings go between <4.1% or >6.1%.

    Line graph titled Swinging Thresholds showing a blue base threshold line and an orange position line moving from 4.9% to 6.5%.

Day 1

Day 2

Day 3

Day 4

Day 5

Position

4.9%

5.1%

5.6%

6.5%

5%

% Change

0%

0.2%

0.6%

1.5%

0.6%

Disclosure

No Disclosure

Initial Disclosure

No Disclosure

Subsequent Disclosure

No Disclosure

  • Anchor Points - After a disclosure is made, the holdings of the top entity and co-holders must be anchored, and the swinging thresholds will be based on those anchor points.

The Rules

There are 8 rules in total covering Major: Japan, divided into four for SRS clients and four for non-SRS clients. The rules are:

MajorJP: Non-SRS

  • MajorJP-Top-NonSRS

  • MajorJP-Top-Complement-NonSRS

  • MajorJP-Entities-NonSRS

  • MajorJP-Entities-Complement-NonSRS

MajorJP: SRS

  • MajorJP-Top-SRS

  • MajorJP-Top-Complement-SRS

  • MajorJP-Entities-SRS

  • MajorJP-Entities-Complement-SRS

Please note that, in addition to the aforementioned eight rules, the rule engine relies on the Major: Japan - Diluted Denominator rule to produce accurate results (please see details below for more information). Furthermore, clients can monitor a lending change of 1% or more using the Major: Japan - Lending/Lending Prime rules, which are also explained in more detail below.

Rules Execution

The rules engine relies on a specific sequence to calculate accurate results, including the Diluted Denominator rule.

Flowchart showing execution order starting with Denominator Rule, followed by Lending-Prime, then branching into SRS and Non-SRS entity checks.

How the Rules Function

Initial Disclosure (When Shareholdings First Breach 5%)

Example:

Flowchart titled 'The rules check for 1% changes' starting with a check for the MajorJP-Top rule. If 'Yes', a disclosure is triggered via the Entities-Complement rule. If 'No', the system checks for a 1% co-holder movement; a 'Yes' triggers the Entities-Complement and Top-Complement rules, while a 'No' results in no disclosure.

For Movements Between 5% to 10%

The new rules check if there is a ≥1% movement at either the top entity or co-holder level. If there are, disclosures will be made at both levels. It also registers the new shareholding levels of the co-holders if there is a disclosure at the top entity or vice versa.

Flowchart titled 'The rules check for 1% changes' starting with a check for the MajorJP-Top rule. If 'Yes', a disclosure is triggered via the Entities-Complement rule. If 'No', the system checks for a 1% co-holder movement; a 'Yes' triggers the Entities-Complement and Top-Complement rules, while a 'No' results in no disclosure.

Example 1:

Aggregation diagram showing Top Entity movement from 6% to 6.7%. A disclosure is triggered because a co-holder's position moved by 1%, establishing new anchor points for both levels.

Example 2:

Diagram showing a Top Entity position rising from 6% to 7%. This 1% movement triggers an aggregated disclosure at the top level and an Entity-Complement disclosure for all co-holders to reset anchors.

Exit Disclosures (Shareholdings >10%)

As mentioned above, investors who qualify for SRS have less onerous reporting requirements when their shareholding is between 5 and 10%. Shareholding disclosure will default to normal if your shareholding exceeds 10%. Upon re-entry to the SRS range, FundApps will revert to base date reporting once a disclosure is made within the SRS range, i.e. on the next base date.

Exit Disclosures (From >5% to Below 5%)

Graph titled Exit Disclosure showing a position falling below 5%; disclosure is only triggered on Day 4 when the 1% movement is confirmed.

Day 1

Day 2

Day 3

Day 4

Position

5.5%

4.9%

5.5%

4.5%

% Change

0%

0.6%

0.6%

1%

Disclosure

Initial Disclosure

No Disclosure

Disclosure

Disclosure

Example 1:

Diagram showing an exit disclosure triggered when the aggregated position moves from 5.6% to 4.5%, exceeding the 1% movement requirement.

Example 2:

Flowchart titled 'The rules check for 1% changes' starting with a check for the MajorJP-Top rule. If 'Yes', a disclosure is triggered via the Entities-Complement rule. If 'No', the system checks for a 1% co-holder movement; a 'Yes' triggers the Entities-Complement and Top-Complement rules, while a 'No' results in no disclosure.

How to Set Up Base Dates Reporting for SRS-Qualified Investors

Clients who are SRS-qualified should activate the SRS set of rules and provide base dates in the rule properties field.

Accessing the Rule Properties Menu

Log in to your environment and navigate to the Portfolios & Entities screen via the folder icon located in the top right corner of the navigation bar.

Select any of your existing portfolios, entities, or umbrellas, and then click the Rule Properties tab on the left-hand side of your screen.

Disclosure Requirements for SRS-Clients

Disclosure requirements for SRS-clients only differ when their holdings are between 5 and 10%. In that range, they are only required to disclose on-base dates. If you exceed 10%, the shareholding disclosure requirements revert to normal (just like non-SRS clients).

Three-panel diagram showing SRS reporting logic: Panel 1 (T=0) shows an initial disclosure at 5.6% on a base date. Panel 2 (T=1) shows no disclosure despite a move to 6.7% because it is not a base date. Panel 3 (T=2) shows a disclosure at 7% because it is a base date and the movement exceeds 1%.

If your holdings exceed 10% and then return to between 5% and 10%, you will be prompted to disclose. Subsequently, you would return to reporting on base dates.

Timeline showing three stages: Purple (t=0) for holdings between 5-10% (base date reporting); Orange (t=1) for breaching 10% (normal daily reporting); and Grey (t=2) for re-entry into the 5-10% zone. The note explains that FundApps reverts to base date reporting only after a manual disclosure is filed upon re-entry.

0.1% Mandatory Exemption from Aggregation for Controlled Undertakings

What Is the Exemption?

Any individual co-holders with holdings of Japanese shares less than 0.1% are exempted from aggregation.

Who Does the Exemption Apply To?

There are two different types of co-holder arrangements, controlled undertakings and concert parties. The mandatory exemption applies only to co-holders in a controlled undertaking arrangement.

Controlled Undertaking describes co-holders who are under the control of the parent company (the parent company holds >50% of the voting rights in the subsidiary) and will typically transact and vote according to the parent company's discretion.

Concert Parties describes co-holders who have jointly agreed to transact or vote (most likely when the parent only has a minority of the voting rights in the subsidiary).

As the label 'mandatory' suggests, if co-holders are in a controlled undertaking arrangement, the exemption must be applied.

Diagram showing how an entity holding 0.05% is excluded from the 6% top-level aggregation when the mandatory 0.1% exemption is applied.

Setting Up in FundApps

We assume that most clients have entities that are controlled undertakings. Hence, by default, if you approve the new rule, the exemption will apply.

For clients with a concert parties arrangement, please specify 'NotJPAggExempt' in the CompanyType list for each entity, including the top entity.

Exceptions Not Accounted For

The rule limits the maximum exemption to 1%. However, we have not accounted for that in our rule because we believe that it is unlikely to happen.

Scenario 2 shows when the calculated figure may be incorrect.

Scenario 1:

We have 12 entities. 1 entity holds 4.5%, and 11 entities each hold 0.09%.

Aggregated result: 5.49% (4.5% + 11*0.09%).

FundApps result: 4.5% correct result.

Scenario 2:

We have 13 entities. 1 entity holds 4.5%, 12 entities hold 0.09% each.

Aggregated result: 5.58% (4.5% + 12*0.09%) correct result.

FundApps result: 4.5%.

In scenario 2, the total holdings from entities with <0.1% each are 1.08%. However, FundApps does not factor in that part and still applies for the exemption.

Major: Japan - Diluted Denominator

In short, if a client holds shares and convertible instruments in a Japanese issuer, the Major: Japan - Diluted Denominator rule will ensure that the denominator for this issuer is increased accordingly.

When calculating the denominator, all Major: Japan rules require the total number of convertible instruments (which convert into unissued shares) held by an investment manager to be added to the total number of issued shares of an issuer. The Major: Japan - Diluted Denominator rule is used to calculate that additional part of the diluted denominator. Please note that the rule calculates the diluted denominator at the group level - therefore, if any group entity holds relevant convertibles, the denominator will be increased accordingly for all group entities.

The 1% Lending Rule

The memo suggests that lending of 1% or more is considered a material change. We have coded our rules to look at lent securities on an aggregated basis and trigger a disclosure if there is a 1% or greater change in lent positions since the last disclosed value.

Please note: for the lending rules to work, both SRS and non-SRS rules have to be activated. This means you should have 11 Major: Japan rules activated in total.

The illustrations below explain how the two lending rules work in conjunction with the existing rules.

Logic flowchart for Lending-Prime Rule 1412, checking for a Top rule trigger and a 1% lending change since the last disclosure.
Logic flowchart for Lending-Prime Rule 1421, assessing if Top or Complement rules have already triggered to prevent duplicate alerts.

Converting a Non-Disclosure Result into a Disclosure

Our Major: Japan rules have been updated to allow clients to convert any non-disclosure result into a disclosure alert. This new capability covers all Major rules, with the exception of the Major: Japan - Diluted Denominator and the Major: Japan - Lending - Prime rules.

In the context of our Major: Japan rules, this enhancement is especially valuable as the rule sets rely on swinging thresholds. Additionally, there are various scenarios that require disclosure, e.g., a change of purpose of the holding or a change of address for the joint holders, but are not covered by the FundApps rule engine. For more detailed information, please refer to the aosphere memorandum on Japan.

When using the new functionality, it is absolutely crucial to convert to disclosure all results of all entities and all Major: Japan rules (with the exception of Major: Japan - Diluted Denominator and Major: Japan - Lending - Prime) for a given issuer for the day on which you wish to anchor a value, for a disclosure that was made outside of FundApps.

As an aside, in certain circumstances where an entity has been fully sold out/dropped below 0.1% without triggering a disclosure, there will be no alert in FundApps that can be converted into a disclosure. Since no assets are captured by the rule on that day, the engine does not calculate a holding and thus triggers no alert that is convertible.

Sold Out/Below 0.1% Entity Limitation

We identified that the logic to re-anchor entity/lending positions might lead to incorrect disclosure triggers following this specific chain of events:

  1. A disclosure is triggered for a given issuer at below 1% for Entity A.

  2. The position then becomes non-reportable in Entity A (due to a sellout or a drop to below 0.1%).

  3. Subsequently, while the position is non-reportable in Entity A, a separate disclosure obligation occurs outside of Entity A, meaning that the latest public disclosure shows a position of 0 for Entity A.

In this specific case, FundApps will continue to use the last disclosed value prior to the sellout/drop below 0.1% for Entity A as an anchor point for the 1% swinging threshold. This anchor value will remain in the system until a new disclosure is triggered, while Entity A holds over 0.1%. However, in this scenario, the correct anchor value would be 0%.

This means that, theoretically, Entity A could cross the 1% swinging threshold by building up a position without triggering a disclosure in FundApps. However, we would anticipate either another disclosure obligation to arise or the group level 1% threshold to be reached first.

Did this answer your question?