We use cookies to personalise the website and offer you the greatest added value. They are, among other purposes, used to analyse visitor usage in order to improve the website for you. By using this website, you agree to their use. Further information can be found in our data privacy statement.



Inside RBI's New Blueprint for Data Governance in Finance Sector

​​​​​​​​​​​​​​​​published on 20 July 2026 | reading time approx. 6 minutes​​​


The Reserve Bank of India's draft "Guidance on Regulatory Expectations for Data Governance" asks banks and financial institutions to name specific people responsible for personal or non-personal data handling, map out how it moves, and tighten how it's shared with vendors. Here's what the draft actually proposes, and why it matters even if you're not a bank.​​

Introduction​​

India's banking regulator, the Reserve Bank of India  (RBI) has decided that data deserves the same discipline as money. Data has become one of the most important assets for banks and financial institutions, shaping everything from customer service to risk management and regulatory reporting. As digital finance, interconnected technology systems, and automated decision-making have grown, so has the sheer volume and complexity of data these institutions handle. The RBI has observed that while financial entities have improved their data management practices over time, gaps still remain that could expose them to operational, compliance, and financial risks. To address this, the RBI issued its draft Guidance on Regulatory Expectations for Data Governance (“Draft Guidance”) on July 15, 2026, drawing on supervisory experience and international standards such as the Basel Committee's principles on risk data aggregation (BCBS 239).

The Draft Guidance sets out expectations covering governance structures, defined data roles, the data lifecycle, system architecture, and third-party arrangements, with the broader goal of making data more reliable, consistent, and secure across the financial sector. 

Why Now?​​

The RBI, having identified certain systemic vulnerabilities in the existing data management frameworks of Regulated Entities (REs), more specifically data redundancy, fragmentation, and inadequate tracking within critical repositories such as customer records, transaction histories, credit scores, and AI-driven analytics, issued a Draft Guidance document on July 15, 2026, to mitigate the attendant risks of defective credit underwriting, regulatory non-compliance, and reputational damage. Accordingly, this regulatory framework has been positioned for public consultation, with all stakeholders invited to submit formal comments and representations on or before the close of the review window on August 17, 2026.

Who Does This Apply To?​​

The Guidance shall apply to RBI-regulated entities viz.,  commercial banks, small finance banks, payment banks, regional rural banks, cooperative banks, Non-banking Financial Companies, All India Financial Institutions, asset reconstruction companies, and credit information companies. But if you're a fintech, lender, or vendor working closely with any of these, expect the ripple effects to reach you too.

Organizational Structure and Data Architecture​​

From an oversight perspective, the Draft Guidance expects every RE to either set up a dedicated Board-level Data Governance Committee or assign the responsibility to an existing board committee. This committee is expected to approve the organisation's data governance policies, spanning architecture, ownership, quality, classification, lifecycle management, and third-party arrangements, and to review these periodically. Any major breaches or unresolved conflicts must be escalated straight to this Board. 

The Draft Guidance also requires every RE to set up a dedicated “Data Function”, a team led by someone senior (at least Chief General Manager level or equivalent) to coordinate data governance across business, risk, and technology teams. 

The Draft Guidance also introduces a clear chain of accountability, built around three roles:
  • Data Owner, who decides how a particular set of data should be classified, used, and shared. This person also designates the "Single Source of Truth" (the one authoritative version of a dataset) and signs off on any changes to it;
  • Data Steward, who handles the day-to-day work like keeping definitions consistent, tracking data flows, and flagging problems up the chain;
  • Data Custodian, who manages the technical side like access controls, storage security, backups, and disaster recovery.

Together, these roles are meant to close a common gap, where technology teams manage data, but nobody is formally accountable for whether it's accurate or well-governed.

A Documented Map Of Who Does What​​

Beyond appointing people for the roles described above, RE will need to maintain a written map showing exactly who is accountable, who executes, who is consulted, and who is informed at each stage of the data lifecycle. This map isn't a one-time exercise, it must be reviewed periodically and updated whenever business operations, systems, or regulations change.

At the point of collection, entities must gather data only for clearly defined purposes, establish ownership and consent upfront, and apply the same quality checks to third-party data as to their own. When data is processed or shared, it must follow approved rules, carry adequate security safeguards such as encryption and anonymisation, and remain traceable back to its source, with clear accountability for any derived or transformed datasets. On retention and disposal, entities need a formal retention policy, must keep data only as long as there's a genuine business or legal reason, preserve its history and classification while archived, and dispose of it securely once it's no longer needed.

The Draft Guidance also expects Res to maintain metadata throughout a dataset's life, recording details like ownership, purpose, and classification from the moment data is created, and updating this information whenever the data is transformed or moved across systems. This should build into an end-to-end lineage, so entities can trace exactly how data has moved and changed over time. The data itself must be classified based on factors such as business criticality, customer impact, sensitivity, and regulatory requirements, with this classification kept accurate even as data is combined or enriched. Finally, REs need proportionate data quality processes, with measurable metrics to catch problems before they affect decision-making or regulatory reporting, and persistent quality issues must be reported to the Data Governance Committee at least once every quarter.

Third-Party Data Sharing Gets Stricter​​​

Many financial institutions rely on external vendors and partners for services like analytics, cloud storage, or credit scoring. The Draft Guidance expects tighter safeguards around this through clearer contracts with non-disclosure clauses, defined purposes for sharing, and stronger oversight of what happens to data once it leaves the organization’s own systems.

The DPDPA connection​​

This Draft Guidance is not to be read in isolation, rather it explicitly expects RE to align with India's Digital Personal Data Protection Act, 2023 (DPDPA) and its prescribed rules. In practice, this means data governance and data protection compliance are converging. A business can no longer treat "governance" as an internal efficiency project and "privacy" as a separate legal checkbox. They're essentially becoming the same conversation.

What Does This Means In Practice​

For business owners, especially those without an in-house legal team, the takeaway is straightforward:
  1. If you're a RE, expect to formally designate data ownership, build (or tighten) a data governance framework, and document data flows and vendor arrangements before this becomes final;
  2. If you're a vendor or partner to a RE, expect your contracts to come under closer scrutiny. Clients may soon ask sharper questions about how you handle the data they share with you;
  3. If you're neither, this is still a useful signal. It shows where Indian regulators are heading on data accountability, and similar expectations may eventually extend to other regulated sectors.

Conclusion​​

The Draft Guidance is open for comments, so the final shape of these rules could still change. But the direction is clear, data governance in India's financial sector is moving from a "good practice" to a supervisory expectation, with named individuals accountable for getting it right. Businesses that start mapping their data ownership, vendor arrangements and aligning with the Draft Guidance are likely to have a head start rather than scrambling once the guidance is finalized.​

Tech & Data Bites

author

Contact Person Picture

Prarthana Vasudevan

Consultant

+91 80 44784 803

Send inquiry

Rödl INDIA

Discover more about our offices in India​​. Re​​a​d more »​
Skip Ribbon Commands
Skip to main content
Deutschland Weltweit Search Menu