Quarterly TDS Filing in Koyambedu Flower Market, Chennai

Section 192 of the Income-tax Act 1961 casts an obligation on every person responsible for paying any income chargeable under the head Salaries to deduct income-tax at the average rate of tax computed on the basis of rates in force for the financial year. It is to be noted that the deduction is to be effected at the time of payment and not on accrual. Sub-section (2B) permits the employee to furnish particulars of other income for inclusion. The aggregated tax so deducted is reportable in Form 24Q on a quarterly basis.

Section 194A applies to any person, not being an individual or HUF below the audit threshold under Section 44AB, paying interest other than interest on securities to a resident. Sub-section (1) requires deduction at rates in force at the time of credit or payment, whichever is earlier. Sub-section (3) lists thresholds — currently forty thousand rupees per payee per financial year for banks and ten thousand rupees in other cases, with fifty thousand rupees for senior citizens. The deductions are aggregated in Form 26Q.

Sub-section (1) of Section 194C provides that any person responsible for paying a sum to a resident contractor for carrying out any work, including supply of labour, in pursuance of a contract is required to deduct tax at one per cent where the payee is an individual or HUF and at two per cent in other cases. Sub-section (5) sets the thresholds at thirty thousand rupees per single payment and one lakh rupees in the aggregate for a financial year. The deductions are reportable in Form 26Q.

Section 194J governs deduction of tax at source on payments for professional services, technical services, royalty, non-compete fees and remuneration to directors. Sub-section (1) prescribes deduction at ten per cent on professional services and two per cent on fees for technical services where the payer is not an individual or HUF below the audit threshold. The threshold is thirty thousand rupees in the aggregate per financial year per service category. Form 26Q reports these deductions.

Section 195 requires any person responsible for paying to a non-resident, not being a company, or to a foreign company any interest or any other sum chargeable under the provisions of the Act, to deduct tax at the rates in force. Sub-section (1) operates at the time of credit or payment, whichever is earlier. Sub-section (2) permits the payer to apply to the Assessing Officer for determination of the appropriate portion chargeable to tax. The deductions populate Form 27Q quarterly.

Sub-section (1) of Section 200 obliges any person deducting any sum under the foregoing provisions of Chapter XVII-B to pay the sum so deducted to the credit of the Central Government in the prescribed manner. Sub-section (3) further requires that the deductor prepare and furnish a quarterly statement of deductions in such form and verified in such manner as may be prescribed. Rule 31A operationalises this requirement and prescribes Forms 24Q, 26Q, 27Q and 27EQ.

What is TDS quarterly filing and when is it required

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.

Trigger events for the deduction obligation

Sub-section (1) of each provision under Sections 192 to 196D specifies the trigger event — for Section 192 it is the actual payment of salary, while for Section 194C, Section 194J, Section 194-I and most non-salary provisions it is the earlier of credit to the payee's account or actual payment. The credit-or-payment-whichever-is-earlier formulation, encoded uniformly across the Chapter, was clarified by CBDT Circular 3/2010 to apply even to suspense accounts, provision accounts, and any other credit by whatever name called in the deductor's books. Section 194Q, introduced by the Finance Act 2021, applies the trigger to buyers whose preceding-year turnover exceeds ₹10 crore making purchases above ₹50 lakh per seller per year. The Section 206AB higher-rate trigger applies where the deductee is a specified person who has not filed returns for the preceding two years and has aggregate TDS-TCS of ₹50,000 or more in each of those years — verified through the Compliance Check utility on the reporting portal before each payment.

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.

TRACES portal architecture

Online correction versus offline FVU correction

Two correction routes operate parallel — online corrections through the TRACES portal interface for simple updates including C1 deductor-details and C5 PAN-update, and offline corrections through the Return Preparation Utility followed by FVU validation and conso-file upload for complex updates including C3 deductee-row-update and C9 new-challan-and-deductee. The online route requires digital-signature-certificate authentication of the authorised signatory and processes within seconds. The offline route requires download of the consolidated file from TRACES, modification through RPU, FVU validation, and upload through the income-tax e-filing portal — processing takes hours to days. Choice of route depends on correction type and statement volume — small corrections favour online, bulk corrections affecting hundreds of deductee rows favour offline. The CBDT Notification 36/2019 unified the correction-statement architecture and eliminated the legacy paper-based correction workflow.

Deductor-side functionality

The TRACES portal at the tdscpc.gov.in domain provides the operational interface for deductors — registration of TAN with authorised-signatory details and digital-signature-certificate, request and download of consolidated files for correction-statement preparation, request and download of Form 16 Part A and bulk Form 16A, certificate generation under Section 197 reference matching, declaration filing under Form 27C for sub-section (1A) of Section 206C nil collection on manufacturing-purpose declarations, online correction submission for C1 through C9 correction types, and challan-status query against deposited ITNS-281. The PAN-verification utility and the Section 206AB Compliance Check utility are accessed through TRACES with API-based bulk-query support for large deductors. The deductor inbox aggregates intimations under Section 200A(1) on processing of quarterly statements, demand notices under Section 156 read with Section 201, and Form 26AS reconciliation prompts.

Deductee-side functionality and Form 26AS

Deductees access TRACES through the income-tax e-filing portal SSO integration. Form 26AS — the Annual Tax Statement under Section 203AA and Rule 31AB — consolidates per-deductee data from all deductors across the financial year covering TDS deductions under Form 26Q, salary deductions under Form 24Q, non-resident deductions under Form 27Q, TCS collections under Form 27EQ, advance-tax and self-assessment-tax payments through OLTAS, Section 285BA Statement of Financial Transactions high-value transactions, and turnover information from GSTN. The migration of high-volume reporting to the Annual Information Statement under Rule 114-I from 2021 has shifted the comprehensive deductee picture to AIS while Form 26AS retains the tax-credit core. The deductee reconciles the pre-filled return Schedule TDS columns against AIS and Form 26AS at return filing — discrepancies are flagged through the feedback mechanism in AIS for deductor-side correction action.

PAN validation and Section 206AA

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.

PAN format and active-status check

PAN validation in TDS quarterly statements operates at two levels. Format validation at the FVU stage applies the standard ten-character structure — first three letters alphabetic, fourth letter the entity-type code (P for individual, C for company, H for HUF, F for firm, A for AOP, T for trust, B for BOI, L for local authority, J for AJP, G for government), fifth letter the first character of the surname for individuals or the first character of the name for non-individuals, next four characters numeric, last character alphabetic check-digit. Active-status validation at the TRACES processing stage queries the income-tax department PAN master to verify that the PAN is allotted and active — PANs that are de-duplicated, inoperative under Section 139AA for Aadhaar non-linkage, or otherwise flagged trigger Section 206AA higher-rate consequences. The Section 139AA Aadhaar-PAN linkage requirement, with the post-2023 inoperative-PAN consequences under CBDT Circular 3/2023, has materially expanded the PAN-validation reconciliation workload.

Section 234E late filing fee

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.

OECD framework on late-filing penalty design

The OECD Forum on Tax Administration 2013 study on tax-administration penalties identifies a global convergence on day-based late-filing fees for withholding statements, with rates typically calibrated to a small multiple of the underlying tax-at-risk per day. The Indian Section 234E ₹200 per day fee falls within this range relative to the typical TDS quantum per quarter, and the capping at total tax deductible aligns with the OECD principle of proportionality between regulatory fee and underlying compliance value. The United Kingdom Real Time Information regime imposes parallel late-submission penalties scaled by employer size. The Australian Single Touch Payroll regime applies a similar day-based framework. Comparison with the European Union Directive on Administrative Cooperation in Direct Taxation enforcement framework shows that the Indian Section 234E framework is structurally aligned with international good practice in design, though enforcement automation through Section 200A CPC processing is at the leading edge of administrative practice.

Q1 Form 26Q late fee capped at deduction amount under Section 234E proviso

Q4 Annexure II salary-detail correction enabled employee refund claim

Section 194Q vs 206C(1H) overlap settled by buyer-take-precedence rule

Section 194N cash-withdrawal default avoided through bank-side reconciliation

Other Services in Koyambedu Flower Market, Chennai

What Koyambedu Flower Market Clients Say