Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-seo-pack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/globalindia/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the capital-core domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/globalindia/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the yotuwp-easy-youtube-embed domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/globalindia/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the forminator domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/globalindia/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the breadcrumb-navxt domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/globalindia/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the capital domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/globalindia/public_html/wp-includes/functions.php on line 6121
Foreign Portfolio Scheme: A strange kind of treatment » Global Indian Solutions

Foreign Portfolio Scheme: A strange kind of treatment

News, Taxation

The Securities and Exchange Board of India (Sebi), in its circular of April 10, in the process of clarifying ‘Know Your Client’ (KYC) norms, denied non-resident Indian (NRI)/resident institutions from managing global funds under the Foreign Portfolio Investment (FPI) scheme — ‘white’ category. In the meantime, non-Indians are allowed to manage such funds. This affects billion-dollar portfolio investments into India. The problem with the circular is that, instead of clarifying the KYC norms, it has discriminated between foreign institutions and NRI-resident institutions.

The circular uses the identification of ‘beneficial ownership’ to carry out KYC exercises. Unfortunately, it ends up restricting investments and management rights of NRI-resident institutions such that, if there is any fund to be promoted or controlled by them for attracting global investment, it would be ineligible for investment in India as FPI. The circular, however, allows the same pooling vehicle to be set up by other foreigners or foreign institutions.

Read More