Expert Guide
A complete walkthrough — Quarterly Tds Filing
Localised for Chintadripet, Chennai — where wholesale trade businesses dominate the local compliance profile.
Reading this guide locally — Chintadripet businesses operate where around the Cooum River catchment of Chintadripet, and Chintadripet businesses largely operate under standard GST monthly-return cycles and quarterly TDS streams.
What is TDS quarterly filing and when is it required
TAN as the unique identifier
Every deductor and collector requires a Tax Deduction Account Number under Section 203A obtained through Form 49B online via the Protean eGov-NSDL or UTIITSL portal. The ten-character TAN identifies the deductor across all four quarterly statements, all challans deposited under ITNS-281, all certificates issued in Forms 16, 16A, 16B, 16C, 16D, 16E and 27D, and the entire TRACES correspondence trail. Failure to obtain TAN before deduction does not relieve the deduction obligation but adds a Section 272BB penalty of ₹10,000. A single deductor may operate multiple TANs across branches, but the consolidated employer-level Form 24Q Annexure-II must reflect the salary breakup against the TAN under which Section 192 deductions are actually deposited. Branch-level deduction with consolidated reporting under a single TAN is permissible only where authorised under sub-rule (1A) of Rule 30, subject to the deductor selecting the consolidation option at the TAN registration stage.
OECD comparator on withholding architectures
The OECD Forum on Tax Administration Pay-As-You-Earn study identifies three withholding-architecture archetypes — cumulative annualised withholding (United Kingdom PAYE), per-period rate-table withholding (United States Federal Income Tax Withholding), and average-rate annualised withholding (Indian Section 192). The Indian Section 192 model under sub-section (3) requires the employer to estimate the employee's total annual salary, compute tax under the applicable regime — old or new under Section 115BAC — and apportion the resulting liability across remaining pay periods. This places India closer to the United Kingdom cumulative model than to the United States table-based model. The OECD International Compliance Assurance Programme recognises the average-rate model as administratively efficient where the employer has end-of-year reconciliation capacity, which Section 192 enables through Form 24Q Annexure-II at Q4. The non-salary withholding architecture under Section 194 series and Section 195 follows a transaction-rate model closer to the United States Form 1042 framework for payments to foreign persons, again reconciled quarterly through Form 26Q and Form 27Q.
Statutory architecture of Chapter XVII-B
Tax Deduction at Source in India is governed by Chapter XVII-B of the Income-tax Act 1961, spanning Sections 192 to 196D, and is supplemented by Tax Collected at Source under Section 206C. The substantive provisions impose a withholding obligation on the payer for specified categories of payment, while the procedural framework under Section 200(3) read with Rule 31A of the Income-tax Rules 1962 prescribes quarterly statements consolidating all deductions made during the quarter. The constitutional basis traces to Entry 82 of the Union List read with Article 246, with the withholding mechanism characterised by the Supreme Court in CIT v Eli Lilly and Company as a vicarious obligation discharged on behalf of the deductee. Four return forms cover the universe — Form 24Q for salary deductions under Section 192, Form 26Q for non-salary resident payments, Form 27Q for non-resident payments under Section 195 and allied provisions, and Form 27EQ for tax collected at source under Section 206C. The framework dates structurally to the 2003 amendments through the Finance Act 2002 which moved India from annual Form 26 reporting to a quarterly statement architecture aligned with OECD Forum on Tax Administration recommendations on real-time withholding compliance.
PAN validation and Section 206AA
Higher-rate consequence of non-PAN
Section 206AA inserted by the Finance Act 2009 prescribes a higher rate of withholding where the deductee does not furnish PAN — twenty per cent or the rate-in-force or the rate specified in the relevant provision, whichever is higher. The provision applies to both resident and non-resident deductees by its terms. For non-resident deductees, the interaction with treaty-rate access has been a contested area — the Special Bench of Pune ITAT in Serum Institute of India v Department of Customs and subsequent benches have held that Section 206AA cannot override treaty rates where the deductee provides alternate identification under Rule 37BC, while the Department's position relies on the textual primacy of Section 206AA non-obstante clause. Sub-section (7) of Section 206AA provides a statutory carve-out for interest on long-term infrastructure bonds issued by Indian companies under Section 194LC.
Section 206AB specified non-filer regime
Section 206AB inserted by the Finance Act 2021 and amended by the Finance Act 2022 imposes a higher-rate withholding on specified persons — deductees who have not filed an income-tax return for the relevant assessment year for which the time limit under Section 139(1) has expired, and whose aggregate TDS and TCS in that year is ₹50,000 or more. The applicable rate is twice the rate-in-force or twice the rate specified in the relevant provision, or five per cent, whichever is higher. The deductor identifies specified persons through the Compliance Check utility on the reporting-portal accessible through TRACES — bulk-query and per-PAN-query interfaces operate with API integration support for large deductors. The deductee row in Form 26Q and Form 27Q carries an indicator field for Section 206AB application, with FVU validation enforcing rate-consistency where the indicator is set.
Inoperative-PAN consequences under Section 139AA
Section 139AA(2) mandates linkage of Aadhaar with PAN, with the consequence of PAN becoming inoperative on failure to link by the prescribed date. CBDT Circular 3/2023 dated 28 March 2023 clarified that inoperative PAN attracts Section 206AA higher-rate consequences — twenty per cent or rate-in-force whichever is higher — equivalent to the no-PAN scenario, even though the PAN technically exists in the income-tax master. The deductor query through the TRACES PAN-verification utility returns the operative-or-inoperative status alongside the active-status check. Post-1-July-2023, deductors filing Form 26Q and Form 27Q must validate operative status for every deductee row to avoid Section 201(1) short-deduction demands. The Section 234H late-linkage fee imposed by the Finance Act 2021 applies at the deductee end for re-activation of inoperative PAN.
Section 234E late filing fee
Quantum and operation
Section 234E inserted by the Finance Act 2012 from 1 July 2012 imposes a fee of ₹200 for each day of default in filing the quarterly TDS or TCS statement under Section 200(3) or Section 206C(3) read with Rule 31A. The fee is capped at the total tax deductible or collectible during the relevant quarter — a deductor with ₹1,00,000 TDS deductible in a quarter cannot face Section 234E fee exceeding ₹1,00,000 regardless of the default duration. The fee is payable before furnishing the statement under sub-section (3) of Section 234E, which means delayed deductors must compute the fee, deposit it under ITNS-281 minor head code 400, and reflect the challan in the statement at upload. The provision faced constitutional challenge in Rashmikant Kundalia v UoI before the Bombay High Court, which upheld the validity on the basis that it is a fee for the regulatory cost of delayed reporting rather than a penalty requiring Section 273B mens-rea analysis.
Pre-2015 retrospectivity controversy
Section 234E enabled by the Finance Act 2012 was operative from 1 July 2012, but the enabling machinery provision under Section 200A — empowering the CPC-TDS to compute and demand the fee through statement processing — was inserted only by the Finance Act 2015 from 1 June 2015. The intervening three-year gap produced extensive litigation on whether Section 234E could be enforced through pre-2015 Section 200A intimations. The Karnataka High Court in Fatheraj Singhvi v UoI held that pre-1-June-2015 Section 200A intimations could not be the basis for Section 234E demands, requiring separate Section 271H proceedings. The Gujarat High Court in Rajesh Kourani v UoI took a contrary view upholding the pre-2015 intimations. The Bombay High Court in Rashmikant Kundalia took a middle position. The position remains unsettled at the Supreme Court level, with several Special Leave Petitions pending. Post-1-June-2015 enforcement is uncontroversial.
Interaction with Section 271H penalty
Section 234E operates parallel to Section 271H which imposes a separate penalty for failure to deliver the quarterly statement within the prescribed time — minimum ₹10,000 extending up to ₹1,00,000 per default. Section 271H(3) provides a saving where the deductor proves that the tax along with applicable fee and interest has been paid to the credit of the central government and the statement has been delivered before the expiry of one year from the time prescribed for delivering the statement. The interaction is therefore — Section 234E fee runs from the due date until the statement is filed irrespective of the underlying tax position, while Section 271H penalty applies only where the one-year-savings clause is not satisfied. A deductor who files within one year and has paid all underlying tax, fee and interest avoids Section 271H but still pays Section 234E. A deductor who files beyond one year faces both.
Section 271H penalty for non-filing
Saving under Section 271H(3) one-year window
Sub-section (3) of Section 271H provides a statutory saving — no penalty shall be imposed for failure under sub-section (1)(a) failure-to-deliver if the deductor proves that the tax deducted along with the fee and interest, if any, has been paid to the credit of the central government, and the statement has been delivered before the expiry of one year from the time prescribed for delivering the statement. The one-year window starts from the original due date under Section 200(3) — for Q1 due thirty-first of July, the one-year window expires thirty-first of July of the following year. The saving requires cumulative satisfaction — payment of all underlying tax, fee and interest, and delivery of the statement, both within the one-year window. The saving does not extend to sub-section (1)(b) incorrect-information penalty, which remains exposed independent of the one-year window. The Section 271H(3) saving is the single most important compliance backstop for delayed deductors.
Statutory architecture and triggers
Section 271H inserted by the Finance Act 2012 from 1 July 2012 empowers the Assessing Officer to impose penalty for failure to deliver the quarterly statement within the prescribed time under Section 200(3) or Section 206C(3), or for furnishing incorrect information in the statement. The penalty is not less than ₹10,000 and not exceeding ₹1,00,000 per default — each quarter's default is a separate offence attracting independent penalty exposure. The penalty under Section 271H is in addition to the fee under Section 234E, and both can be imposed on the same default. Unlike Section 234E which operates automatically through Section 200A processing, Section 271H requires a separate penalty proceeding initiated by the Assessing Officer with show-cause notice under Section 274 and the deductor's opportunity to respond. The Section 273B reasonable-cause defence is available against Section 271H but not against Section 234E.
Reasonable-cause defence under Section 273B
Section 273B operates as a saving provision against Section 271H, providing that no penalty shall be imposed for any failure referred to in Section 271H if the deductor proves that there was reasonable cause for the failure. The jurisprudence on reasonable cause is extensive — Hindustan Steel Limited v State of Orissa established the foundational principle that penalty discretion must be exercised judicially with attention to mens-rea and bona-fide conduct, and successive Tribunal decisions have applied the principle to Section 271H proceedings. Common reasonable causes accepted by Tribunals include technical-failure of the income-tax e-filing portal during the filing window, illness or unavailability of the authorised signatory with corroborating evidence, force-majeure events including natural disasters and pandemic disruptions, and good-faith reliance on tax-professional advice subsequently shown to be erroneous. The reasonable-cause defence requires affirmative proof — generic statements without documentary corroboration are routinely rejected.
What Chintadripet clients usually ask next: Closer to Chintadripet, where wholesale trade businesses dominate the local compliance profile, which is why for Chintadripet businesses balancing growth ambitions with tight statutory compliance.