RBI Penalty Report – 27th March 2026 | Union Bank of India

Executive Summary

The Reserve Bank of India (RBI) has imposed a monetary penalty of ₹95.40 Lakh on Union Bank of India. The penalty, ordered on March 23, 2026, penalizes the bank for regulatory non-compliances concerning customer liability limits in electronic banking and the automation of asset classification processes. The action follows findings from the Statutory Inspection for Supervisory Evaluation (ISE) concerning the bank’s financial position as of March 31, 2025.

1. Key Details of the Penalty

Regulated Entity Union Bank of India
Penalty Amount ₹95.40 Lakh (Rupees Ninety-Five Lakh Forty Thousand)
Regulatory Provisions Section 47 A(1)(c) read with sections 46(4)(i) and 51(1) of the Banking Regulation Act, 1949.
Identified Violations
  • Delayed Customer Redressal: Failure to credit (shadow reversal) the amount involved in unauthorized electronic transactions within the mandated 10 working days.
  • Inadequate Reporting Channels: Failure to provide customers with 24×7 access across multiple channels to report unauthorized banking transactions.
  • System Override (IRACP): Resorting to manual intervention in the System-based asset classification process for specific Kisan Credit Card (KCC) accounts.

2. Root Cause Analysis (RCA)

Based on the specific charges sustained by the RBI, the following operational, technological, and procedural root causes can be inferred:

A. Process Inefficiencies in Dispute Resolution The inability to execute shadow reversals within 10 days indicates fragmented workflow management between the customer service, fraud monitoring, and core banking operational teams. Manual verification bottlenecks likely hindered the SLA.
B. IT Infrastructure Gaps for Omnichannel Support The absence of 24×7 multi-channel reporting suggests either a lack of integration between the Core Banking System (CBS) and customer touchpoints (IVR, Mobile App, Web portal) or significant system downtime during off-hours, restricting continuous reporting capabilities.
C. Deficient Logic in Agricultural Loan (KCC) Classification Manual intervention in KCC accounts typically occurs when the automated IT systems fail to accurately capture complex agricultural cycles (sowing/harvesting seasons) or local state-level extensions. Branch staff likely used manual overrides to “correct” perceived system errors or improperly defer Non-Performing Asset (NPA) tagging.

3. Preventive Controls & Remediation Plan

  • Automated SLA Tracking System: Deploy a centralized ticket management system that automatically triggers a provisional shadow reversal on the 9th day of a customer raising a fraud dispute if the internal investigation is still pending.
  • Omnichannel API Integration & High Availability: Upgrade digital infrastructure to ensure zero-downtime availability for “Report Fraud/Block Card” features across SMS, WhatsApp, IVR, Internet Banking, and Mobile Apps.
  • CBS Parameter Enhancement for Agriculture: Update the Core Banking System parameters to accurately reflect State Level Bankers’ Committee (SLBC) guidelines on crop seasons for KCC. Remove all manual override privileges for asset classification.
  • Exception Reporting to Board: Implement a mandatory, automated daily report flagged directly to the Chief Compliance Officer (CCO) and Audit Committee highlighting any system-level manual bypasses.

4. Lessons Learnt

1. Customer Protection is Highly Time-Sensitive: Regulatory guidelines on electronic transaction liability are absolute. Delays in provisional crediting directly harm customer trust and attract severe regulatory penalties. Automation is the only sustainable way to meet strict TATs.

2. “System-Driven” Means Zero Manual Intervention: The RBI strictly monitors the integrity of the Income Recognition, Asset Classification, and Provisioning (IRACP) framework. Any manual override, even if done to correct system logic flaws, is viewed as a significant compliance breach. IT systems must be fixed at the source code/parameter level, not via daily manual adjustments.

3. Continuous Compliance Monitoring: Compliance cannot be a periodic exercise. Banks must deploy concurrent auditing tools that simulate RBI’s supervisory evaluation on an ongoing basis to catch 24×7 reporting downtimes or TAT breaches before the regulator steps in.

RBI Press Release

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top