Form 24Q Filing: A Quarterly TDS Guide for Employers

Form 24Q filing is the quarterly statement every Indian employer files to report tax deducted at source on salary payments. If you run payroll for even one salaried employee whose income crosses the taxable threshold, you are in the TDS system, and Form 24Q is how you tell the Income Tax Department what you deducted, from whom, and where you deposited it. Get it right and Form 16 generation becomes a two-click exercise. Get it wrong and you inherit a queue of default notices, blocked Form 16 downloads, and employees who cannot see their TDS in Form 26AS.

This guide is a working playbook for SMB payroll teams in India — the people who actually run the quarter-end grind. It covers what goes into Annexure I and Annexure II, how to prepare and validate the return, how challans map to deductee records, why PAN quality drives higher-rate deduction risk, how correction statements work, how to reconcile TDS against your payroll register, and what to do when the department flags a default.

One standing note before we begin: TDS rates, threshold limits, due dates, fee provisions, and utility versions change. Everything below is written in general terms so it stays useful across years. Always verify the current rates, due dates, and rules on the Income Tax Department and TRACES portals, or with your tax advisor, before you file.

What Form 24Q Actually Is

Form 24Q is the quarterly e-TDS statement for tax deducted at source under the salary head. It is filed by the deductor — the employer — using its TAN (Tax Deduction and Collection Account Number), not its PAN.

Think of the Indian TDS reporting system as a family of quarterly statements, each covering a different kind of payment:

For a payroll team, 24Q is the one that matters most, because it is the only statement that feeds employee-facing documents. Your vendors do not usually chase you for their TDS certificate on the second of every month. Your employees absolutely will chase you for Form 16 in May and June.

Why Form 24Q matters more than most compliance filings

Three reasons:

1. It is employee-visible. The data you file flows to each employee's Form 26AS and Annual Information Statement (AIS). If your filing is wrong, the employee's own income tax return goes wrong, and they will not get credit for tax you actually deducted from their salary.
2. It generates Form 16 Part A. You cannot hand-make Part A. It is downloaded from TRACES and is generated only from what you filed and what the department could match to a valid challan.
3. Defaults compound. A short payment in Q1 that you ignore does not sit quietly. Interest accrues, the demand shows in your TRACES account, and it can block downloads and consolidated file requests you need for later corrections.

Who has to file

If you have deducted tax on salary during a quarter, you file. Two practical clarifications SMB teams ask about constantly:

• If you deducted nothing in a quarter, there is generally no statutory obligation to file a return with zero deductions. Many deductors still file a "nil" declaration on the TRACES portal to keep their compliance record clean and avoid non-filing notices. Check the current mechanism, as the department has changed how nil declarations are captured over time.
• If you deducted something in any quarter of the year, you should file for that quarter even if the amounts are small. Skipping a quarter because "it was only two employees" is how late fees start.

A separate point that trips up first-time filers: TDS deduction obligations do not wait for your first Form 24Q. You must deposit deducted tax by the statutory monthly deadline regardless of when the quarterly return is due. Filing is reporting; depositing is the actual payment obligation. They are two different clocks.

Annexure I vs Annexure II: The Core Structure

Every Form 24Q return has a common header block plus challan details, and then one or two annexures. Understanding the difference between them removes most of the confusion around quarter-end.

Annexure I — the deductee-wise breakup, filed every quarter

Annexure I is the quarterly detail. For each challan you deposited during the quarter, it lists every employee against whom that tax was allocated.

What Annexure I typically carries per deductee record:

• Employee PAN and name
• Employee reference number or serial (your internal identifier)
• Date of payment or credit of salary
• Amount paid or credited during the quarter
• TDS amount deducted
• TDS amount deposited
• Rate at which deduction was made
• Applicable section code for salary TDS
• Reason for non-deduction or lower deduction, where relevant

Annexure I answers: "During this quarter, who did you pay, how much, and how much tax did you take out?"

It is filed in all four quarters — Q1, Q2, Q3, and Q4.

Annexure II — the annual salary detail, filed with the last quarter

Annexure II is the full-year salary and tax computation for each employee who was on payroll during the financial year. It is filed once, typically with the Q4 return.

What Annexure II typically carries per employee:

• Gross salary broken into components (salary as per relevant provisions, perquisites, profits in lieu of salary)
• Allowances exempt under the relevant sections
• Deduction for standard deduction and professional tax, as applicable to the regime chosen
• Income or loss from house property reported by the employee
• Other income declared by the employee to the employer
• Gross total income
• Chapter VI-A deductions claimed and allowed
• Total taxable income
• Tax on total income, rebate, surcharge, and cess
• Relief claimed under the applicable section for arrears
• Net tax payable
• Total TDS deducted for the year by the current employer and by any previous employer
• Whether the employee opted for the new tax regime or the old regime
• Whether the employee is a senior citizen or super senior citizen, where relevant

Annexure II answers: "For the whole year, what was this employee's taxable income, what tax was due, and how did the deductions across four quarters add up?"

Why the distinction matters operationally

The practical consequence: Q4 is not just another quarter. It carries both a normal Annexure I for January–March and the entire year's Annexure II. Teams that treat Q4 like Q1 discover in May that their Form 16 Part B numbers are unusable. Budget two to three times the effort for Q4.

The regime question in Annexure II

Since the introduction of the alternative tax regime, Annexure II includes a flag for which regime the employee's tax was computed under. This must match what you actually applied in payroll all year.

The common failure is this: an employee declares one regime in April, you compute payroll on that basis, they change their mind in January, you re-compute the last three months, but the regime flag in Annexure II reflects only the final position while the earlier deductions reflect the original position. The arithmetic still has to reconcile — total tax deducted must tie to total tax payable under the regime you report. If you switched mid-year, you need the final position to be the reported one and the full-year deduction to have been trued up in the last months of the year. Document the declaration and the date you received it.

Quarterly Due Dates — In General Terms

TDS compliance runs on two separate calendars, and confusing them is one of the most expensive mistakes in payroll.

The deposit calendar

Tax deducted in a month must generally be deposited to the government by a specified date in the following month. There is typically a special, later treatment for tax deducted in the final month of the financial year. Government deductors paying without production of a challan follow a same-day book-entry process instead.

Practical rule for an SMB: deduct in month N, deposit early in month N+1, with a different deadline for the March deduction. Verify the exact dates each year — they have been adjusted before, and extensions are occasionally granted.

The return filing calendar

Quarterly statements are due after the end of each quarter, with the fourth-quarter statement generally allowed a longer window because of the Annexure II annual data.

Rather than memorising dates that may change, build your internal calendar with a buffer:

Two things to internalise:

• Filing early is free. Filing late is not. There is a per-day late filing fee for delayed TDS statements, subject to a cap linked to the TDS amount in the statement. Since the fee is per day, a five-day slip costs real money for no benefit.
• The department's certificate download timelines are downstream of your filing. Form 16 Part A becomes available only after your Q4 statement is processed. Filing on the last permitted day pushes your Form 16 distribution into a crunch.

Also verify whether any extensions have been notified for the period you are filing. Extensions do happen, but they are announced, not assumed.

Preparing the Return: RPU and FVU, Step by Step

The standard workflow uses two free utilities published by the tax infrastructure provider: the Return Preparation Utility (RPU) to build the file, and the File Validation Utility (FVU) to validate it. Most payroll software, including CozyHR, can export a text file in the prescribed format that you feed directly to the FVU, skipping manual RPU data entry — but you should understand the underlying flow so you can debug it.

Step 1: Assemble your source data

Before you touch any utility, gather:

• Your TAN, PAN of the deductor, and the responsible person's details (name, designation, address, PAN, contact)
• The payroll register for each month in the quarter, employee-wise, with gross salary and TDS deducted
• Every TDS challan paid during the quarter, with CIN details
• The employee master with PANs, joining and exit dates
• The previous quarter's acknowledgement number (the provisional receipt number), which you may need as a reference
• For Q4 only: full-year salary computation per employee, investment proofs finalised, previous-employer income where declared

Step 2: Download the current RPU and FVU versions

Utility versions change. An older FVU version will reject your file with an unhelpful error. Always download the current version at filing time rather than reusing last quarter's download. Note that separate FVU versions may exist for older financial years and current ones — pick the right one for the period you are filing.

The utilities are Java-based, so a compatible Java runtime must be installed on the machine.

Step 3: Enter or import the header (Form section)

The header block captures:

• TAN, PAN, financial year, quarter, and form type (24Q)
• Whether it is a regular statement or a correction
• Deductor category (company, firm, individual, government, etc.)
• Deductor name and address
• Responsible person's name, designation, PAN, address, email, and mobile
• Whether the address of the deductor or responsible person has changed since the last return

Common failure: stale responsible-person details. When the finance head changes, this block must change. TRACES notices and OTPs go to the contact details in the statement.

Step 4: Enter the challan details

For each challan deposited during the quarter, record:

• BSR code of the collecting bank branch
• Date of deposit
• Challan serial number
• Total amount as per challan, split into tax, surcharge, cess, interest, fee, and others
• Section code
• Whether it is a book-entry (government) transaction

The tax, surcharge, cess, interest, fee, and "others" split must add up exactly to the total challan amount. If you paid interest along with tax in one challan, it must be captured in the interest field, not lumped into tax — otherwise the department will compute a short payment on the tax portion.

Step 5: Enter Annexure I deductee records

Under each challan, add the employees against whom the challan amount is allocated. For each record:

• Serial number
• Employee PAN (or the prescribed marker if PAN is not available)
• Employee name
• Section code for salary TDS
• Date of payment or credit
• Amount paid or credited
• TDS, surcharge, education cess, and total tax deducted
• Total tax deposited
• Rate at which deducted
• Reason for lower or non-deduction, if applicable

The hard rule: the sum of "tax deposited" across all deductee records under a challan must not exceed the tax available in that challan. If it exceeds, the FVU will reject the file. If it falls short, the balance sits unconsumed in the challan — which is fine, and can be consumed later or in another statement, but you should know it is there.

Step 6: For Q4, enter Annexure II salary details

This is where the annual computation goes. Each employee who received salary during the financial year gets a record — including employees who left mid-year and employees who joined mid-year.

Points that reliably cause trouble:

• Employees with zero tax. Whether to include employees whose taxable income fell below the threshold has been a recurring question; the reporting requirement has expanded over time. Verify the current requirement, and when in doubt, include the full salary population so the annexure reconciles to your payroll register.
• Exited employees. They still need an Annexure II record for the portion of the year they were with you, and they still need a Form 16.
• Previous employer income. If an employee gave you a Form 12B or equivalent declaration of prior salary, that income and the prior TDS must be reported so the annual tax computation makes sense.
• Relief for arrears. If you allowed relief under the applicable section based on the employee's submitted computation, report it in the designated field.

Step 7: Generate and validate with the FVU

Once the data is complete, generate the text file and run it through the FVU. Three outcomes:

1. Validation successful. The FVU produces an .fvu file (the file you submit), a statement statistics report, and a validation report. Keep all three.
2. Validation errors. You get an error file listing record numbers and error codes. Fix in the RPU and re-validate.
3. Warnings. The file validates but the FVU flags something — most commonly PAN mismatches or structural oddities. Read them; warnings are the early-warning system for defaults.

Always run the file through the online PAN verification and challan verification steps before finalising. The RPU can import a challan file downloaded from the tax information network, which pre-fills verified challan details and eliminates typo risk on BSR codes and serial numbers. Use it.

Step 8: Submit

Two routes:

• Online through the e-filing portal, using a Digital Signature Certificate or an Electronic Verification Code. This is the increasingly standard path and gives you immediate acknowledgement.
• Physical submission at a TIN Facilitation Centre, carrying the .fvu file on media along with the signed Form 27A. Fees apply based on the number of records.

Either way, you receive a provisional receipt / token number. Store it. You need it to check statement status, to request consolidated files for corrections, and to reference in the next quarter's return.

Step 9: Track processing

Filing is not the end. The statement goes for processing, after which you can see its status on TRACES:

• Processed without defaults — the goal.
• Processed with defaults — a demand exists. Open the justification report.
• Rejected — something structural failed. Re-file.

Set a calendar reminder to check status roughly a week or two after filing. Do not wait for a notice to arrive.

Challan Mapping: CIN, BIN, and Book Entries

Challan mapping is where most short-payment defaults are born. The concept is simple; the execution is fiddly.

What CIN is

For a non-government deductor paying tax through a bank (including online payment), the Challan Identification Number (CIN) is the composite key that identifies your payment. It has three parts:

1. BSR code — a seven-digit code identifying the bank branch that collected the payment
2. Date of deposit — the tender date, in the prescribed format
3. Challan serial number — a five-digit number assigned to the challan

These three together must exactly match what the bank reported to the tax system. A single wrong digit in the BSR code means the department cannot find your payment, and your entire challan's worth of deductee records shows as unmatched.

What BIN is

Government deductors who pay tax by book adjustment do not get a bank challan. Instead, the Pay and Accounts Officer or equivalent files a Form 24G, and the system generates a Book Identification Number (BIN) with three parts:

1. Receipt number of the Form 24G statement
2. DDO serial number
3. Date of transfer voucher

If you are a government office deductor, your Form 24Q must carry the BIN and the transaction must be flagged as a book entry. If you are a private company, you should almost never be using the book-entry flag — setting it by accident is a classic error that makes your challan unverifiable.

The book-entry flag

In the RPU, each challan row has a field indicating whether tax was paid by book entry. Set it to "yes" only if you are a government deductor paying without a physical challan. For every other deductor, it stays "no" and you supply CIN details.

Practical challan hygiene

Adopt these habits and short-payment defaults mostly disappear:

• Use the challan download feature. Instead of typing CIN details, import the verified challan file. This eliminates transcription errors entirely.
• Verify the assessment year on the challan itself. Tax deducted in a financial year is deposited against the corresponding assessment year. Selecting the wrong assessment year on the payment challan means the challan will not match against your statement, and correcting it requires a challan correction process with the assessing officer or the bank, depending on how much time has passed and which field is wrong.
• Verify the section and the nature of payment. Salary TDS goes against the salary section code. A challan paid under a contractor section cannot be consumed by a 24Q statement.
• Check the minor head. TDS payable by the deductor and TDS on regular assessment are different minor heads. Routine monthly payments go under the "payable by deductor" head. Paying a demand raised by the department goes under the other head. Mixing them causes matching failures.
• Reconcile total challans to your payroll register every month. The monthly total of TDS deducted in payroll must equal the monthly challan amount for tax. Catching a mismatch in month two is trivial; catching it at quarter-end is painful; catching it at Form 16 time is a crisis.
• Keep the interest and fee amounts separate. If you pay tax late and add interest, the challan must show tax and interest in their own fields, and the return must reflect that split.

Worked example: challan allocation

A company with 22 employees deducts as follows in Q2:

In Annexure I, the July challan of ₹1,84,000 gets 22 deductee rows summing exactly to ₹1,84,000. Same for August and September. Total deductee rows across the quarter: 66. Total tax deposited across all rows: ₹5,81,700.

Now the failure mode. Suppose one employee's ₹4,200 TDS for August was deducted in payroll but the finance team paid only ₹1,87,300 because they used a stale payroll report. You now have:

• Payroll register says ₹1,91,500 deducted in August
• Challan says ₹1,87,300 paid
• Gap: ₹4,200

If you file Annexure I claiming ₹1,91,500 deposited under a ₹1,87,300 challan, the FVU rejects it. If you file only ₹1,87,300 in deductee records to make it validate, one employee's TDS goes unreported, they do not see it in 26AS, and you have a short deduction reported for them.

The correct fix: pay the ₹4,200 with applicable interest as a separate challan, then include both challans in the statement with the deductee rows allocated correctly. Two challans in a month is completely normal and raises no flags.

PAN Validation and Higher-Rate Deduction Risk

This section deserves its own place in your quarter-end checklist because the financial consequence lands on your company, not on the employee.

The rule in plain terms

Where a deductee does not furnish a valid PAN, tax must be deducted at a higher rate than would otherwise apply — broadly, the higher of the rate in force, the rate specified in the relevant provision, or a specified floor rate. A separate provision applies a higher deduction rate to specified persons who have not filed their income tax returns for the prescribed period, though the applicability of that provision to salary and its current status should be verified.

There is also a distinct risk from PANs that have become inoperative because they are not linked with Aadhaar. An inoperative PAN can be treated as though PAN were not furnished, triggering the higher rate. The department has issued relief and grace periods on this in the past; verify the current position before acting.

Why this hurts the employer

If you deducted at the normal rate and the department determines a higher rate applied, the difference is a short deduction. As deductor, you are liable for that difference plus interest, and recovering it from an employee who has already been paid — or who has left — is a commercial problem, not a legal remedy.

PAN quality controls that actually work

Build these into your onboarding and quarter-end process:

At onboarding:

1. Collect PAN as a mandatory field before the first payroll run, not "sometime in the first month."
2. Validate the format at entry: five letters, four digits, one letter, with the fourth character indicating the holder type. For an individual, that fourth character should be the one denoting an individual — a PAN with a company-type fourth character on an employee record is either a typo or the wrong document.
3. Verify the name against the PAN database. The e-filing portal and the tax information network offer PAN verification services; bulk verification is available for deductors. A PAN that exists but belongs to a different name is as dangerous as a wrong PAN, because it puts one employee's TDS credit into a stranger's 26AS.
4. Ask for a copy of the PAN card or an e-PAN, and check that the name and date of birth match your employee master.

At quarter-end:

1. Run the FVU and read every PAN-related warning.
2. Cross-check against the TRACES PAN verification and the consolidated file, which shows PANs the department has flagged.
3. Look at any employee where the effective TDS rate looks unusual. A rate materially above what the salary would suggest often means someone applied a no-PAN rate; a rate far below often means a missed deduction.

When PAN is genuinely unavailable:

• Use the prescribed marker in the PAN field for not-available cases.
• Deduct at the higher applicable rate, and tell the employee in writing why their take-home is lower and what will change once they furnish PAN.
• Note that Form 16 Part A generation for a record without valid PAN is constrained — another reason to resolve this fast.

When PAN was wrong and later corrected:

You cannot simply start using the right PAN going forward and leave the past alone. The earlier quarters carry the wrong PAN, so the earlier TDS is credited to the wrong account. File a correction statement (PAN update) for the affected quarters. Note that there are restrictions on how much of a PAN can be changed in a correction — the system prevents wholesale replacement to stop misuse, so a completely different PAN may require a different route. Check the current rules and, where the change is not permitted online, follow the prescribed process with the assessing officer.

Worked example: no-PAN cost

An employee joins in April on a salary where normal monthly TDS would be about ₹6,000. They do not furnish PAN until August. If the higher no-PAN rate applies and produces a monthly deduction of, say, ₹15,000, the employee loses ₹9,000 a month in take-home for four months — ₹36,000 — and cannot claim credit for it easily until the PAN is regularised and the returns are corrected.

If instead you deducted ₹6,000 a month without PAN, the department computes short deduction of ₹9,000 per month against you, plus interest from the date deduction was due to the date of actual deduction. Now it is your problem, and you are chasing an employee for ₹36,000.

The lesson: no PAN, no first payroll run. Make it a hard gate in onboarding.

Correction Statements Explained Plainly

You will file corrections. Everyone does. The skill is in filing the right type quickly rather than avoiding them.

Historically the correction categories were labelled C1 through C9, and while the labels are less visible in modern online correction workflows, the underlying categories are exactly what the system still handles. Understanding them tells you what is fixable and how.

The correction categories in plain English

There were also intermediate categories used in older workflows for combinations of the above. The practical point is that corrections are additive and layered — each correction is filed against the last accepted statement, so you must always start from the current consolidated file.

The golden rule of corrections

Always download a fresh consolidated file ("conso file") from TRACES before preparing a correction. The conso file reflects the statement as the department currently holds it, including any prior corrections. Preparing a correction from your own last saved RPU file — rather than from the conso file — is how deductors accidentally undo an earlier correction.

Step-by-step: filing an offline correction

1. Log in to TRACES with your TAN credentials.
2. Request the conso file for the specific financial year, quarter, and form type. You will need verification details, typically including the token number of the original statement and challan or deductee details from it.
3. Download the conso file once the request is processed. It comes as a password-protected archive; the password format is documented on the portal.
4. Open the conso file in the current RPU. Choose the correction option when importing.
5. Make only the changes you intend. The RPU marks updated records. Do not touch rows you did not mean to change.
6. Validate through the FVU, which will produce a correction .fvu file.
7. Submit through the e-filing portal or a facilitation centre, and note the new token number.
8. Track processing and confirm the default is cleared.

Online correction on TRACES

For many common fixes, TRACES offers an online correction facility that avoids the conso file round trip. Typical online-correctable items include:

• Challan correction / challan tagging — moving unconsumed challan amounts to cover a short payment, or attaching an available challan to a demand
• PAN correction — subject to change-limit rules
• Add challan to statement — attaching a challan you paid but did not report
• Interest and late fee payment against a demand
• Personal information updates

Online correction requires a Digital Signature Certificate for some actions and works without one for others; check the current requirement for the specific correction type. It is dramatically faster than the offline route for challan-level fixes, and it is the first thing to try when you get a short-payment default.

What corrections cannot fix

• A challan paid under the wrong assessment year or wrong major head. That needs a challan correction with the bank (within a limited window) or the assessing officer, not a statement correction.
• Tax you never deducted. A correction reports reality; it does not create a deduction retroactively. If you under-deducted, you deduct and deposit the shortfall (with interest) and then report it.
• A missing statement. If you never filed a quarter, you file a regular statement for it, not a correction — and the late fee applies.

Reconciling TDS With Payroll Registers and Form 26AS/AIS

Reconciliation is the discipline that keeps Form 24Q filing boring. Here is the three-way reconciliation every payroll team should run.

The three sources

1. Payroll register — what your payroll system says you deducted, per employee, per month
2. Bank / challan records — what you actually deposited, per month
3. TRACES / 26AS / AIS — what the department has recorded and credited to employees

Monthly reconciliation (do this every month, not at quarter-end)

Check 1: Payroll TDS = Challan amount

Sum the TDS column in the payroll register for the month. It must equal the tax portion of the challan(s) paid for that month. Any difference is either a payment error or a payroll rerun that happened after the payment.

Check 2: No employee has a blank or invalid PAN

Run a simple filter. Zero tolerance.

Check 3: Effective rate sanity check

For each employee, compute TDS ÷ gross salary for the month. Flag outliers — anyone at 0% who should be paying, anyone materially above the top slab rate, anyone whose rate jumped or dropped by more than a few points versus last month without an explanation (a bonus, a fresh investment declaration, a regime change).

Quarterly reconciliation (before you file)

Check 4: Statement totals tie to payroll

A must equal B. C must equal D must equal E. Any break gets explained in writing before filing, not after.

Check 5: Headcount tie-out

Number of unique employees in the payroll register for the quarter must equal the number of unique PANs in Annexure I, adjusted for employees whose TDS was zero (who may not appear in Annexure I depending on how you report). Document the reconciling items.

Check 6: New joiners and leavers

Every joiner in the quarter should appear from their first paid month. Every leaver should appear up to their final settlement month, including tax on final settlement components.

Post-filing reconciliation (after processing)

Check 7: Statement status

Log in to TRACES a week or two after filing. Confirm the statement is processed, and if it is processed with defaults, open the justification report immediately.

Check 8: Form 26AS / AIS spot check

Ask two or three employees to check that their 26AS reflects the quarter's TDS. Better still, do this internally by reviewing the TRACES deductor-side reports. This catches the class of error where the statement processed cleanly but the credit landed on the wrong PAN.

Annual reconciliation (Q4 and Form 16 season)

Check 9: Annexure II ties to the year

For each employee: gross salary in Annexure II = sum of monthly gross in the payroll register for the year. Total TDS in Annexure II = sum of the employee's TDS across all four quarters' Annexure I records.

Check 10: Tax payable vs tax deducted

For each employee, tax payable per the annual computation should equal tax deducted for the year (or differ only by an amount you can explain — typically because the employee joined mid-year and had prior-employer TDS, or because a February-March true-up was under- or over-shot).

Check 11: Form 16 Part A vs Part B

The total TDS on Part A (generated by TRACES from your filings) must equal the total TDS on Part B (generated from your Annexure II data). If they differ, one of them is wrong and you have a correction to file.

What employees see in AIS

The Annual Information Statement aggregates the salary and TDS reported by you along with other financial information. When an employee says "my AIS shows the wrong salary," the source is almost always your Annexure II. Take those queries seriously — they are free audits of your filing quality, delivered by people with a strong incentive to be accurate.

Common Defaults and How to Clear Them

TRACES will tell you what is wrong through the justification report, a downloadable file that lists every default line by line. Learn to read it; it is the single most useful document in TDS compliance.

Short deduction

What it means: you deducted less than the department computed as due — usually because of a no-PAN or inoperative-PAN case, a wrong rate, or an incorrect exemption applied.

How to clear it: 1. Read the justification report to identify the specific deductee rows. 2. Determine whether the department is right. Sometimes the flag is caused by your own data error (a wrong PAN or a wrong section code), not by an actual under-deduction. 3. If it is a data error, file a correction. 4. If it is a genuine under-deduction, deposit the shortfall with applicable interest, then file a correction to report it and tag the new challan.

Short payment

What it means: the tax you claimed as deposited in your deductee rows exceeds what the department can match to a verified challan. Most often it is a challan mismatch — a wrong BSR code, serial number, or date — not actual non-payment.

How to clear it: 1. Check whether the challan actually exists. Look at your bank record and the challan status enquiry. 2. If the challan exists but the details in the statement are wrong, use TRACES online correction → challan correction to fix the tagging. This often clears the demand within days. 3. If you have an unconsumed challan elsewhere, use challan tagging to move the available amount to cover the default. 4. If the payment genuinely was not made, pay it with interest and add the challan through correction.

This is the most common default and usually the cheapest to fix, because in most cases the money was paid and the mapping was wrong.

Late payment interest

What it means: you deducted on time but deposited late. Interest runs at a specified monthly rate from the date of deduction to the date of deposit, generally computed on a part-month-counts-as-full-month basis.

How to clear it: pay the interest via a challan under the appropriate minor head and tag it to the demand, or use the TRACES facility to pay against the demand directly.

Late deduction interest

What it means: you deducted later than you should have — for example, deduction was due at credit of salary but you deducted at payment in a later month. A different (typically lower) monthly rate applies from the date deduction was due to the date it was made.

How to clear it: same mechanism — pay and tag.

Late filing fee

What it means: the statement was filed after the due date. A per-day fee applies, capped at the total TDS amount of the statement.

How to clear it: the fee must be paid; it is not waivable by simply filing. Pay through a challan with the amount placed in the fee field (not the tax field — a very common error that creates a fresh short payment) and tag it.

Note there is also a separate, more serious penalty provision for statements not filed within an extended period, and prosecution provisions for failure to deposit deducted tax. Those are rare for a compliant SMB but worth knowing they exist.

PAN error / invalid PAN

What it means: the PAN reported does not exist, is structurally invalid, or does not match the name.

How to clear it: correction statement with a PAN update, subject to change limits. If the PAN is entirely different from what you reported, follow the prescribed route.

The default-clearing playbook

Regardless of default type, the sequence is the same:

1. Download the justification report from TRACES for the specific statement.
2. Categorise every line — data error vs genuine shortfall.
3. Fix data errors by correction first. A surprising share of demands evaporates at this step.
4. Compute the true residual liability on what remains.
5. Pay it with the amounts in the correct fields (tax / interest / fee).
6. Tag the challan to the demand via online correction.
7. Re-check the demand status after processing.
8. Log the root cause in your process notes so it does not recur.

How Form 24Q Feeds Form 16 Part A

This is the payoff. Everything above exists so that Form 16 works.

The two parts

Part A contains the employer and employee identification, the assessment year, the period of employment, a quarter-wise summary of salary paid and tax deducted, and the challan/BIN details corresponding to each deposit. It carries a unique certificate number and is generated and downloaded only from TRACES. You cannot type it up yourself.

Part B is the annexure with the detailed salary breakup, exemptions, deductions, and tax computation. It can be generated from TRACES using Annexure II data or prepared by the employer, depending on the current prescribed process. Verify the current requirement, as the department has tightened this over time.

The chain of dependency

1. You deduct TDS in payroll and deposit it against a valid challan.
2. You file Form 24Q for each quarter, with Annexure I mapping the deductee rows to the challan.
3. You file Q4 with Annexure II carrying the annual computation.
4. The department processes the statements.
5. Once all four quarters for the year are processed, you request Form 16 on TRACES.
6. TRACES generates Part A from the processed statement data, with certificate numbers.
7. You download the zip, and use the TRACES PDF Converter utility to convert the text file into individual PDFs, optionally digitally signed.
8. You distribute to employees.

Every link in this chain must hold. If Q2 was never filed, Part A shows no Q2 data. If a challan is unmatched, that quarter's tax may not appear. If an employee's PAN was wrong in Q1 and right in Q2–Q4, their Part A shows only three quarters of tax.

Practical Form 16 season checklist

• File Q4 well ahead of the deadline. Part A cannot be generated before Q4 is processed.
• Clear all defaults for the year before requesting Form 16. Open demands can block generation.
• Verify all four quarters show as "processed" for the financial year.
• Request Form 16 in bulk for all PANs rather than one by one.
• Run the downloaded file through the PDF Converter utility with your digital signature if you sign digitally.
• Reconcile total TDS on Part A against total TDS on Part B for every employee before distributing. A mismatch will come back to you as an employee query in July.
• Distribute with a short explainer note. Most employee queries are about understanding the document, not about errors in it.

The exited-employee case

Employees who left mid-year still get a Form 16 for the period they worked. Their Part A will show only the quarters in which they were paid. Make sure your Annexure II includes them and that you have a current email or address to send the certificate to. Building this into your exit checklist saves a lot of chasing in June.

An Annual TDS Operating Calendar

Here is a rhythm that works for an SMB payroll team. Adjust to your payroll cycle and always confirm statutory dates for the current year.

Every month

• Payroll lock date: finalise payroll, freeze the TDS computation, produce the payroll register.
• Within a few days of payroll: review the TDS register — new joiners have PAN, leavers have final settlement tax, no unexplained rate outliers.
• Before the statutory deposit date: pay the TDS challan. Verify assessment year, section, and minor head before submitting. Save the challan receipt.
• Immediately after payment: reconcile payroll TDS total against the challan amount. File the CIN in a shared challan register.

Every quarter

• Week 1 after quarter-end: pull the quarter's payroll registers and challans. Run the reconciliation checks.
• Week 1–2: prepare the return in the RPU or export from payroll software. Import the verified challan file. Validate with the current FVU.
• Before the due date: submit. Record the token number.
• One to two weeks after filing: check statement status on TRACES. Download the justification report if there are defaults, and start clearing them the same week.
• Also each quarter: download and review any TRACES communications and the deductor dashboard for aggregated defaults across periods.

Specific to the annual cycle

• Start of the financial year: collect regime declarations and provisional investment declarations from all employees. Set up the tax projection in payroll. Verify PANs for all new joiners.
• Mid-year: run a mid-year tax projection review. Employees who joined mid-year should have submitted prior-employer income. Chase anyone who has not.
• Around the third quarter: issue the investment proof submission window. Communicate the deadline clearly and early. This is the single highest-leverage communication of the year — proofs that arrive late force painful February and March deductions.
• After proof verification: re-run the annual tax computation with actual proofs and true up the remaining months' TDS. Aim to complete the true-up across the last two months rather than dumping it all into March.
• March payroll: final true-up. Confirm each employee's year-to-date TDS equals the annual liability. Deposit March TDS by the applicable (typically later) deadline.
• Q4 filing window: prepare Annexure I for Jan–Mar plus the full Annexure II. Reconcile every employee's annual figures before validating.
• After Q4 is processed: clear any remaining defaults for the year, then request and distribute Form 16.
• Post-Form 16: handle employee queries, file any corrections needed, and archive the year's challans, token numbers, conso files, and justification reports.

A one-page control sheet worth maintaining

Keep a single sheet per financial year with these columns, one row per quarter:

• Quarter
• Total salary paid
• Total TDS deducted (payroll)
• Total TDS deposited (challans)
• Number of challans
• Number of deductee records
• Date filed
• Token number
• Processing status
• Defaults (yes/no, amount)
• Correction token numbers, if any
• Date defaults cleared

This sheet is what you hand to your auditor, and it is what saves you when someone asks in November what happened in Q1.

Ten Mistakes That Cost SMB Payroll Teams the Most

1. Paying TDS from a payroll report that was later revised. Always pay from the locked, final register.
2. Onboarding without PAN. Make it a hard gate.
3. Putting late fee or interest in the tax field of a challan. Creates a fresh short payment on top of the original problem.
4. Wrong assessment year on the challan. Hard to fix, easy to prevent.
5. Filing Q4 at the last moment. Delays Form 16 for the whole company.
6. Preparing corrections from a local file instead of the TRACES conso file. Silently reverses earlier corrections.
7. Ignoring FVU warnings. They are the cheapest defect detection available.
8. Not checking statement status after filing. Defaults compound interest while you assume everything is fine.
9. Forgetting exited employees in Annexure II. They still need a Form 16 and their data still has to reconcile.
10. Not documenting regime declarations. When an employee disputes their tax computation a year later, the dated declaration is your only defence.

Frequently Asked Questions

Do I need to file Form 24Q if I did not deduct any TDS in a quarter?

Generally, if there was no deduction, there is no obligation to file a statement for that quarter. Many deductors nonetheless submit a nil declaration on the portal so their record shows an affirmative filing rather than a gap that may trigger a non-filing communication. The mechanism for nil declarations has changed over time, so check the current process on TRACES. If you deducted anything at all in the quarter, file.

What is the difference between Annexure I and Annexure II in Form 24Q?

Annexure I is the quarterly, transaction-level detail: which employees you paid during the quarter, how much, how much tax you deducted, and which challan that tax sits under. It is filed in all four quarters. Annexure II is the annual salary computation for each employee — gross salary, exemptions, deductions, taxable income, tax payable, and total TDS for the whole year. It is filed once, with the fourth-quarter statement, and it is what feeds Form 16 Part B.

Can I file Form 24Q without RPU?

Yes. The RPU is a free option, not a mandate. Most payroll platforms, including CozyHR, generate the Form 24Q text file directly from payroll data. You still validate that file through the FVU before submission, since the FVU output is what you actually file. The advantage of generating from payroll is that the deductee data comes from the same source as your salary register, which removes an entire class of transcription error.

What happens if I file Form 24Q late?

A per-day late filing fee applies from the due date until the date of filing, capped at the total TDS amount reported in that statement. The fee is not discretionary and must be paid with the amount recorded in the fee field of a challan and tagged to the demand. Separately, a penalty provision exists for statements not filed within an extended period, and interest applies independently if the tax itself was deposited late. Filing early costs nothing, so build a buffer.

Why does my employee's Form 26AS not show the TDS I deducted?

Work through the chain: was the tax actually deposited; does the challan detail in your statement exactly match the bank's record (BSR code, date, serial); was the employee's PAN correct in the statement; and has the statement been processed? The most common causes are a challan mismatch (money paid, mapping wrong) and a PAN error (money credited to a different account). Both are fixed with a correction — the challan case often through TRACES online correction within days.

How do I fix a wrong PAN in a filed Form 24Q?

Download the consolidated file from TRACES for that quarter, open it in the current RPU as a correction, update the PAN, validate through the FVU, and submit the correction. For many cases you can instead use the TRACES online PAN correction facility, which is faster. Note that the system limits how many characters of a PAN can be changed in a correction, to prevent misuse. If the correct PAN is entirely different from what was reported, you may need to follow a different prescribed route — check the current rules on TRACES.

What is the difference between CIN and BIN?

CIN — Challan Identification Number — applies to deductors who pay tax through a bank, whether online or over the counter. It consists of the BSR code of the bank branch, the date of deposit, and the challan serial number. BIN — Book Identification Number — applies to government deductors who pay by book adjustment without a physical challan; it consists of the Form 24G receipt number, the DDO serial number, and the transfer voucher date. A private company should use CIN and should leave the book-entry flag set to "no."

When can I download Form 16 after filing Form 24Q?

After the fourth-quarter statement has been filed and processed, and generally once all four quarters for the financial year are processed and outstanding defaults are cleared. You request Form 16 on TRACES, download the file, and convert it to individual PDFs using the TRACES PDF Converter utility, optionally applying a digital signature. Because generation depends on processing, filing Q4 early is the single biggest lever on how quickly your employees get their certificates.

What is a justification report and why does it matter?

It is a downloadable file from TRACES that itemises every default the department has computed against a specific statement — short deduction, short payment, late payment interest, late deduction interest, and late filing fee — with the deductee or challan rows that caused each one. It is the only document that tells you precisely what to fix. Do not pay a demand without reading it first; a large share of demands turn out to be data errors that a correction clears at zero cost.

Bringing It Together

Form 24Q filing is not intellectually difficult. It is an exercise in data discipline performed under a deadline four times a year, and it punishes exactly one thing: letting the payroll register, the challan record, and the filed statement drift apart from each other.

The teams that never get default notices do a small number of unglamorous things consistently:

• They collect and verify PAN before the first payroll run, every time.
• They pay TDS from the locked payroll register, and reconcile the challan to the register the same day.
• They keep a challan register with CIN details, so no one is retyping BSR codes at quarter-end.
• They import verified challan files instead of typing them.
• They read FVU warnings instead of dismissing them.
• They check statement status a week after filing instead of waiting for a notice.
• They start Q4 early because Annexure II is a different animal.
• They clear defaults with a correction before reaching for the chequebook.

Everything else — the RPU, the FVU, the correction categories, the TRACES workflows — is mechanics you learn once and repeat.

If your payroll system already holds the salary data, the PANs, the monthly TDS computation, and the challan record, the quarterly statement should be an export, not a project. That is the design principle behind CozyHR's payroll and statutory compliance module: employee master with PAN validation built into onboarding, an automatic TDS engine that handles both regimes and the investment-proof true-up, a challan register linked to each payroll run, and Form 24Q data generated straight from the same register that produced the payslips — so your Annexure I reconciles to your payroll by construction rather than by heroic effort at quarter-end.

If quarter-end currently means three days of spreadsheets and a nervous wait for the justification report, it is worth seeing what the alternative looks like. Book a walkthrough of CozyHR's payroll and compliance module and bring your last quarter's numbers — the fastest way to judge a payroll system is to watch it reproduce a quarter you already know the answer to.

---

This article is general guidance for Indian employers and payroll teams and is not tax or legal advice. TDS rates, thresholds, due dates, fee and penalty provisions, utility versions, and TRACES procedures change from time to time. Always verify the current rules on the Income Tax Department and TRACES portals, or consult a qualified tax professional, before filing.