Asset Care & Reconstruction Enterprise Limited
| Penalty Amount | ₹27.30 Lakh (Rupees Twenty-Seven Lakh Thirty Thousand) |
|---|---|
| Order Date | September 08, 2026 |
| Statutory Provision | Section 12 read with section 30A(1) of the SARFAESI Act, 2002 |
| Primary Violation | Non-compliance with RBI directions on ‘Income Recognition’, specifically regarding the charging of management fees. |
| Inspection Reference | Financial position as on March 31, 2025 |
Root Cause Analysis (RCA)
The core issue stems from gaps in the company’s internal accounting and compliance systems regarding the recognition of income. Under RBI norms, Asset Reconstruction Companies (ARCs) are strictly regulated on how and when management fees can be recognized (often requiring realization rather than mere accrual, especially for stressed assets). The root cause likely involves a misalignment between the ARC’s internal fee booking logic and the stringent regulatory directives, leading to premature or inappropriate charging of management fees to inflate recognized income.
Preventive Controls
- System-Level Guardrails: Hardcode regulatory income recognition logic into the core accounting software to prevent manual overrides of management fee accruals.
- Concurrent Audits: Institute mandatory concurrent compliance audits specifically focused on fee generation and income realization events before finalizing quarterly financials.
- Checklist Validation: Implement a secondary maker-checker workflow where the compliance head must sign off on the regulatory validity of recognized management fees against actual cash flows.
Lessons Learnt
Regulatory authorities maintain a zero-tolerance policy towards aggressive accounting practices in income recognition. ARCs must ensure that management fees are strictly charged in tandem with RBI directives (realization basis), rather than projected or accrued basis. Compliance must take precedence over short-term financial reporting gains to avoid reputational and financial penalties.
RBI Press Release
Jilla Sahakari Bank Ltd., Azamgarh, Uttar Pradesh
| Penalty Amount | ₹1.15 Lakh (Rupees One Lakh and Fifteen Thousand) |
|---|---|
| Order Date | September 09, 2026 |
| Statutory Provision | Section 25(1)(iii) & 23(4) of CIC (Regulation) Act, 2005; Section 47A(1)(c), 46(4)(i) & 56 of the BR Act, 1949 |
| Primary Violation | Failure to report credit info to all Credit Information Companies (CICs) and failure to upload KYC records to Central KYC Records Registry (CKYCR) within prescribed timelines. |
| Inspection Reference | Financial position as on March 31, 2025 (NABARD Inspection) |
Root Cause Analysis (RCA)
The failures highlight severe operational and technological deficiencies at the co-operative bank level. The root cause for failing to report to all CICs is likely an absence of automated API integration with all credit bureaus, relying instead on manual or fragmented reporting. Similarly, the delay in CKYCR uploads points to inadequate digital infrastructure at the branch level, lack of proper workflow automation for customer onboarding, and insufficient compliance tracking mechanisms.
Preventive Controls
- Automated Data Integration: Deploy middleware that automatically syncs and submits core banking system (CBS) credit data to all mandated CICs simultaneously on a scheduled basis.
- CKYCR Alert System: Implement a dashboard with a countdown timer for new account openings. If KYC is not uploaded to CKYCR within the T+X days window, the system should flag the account and escalate to the branch manager.
- SOP and Training: Overhaul the standard operating procedures (SOPs) for account opening and credit disbursement, followed by mandatory staff training on the legal implications of data reporting delays.
Lessons Learnt
Co-operative banks cannot use operational constraints as a shield against core regulatory duties. Real-time or near-real-time data sharing (both credit and KYC) is a non-negotiable pillar of the modern financial ecosystem aimed at mitigating systemic risks. Failure to digitize and automate these basic compliance workflows will result in ongoing regulatory scrutiny and penalties.