Form 24Q: TDS Return Filing Guide for Employers

Form 24Q Explained: A 2026 TDS Return Filing Guide for Employers

Most employers in India understand that they must deduct tax at source (TDS) from salaries. Fewer fully understand the quarterly reporting that sits behind it — and that is where penalties, mismatched Form 16s, and frustrated employees come from. The instrument at the centre of this reporting is Form 24Q, the quarterly TDS return for salary payments.

If you run payroll for a startup or SMB, Form 24Q is one of those compliance obligations that is entirely manageable once you understand its rhythm, but quietly expensive if you let it slip. Late filing carries a daily fee, errors cascade into incorrect Form 16s, and unresolved mismatches show up in your employees' Form 26AS and Annual Information Statement, generating exactly the kind of "why does the tax department think I earned this?" query that erodes trust in your payroll team.

This guide explains what Form 24Q is, how its annexures work, the quarterly calendar you must keep, how the salary TDS reporting connects to the Form 16 you eventually issue, the penalties for getting it wrong, and a practical workflow to keep filings clean. As always with tax, treat specific thresholds and rates as illustrative; verify the current figures on the official Income Tax and TRACES portals before filing, since they change with each Finance Act.

What Form 24Q actually is

Form 24Q is the statement an employer ("deductor") files every quarter to report the salary it paid to employees and the TDS it deducted and deposited against those payments. Think of it as the bridge between three things: the tax you withheld from each salary, the tax you deposited with the government, and the credit your employees ultimately claim when they file their income tax returns.

When you deduct TDS from a salary, you deposit it with the government using a challan, quoting your Tax Deduction and Collection Account Number (TAN). But depositing the money is not enough. The government needs to know whose tax that was — which employee, against which PAN, for how much income. Form 24Q carries that attribution. Without it, the deposited tax cannot be credited to the right employee, and your staff cannot claim it.

This is why Form 24Q is filed against your TAN (not your PAN), why it lists every salaried employee from whom tax was deducted, and why accuracy of PAN and amounts is so critical: the entire downstream chain — Form 26AS, the Annual Information Statement, the employee's pre-filled return, and the Form 16 you issue — is built from what you report here.

The two annexures: where the detail lives

Form 24Q has two parts, and understanding the difference between them is the key to filing it correctly.

Annexure I is filed for every quarter. It contains the deductee-wise (employee-wise) breakup of salary paid and tax deducted during that quarter, along with the challan details showing that the deducted tax was actually deposited. In essence, Annexure I answers: "This quarter, for each employee, how much did you pay, how much did you deduct, and into which challan did it go?"

Annexure II is filed only with the fourth-quarter return (the January–March quarter). It is the annual salary statement — the complete picture of each employee's total income for the financial year, the deductions and exemptions claimed, the chosen tax regime, the tax computed, and the tax deducted across the whole year. Annexure II is, effectively, the raw material from which Form 16 Part B is generated.

This structure has an important practical consequence: the fourth-quarter Form 24Q is the most important and most detailed filing of the year. Get Annexure II right and your Form 16s flow cleanly. Get it wrong and you will be issuing corrections to employees right in the middle of their own tax-filing season.

The quarterly calendar you must keep

Form 24Q follows the financial year's four quarters, each with its own filing deadline that falls after the quarter closes. The standard pattern is:

• Quarter 1 (April–June): return due by the end of July.
• Quarter 2 (July–September): return due by the end of October.
• Quarter 3 (October–December): return due by the end of January.
• Quarter 4 (January–March): return due by the end of May, and this is the return that carries Annexure II.

These are the conventional due dates; the government occasionally extends them, and exact dates can shift, so confirm each quarter's deadline on the official portal. Build the four dates into your compliance calendar at the start of every financial year, with internal reminders a week or two ahead so your team has buffer to fix validation errors.

Separately — and this trips up many new payroll teams — the TDS deposit deadline is monthly, not quarterly. The tax you deduct in a given month generally must be deposited by the seventh of the following month (with a special rule for March). Form 24Q reports those deposits quarterly, but the cash must reach the government monthly. Missing the monthly deposit triggers interest, independent of the quarterly return.

How Form 24Q connects to Form 16

Employees rarely see Form 24Q, but they care deeply about its output: Form 16, the TDS certificate you issue annually. Understanding the link prevents a lot of confusion.

Form 16 has two parts. Part A — containing the summary of tax deducted and deposited, quarter by quarter — is generated and downloaded from the TRACES portal and bears a unique certificate number. It is built directly from the challan and deduction data you reported across your four Form 24Q filings. Part B, the detailed annexure showing salary breakup, exemptions, deductions, and tax computed, is built from the Annexure II data in your fourth-quarter return.

The chain of dependency is therefore: accurate monthly TDS deposit → accurate quarterly Annexure I → complete and correct Annexure II in Q4 → correct Form 16 Part A and Part B → correct credit in the employee's Form 26AS and pre-filled return. A break anywhere in this chain surfaces as an employee-facing problem. If an employee complains that their Form 26AS shows less TDS than their payslips, the root cause is almost always a Form 24Q reporting gap or a PAN error, not a deposit failure.

This is why disciplined Form 24Q filing is, ultimately, an employee-experience issue as much as a compliance one.

Information you need before you file

Filing goes smoothly when the inputs are ready. Before preparing a Form 24Q return, assemble:

• Your TAN, valid and active. Returns are filed against it.
• Employee PANs, verified and correct. An invalid or missing PAN attracts a higher rate of tax deduction and creates credit-allocation failures. PAN accuracy is the single highest-leverage data-quality item in the whole process.
• Challan details for every TDS deposit made during the quarter — the challan identification number, the amount, and the date — so deductions can be mapped to deposits.
• Salary and deduction data per employee: gross salary, exemptions, the tax regime each employee elected, deductions declared and proof-verified, and tax deducted each month.
• The applicable return-preparation utility, since returns are validated and generated in a prescribed electronic format before submission.

A surprising amount of filing pain comes from challan mismatches — where the tax reported as deducted does not reconcile to the tax shown as deposited in the challan. Reconciling challans to deductions before you generate the file, rather than after the portal rejects it, is the habit that separates calm filers from stressed ones.

The filing workflow, step by step

While the exact screens evolve, the logical workflow for each quarter is consistent:

Step 1 — Reconcile the quarter. Confirm that the TDS deducted from salaries matches the TDS deposited via challans for each month of the quarter. Resolve any gaps first.

Step 2 — Prepare the return in the prescribed utility. Enter or import deductor details (TAN), challan details, and the deductee-wise breakup for Annexure I. For the Q4 return, also complete Annexure II with each employee's annual salary, regime, deductions, and computed tax.

Step 3 — Validate the file. Run the file through the validation utility, which checks structure, PAN formats, and internal consistency, and flags errors. Fix every error; do not attempt to file around them.

Step 4 — Submit the return. File the validated return through the authorised channel against your TAN. You receive an acknowledgement/token number — retain it.

Step 5 — Reconcile on TRACES. After processing, log into the TRACES portal to confirm the return is accepted, check for any defaults raised (such as short deduction or late fees), and resolve them.

Step 6 — Generate Form 16. After the Q4 return is processed, download Part A from TRACES and generate Part B, then issue Form 16 to employees within the prescribed timeline.

Treat steps 5 and 6 as integral, not optional. Many employers file the return and stop, only to discover months later that TRACES raised a default they never addressed — by which time interest and fees have compounded.

Penalties and consequences of getting it wrong

The cost of careless Form 24Q handling comes in several distinct forms, and they can stack.

Late filing fee. Filing the quarterly return after the due date attracts a fee that accrues for each day of delay until the return is filed, capped at the amount of TDS involved. Because it is a daily fee, a return that drifts a few weeks late can accumulate a meaningful sum.

Penalty for non-filing or serious inaccuracy. Beyond the daily late fee, the law provides for a separate penalty where a return is not filed for an extended period or contains significant inaccuracies, within a prescribed range. This is discretionary but real.

Interest on late deposit. Distinct from the return itself, if the TDS was deducted but deposited late, interest accrues per month (or part thereof) of delay. If tax that should have been deducted was not deducted at all, a different interest rate applies for that lapse.

Higher deduction for missing/invalid PAN. Where an employee's PAN is not available or is invalid, tax must be deducted at a higher rate. This is both a compliance exposure and a source of employee grievance when their take-home shrinks.

Downstream employee harm. Perhaps the most underrated consequence: errors deny employees the tax credit they are owed, force them to chase corrections during their own filing season, and damage trust in the payroll function.

The reassuring flip side is that all of these are avoidable with timely monthly deposits, accurate PANs, quarterly reconciliation, and on-time filing. None of them require heroics — only routine.

Correcting mistakes: revised returns

Errors happen — a wrong PAN, a misreported amount, a challan that did not map correctly. The system anticipates this through correction (revised) returns. If you discover a mistake after filing, you prepare and submit a correction statement that amends the specific records, referencing the original return's token. Corrections can address deductee details, challan mapping, PAN errors, and amounts.

The practical guidance is twofold. First, file corrections promptly, because uncorrected errors flow into employees' Form 26AS and Form 16. Second, treat the correction facility as a safety net, not a routine: relying on it quarter after quarter signals an upstream data-quality problem worth fixing at the source — usually PAN verification and challan reconciliation.

A practical compliance routine for SMBs

For a small or mid-sized employer, Form 24Q becomes painless when wrapped in a simple, repeatable routine:

1. Verify PANs at onboarding. Make valid PAN capture and verification part of the joining checklist so you never deduct at a higher rate or misallocate credit.
2. Deposit TDS monthly, on time. Calendar the monthly deposit deadline and treat it as non-negotiable; interest for late deposit is pure avoidable cost.
3. Reconcile challans to deductions each month. A short monthly reconciliation prevents a painful quarter-end scramble.
4. File each quarterly return a few days early. Give yourself buffer to fix validation errors before the deadline.
5. Reconcile on TRACES after each filing. Catch and clear defaults while they are small.
6. Prepare Annexure II carefully in Q4. This is the return that drives every Form 16; invest extra review time here.
7. Issue Form 16 on time and be ready to answer employee queries with the underlying data.

Embedding these steps into payroll software — so that TDS is computed, deposited, reconciled, and reported from a single source of truth — removes most of the manual error risk. Modern HRMS and payroll platforms generate the data files in the prescribed format and flag PAN and challan issues before they reach the portal.

Special situations worth knowing

Employees who switch jobs mid-year. When an employee joins from another employer during the year, their previous salary and TDS should be considered for accurate computation if they declare it. This affects the annual figures reported in Annexure II and the eventual Form 16.

The tax regime choice. Employees electing different tax regimes are taxed under different slab structures and exemption rules. Capturing each employee's elected regime accurately is essential because it changes the computed tax reported in Annexure II.

Nil deductions. If, in a given quarter, no tax was deducted from any employee, there are still reporting expectations to consider; a declaration mechanism exists for periods with no deductions. Do not simply assume "nothing to file" without confirming the current requirement.

Employees with no taxable liability. Some employees will have salaries below the threshold or sufficient deductions to owe no tax. They still appear in your payroll, but TDS reporting focuses on those from whom tax was deducted; the annual statement still captures the full picture in Q4.

These nuances are exactly why the Q4 return deserves the most attention: it is where the year's full story, across regimes and mid-year joiners, has to reconcile into a coherent annual statement.

Where Form 24Q sits in the family of TDS returns

It helps to see Form 24Q in context, because employers often deduct tax on payments beyond salary and need to know which return carries what.

Form 24Q reports TDS on salary paid to employees. Form 26Q reports TDS on most non-salary payments made to residents — think professional fees, contractor payments, rent, commission, and interest. Form 27Q reports TDS on payments to non-residents. Form 27EQ reports tax collected at source (TCS) rather than deducted. All follow a broadly similar quarterly rhythm and are filed against the same TAN, but they cover different payment types.

For a typical SMB, Form 24Q (salaries) and Form 26Q (vendor and professional payments) are the two that matter most. The discipline you build for one — reconciling challans, verifying PANs, filing on time — transfers directly to the other. Many payroll and accounting teams run them on the same quarterly calendar to share the reconciliation effort.

A worked example of a clean quarter

Concrete steps make the rhythm tangible. Imagine a small company running its first-quarter (April–June) salary TDS process (illustrative, not a substitute for current rules).

Through April, May, and June, the company computes each employee's monthly TDS based on their projected annual income, declared investments, and chosen tax regime, and deducts it from salary. By the seventh of May, June, and July respectively, it deposits each month's deducted tax via challan, quoting its TAN. It retains the three challan identification numbers.

At quarter-end, the payroll team reconciles: the total TDS deducted from payslips across the three months should equal the total deposited across the three challans. Suppose they match. The team then prepares the Form 24Q return for Q1, entering deductor details, the three challans, and the employee-wise breakup in Annexure I (Annexure II is not needed for Q1). They run the file through the validation utility, which flags one employee whose PAN was entered with a typo. They correct it, re-validate cleanly, and file before the end of July, receiving a token number.

A week later, they log into TRACES, confirm the return processed without defaults, and file the result. No penalties, no employee complaints, no year-end scramble. This is the unremarkable, repeatable outcome that good process produces — and it is entirely achievable for a team of any size.

Responding to a TRACES default notice

Even careful filers sometimes receive a "default" intimation from the TRACES system after a return is processed. Common defaults include a short deduction (you deducted less than required for some deductee), a short payment (the challan amount does not fully cover the reported deductions), a late deduction or late payment (interest applies), or a late filing fee. A default is not an accusation of fraud; it is the system flagging a discrepancy that needs resolving.

The response process is methodical. First, read the intimation to understand exactly which records and amounts are flagged. Second, investigate the root cause — often a challan that was not mapped correctly, a PAN error that caused a higher-rate shortfall, or a genuine timing lapse. Third, if the default arose from a data error rather than an actual shortfall, file a correction return to fix the mapping or details. Fourth, if there is a genuine shortfall or interest due, deposit the additional amount via challan and reflect it. Resolving defaults promptly stops interest and fees from compounding and keeps your employees' tax credits accurate. Ignoring them is how a small discrepancy becomes a large, aged liability.

Lower or nil deduction situations

Not every employee should have tax deducted at the standard computed rate. Some present a certificate authorising deduction at a lower or nil rate, obtained from the tax authorities when their overall tax liability justifies it. When an employee provides such a certificate, the employer deducts at the certified rate and reports it appropriately in the return, referencing the certificate. Honouring a valid lower-deduction certificate prevents over-deduction that the employee would otherwise have to claim back as a refund.

Equally, employees whose income falls below the taxable threshold should not have tax deducted simply by default. Accurate computation — factoring in the chosen regime, eligible deductions, and declared investments — ensures you deduct the right amount, neither short (which creates defaults) nor excess (which annoys employees and ties up their cash until refund). This is another reason robust payroll software earns its keep: it computes each employee's correct liability continuously as declarations and proofs are updated, rather than guessing.

Guidance for first-time deductors

If your organisation is filing Form 24Q for the first time, a few foundational steps prevent early mistakes. Obtain a valid TAN before you deduct any tax; it is mandatory and quoting an incorrect or absent TAN invalidates filings. Set up a simple monthly checklist covering deduction, deposit by the due date, and challan record-keeping. Verify every employee's PAN at onboarding, because PAN errors are the most common and most damaging data fault. Calendar all four quarterly due dates plus the monthly deposit dates at the start of the year. And register on the TRACES portal early, since you will need it to reconcile returns and generate Form 16.

First-time filers often underestimate the importance of the validation-and-reconcile loop. The single habit that most reliably keeps new deductors out of trouble is reconciling deductions to challans every month and filing each quarterly return a few days before the deadline, leaving room to fix validation errors calmly rather than against the clock.

The cost of doing it well versus doing it badly

It is worth contrasting the two trajectories plainly. The employer who deducts accurately, deposits monthly, reconciles challans, files on time, and clears TRACES defaults spends a modest, predictable amount of effort each month and essentially nothing on penalties. Their employees' Form 26AS and Form 16 reconcile cleanly, so tax-season queries are rare and trust in payroll is high.

The employer who improvises — deducting roughly, depositing late, never reconciling, filing returns at the last minute with PAN errors, and ignoring TRACES intimations — pays the daily late-filing fee, interest on late deposits, possible penalties, and the recurring cost of employees chasing missing credits. Worse, the damage is cumulative: uncorrected errors flow into employee records year after year, and the eventual clean-up is far more expensive than the discipline would have been. The lesson is not that Form 24Q is hard; it is that neglect compounds while discipline is cheap.

Record-keeping and documentation

Compliance does not end when the return is filed; it depends on the records you keep. Sound documentation protects you in the event of a query, an inspection, or an employee dispute, and it makes each subsequent filing easier.

Retain, in an organised and retrievable form: the challans for every TDS deposit, with their identification numbers and dates; the filed returns and their acknowledgement/token numbers; the TRACES intimations and your responses to any defaults; the investment declarations and proofs that justified each employee's computed tax; and copies of the Form 16s issued. Keeping these for the period the law expects means that if a discrepancy surfaces months or years later, you can reconstruct exactly what was deducted, deposited, reported, and certified.

A common, avoidable failure is treating each quarter as a fresh start and discarding the trail. The employer who maintains a clean, year-on-year archive — ideally within a payroll system that stores it automatically — spends minutes resolving a query that would otherwise consume days. Good documentation is the cheap insurance that makes the whole TDS obligation defensible.

Frequently asked questions

What is Form 24Q used for? It is the quarterly TDS return through which an employer reports salary paid and tax deducted, employee by employee, and links those deductions to the challans used to deposit the tax. It is the basis for employees' TDS credit and for Form 16.

How is Form 24Q different from Form 26Q? Form 24Q reports TDS on salaries. Form 26Q reports TDS on most non-salary payments to residents (such as contractor or professional fees). Different payments, different forms, but a similar quarterly rhythm.

When is Form 24Q due? Conventionally by the end of the month following each quarter — end of July, October, January, and May — with the Q4 (year-end) return carrying the annual Annexure II. Confirm exact dates each quarter, as extensions occur.

What is the difference between Annexure I and Annexure II? Annexure I is filed every quarter with the deductee-wise deduction and challan detail for that quarter. Annexure II is filed only with the Q4 return and contains each employee's full-year salary, deductions, regime, and tax — the basis for Form 16 Part B.

What happens if I file Form 24Q late? A daily late-filing fee accrues until you file, capped at the TDS amount, and a separate penalty can apply for prolonged non-filing or serious inaccuracy. Late deposit of the tax itself attracts interest independently.

Why does my employee's Form 26AS show less TDS than their payslips? Almost always a reporting gap or PAN error in Form 24Q, or a challan that did not map correctly — rarely a deposit failure. File a correction return to fix the attribution.

Do I need a TAN to file Form 24Q? Yes. The return is filed against your Tax Deduction and Collection Account Number, not your PAN. If you deduct TDS, you must have a valid TAN.

How do I fix a mistake after filing? Submit a correction (revised) return referencing the original token number, amending the specific records. File corrections promptly so errors do not flow into employees' tax records.

Conclusion

Form 24Q is not complicated, but it is unforgiving of neglect. Its quarterly rhythm, its two-annexure structure, and its direct line to every employee's Form 16 mean that small lapses — a missing PAN here, a late deposit there, an unreconciled challan — surface as penalties for you and credit denials for your staff. The good news is that the entire obligation collapses into a short list of habits: verify PANs at onboarding, deposit monthly on time, reconcile challans, file each quarter a few days early, clear TRACES defaults, and prepare Annexure II with extra care so Form 16s flow cleanly.

Employers who internalise that routine spend almost no energy on TDS compliance; those who improvise spend it on penalties and apologies. If you would rather your payroll system handle the heavy lifting — computing TDS, prompting timely deposits, reconciling challans, and generating return-ready files and Form 16s from one source of truth — a modern HRMS and payroll platform like CozyHR is built precisely for that. Whatever tool you use, confirm the current due dates, rates, and thresholds on the official Income Tax and TRACES portals before each filing, because they are revised from year to year.