Expert Guide
A complete walkthrough — Quarterly Tds Filing
Localised for Royapettah, Chennai — where hotels restaurants and serviced-apartment operators file GST under composite supply rules and seasonal-occupancy cycles.
Reading this guide locally — Royapettah businesses operate where in the healthcare hospitality residential micro-market of Royapettah, and Royapettah businesses in the hospitality arm find that GST rate disputes between 5% non-AC and 12% AC service composite-supply versus mixed-supply classification arise repeatedly.
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.
Section 200(3) statutory due dates
OECD comparator on statement-filing cadence
The OECD Forum on Tax Administration 2019 study on real-time reporting identifies a global trend from quarterly toward monthly and real-time withholding reporting. The United Kingdom Real Time Information regime requires payroll withholding reporting on or before each payment under the Full Payment Submission framework. The Australian Single Touch Payroll regime operates similarly. The European Union Directive on Administrative Cooperation in Direct Taxation extension under DAC7 imposes platform-economy reporting closer to annual cadence. India's Section 200(3) quarterly cadence sits between the OECD monthly trendline and the legacy annual-reporting baseline, with the Section 285BA Statement of Financial Transactions adding annual reporting on top. Discussion at the Tax Administration Reforms Commission and at successive Budget consultations has periodically raised proposals to move to monthly Form 24Q-equivalent reporting, but no statutory amendment has been enacted as of the current framework.
Quarterly statement filing window under Rule 31A
Sub-section (3) of Section 200 read with Rule 31A prescribes the due date for filing quarterly TDS statements as the thirty-first day of the month following the quarter-end, except for the Q4 January-to-March quarter where the due date is the thirty-first of May to allow time for Annexure-II salary breakup compilation. The Q1 April-to-June statement is due thirty-first of July, Q2 July-to-September is due thirty-first of October, Q3 October-to-December is due thirty-first of January, and Q4 is due thirty-first of May. For Form 27EQ TCS quarterly statements, the due dates are fifteen days earlier — fifteenth of July, fifteenth of October, fifteenth of January and fifteenth of May respectively. The TCS-earlier-by-fifteen-days structure recognises the higher transaction volume and the need to flow into the buyer-side credit availability faster. Government deductors filing through Form 24G face a separate due-date framework under Rule 30(4) — fifteenth of the next month for monthly statements.
Challan deposit timeline under Rule 30
Rule 30 of the Income-tax Rules prescribes the challan-deposit timeline separately from the statement-filing timeline. For non-government deductors, the deposit is due by the seventh of the month following the month of deduction, except for deductions made in March which are deposited by the thirtieth of April. For government deductors making payment without the production of a challan — the treasury-route deductors — deposit is on the same day as deduction. Where deduction is made on a payment to a non-resident, the seventh-of-next-month deadline applies uniformly with the Form 27Q quarterly reporting following on the standard end-of-month-after-quarter timeline. The ITNS-281 challan must specify the section code under which the deduction is made, the deductor TAN, and the assessment year — errors in the assessment year field flow into the Form 26Q upload as challan-unmatched defects requiring TRACES-portal correction before the FVU validation will accept the statement.
Form 24Q Q4 Annexure-II salary breakup
Regime declaration field
Annexure-II includes a dedicated field for the regime under which the salary is taxed — the new regime under Section 115BAC(1A) is the default, with the old regime applying only where the employee files Form 10-IEA exercise. The regime field has downstream consequences — under the new regime, the Chapter VI-A columns other than Section 80CCD(2) and Section 80JJAA are nil, the Section 10 exemption columns other than agricultural income are nil, and the standard deduction under Section 16(ia) at ₹50,000 is available (enhanced to ₹75,000 under the new regime from assessment year 2024-25 by the Finance Act 2023). The employee's pre-filled return at the deductee end reflects the regime declared in Annexure-II — a mid-year regime switch by the employee at the return-filing stage creates a reconciliation gap that the deductee must resolve through Schedule TR or by writing the correct allowable deduction position into the return manually.
Common reconciliation defects
Quarterly review of Annexure-II reveals recurring defect patterns — under-reporting of perquisite values where the payroll system does not load ESOP exercise data, mis-mapping of leave-encashment under Section 10(10AA) where the deductor classifies a private-sector employee under the government-employee exemption limb, omission of the Section 192A withholding on premature provident-fund withdrawals which require separate Form 26Q reporting under Section 192A rather than aggregation into the Form 24Q salary line, and aggregation of relocation reimbursement actuals into the gross salary rather than treating them as non-taxable reimbursements under CBDT Circular 5/2010 paragraph 5.3.4. Each defect propagates to the Form 16 Part B issued to the employee and to the pre-filled return data — early reconciliation at FVU validation stage avoids downstream Section 143(1)(a) notices at the employee end.
Section 17 component reporting
Annexure-II of Form 24Q for the Q4 quarter consolidates the full-year salary picture per employee. The reporting structure mirrors Section 17 — sub-section (1) salary including basic pay, dearness allowance, fees, commission, perquisites and profits in lieu; sub-section (2) value of perquisites computed under Rule 3 covering rent-free accommodation, motor car, free or concessional travel, free meals beyond Rule 3(7)(iii), gifts beyond ₹5,000, club membership, credit-card facility, interest-free or concessional loans, ESOP perquisite under Rule 3(8); sub-section (3) profits in lieu of salary covering compensation for termination, payments from unrecognised funds, and certain key-man insurance receipts. Each sub-section feeds a distinct column in Annexure-II, and the deductor must reconcile the payroll register to the Annexure-II columns line by line. Errors in this allocation propagate to Form 16 Part B and to defective-return notices at the employee end.
Form 26Q vendor TDS framework
Deductee row population and PAN validation
Each deductee row in Form 26Q carries the deductee PAN, name, date of payment or credit, amount paid or credited, amount of tax deducted, surcharge, health and education cess, total tax deposited, challan-identification-number reference linking to the challan deposited under ITNS-281, certificate number for any Section 197 lower-deduction certificate applied, and remarks for any special characterisation. PAN validation occurs at two stages — at FVU validation through PAN-format-check (ten characters, fourth character status code, fifth character first letter of surname), and at TRACES portal processing through PAN-active-status check against the income-tax department PAN master. Invalid or inactive PAN rows trigger Section 206AA higher-rate withholding at twenty per cent or rate-in-force whichever is higher, and the deductor must re-upload corrected statements once PAN is validated.
Section 197 lower-deduction certificates
Section 197 read with Rule 28AA permits the deductee to apply for a certificate authorising deduction at a lower rate or nil rate. The application is filed in Form 13 through the TRACES portal by the deductee, with the Assessing Officer issuing a certificate addressed to the deductor specifying the rate, the period of validity, and the maximum amount on which the lower rate applies. The certificate number must be populated in the certificate-number column of the deductee row in Form 26Q for the lower rate to be accepted at FVU validation. Where the certificate-validity period spans multiple quarters, the same certificate number is repeated across quarterly statements. Where the maximum-amount cap is reached during the validity period, subsequent payments revert to the rate-in-force without certificate reliance. The post-2018 fully-online Form 13 workflow under CBDT Notification 8/2018 has eliminated the historical physical-certificate exchange friction.
Correction statement architecture
Form 26Q corrections are governed by Rule 31A(5) and the TRACES portal correction-statement workflow. Six types of corrections are supported — C1 update of deductor details, C2 update of challan details, C3 update of deductee row details, C4 addition of new salary detail (24Q only), C5 update of PAN of deductee, and C9 addition of new challan and underlying deductee rows. Corrections are filed against the same TAN and quarter as the original statement, identified through the original-token-number reference. The consolidated file generated by TRACES after correction processing supersedes the original statement and feeds the deductee Annual Information Statement. Correction-statement filings are not subject to a separate Section 234E fee window — the Section 234E ₹200 per day fee under sub-section (1) applies to the original statement default and is computed based on the gap between the due date and the first valid statement filing.
What Royapettah clients usually ask next: For Royapettah engagements specifically — supporting medical professionals and allied healthcare staff commuting from the surrounding residential pockets; where hotels restaurants and serviced-apartment operators file GST under composite supply rules and seasonal-occupancy cycles; for the professional and salaried population of Royapettah navigating personal-tax and home-office GST.