Grievance

Managing customer grievances with a proper audit trail: what Indian banks need under the 2026 SOP

The grievance is not the problem. It is the receipt for a problem you already had.

In short

A grievance is a case that already failed once. By the time it reaches the grievance route, the bank has handled the underlying issue and the customer has rejected the outcome.

So the useful question is not how fast grievances get closed. It is whether somebody who was not there can reconstruct, from the file alone, what the bank did the first time and why.

What the 2026 SOP now requires

Grievances about held money finally have a defined route. The Ministry of Home Affairs SOP of 2 January 2026 sets out the Grievance Redressal Module, and the ministry made it functional from April 2026.

The bank does the first check. It runs customer due diligence as the relevant RBI circulars require, applies enhanced due diligence, and if convinced of the transaction's bona fides submits the grievance within 7 calendar days of the complaint. The investigating officer then has 15 calendar days to decide it. Unanswered grievances escalate automatically to a district grievance officer.

Every bank onboarded on CFCFRMS also has to appoint central and state-level grievance officers, and branch-level officers who raise grievances on a customer's behalf.

A grievance is a second failure, not a first complaint

Treating a grievance as a second failure changes what you build. A grievance arrives with history: an earlier case, an earlier decision, an earlier communication the customer did not accept.

Handling it well means reconstructing all of that before anyone responds. Handling it badly means treating it as a fresh complaint and reaching the same conclusion by the same route, which produces the same rejection.

That second loop is expensive in a way nobody measures. It consumes senior time, it escalates further, and it arrives in a channel with more scrutiny attached.

Where grievances actually come from

In an Indian bank running NCRP and I4C post-complaint operations, a large share of grievances trace back to actions taken on the account rather than to the original fraud.

Frozen-account cases were 3,755 out of 16,736 in one operation, or 22.4% of the queue, across 37 distinct scenarios. Each slow reversal on that pile is a grievance waiting to be filed.

This is why mean time to holds reversed is the measure worth watching. It counts the cases where the operation got it wrong, and every one of those is a grievance the bank has not received yet.

We automate the repetitive parts while preserving control, review, and auditability.

Rohan Sood, CEO, Patched

What the file has to contain

There is a simple test for a grievance file, and most fail it.

Can somebody who was not there reconstruct the original decision from what is written down? If the reasoning lived in an analyst's head and the record states only the outcome, there is nothing to stand on when the grievance arrives.

  • What was checked. Which systems were consulted and what they returned.
  • What was submitted. The exact response that went out, in the format it went out in.
  • What was skipped, and why. The step nobody asks for until they need it.
  • When each of those happened. Timestamps, not a general sense of sequence.
  • Who approved it. Under which threshold, and whether that threshold was the right one.

In one deployment that record runs at 98%+ completeness and accuracy, including the skipped steps.

The SOP adds a clock the file has to survive. If no lawful direction on a contested hold arrives within 90 calendar days of the grievance, the bank has to tell the law enforcement agency before the hold is lifted. Nobody can meet that date from memory.

Why the retrieval problem shows up here too

Reconstructing a case is retrieval, and retrieval is where this operation loses its time everywhere else.

An analyst handling a grievance opens the same five systems: the core banking portal, the API, the data lake, the internal service desk and the email inbox. KYC records and the LEA instruction behind a freeze both have to be found again. Then they read an old email thread to work out what was said.

In one Indian banking deployment, complaint response time ran at about three days before the retrieval stopped being manual, and almost none of it was decision-making.

Grievances inherit that cost and add to it, because the history has to be gathered on top of the facts.

The outcomes that make a grievance answerable

A closure percentage cannot answer a grievance. A named outcome can.

On a CaseLEA deployment every case ends in one of seven states: closed, partially handled, pending review, failed validation, freeze required, no records, or manual exception. Each exception carries its reason.

When a grievance lands on a case marked no records, the bank knows immediately that the issue was data availability rather than judgement, and the conversation with the customer starts from a true statement.

What changes when the history arrives with the case

22.4%of the queue frozen-account cases
37scenarios in that group alone
98%+audit trail completeness
~75%fewer analyst hours per case

Figures from one Indian banking operation, 2026.

The analyst opens a grievance and sees the original case, what was checked, what went out and when, without assembling any of it.

They then spend their time on the part that needs a person: deciding whether the bank got it right, and saying so clearly.

The test to run this month

Pull five grievances closed last quarter and hand them to someone who did not work them.

Ask each of them to explain, from the file alone, what the bank decided the first time and on what basis. Time how long it takes and note how often they have to ask a colleague.

That number is your real grievance cost - and it is also, almost exactly, what an internal auditor will experience when they run the same exercise without telling you.

The four reasons a grievance gets filed

In practice they cluster, and three of the four are operational rather than judgemental.

Source: CaseLEA operating documentation, 2026.
ReasonWhat it actually indicates
Nothing happened for too longA queue problem, not a decision problem
The explanation was unclearThe outcome was right and the letter was not
The customer was asked repeatedlyThe first request was incomplete
The decision was wrongThe only one that is genuinely about judgement

Most grievance programmes are designed around the fourth row and staffed for the first three. Categorising them on arrival tells you which of your four problems you actually have.

Writing the outcome so it survives a year

The letter is evidence, not correspondence, and it should be written that way without becoming unreadable.

Three things make the difference: state what was checked rather than only what was concluded, give the dates, and name what was not available if something was missing. A customer can accept that a record did not exist. They cannot accept a conclusion with no working shown.

Applied consistently this also protects the bank, because the letter and the file behind it are what a reviewer reads when nobody involved is still in the role.

Sources

About CaseLEA

CaseLEA is a managed post-complaint operations service for Indian banks. It works NCRP and I4C complaints, LEA notices and court orders, customer and merchant email, money restoration and grievance redressal as case management on top of the systems a bank already runs, with human review for uncertain cases and a full audit trail. CaseLEA is built by Patched, a Y Combinator-backed company, and runs RBI SAR compliant and SOC 2 certified in the Mumbai region.

32k+complaints closed
95%backlog reduction
3.4xoperational ROI

Production outcomes at a leading Indian payments bank.

Next