RBI Penalties Report – 28th August 2025

The Vijayapura District Central Co-operative Bank Ltd., Karnataka

Key Details

  • Penalty Amount: ₹1.00 lakh (Rupees One Lakh only)
  • Date of Order: August 19, 2025
  • Reason for Penalty: Contravention of provisions of Section 20 read with Section 56 of the Banking Regulation Act, 1949 (BR Act). The specific charge was that the bank sanctioned a loan to one of its directors.
  • Inspection: The statutory inspection was conducted by the National Bank for Agriculture and Rural Development (NABARD) with reference to the bank’s financial position as of March 31, 2024.

Root Cause Analysis (RCA)

The primary issue stems from a failure in governance and internal controls. The act of sanctioning a loan to a director suggests a breakdown in the bank’s internal policy adherence and a potential conflict of interest. This could be due to:

  • Lack of effective oversight: The board or a dedicated credit committee may not have had sufficient oversight to prevent or detect the loan sanction.
  • Weak internal policies: The bank’s policies regarding loans to directors or related parties may have been unclear, incomplete, or not robust enough to prevent this action.
  • Inadequate training: Personnel involved in the loan sanctioning process may not have been adequately trained on the legal and regulatory restrictions, such as those in Section 20 of the Banking Regulation Act.

Preventive Controls

To prevent similar issues, the bank should implement the following controls:

  • Strengthen internal policies: Revise and formalize policies that explicitly prohibit or strictly regulate loans to directors and other related parties. These policies should align with all applicable sections of the Banking Regulation Act.
  • Mandatory approval layers: Implement a system requiring multiple levels of approval for all loan sanctions, especially for significant amounts. This should include a review by a compliance officer and/or an independent committee to ensure there’s no conflict of interest.
  • Regular audits and checks: Conduct frequent internal and external audits focused specifically on compliance with lending norms and related-party transactions.
  • Compliance training: Provide mandatory and regular training to all directors, board members, and lending staff on the RBI’s regulations, particularly those concerning conflict of interest and restricted transactions.

Lessons Learned

The primary lesson is that governance and compliance are non-negotiable. A strong control environment is crucial to prevent instances of conflict of interest and non-compliance with statutory provisions. Adhering to the letter and spirit of the law, such as Section 20 of the BR Act, is paramount to maintaining regulatory compliance and avoiding penalties.

RBI Press Release


The Purasawalkam Co-operative Bank Limited, Tamil Nadu 🏦

Key Details

  • Penalty Amount: ₹1.00 lakh (Rupees One Lakh only)
  • Date of Order: August 19, 2025
  • Reason for Penalty: Non-compliance with specific RBI directions on ‘Prudential Norms on Capital Adequacy Primary (Urban) Co-operative Banks (UCBs)’ and ‘Supervisory Action Framework (SAF)’. The bank was found to have:
    • Allowed the refund of share capital to members despite its Capital to Risk-weighted Assets Ratio (CRAR) being below the regulatory minimum.
    • Failed to reduce the single borrower exposure limit for new loans by 50% as directed under the SAF.
  • Inspection: The statutory inspection was conducted by the RBI with reference to the bank’s financial position as of March 31, 2024.

Root Cause Analysis (RCA)

This case points to a clear failure in risk management and adherence to supervisory directives. The root cause is likely a combination of:

  • Inadequate internal communication: There may have been a breakdown in communication between the bank’s management and its operational teams, leading to a failure to implement the directions issued under the SAF.
  • Flawed systems or processes: The bank’s internal systems may not have been configured to automatically restrict share capital refunds or new loans based on the CRAR and SAF directives, allowing non-compliant transactions to occur.
  • Lack of oversight: Management may not have effectively monitored the bank’s compliance with the specific directions issued by the RBI.

Preventive Controls

To prevent recurrence, the bank should implement:

  • Automated system alerts: Integrate its core banking software with automated alerts that block transactions (like share capital refunds) or flag loan applications when the CRAR falls below the minimum threshold or when SAF is in effect.
  • Formalize a response plan: Develop a clear and documented plan for responding to and implementing RBI’s specific directives, including the SAF. This plan should assign clear responsibilities and timelines for implementation.
  • Enhanced risk monitoring: Establish a dedicated risk management committee to regularly monitor the bank’s CRAR and ensure strict adherence to all prudential norms and supervisory directives.

Lessons Learned

The key lesson here is the critical importance of proactive compliance and timely action in response to regulatory directives. Banks must not only be aware of the rules but also have the systems and processes in place to immediately and effectively implement them, especially when operating under a Supervisory Action Framework.

RBI Press Release


The Ponani Co-operative Urban Bank Limited, Kerala 🏦

Key Details

  • Penalty Amount: ₹50,000/- (Rupees Fifty Thousand only)
  • Date of Order: August 19, 2025
  • Reason for Penalty: Non-compliance with certain directions on ‘Co-operative Banks Interest Rate on Deposits’. Specifically, the bank opened savings deposit accounts in the name of ineligible entities.
  • Inspection: The statutory inspection was conducted by the RBI with reference to the bank’s financial position as of March 31, 2024.

Root Cause Analysis (RCA)

The root cause is a failure in Know Your Customer (KYC) and account opening procedures. This could be due to:

  • Lack of clear guidelines: Staff may not have had clear, accessible guidelines on which entities are eligible to open a savings deposit account.
  • Inadequate training: Frontline staff responsible for account opening might not have been properly trained on the regulatory requirements for different types of accounts and the eligibility of entities to hold them.
  • Manual process errors: The process for verifying customer eligibility might have been manual and prone to human error or oversight, leading to the opening of accounts for ineligible entities.

Preventive Controls

To prevent this issue, the bank should:

  • Standardize account opening procedures: Implement a checklist-based, and ideally, an automated process for account opening that verifies entity type against regulatory norms.
  • Provide clear training: All staff involved in customer onboarding must receive comprehensive and updated training on the KYC norms and specific RBI directions regarding savings accounts for different entities.
  • Introduce a supervisory review: A senior officer or a dedicated team should review a sample of newly opened accounts on a daily or weekly basis to ensure compliance with eligibility criteria.

Lessons Learned

The lesson learned is the importance of meticulous adherence to account opening and KYC procedures. Failing to correctly identify and onboard customers according to RBI’s guidelines can lead to penalties, even for what might seem like a minor procedural error.

RBI Press Release


The Nanded District Central Co-operative Bank Ltd., Maharashtra 🏦

Key Details

  • Penalty Amount: ₹45,000/- (Rupees Forty Five Thousand only)
  • Date of Order: August 22, 2025
  • Reason for Penalty: Non-compliance with directions on ‘Know Your Customers (KYC)’ and ‘Membership of Credit Information Companies (CICs) by Co-operative Banks’. The sustained charges were:
    • Failure to implement robust software to identify suspicious transactions.
    • Failure to submit credit information of its borrowers to all four CICs.
  • Inspection: The statutory inspection was conducted by NABARD with reference to the bank’s financial position as of March 31, 2024.

Root Cause Analysis (RCA)

This case highlights a failure in technology and data governance. The likely root causes are:

  • Outdated technology infrastructure: The bank’s software systems may be outdated or lack the necessary features to generate alerts for suspicious transactions, which is a key component of a robust KYC framework.
  • Insufficient data management: The bank may not have a proper system for collecting and submitting credit information to all mandated CICs, indicating a lack of a standardized data governance process.
  • Lack of resource allocation: The bank may have failed to allocate the necessary resources, both financial and human, to upgrade its IT systems and ensure full compliance with the CIC membership and data submission requirements.

Preventive Controls

To avoid similar penalties, the bank should:

  • Invest in upgraded software: Implement a modern anti-money laundering (AML) and KYC software solution that can automatically monitor transactions, identify anomalies, and generate alerts for potential suspicious activity.
  • Automate data submission: Establish an automated process for the periodic and timely submission of credit information to all four CICs as mandated by the RBI.
  • Regular audits: Conduct frequent audits of its IT systems and data submission processes to ensure they are functioning correctly and complying with regulatory requirements.

Lessons Learned

The key takeaway is that technology and robust data management are crucial for regulatory compliance. Banks must ensure their systems are not only up-to-date but also fully integrated to meet the evolving demands of regulatory bodies like the RBI, especially concerning KYC, suspicious transaction monitoring, and credit information sharing.

RBI Press Release

Scroll to Top