Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

India lengthens foreign-investor KYC cycles to eight years for qualifying categories

SEBI moves selected FPI reviews to eight-year intervals from 1 December, while retaining two-year reviews for higher-risk categories and separate exceptions.

India's securities regulator has changed the timetable for recurring identity reviews of foreign portfolio investors, creating a concrete compliance-calendar adjustment for custody and brokerage providers. SEBI's 30 October circular takes effect on 1 December 2026. Qualifying Category I investors may move to KYC reviews once every eight years, while several Category II populations retain two-year reviews. The classification depends both on investor category and the risk status of the jurisdiction; it is not a universal eight-year exemption for foreign investors.[1][2]

The regulator's replacement table differentiates high-risk and non-high-risk jurisdictions. For Category I investors in high-risk jurisdictions, only those registered under the specified Regulation 5(a)(i) condition receive the eight-year interval; other Category I investors remain on two years. In non-high-risk jurisdictions, Category I investors receive eight years. Category II investors in high-risk jurisdictions have two-year reviews, while in non-high-risk jurisdictions regulated entities can receive eight years and other investors remain on two.[1][2]

There are two explicit exceptions to the new ordinary review timetable: government-securities-only FPIs and the SWAGAT-FI category retain the periodicity applicable under their separate regimes. The circular also removes an information-change declaration requirement at the point of continuance of registration. It does not abolish the underlying duty to maintain accurate investor information, initial KYC, anti-money-laundering screening or prompt notifications otherwise required by applicable rules.[1][2]

At a glance01

Verified scope and operational details

Verified scope and operational details
MeasurePublished evidence
Circular30 October 2026
Effective date1 December 2026
Category I, qualifying non-high-riskEight-year KYC review
Category II, non-high-risk regulatedEight-year review; others generally two years
High-risk jurisdictionTwo years except specified Category I Regulation 5(a)(i) investors
Continuance feePay DDP at least 15 days before current registration validity ends

Why this development matters

One timing obligation becomes especially practical for designated depository participants: an FPI seeking to continue registration must pay its fee at least 15 days before the current registration expires. The subsequent registration block is generally three years, while the circular specifies ten years for SWAGAT-FI. These are continuation periods, not the same thing as every category's periodic KYC-recheck interval. Conflating them could produce an incorrect compliance schedule.[1][2]

Depositories, custodians and DDPs are instructed to change systems and communicate the revision to affected investors. For institutional access providers, the work includes mapping each client's regulator category and jurisdictional risk label to the correct next-review date, rather than simply shifting all existing diary entries forward by a fixed number of years. Control teams also need to distinguish a recurring file review from transaction-triggered or sanctions-triggered checks.[1][2]

The document changes administrative processes for market access but does not open new derivatives permissions or relax custody requirements across the board. A defensible implementation report would track the number of investors moved to each review interval, the exceptions and any late fee-continuance problems, which are not yet available in the regulator's announcement.[1][2]

Follow the evidence

Sources & further reading

  1. Ease of Compliance for FPIs – Rationalisation of KYC Review Periodicity Securities and Exchange Board of India · 30 Oct 2026 · Accessed 7 Nov 2026

Report an error or submit an update