Clause 262 Permanent Account Number.

Income Tax Bill, 2025

Introduction

Clause 262 of the Income Tax Bill, 2025, represents a comprehensive statutory framework governing the allotment, quoting, and authentication of the Permanent Account Number (PAN), and its interlinkage with Aadhaar numbers. Specifically, sub-clause (9) introduces significant procedural and compliance obligations concerning the quoting and authentication of PAN or Aadhaar in prescribed transactions. This clause must be analyzed not in isolation, but in the context of the broader legislative intent to strengthen tax administration, ensure transparency in financial transactions, and curb tax evasion by leveraging digital identity infrastructure.

Section 139AA of the Income Tax Act, 1961, introduced in 2017, marked the beginning of the statutory mandate to quote and link Aadhaar numbers with PAN. However, the scope and operational mechanics of Section 139AA are comparatively narrow, focusing primarily on the linking and quoting of Aadhaar in PAN applications and income tax returns. The evolution from Section 139AA to Clause 262, particularly sub-clause (9), signifies an expansion and deepening of the regulatory regime, reflecting both technological advancements and policy learnings over the past decade.

Objective and Purpose

The core legislative intent behind Clause 262(9) is to ensure that every person entering into specified transactions quotes and authenticates their PAN or Aadhaar number. This requirement aims to establish an auditable trail for high-value or sensitive transactions, thereby enhancing the ability of tax authorities to monitor, verify, and, where necessary, investigate financial flows. The authentication requirement further seeks to prevent impersonation, identity fraud, and the proliferation of multiple PANs, issues that have historically undermined tax compliance and enforcement.

The policy rationale draws from the increasing digitization of the Indian economy and the centrality of Aadhaar as a unique biometric identifier. By integrating PAN and Aadhaar authentication into the documentation of transactions, the legislature intends to create a robust ecosystem for taxpayer identification, reduce the scope for benami (proxy) transactions, and facilitate seamless information exchange between various regulatory authorities.

Detailed Analysis of Clause 262(9) of the Income Tax Bill, 2025

Text of Clause 262(9)

(a) Every person entering into such transaction, as prescribed, shall quote his Permanent Account Number or Aadhaar number, in the documents pertaining to such transactions and also authenticate such Permanent Account Number or Aadhaar number, in the manner, as prescribed;
(b) every person receiving any document relating to the transactions referred to in clause (a), shall ensure that Permanent Account Number or Aadhaar number, has been duly quoted in such document and that such Permanent Account Number or Aadhaar number is authenticated as prescribed.

Key Provisions and Their Interpretation

• Scope of Applicability:
  • Clause 262(9)(a) applies to "every person entering into such transaction, as prescribed." The phrase "as prescribed" delegates the authority to the Central Board of Direct Taxes (CBDT) to specify, via rules or notifications, the categories of transactions that will require quoting and authentication of PAN or Aadhaar. This could encompass high-value cash transactions, property purchases, investments, or any other transaction deemed sensitive from a tax compliance perspective.
  • Clause 262(9)(b) places a corresponding obligation on the recipient of such documents (e.g., banks, registrars, brokers, or any other counterparty) to ensure not only that the PAN or Aadhaar number is quoted but also that it is authenticated as prescribed. This creates a dual compliance regime, targeting both the initiator and the receiver of the transaction.
• Quoting and Authentication:
  • The requirement is not limited to mere quoting of PAN/Aadhaar but extends to "authentication." Authentication, as defined in Clause 262(13)(c), involves verification of the number along with demographic or biometric information, to confirm its correctness through prescribed authorities or agencies. This is a marked shift from earlier regimes where quoting was often a formality and not subject to real-time verification.
  • The authentication process leverages the digital infrastructure established under the Aadhaar Act, 2016, and the PAN database maintained by the Income Tax Department. This may involve online verification, OTP-based confirmation, or biometric checks, depending on the nature of the transaction and the rules framed by the CBDT.
• Prescribed Transactions:
  • The clause does not, in itself, enumerate the specific transactions to which it applies. This is a deliberate legislative choice, conferring flexibility on the executive to adapt to emerging risks and patterns of tax evasion. Historically, prescribed transactions for PAN quoting have included property transactions above certain thresholds, opening of bank accounts, purchase of mutual funds, etc. The new framework is likely to expand this ambit, given the explicit reference to authentication.
• Enforcement and Compliance:
  • By making both parties to a transaction responsible for compliance, the clause creates a system of mutual checks and balances. The recipient is not only a passive collector of information but an active verifier of its authenticity. This is expected to significantly reduce the incidence of forged or invalid PANs/Aadhaars being used in financial transactions.
  • Non-compliance, though not specifically penalized in Clause 262(9), is likely to attract consequences under the broader penalty provisions of the Income Tax Act, such as Section 272B (for failure to comply with PAN quoting requirements), or other relevant sections as may be amended or introduced in the 2025 Bill.
• Delegated Legislation:
  • The clause relies heavily on subordinate legislation for operational details-what transactions are covered, how authentication is to be carried out, what exceptions apply, etc. This enables rapid regulatory responses but may also create uncertainty for stakeholders until the rules are notified.

Ambiguities and Potential Issues in Interpretation

• Ambit of "Prescribed Transactions": The open-ended delegation to the CBDT to specify transactions could lead to regulatory overreach or frequent changes, creating compliance challenges for businesses and individuals.
• Authentication Modalities: The clause does not specify whether authentication must be online, biometric, or demographic. The rules may prescribe different standards for different transactions, which could lead to operational complexity.
• Privacy and Data Security: The requirement to authenticate Aadhaar/PAN in every prescribed transaction raises concerns about data privacy, especially in the absence of a comprehensive data protection regime. The sharing of biometric or demographic information with multiple agencies increases the risk of data breaches and misuse.
• Enforcement Burden: The responsibility placed on recipients (e.g., banks, real estate registrars) to verify and authenticate PAN/Aadhaar may necessitate significant investment in IT systems, training, and compliance processes.
• Overlap with Other Laws: The interplay between this clause and other laws (such as the Prevention of Money Laundering Act, 2002, and the Aadhaar Act, 2016) may result in conflicting obligations or duplicative compliance requirements.

Practical Implications

• For Individuals: Individuals entering into high-value or specified transactions will be required not only to quote but also to authenticate their PAN or Aadhaar. This may require access to digital devices or biometric authentication points, potentially excluding those without digital literacy or access.
• For Businesses and Institutions: Entities receiving documents (banks, financial institutions, property registrars, etc.) must implement systems to verify the authenticity of PAN/Aadhaar numbers. This may involve integration with government databases and adherence to prescribed protocols, increasing compliance costs.
• For Tax Authorities: The clause provides a powerful tool for data-driven monitoring and risk assessment. By ensuring that every significant transaction is linked to a verified identity, the authorities can better detect tax evasion, benami transactions, and money laundering.
• For Regulators: The cross-referencing of PAN and Aadhaar across multiple regulatory filings (income tax returns, GST returns, property registries, etc.) will facilitate greater inter-agency coordination and information sharing.
• For Technology Providers: There will be increased demand for secure, user-friendly authentication solutions that comply with the evolving regulatory landscape.

Comparative Analysis with Section 139AA of the Income Tax Act, 1961

1. Scope and Focus

• Section 139AA, introduced by the Finance Act, 2017, primarily mandates the quoting of Aadhaar numbers in applications for PAN and in income-tax returns, and the linking of PAN and Aadhaar for persons eligible to obtain Aadhaar. Its principal focus is on the integration of Aadhaar with PAN for the purposes of tax identification and return filing. The section also provides for the inoperability of PAN in case of non-linking with Aadhaar.
• Clause 262(9) goes beyond the mere quoting and linking of Aadhaar and PAN. It extends the requirement to a broader class of transactions (to be prescribed) and introduces a mandatory authentication process, as well as a reciprocal obligation on recipients of transaction documents.

2. Quoting and Authentication

• Section 139AA: Requires quoting of Aadhaar in (i) the application for PAN and (ii) the return of income. There is no explicit requirement for authentication of the Aadhaar number at the point of transaction or return filing, although the process of PAN-Aadhaar linking may involve some verification.
• Clause 262(9): Mandates not only quoting but also authentication of PAN/Aadhaar in prescribed transactions, and requires both parties to the transaction to ensure compliance. This represents a significant tightening of the compliance regime, with an emphasis on real-time verification and traceability.

3. Applicability

• Section 139AA: Applies primarily to individuals eligible for Aadhaar, and is limited to PAN application and income-tax return filing. It does not directly address transactional compliance or obligations of document recipients.
• Clause 262(9): Applies to "every person" entering into prescribed transactions, regardless of whether the transaction is related to return filing or PAN application. It also imposes obligations on the recipients of documents, such as banks, property registrars, and other intermediaries.

4. Delegated Legislation

• Section 139AA: Empowers the Central Government to notify classes of persons or areas to which the section does not apply, but does not provide for the prescription of specific transactions or detailed authentication protocols.
• Clause 262(9): Delegates significant rule-making authority to the CBDT to specify transactions, authentication methods, and compliance procedures, thereby enabling a dynamic and evolving compliance framework.

5. Enforcement and Sanctions

• Section 139AA: Provides for the inoperability of PAN in cases of non-linking with Aadhaar, but does not address penalties for non-quoting or non-authentication in transactional contexts.
• Clause 262(9): While not specifying penalties within the clause itself, it is to be read in conjunction with other provisions of the Bill/Act that provide for penal consequences for failure to comply with PAN-related obligations in transactions.

6. Data Privacy Considerations

• Section 139AA: Does not specifically address privacy or data security, though the Aadhaar Act and IT Act apply.
• Clause 262(9): By introducing authentication, it raises heightened privacy and security issues, necessitating robust safeguards in subordinate legislation and operational practice.

7. Technological and Administrative Implications

• Section 139AA: Involves relatively straightforward administrative processes (PAN application, return filing, linking).
• Clause 262(9): Requires the development and deployment of authentication infrastructure, integration with government databases, and potentially the use of APIs and digital platforms for real-time verification.

Comparative Points Table

Key Similarities

• Both provisions aim to link the tax identity (PAN) with the unique biometric identifier (Aadhaar) to improve taxpayer identification and compliance.
• Both allow for exceptions to be notified by the Central Government for specified persons, classes, or regions.
• Both rely on subordinate legislation for operational details.

Key Contrasts

• Expansion of Compliance Net: Clause 262(9) extends the requirement far beyond the realm of income tax returns and PAN applications, bringing a much wider array of economic activities within the compliance net.
• Active Verification: The authentication requirement in Clause 262(9) marks a qualitative leap from the passive quoting regime of Section 139AA, aiming to eliminate the use of false or duplicate identities in financial transactions.
• Recipient's Responsibility: The new regime makes the recipient of transaction documents an active participant in the compliance process, creating a two-sided enforcement mechanism.
• Technological and Operational Demands: The new regime will require significant technological upgrades and operational changes for businesses and institutions, in contrast to the relatively straightforward compliance u/s 139AA.

Potential Conflicts and Harmonization

While the two provisions are broadly complementary, there is potential for overlap and confusion, particularly where the same transaction triggers obligations under both. Harmonization of rules and clear guidance from the CBDT will be essential to avoid duplicative compliance and ensure smooth implementation.

Conclusion

Clause 262(9) of the Income Tax Bill, 2025 , represents a paradigm shift in the regulatory approach to taxpayer identification and transaction monitoring. By mandating not only the quoting but also the authentication of PAN/Aadhaar in prescribed transactions, and by placing compliance obligations on both parties to a transaction, the clause seeks to create a robust, technologically-enabled framework for tax compliance and enforcement. This stands in marked contrast to the more limited and passive regime of Section 139AA, which focused primarily on linking Aadhaar with PAN at the point of application and return filing.

The success of the new regime will depend on the clarity and practicality of the rules framed under the clause, the adequacy of technological infrastructure, and the protection of individual privacy. As the compliance net widens, stakeholders must prepare for increased procedural rigor and potential scrutiny, even as the tax administration gains powerful new tools to combat evasion and promote transparency. The transition from Section 139AA to Clause 262(9) thus reflects both the promise and the challenges of a digital, interconnected tax compliance ecosystem.

Full Text:

Clause 262 Permanent Account Number.