Airtel faces two DoT penalty notices over CAF compliance, accepting the larger Andhra Pradesh penalty while challenging the Madhya Pradesh notice.
The Department of Telecommunications (DoT) has issued two penalty notices to Bharti Airtel over customer verification and Customer Application Form (CAF) compliance, with the combined amount reaching Rs 8.91 lakh.
The disclosures, made by Airtel under the SEBI Regulation 30 framework on September 9, relate to compliance audits conducted by DoT’s Andhra Pradesh and Madhya Pradesh Licensed Service Areas (LSAs). The two cases involve separate audit periods and penalty amounts.
Airtel Faces Two Separate DoT Penalty Notices
According to Airtel’s regulatory disclosures, the larger penalty of Rs 6.75 lakh relates to a CAF compliance audit conducted by the Andhra Pradesh LSA for May 2026.
A second notice from the Madhya Pradesh LSA involves a penalty of Rs 2.16 lakh following an audit for June 2026. Together, the two notices amount to Rs 8.91 lakh.
The penalties are linked to compliance requirements around customer enrolment and verification procedures. CAF-related checks are part of the telecom industry’s regulatory framework for ensuring that subscriber records and customer verification processes meet prescribed requirements.
Airtel Takes Different Positions on the Two Notices
An important aspect of the disclosures is that Airtel is not treating the two cases in the same way.
For the Andhra Pradesh notice involving Rs 6.75 lakh, Airtel has decided to pay the penalty without disputing the amount. The company therefore appears to have accepted the regulatory finding in that case.
Airtel, however, has indicated that it will contest the Rs 2.16 lakh Madhya Pradesh notice and seek rectification. This means the smaller penalty remains subject to the company’s regulatory response rather than being treated as an uncontested payment.
The contrasting responses highlight how individual compliance findings can be handled differently depending on the circumstances of the underlying audit and the company’s assessment of the regulatory observations.
Why CAF Compliance Matters for Telecom Operators
Customer verification is a fundamental part of India’s telecom regulatory framework. Mobile operators are required to maintain accurate subscriber information and follow prescribed procedures when issuing and activating connections.
The CAF process has historically involved physical documentation, but telecom operators have increasingly shifted customer onboarding towards digital and paperless processes. As these systems evolve, operators continue to face compliance requirements covering documentation, verification, subscriber records and activation procedures.
For operators such as Airtel, these requirements apply across a very large subscriber base and multiple telecom circles. Even relatively small audit findings can therefore result in separate regulatory actions across individual LSAs.
DoT Continues to Tighten Telecom Compliance
The Airtel disclosures come as India’s telecom regulatory framework continues to place greater emphasis on subscriber verification and compliance. DoT’s LSA structure allows regulatory authorities to conduct circle-level checks and take action when operators are found to have fallen short of prescribed requirements.
The two Airtel cases also demonstrate why regulatory disclosures need to be read individually. A penalty notice does not necessarily mean that every observation is accepted by the operator, as illustrated by Airtel’s decision to challenge the Madhya Pradesh case.
For Airtel, the immediate financial impact of Rs 8.91 lakh is relatively small compared with the company’s overall operations. The more significant issue is the compliance process itself, particularly as telecom operators move between physical documentation and increasingly digital customer-enrolment systems.
The company’s decision to pay the Andhra Pradesh penalty while seeking rectification of the Madhya Pradesh notice also shows that regulatory disputes can vary from one LSA audit to another.












Leave a Reply
View Comments