1 Key Details & Regulatory Snapshot
Penalty Imposed
₹7.50 Lakh
Order Date
November 17, 2026
Press Release Date
November 20, 2026
Inspection Reference
March 31, 2026
| Regulated Entity | Fusion Finance Limited (NBFC regulated under the RBI Act, 1934) |
|---|---|
| Monetary Penalty | ₹7.50 lakh (Rupees Seven Lakh Fifty Thousand only) |
| Statutory Authority | Section 58G(1)(b) read with Section 58B(5)(aa) of the Reserve Bank of India Act, 1934 |
| Regulatory Directions Violated |
1. RBI Directions on Know Your Customer (KYC) 2. RBI Directions on Internal Ombudsman (IO) |
| Supervisory Process | Statutory inspection conducted with reference to financial position as on March 31, 2026 → Show Cause Notice (SCN) issued → Written reply, additional submissions, and oral submissions during personal hearing reviewed by RBI. |
| Issuing Authority | Department of Communication, Central Office, Mumbai (Signed by Brij Raj, Chief General Manager) |
Sustained Charges Warranting Monetary Penalty:
- KYC Onboarding Lapse: The company failed to obtain Permanent Account Number (PAN), an equivalent e-document thereof, or Form 60 from customers while establishing an account-based relationship.
- Internal Ombudsman Escalation Lapse: The company failed to escalate partly or wholly rejected customer complaints to the Internal Ombudsman (IO) for a final decision within the prescribed turnaround time.
2 Root Cause Analysis (RCA)
While the press release records the regulatory findings, an institutional compliance assessment points to four interrelated root causes behind the two sustained violations:
A. KYC Documentation Failure (PAN / Form 60)
- Missing System Hard-Stops: Loan Origination Systems (LOS) or digital onboarding apps likely treated PAN / Form 60 fields as optional or allowed manual overrides during high-volume field onboarding.
- Field-Level Operational Pressure: Frontline relationship officers prioritizing disbursement turnaround times over strict pre-onboarding KYC verification, especially in semi-urban or rural microfinance segments where customers may not hold a PAN card and require Form 60 execution.
- Weak Maker-Checker & Post-Onboarding QA: Absence of automated exception flagging before account activation or loan disbursement, allowing incomplete customer files to bypass central KYC quality checks.
B. Internal Ombudsman (IO) Escalation Delays
- Manual Escalation Dependency: Grievance Redressal Management (GRM) workflows relying on manual triage rather than automated routing of partly or wholly rejected complaints to the IO portal.
- Lack of SLA / TAT Tracking: Absence of system-driven countdown alerts and auto-escalation rules when a complaint approaches the regulatory cut-off window for IO referral.
- Misclassification of Rejections: Frontline grievance teams closing or marking complaints as “resolved” when they were actually partly rejected, thereby unintentionally bypassing mandatory IO review.
3 Preventive & Detective Controls
| Control Domain | KYC (PAN / e-Document / Form 60) | Internal Ombudsman (IO) Escalation |
|---|---|---|
| System & Technology Controls (Preventive) | Enforce mandatory hard-stops in LOS/CBS preventing Customer ID (CIF) creation or account activation unless a validated PAN (via NSDL/UTIITSL API), equivalent e-document, or digitized Form 60 is uploaded and verified. | Configure auto-routing rules in the CRM/Grievance Portal so every complaint tagged as “Wholly Rejected” or “Partly Rejected” is automatically pushed to the IO queue well before the statutory deadline. |
| Process & Workflow Controls (Preventive) | Implement dual-control (maker-checker) verification at centralized CPCs for all Form 60 submissions and disable branch-level override permissions. | Standardize complaint closure codes with clear definitions for “Fully Resolved,” “Partly Rejected,” and “Wholly Rejected,” preventing premature closure without IO sign-off. |
| Monitoring & Audit Controls (Detective) | Run automated daily/weekly exception scripts comparing newly onboarded accounts against PAN/Form 60 repositories; integrate KYC completeness into Internal Audit and Concurrent Audit scopes. | Establish automated TAT breach alerts (e.g., at 50% and 75% of the prescribed window) and conduct monthly sample audits of “Closed/Resolved” tickets to detect disguised partial rejections. |
| Governance & Training | Conduct periodic refresher training for field staff on KYC Master Direction mandates and link compliance hygiene to branch-level KPIs. | Place a monthly IO Escalation & TAT Compliance Dashboard before the Customer Service Committee of the Board (CSCB) and Chief Compliance Officer (CCO). |
4 Key Lessons Learnt for Regulated Entities
1. Regulatory Compliance Must Be “Engineered In,” Not Audited Afterward:
Relying on manual checklists for high-frequency processes like customer onboarding (PAN/Form 60) and grievance escalation inevitably leads to leakage. Regulatory rules must be embedded as non-bypassable system logic.
- “Partly Rejected” Complaints Carry Equal Regulatory Weight: Institutions often focus IO workflows on outright rejections while overlooking partial rejections. Clear taxonomy and automated routing for both categories are critical to avoiding supervisory censure.
- Form 60 Hygiene Is Crucial in Financial Inclusion Segments: Entities serving underbanked or microfinance borrowers—where PAN penetration may be lower—must maintain frictionless, digital, and legally compliant Form 60 capture workflows at onboarding.
- Reputational Cost Exceeds Monetary Penalty: Although ₹7.50 lakh may appear modest relative to balance sheet size, public RBI enforcement orders draw heightened scrutiny from investors, rating agencies, lenders, and customers, and remain without prejudice to further supervisory action.
- Proactive Self-Identification Before Inspection: Regular internal compliance testing aligned with the RBI’s supervisory inspection calendar (March 31 financial position reviews) enables timely remediation before gaps escalate into Show Cause Notices.
Regulatory Note: As stated by the RBI, this action is based on deficiencies in regulatory compliance and is not intended to pronounce upon the validity of any transaction or agreement entered into by the company with its customers. Further, imposition of this monetary penalty is without prejudice to any other action that may be initiated by the RBI against the company.