160 Series Non-Compliance Penalties: What BFSI Entities Risk in 2026

Last updated on October 14th, 2026 at 10:56 pm

AI Summary: Most coverage of the 160 series non-compliance penalty in India gets one thing wrong. TRAI imposes the Rs 2 lakh, Rs 5 lakh and Rs 10 lakh disincentives on telecom access providers, not on the bank or NBFC making the call. What hits the BFSI entity is operational. Five valid complaints in ten days bar outgoing services on every telecom resource it holds for 15 days. A repeat can disconnect it across all access providers for one year. TRAI set last dates between 1 January and 15 March 2026, and every one has passed.

Key Facts at a Glance

The Seven Points That Matter Most

• Every 1600-series deadline has passed. Exposure is live today for any entity still calling from 10-digit numbers.
• TRAI levies the graded Rs 2 lakh to Rs 10 lakh disincentives on access providers, mainly for misreporting UCC counts.
• Cost can still reach your entity contractually. Access providers must sign binding agreements with senders and may take forfeitable security deposits.
• Five valid complaints in any 10-day window bar outgoing services on every telecom resource you hold for 15 days.
• Later violations can disconnect you across every access provider for one year, with blacklisting.
• Consent rules tightened at the same time. Implicit consent for service calls now ends when the contract ends.
• FreJun supports 1600-series provisioning, DLT template registration, routing segregation and call logging.

Table of Contents

1. What Is the 160 Series Mandate and Why Does It Exist?
2. What Are the Phase-Wise Deadlines for Each BFSI Category?
3. What Happens When a BFSI Entity Misses Its 160 Series Deadline?
4. How Do the TCCCPR Financial Penalties Actually Work?
5. What Is the 15-Day Suspension and One-Year Blacklist?
6. What Is UTM Classification and When Does It Apply?
7. Which Consent Rules Apply Even From a 1600 Number?
8. Where Do RBI, SEBI, IRDAI and PFRDA Fit In?
9. Does the DPDP Act, 2023 Add to the Penalty Exposure?
10. Is There Criminal Liability for Number Misuse?
11. What Calling Behaviours Are Most Likely to Trigger a Complaint?
12. How FreJun Helps BFSI Entities Avoid These Penalties
13. Frequently Asked Questions
14. Key Takeaways
15. Compliance Disclaimer
16. References and Sources

What Is the 160 Series Mandate and Why Does It Exist?

What a 1600-Series Number Is

DoT allocated the 1600 series in May 2024. It covers service and transactional voice calls by verified principal entities, and nothing else. The DoT office memorandum sets two formats. Government bodies and regulators use 1600ABCXXX. Financial entities under RBI, SEBI, PFRDA and IRDAI use 1601ABCXXX. In both, AB is the telecom circle code and C is the operator code. No entity may run promotional or marketing calls on a 1600-series number.

Why DoT Created a New Series

The old split stopped working. Telemarketers used the 140 series for promotional, service and transactional calls alike. Promotional volume took over, so consumers stopped answering 140 numbers. Genuine service calls went unanswered with them.

Banks and insurers reacted by moving service calls onto ordinary 10-digit numbers. Fraudsters then impersonated those institutions from similar numbers. Consumers could no longer tell the two apart. DoT allocated 160 to close that gap.

The scale of the problem is on record. In a Lok Sabha reply of 31 July 2024, the Ministry of Communications reported 1.22 million complaints against unregistered telemarketers during 2023. The reply also described the actions telecom companies take: warnings, usage caps and disconnection.

How Adoption Became Mandatory

Allocation alone changed little, because adoption stayed voluntary. TRAI’s Direction of 19 November 2025 fixed that. It set a phase-wise schedule for entities under RBI, SEBI and PFRDA. The Direction of 16 December 2025 then brought IRDAI-regulated entities in, with a last date of 15 February 2026. Together, the two Directions turned migration into a dated obligation.

What this means for your compliance team: every deadline has passed. Any service call still going out from a 10-digit number is a call your TSP may have to account for. The complaint mechanism below runs on its own and does not wait for a notice.

Not sure which category your entity falls into, or whether your 1600-series allocation is live? FreJun’s team can walk you through the obligations for your entity type and get the allocation status confirmed in writing with your TSP.

What Are the Phase-Wise Deadlines for Each BFSI Category?

TRAI set a separate last date for each category across two Directions. Find yours below. Then confirm your allocation status with your access provider in writing, because a date in a Direction proves nothing about whether your numbers are live.

RBI-Regulated Entity Deadlines

SEBI, PFRDA and IRDAI Entity Deadlines

Two Checks Worth Running Against Your Own Classification

First, the Rs 5,000 crore asset threshold separates the February and March dates for NBFCs. If your entity sits near that line, verify which phase applied to you on the relevant date.

Second, ignore any article that still calls the insurance deadline “to be notified separately”. Those pieces predate the 16 December 2025 Direction. Insurers had the same 15 February date as mutual funds and pension entities.

What this means for your compliance team: record the date your migration completed and keep the evidence. A dated migration effort is exactly what you will want on file if a complaint later draws attention to your outbound calling.

What Happens When a BFSI Entity Misses Its 160 Series Deadline?

TRAI’s Directions set dates. They do not prescribe a separate penalty for missing one. Enforcement runs through the TCCCPR framework instead, and consumers drive that framework.

The Second Amendment restricts senders from using normal 10-digit numbers for telemarketing. It keeps 140 for promotional calls and designates 1600 for transactional and service calls. A service call from a 10-digit number therefore sits outside the designated route.

How Enforcement Actually Starts

It starts with one consumer. They can complain through the DND app or the 1909 helpline. Since the 2025 amendments, they no longer need to register a preference first. They also get seven days to complain, up from three.

A complaint counts as valid with four details: the complainant’s number, the sender’s number, the date, and a brief description of the call. Access providers must then act within five days on UCC from unregistered senders, down from thirty.

The Threshold Does Not Scale With Your Size

Five valid complaints against a sender in the last ten days trigger action. The earlier threshold was ten complaints in seven days. Fewer complaints over a longer window now produce the same result.

A large bank and a small NBFC face the same number. The threshold counts complaints. It does not scale with call volume or entity size.

What this means for your compliance team: do not wait for a formal notice. Track complaint volume as an operational metric and review it weekly. The first visible signal is usually a service bar, not a letter.

How Do the TCCCPR Financial Penalties Actually Work?

This is the most misreported part of the framework, so it is worth stating precisely. TRAI’s press note on the Second Amendment introduces graded financial disincentives. They apply when access providers fail to implement the regulations.

The ladder runs Rs 2 lakh for a first instance, Rs 5 lakh for a second, and Rs 10 lakh per instance after that. The press note ties them to access providers in cases of misreporting the count of UCC. It also applies them separately for registered and unregistered senders.

Who the Money Actually Comes From

TRAI levies these amounts on telecom operators. The same press note adds further disincentives on access providers for closing complaints invalidly, and for failing to meet their obligations on message headers and content templates. The pattern repeats throughout: TRAI acts on the operator, and the operator controls the sender.

The Two Routes That Reach Your Entity

Both routes are contractual, not regulatory. The Second Amendment requires access providers to sign legally binding agreements with every registered sender and telemarketer. Those agreements record roles, responsibilities and the actions available on non-compliance.

It also lets access providers prescribe a security deposit from senders and telemarketers. They can forfeit that deposit if the sender breaks the regulations.

What this means for your compliance team: read your TSP agreement before you budget for regulatory fines. Your indemnity and security-deposit clauses define your exposure, not TRAI’s press note. Those clauses are also negotiable at renewal.

What Is the 15-Day Suspension and One-Year Blacklist?

These consequences land on your entity directly. They are operational rather than financial. Access providers must suspend the telecom resources of any sender found guilty of repeated violations, and the Second Amendment sets two stages.

The 15-Day Bar: What Stops Working

On a first breach of the threshold, your access provider bars outgoing services on all your telecom resources for 15 days. Read that scope again. It covers every number and trunk you hold, not just the one that drew the complaints.

Many entities run OTPs, transaction alerts, service calls and collections from the same pool. One event takes out all of them at once.

Now picture that bar landing across a billing cycle or a quarter-end collections push. It becomes an operational incident, not a paperwork problem. TRAI’s press note describes no way to shorten it by paying anything.

The One-Year Disconnection and Blacklist

Later violations escalate sharply. Access providers disconnect all telecom resources of the sender, including PRI and SIP trunks, for one year. They do this across every operator, and they blacklist the sender.

Two features set this apart from the 15-day bar. It reaches every operator, not just the one involved in the violation. And blacklisting blocks new allocations for the whole period, so you cannot simply buy fresh numbers elsewhere.

The amendment also treats deception as misuse. Any call made to deceive or attempt to deceive customers counts as UCC for misuse purposes. That opens the same disconnection and blacklisting route.

What this means for your compliance team: map which customer journeys stop if every outbound number goes dark for 15 days. That list is the number to take to your board, not the fine schedule.

What Is UTM Classification and When Does It Apply?

UTM stands for unregistered telemarketer. It covers an entity making commercial communications without proper registration. It also covers one making calls inconsistent with its registration.

The Second Amendment restricts normal 10-digit numbers for telemarketing. It designates 140 for promotional traffic and 1600 for service traffic.

The Question TRAI Has Not Answered Publicly

Does a BFSI principal entity calling from a 10-digit number after its deadline count as a UTM? TRAI’s published Directions do not spell this out. Your access provider decides in the first instance.

Treat the UTM route as the cautious reading. Ask your TSP in writing how it classifies your traffic. Do not assume either way.

The UTM Enforcement Ladder

The Ministry of Communications has described the ladder in three steps: a warning, then a usage cap, then disconnection for repeat violations. The cap limits a number to twenty outgoing voice calls and twenty messages per day. Under TCCCPR 2018, a third violation can bring disconnection for up to two years, plus blacklisting.

Collections heads react to the cap figure first, and rightly so. Twenty calls a day halts a recovery operation that places thousands of dials. The ladder also runs separately from the complaint-threshold track, so both can apply to the same calling pattern.

What this means for your compliance team: get your traffic classification confirmed by your TSP and keep the reply. It tells you which enforcement track you face. It is also the fastest question to settle this quarter.

See how FreJun handles the technical side of a 1600-series migration: TSP eligibility verification, DLT template registration, routing segregation between promotional and transactional traffic, and call logging that holds up in an audit.

Which Consent Rules Apply Even From a 1600 Number?

Migrating to 1600 does not make every call compliant. The same 2025 amendment shortened how long consent lasts. Four rules apply directly to service and transactional callers.

The Rule That Catches Well-Run Entities

The first rule is the one teams miss. A closed loan account ends the contract. So does a lapsed policy. The implicit consent that justified service calls has ended.

Calling anyway is exactly what generates valid complaints. Your migration can be flawless and this will still catch you.

What this means for your compliance team: reconcile calling lists against contract status, not just the DND registry. Most CRM-driven dialling lists apply none of these three filters today.

Where Do RBI, SEBI, IRDAI and PFRDA Fit In?

The Directions came out of the Joint Committee of Regulators process. TRAI took timeline inputs from RBI, SEBI, PFRDA and IRDAI. That joint origin matters, because each regulator supervises the same entities under its own statute. IRDAI has separately told insurers and intermediaries to comply with the TRAI Direction.

What the Public Record Does Not Show

No regulator has tied a specific penalty section to a missed 1600-series deadline. General supervisory and penalty powers exist, of course. RBI acts under the Banking Regulation Act, 1949 and the RBI Act, 1934. SEBI acts under the SEBI Act, 1992. IRDAI acts under the Insurance Act, 1938, and PFRDA under the PFRDA Act, 2013.

Whether any regulator would invoke those powers on these facts is a question for counsel. Do not infer it from the Directions themselves.

The Overlap That Actually Happens

The real overlap is more mundane. Consumers complain about collection calls outside permitted hours. They complain about calls after an opt-out. Those same complaints can reach a sectoral regulator’s grievance channel while they also count toward TRAI’s threshold. One call, two audiences.

What this means for your compliance team: treat outbound calling conduct as a single risk. The complaint that counts toward a telecom threshold often reaches your sectoral regulator too.

Does the DPDP Act, 2023 Add to the Penalty Exposure?

The Digital Personal Data Protection Act, 2023 is a separate regime with its own triggers. Coverage of the 1600 series routinely misrepresents it.

Its penalties attach to specified failures. Examples include not taking reasonable security safeguards and not notifying a personal data breach. None of them attaches to your choice of number series. So do not read the headline crore figures as a penalty for missing a migration deadline.

Where the Two Regimes Genuinely Meet

Consent and opt-out handling is the real intersection. The customer records that drive outbound calling are personal data. Obligations to act on withdrawal of consent sit alongside the TCCCPR opt-out regime rather than replacing it.

An entity that cannot explain how an opted-out customer reached a dialling list has a problem in both directions.

What this means for your compliance team: audit the data flow that builds your calling list. Check which DPDP provisions apply to your entity before you design controls around any specific penalty figure.

Is There Criminal Liability for Number Misuse?

Criminal exposure exists, but for narrower conduct than general non-compliance. The relevant conduct is tampering with telecommunication identifiers.

Section 42(3)(c) of the Telecommunications Act, 2023 prohibits such tampering. Section 42(3)(e) prohibits obtaining SIMs or identifiers through fraud, cheating or impersonation. Offences under Section 42(3) carry imprisonment up to three years, a fine up to Rs 50 lakh, or both. Section 42(6) applies the same punishment to abetment. Section 42(7) makes these offences cognizable and non-bailable.

Why This Reaches Your Dialler Configuration

DoT’s advisory on misuse of telecom resources covers this directly. Modifying Calling Line Identity, commonly called CLI spoofing, counts as identifier tampering. So does tampering with IMEI numbers and SMS headers.

Read that against any dialler that presents a number other than the one allocated to your entity.

What this means for your compliance team: review your dialler and any vendor platform for CLI overrides or number masking. Your telephony team can answer this in a day, and the exposure here is criminal rather than regulatory.

What Calling Behaviours Are Most Likely to Trigger a Complaint?

Each behaviour below produces valid complaints that count toward the five-in-ten-days threshold. They are ordered by how often they show up in ordinary BFSI operations, not by severity.

You Can Be Flagged Before Anyone Complains

The last row deserves attention. It describes detection, not complaints. TRAI requires access providers to analyse calling patterns in real time and to run honeypots. Your traffic can therefore attract scrutiny before a single consumer complains.

What this means for your compliance team: start with opted-out and discharged-contract data hygiene. It is the highest-frequency complaint source and the easiest one to fix.

How FreJun Helps BFSI Entities Avoid These Penalties

FreJun is a cloud telephony and AI calling platform. BFSI, SaaS and enterprise teams use it to operate inside the 140 and 1600 series framework. The platform covers the technical layer so your compliance team can focus on consent, classification and vendor conduct, which nobody can outsource.

FreJun’s Compliance Stack for 1600-Series Migration

FreJun supports 1600-series provisioning for eligible BFSI entities. That includes the TSP eligibility verification step, which has to happen before any allocation. The platform also handles DLT-side template registration, call routing and call detail record logging in one place.

The platform also enforces routing segregation at the system level. Auditors test exactly this: whether 140 promotional traffic and 1600 transactional traffic run on genuinely separate routes, or only on paper.

Integrations with HubSpot, Zoho, Salesforce and LeadSquared keep opt-out data in sync with the systems that build calling lists. That addresses the most common complaint trigger described above.

For related reading, see our guides on how to get a 160 series number and the 160 series versus 140 series comparison.

FreJun manages 1600-series provisioning, DLT template registration, routing segregation and call logging end to end. Book a call with our team to see how the migration works for your entity type.

Frequently Asked Questions

Does a BFSI entity pay the Rs 2 lakh to Rs 10 lakh penalty per violation?

No, not under TRAI’s published framework. TRAI levies those graded disincentives on access providers, mainly for misreporting UCC counts. Cost can still reach you through your TSP agreement or a forfeited security deposit. The Second Amendment expressly enables both, so your real exposure sits in the contract.

What is the 1600 series deadline for insurance companies?

15 February 2026. TRAI set it in a Direction of 16 December 2025, after consulting IRDAI. The earlier Direction of 19 November 2025 covered RBI, SEBI and PFRDA entities only, and left insurance for later. That is why older articles show no date for insurers.

How many complaints trigger the 15-day bar?

Five valid complaints against the sender in the last ten days, down from ten in seven days. A complaint is valid with the complainant’s number, the sender’s number, the date and a short description. Consumers no longer need to register a preference first, and they get seven days to complain.

Can we use a 1600-series number for promotional calls?

No. The 1600 series covers service and transactional calls. The 140 series carries promotional calls. A cross-sell message on a 1600 number breaks the designation that justified your allocation. Keep the two traffic types on separate routes rather than relying on script controls.

Are recovery agents required to use the principal entity’s 1600 numbers?

Calls made on your behalf should originate from your allocated numbers, not agents’ personal mobiles. Your agents’ conduct reflects on you. The Directions address regulated entities rather than their vendors, so confirm the routing rules with your TSP and write them into your agency contracts.

Does moving to 1600 make our service calls compliant?

Not on its own. The number series only changes how the call identifies you. It says nothing about your right to make that call. Implicit consent now ends with the contract, transaction-linked consent lasts 7 days, and you cannot re-seek consent within 90 days of an opt-out.

Key Takeaways

• TRAI levies the graded Rs 2 lakh, Rs 5 lakh and Rs 10 lakh disincentives on access providers. Cost reaches your entity through the TSP agreement and forfeitable security deposits.
• Five valid complaints in any 10-day window bar outgoing services on all your telecom resources for 15 days, covering every number and trunk you hold.
• Later violations can disconnect you across every access provider for one year, with blacklisting and no new allocations during that period.
• All deadlines have passed: 1 January 2026 for commercial banks, 1 February and 1 March for NBFC tiers, 15 February for mutual funds, pension entities and insurers, and 15 March for qualified stockbrokers.
• Consent rules changed alongside the numbering rules. Implicit consent ends with the contract, transaction consent lasts 7 days, and re-consent waits 90 days after an opt-out.
• Section 42 of the Telecommunications Act, 2023 covers identifier tampering, including CLI spoofing, with up to three years’ imprisonment, a fine up to Rs 50 lakh, or both.
• FreJun supports 1600-series provisioning, DLT template registration, routing segregation and call logging. Classification, consent and vendor conduct stay with your entity.

Compliance Disclaimer

Disclaimer: This article is published for informational purposes only and represents FreJun’s understanding of the relevant legal and regulatory position based on its own independent research and interpretation of publicly available materials. It should not be construed as legal advice, legal opinion, or regulatory guidance. Readers are encouraged to seek independent legal counsel or consult the appropriate regulatory authorities before taking any action based on the information contained herein. While reasonable efforts have been made to ensure the accuracy and completeness of the information presented, laws, regulations, interpretations, and enforcement positions may evolve or vary based on specific facts and circumstances. FreJun does not warrant that the contents are free from inaccuracies, omissions, or inadvertent errors and shall not be responsible or liable for any misinformation, inaccuracies, or reliance placed upon the contents of this article, whether published knowingly or unknowingly.

References and Sources

• TRAI Direction, 19 November 2025, phase-wise adoption of the 1600 series by RBI, SEBI and PFRDA regulated entities: pib.gov.in
• TRAI Press Release No. 151/2025, Direction for IRDAI-regulated entities, 16 December 2025: trai.gov.in (PDF)
• TRAI Press Release No. 11/2025, amendments to TCCCPR 2018, 12 February 2025: trai.gov.in (PDF)
• TCCCPR Second Amendment Regulations, 2025, gazette text: trai.gov.in (PDF)
• DoT allocation of the 160 numbering series, May 2024: dot.gov.in
• Lok Sabha Unstarred Question No. 1536, 31 July 2024, action against unregistered telemarketers: eparlib.nic.in (PDF)
• DoT advisory on misuse of telecom resources and identifier tampering: sancharsaathi.gov.in
• TCCCPR 2018: trai.gov.in

About the Author: Nimish Gavali is a Legal and Compliance Analyst and appointed Data Protection Officer (DPO) with prior experience practising before the Hon’ble Bombay High Court. Having transitioned into a corporate role, he advises on telecom regulation, digital compliance, data governance, and customer communication frameworks. His work spans TRAI regulations, DoT licensing, the TCCCPR 2018 and related amendments, DLT registration, and the 160 and 140 series numbering framework, with a focus on BFSI and communication platforms navigating compliant customer-outreach architectures. Prior to his in-house role, he worked on regulatory, civil, and commercial matters before the Bombay High Court. He holds an LL.B. from Government Law College, Mumbai, an LL.M. in Business and Corporate Law, and a Diploma in Cyber Laws. Connect on LinkedIn.