The RBI KYC deadline transaction monitoring question is easy to misread. In June 2025 the Reserve Bank of India allowed regulated entities to keep serving low-risk individual customers whose periodic KYC updation had fallen due, provided the update is completed within one year of the due date or by 30 June 2026, whichever is later. That is not a single cliff edge on 30 June 2026, and it is not a pause on monitoring.
For non-banking financial companies the practical task is to manage a staggered backlog, keep contacting customers, and keep monitoring their accounts while updation is pending. This article explains the rule, the reminder duties and the monitoring consequences.
What the amendment says
The RBI's KYC Amendment Directions of 12 June 2025 inserted a clause before paragraph 38 of the Master Direction. For an individual customer categorised as low risk, the regulated entity must allow all transactions and ensure KYC is updated within one year of falling due, or up to 30 June 2026, whichever is later. The relief also covers low-risk customers whose updation had already fallen due, and the entity must subject their accounts to regular monitoring.
Because of the words 'whichever is later', a customer whose KYC fell due in, say, March 2026 has until March 2027, while one who fell due in 2023 had until 30 June 2026. Entities should therefore track each customer's own deadline rather than apply a single date across the book. No further RBI extension has been published since the June 2025 amendment, and the November 2025 sector-specific Directions restate the same formula.
Reminders, outreach and customer-friendly routes
The amendment also tightened customer communication. Entities must send advance notice before KYC falls due and, where customers have not complied, at least three follow-up reminders at suitable intervals, including one by letter. The reminder mechanism was to be operational from 1 January 2026. Business correspondents can assist with updation, and self-declaration is allowed for customers with no change in their KYC details.
Those provisions shift part of the burden onto the entity's process. An NBFC needs a record of who was reminded, when, and by what channel, because that record is the evidence of compliance when an inspector asks why an account remains open.
Why monitoring continues during the window
The relief is conditional. The RBI said transactions should be allowed, but accounts remain subject to regular monitoring. A customer with overdue KYC is a customer about whom the entity has less current information, which increases the importance of behavioural monitoring. A sudden change in transaction volume, counterparties or geography on an account with stale KYC is exactly the kind of signal that should prompt an update request or enhanced review.
The relief also does not extend to medium and high-risk customers. Periodic updation for those remains on the risk-based cycle in the Master Direction, commonly cited as every eight years for medium risk and every two years for high risk, and a risk upgrade should shorten the cycle.
A workable approach for NBFCs
A practical approach has four parts. Maintain a customer-level due date and expiry of relief, flagged in the monitoring system. Run a prioritised outreach campaign, starting with accounts showing unusual activity. Make the digital updation route as easy as possible, in line with the RBI's push toward digital and business correspondent channels. And report the backlog, and its ageing, to senior management so that the position is visible before inspection.
RBI replaced the 2016 Master Direction with entity-specific Directions on 28 November 2025, including the Non-Banking Financial Companies Know Your Customer Directions, 2025, which it amended on 29 December 2025. The low-risk updation relief was carried into the sector-specific Directions (the All India Financial Institutions version, for example, restates it), so NBFCs should read the clause in their own Directions rather than paragraph 38 of the 2016 text. Handled well, the RBI KYC deadline transaction monitoring task is a managed backlog with continuing oversight, not a cliff edge.
