No longer current — withdrawn, no replacement on file yet
Source: Reserve Bank of India · RBI/2013-14/250 · issued 11 Sep 2013 · ~2 min read
Quick answerRBI will create a central repository of large credits (exposures over Rs 10 crore) using existing XBRL-based Return on Large Borrowers data. Banks must ensure data accuracy and integrity; non-compliance attracts penalties under the Banking Regulation Act.
The rule, in the simplest words
Banks must send correct data about big loans (over Rs 10 crore) to RBI's special system called OSMOS.
RBI will collect all this data to make a shared list so banks can see if a borrower has too many loans from different banks.
If a bank sends wrong data or forgets to send it, RBI can fine the bank under the Banking Regulation Act (a law for banks).
How it plays out — a real example
A payments & clearing officer in Indore is preparing the monthly Return on Large Borrowers. She double-checks every loan above Rs 10 crore, making sure the amounts and borrower names are correct, because she knows RBI will use this data to spot borrowers who are over-leveraged across multiple banks. She also reminds her team that any mistake could lead to a penalty from RBI.
What changed
RBI announced the creation of a central repository for large common exposures across banks, leveraging data from the Return on Large Borrowers (Form A, Part D) which captures fund and non-fund based exposures above Rs 10 crore. This follows Governor Rajan's September 4, 2013 statement on collecting credit data to monitor building leverage and common exposures. Banks are now directed to submit accurate data, with penal consequences for errors or omissions.
What it means for you
Banks must now treat large credit data submission with heightened seriousness, as RBI will use it to identify systemic concentration risks. The repository will be shared with banks, enabling them to detect over-leverage and common exposures across the system. Non-compliance or inaccurate reporting can lead to penalties under Section 27(2) and Section 35A of the Banking Regulation Act.
Historical instruction — do not use for current compliance. This is what was required at the time; it no longer reflects current RBI requirements. If no replacement rule is linked above, that only means none is recorded on our register yet — it does not prove no later applicable rule exists. Confirm on the official RBI source below.
What banks were required to do at the time
Ensure all large credit data (exposures > Rs 10 crore) in Return on Large Borrowers (Form A, Part D) is accurate and complete.
Implement internal checks to verify data integrity before submission to RBI via the XBRL-based system.
Review OSMOS reporting processes to avoid penalties for non-submission or wrong reporting.
Train relevant staff on the directive's requirements and the importance of data quality.
Who it affects
All Scheduled Commercial Banks (excluding RRBs), Credit risk and reporting teams, Compliance and data management departments
❓ Common questions
Regulatory timeline
Decoded by BankPulse2026-06-18 12:51 IST
repealed_by — Consolidation of Regulations — Withdrawal of circulars (28 Nov 2025)
Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).
What is the threshold for exposures to be reported in this repository?
The repository captures system-wide exposures (both fund and non-fund based) of individuals and entities exceeding Rs 10 crore, as reported in the Return on Large Borrowers (Form A, Part D).
What are the penalties for non-compliance with this directive?
Non-submission or wrong reporting of data in OSMOS returns attracts penalties as specified under the Banking Regulation Act, 1949, as per the powers vested in RBI.
How will this repository benefit banks?
RBI will share the central repository with banks, enabling them to identify building leverage and common exposures across the banking system, thus improving risk awareness.
📜 This document’s life story (1 recorded event, each backed by RBI’s own words)
Repealed byRBI/2025-26/100 — Consolidation of Regulations — Withdrawal of circulars (28 Nov 2025)
RBI’s words: “Official withdrawal register entry #80: DBS.Dir.OSMOS.No.3324/33.01.001/2013-14 — "Creation of a Central Repository of Large Common Exposures - Across Banks" dated September 11, 2013”
📜 Read the original circular — full text as issued by RBI
RBI/2013-14/250
DBS.Dir.OSMOS. No. 3327/33.01.001/2013-14
September 11, 2013
All Scheduled Commercial Banks
(excluding RRBs)
Dear Sir/Madam
Creation of a Central Repository of Large Common Exposures - Across Banks
This has a reference to the statement made on September 4, 2013 by Dr. Raghuram Rajan on his taking over the charge as Governor, RBI wherein it was stated “ RBI proposes to collect credit data and examine large common exposures across banks. This will enable the creation of a central repository on large credits, which we will share with the banks. This will enable banks themselves to be aware of building leverage and common exposures ”.
2. Accordingly, it has been decided to use the information supplied by the banks through the Return on Large Borrowers (Form A) [Part D of Return on Large Credit in the revised XBRL based system], which captures system-wide exposure of individuals and entities having exposure (both fund and non-fund based) of more than Rs 10 crore, for creation of central repository of large credits across banks. As you are aware, the data under OSMOS system is collected through DSB/Adhoc returns in exercise of powers vested in RBI under Section 27(2) of Banking Regulation Act (hereinafter referred to as the Act) and non-submission of or wrong reporting in these returns attracts penalties as specified in the Act.
3. Banks are advised to take utmost care about the data accuracy and integrity, while submitting the data on large credit to the Reserve Bank of India, failing which penal action, as referred to above, would be undertaken.
4. A directive dated September 11, 2013 is enclosed .
Yours faithfully
(G Jaganmohan Rao)
Principal Chief General Manager
DBS.Dir.OSMOS. No.3324/33.01.001/2013-14
September 11, 2013
Creation of a Central Repository of Large Common Exposures - Across Banks
In exercise of the power conferred by Section 27(2) of Banking Regulation Act, the data under OSMOS system is collected through DSB/Adhoc returns by the Reserve Bank of India and non-submission of or wrong reporting in these returns attracts penalties as specified in the Act. The Reserve Bank of India being satisfied that it is necessary to build a repository of large credits and share with the banks for enabling them to be aware of building leverage and common exposures. Accordingly, it has been decided to use the information supplied by the banks through the Return on Large Borrowers (Form A) [ Part D of Return on Large Credit in the revised XBRL based reporting system ] , which captures system-wide exposure of individuals and entities having exposure (both fund and non-fund based) of more than Rs 10 crore, for creation of central repository of large credits across banks .
2. The Reserve Bank, having been satisfied that, in public interest and in the interest of banking policy, it is necessary to issue directions to all scheduled commercial banks (excluding RRBs) (hereinafter referred to as “banks”), in exercise of the powers conferred by sub-section (1) of section 35A of the Banking Regulation Act, 1949 (Act 10 of 1949) and of all the powers enabling it in this behalf, hereby directs all banks to take utmost care about data accuracy and integrity while submitting the data on large credit to the Reserve Bank of India, failing which penal action, as referred to above, would be undertaken.
3. These directions shall come into force with immediate effect.
(G Gopalakrishna)
Executive Director
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2013-14/250 · issued 11 Sep 2013. The plain-English explanation above is BankPulse’s own independent summary.
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 03 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=8405&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.