What the RBI Fair Practices Code actually says about call recording — and what most agencies miss
First published in The Compliance Floor on LinkedIn, 2 June 2026. Regulatory positions are as they stood on that date.
Most agencies believe they have the recording problem solved.
They have a microphone. They have storage. The calls are captured.
So when a lender’s audit team — or, one day, the regulator — asks for a recording, the agency assumes it is covered.
It often is not.
Because recording is only the first link in a chain of four. A call has to be recorded, then retained, then retrievable on demand, then reviewable for audit.
Most agencies pass the first two. Many fail the last two.
And the failure is invisible until someone asks.
The chain breaks where nobody looks
Recorded and retained are engineering problems. You buy a system, you allocate storage, the files accumulate. This is the easy part, and almost everyone clears it.
Retrievable and reviewable are different. They are operational disciplines, not hardware.
Retrievable means: someone asks for one specific call — a named borrower, a date ninety days ago — and you produce it. Not a folder. That call.
Reviewable means: once produced, the recording is intact, audible, and tied to enough metadata that an auditor can verify who called whom, when, and on whose account.
The gap between “we record everything” and “here is the call you asked for” is where compliance quietly fails.
What we see when we ask for one old call
Across our audit network this fortnight, a pattern repeats whenever we ask for a specific recording from a few months back.
The files exist — somewhere. But they are named by extension number and timestamp, not by borrower or by account. So the search becomes a hunt.
A share of the requested files do not open cleanly. Audio is truncated, or the format is one nobody on the floor can play any more.
Some calls carry no metadata at all. The recording is there; the agent identity, the campaign, the disposition are not. You can hear a voice. You cannot prove whose call it was.
And in a meaningful number of cases, the recording simply cannot be produced inside the window an auditor allows. It was never lost. It was just never findable.
These are aggregated observations, not any single operation. But the shape is consistent: the failure is rarely at capture. It is almost always at retrieval and review.
What the regulation actually requires — and what it does not
Here the detail matters, because much of what circulates on the floor is wrong.
The instrument that mandates recording is older than most people think. It is the RBI circular on Recovery Agents engaged by Banks, dated 24 April 2008 (RBI/2007-2008/296). Its clause (iv) covers tape recording of the content of recovery-agent calls to borrowers, and the reverse.
The wording repays attention. The circular says banks “should ensure” the recording, but only that they “may” tell the borrower the call is being recorded. Recording is the obligation. Notifying the borrower is the option. A surprising number of operators have these the wrong way round.
A second common error: attributing the recording mandate to the 12 August 2022 directions (RBI/2022-23/108). Those directions tightened conduct — no harassment, contact only between 8 a.m. and 7 p.m., mandatory disclosure of agent details. They reaffirmed the 2008 circular and the Fair Practices Code. They did not add a fresh recording clause. The mandate still flows from 2008.
For NBFCs, there is no standalone recording rule. The November 2017 outsourcing Master Direction cross-references the Fair Practices Code, which in turn carries the 2008 framework by reference. So an NBFC’s recording obligation is derived rather than separately stated — and it is generally treated as binding in practice, even though it rests on inference rather than an explicit NBFC-specific rule.
The industry standard goes further than the statute. The FACE debt-recovery guidelines (v1.1, 29 August 2025), issued by RBI’s recognised fintech self-regulatory body, ask members to record all borrower calls, audit them for tone and language — including mystery audits — and log every contact on the recovery system the same day. This is an SRO standard adopted by members, not law. But lenders increasingly write it into contracts.
And the frontier is moving. In February 2026 RBI circulated draft “Responsible Business Conduct in Recovery of Loans” directions, separately per lender class, that would for the first time uniformly and explicitly require recording of recovery calls — with prior borrower intimation, documented call timing and number, and public disclosure of empanelled agents. The public-consultation window closed on 31 May 2026; the proposed effective date falls in the second half of 2026 (commentary cites 1 October 2026; an earlier draft referenced 1 July 2026). The directions are not in force as of early June 2026. But the direction of travel is unmistakable.
What this means for you is straightforward. The recording obligation is already firm. What is hardening is everything downstream — retrieval on demand, audit trails, same-day logging, and the lender’s contractual right to audit you. The bar your lender partners hold you to is rising faster than the statute.
That bar has teeth. The FACE penalty ladder for an agency that breaches its standard operating procedure runs from a written warning, to a financial penalty, to blacklisting the erring agent, to permanent termination of the agency — displayed publicly on the lender’s website — and a report to RBI or law enforcement. The point is not the rungs. It is that public blacklisting and a regulator’s file sit only a step or two above a single failure to produce a call. The lender, as principal, stays liable for your conduct, which is exactly why its audit teams have grown less forgiving.
The enforcement record backs this up. RBI fined HDFC Bank ₹1 crore in September 2024, citing among other failures the contacting of borrowers outside permitted hours. Borrower grievances are climbing: the RBI Ombudsman logged 13,34,244 complaints in FY2024-25, up 13.55 per cent, with Loans and Advances the single largest category at 29.25 per cent. Recovery conduct is where the regulator and the borrower both keep looking.
Five questions to ask before someone else does
If RBI — or your lender’s audit team — asked you tomorrow for a specific call from ninety days ago, could you honestly answer yes to all five?
- Can you find it by borrower or by account number, not just by extension and timestamp?
- Will the file open and play cleanly, in full, on a machine someone on your floor actually has?
- Is the recording tied to metadata that proves which agent made the call, on which campaign, with what disposition?
- Can you produce it inside the window an auditor or lender allows — hours, not days?
- Do you know your retention rule, and can you say where it comes from? There is no single RBI-prescribed number; duration is set by your lender’s board-approved policy, your contract, and the limitation window. If you cannot name yours, that is your answer.
A “no” to any one of these is not a recording gap. It is a retrieval or review gap — and that is the gap that fails audits.
Recording was never the hard part. Producing the right call, intact, on demand, always was.