Anna Nagar Quarterly TDS Filing for healthcare Businesses

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.

PAN validation and Section 206AA

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.

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 234E late filing fee

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.

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.

Section 271H penalty for non-filing

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.

Incorrect-information penalty leg

Sub-section (1)(b) of Section 271H imposes penalty for furnishing incorrect information in the quarterly statement — typically incorrect PAN of deductee, incorrect challan-identification-number, incorrect section code, incorrect amount of tax deducted, or any other field-level error that affects the substantive accuracy of the statement. The incorrect-information leg has produced distinct jurisprudence focused on materiality — minor clerical errors corrected through subsequent correction-statements have generally been held to not attract Section 271H, while substantive errors affecting deductee credit have attracted penalty. The Tribunal in several decisions has applied the de-minimis principle — errors below five per cent of the affected statement value typically do not invite penalty, while errors above ten per cent typically do, with the intermediate range subject to facts-and-circumstances analysis. The interaction with the C3 correction-statement workflow is critical — timely C3 correction typically establishes good-faith and supports the reasonable-cause defence.

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.

Q4 Annexure II salary-detail correction enabled employee refund claim

ITAT Chennai allows Section 273B reasonable-cause defence on Section 271C penalty

Section 194O e-commerce-operator deduction confirmed for restaurant aggregator

Form 24Q first-time-filer welcomed on Aadhaar-OTP route

Other Services in Anna Nagar, Chennai

What Anna Nagar Clients Say