Form 24Q step-by-step filing guide for Indian employers

What Form 24Q actually is

Form 24Q is the quarterly statement filed by every TDS deductor under Section 192 — that is, every employer paying taxable salary. It tells the Income Tax Department who you paid, how much, and how much tax you deducted and deposited. Without a correctly filed 24Q, Form 26AS won't reflect your employees' TDS, and Form 16 generation stalls.

The four-quarter calendar

• Q1 (Apr–Jun): due 31 July.
• Q2 (Jul–Sep): due 31 October.
• Q3 (Oct–Dec): due 31 January.
• Q4 (Jan–Mar): due 31 May. This quarter additionally requires Annexure II — the full-year salary detail per employee.

Step 1 — Reconcile before you generate

The fastest 24Q filing is one where the data was correct before the file was generated. Reconcile at month-close, every month — don't wait until the quarter ends. Specifically:

• PAN integrity: every employee on the payroll has a valid PAN, matching ITD records. Use the bulk PAN verification utility on TRACES.
• Challan integrity: every challan deposited has its BSR code, date, serial number and amount recorded. One typo here breaks the linkage to deductee TDS.
• Section code: 92B for resident individuals (the common case). 92A for government employees and 92C for non-residents. Get this wrong and the return processes incorrectly.
• Salary structure: the gross, exemption, deduction and net taxable totals should reconcile to your books.

Step 2 — Generate the e-TDS text file

From your payroll software, generate the 24Q text file in the format prescribed by Protean (formerly NSDL). The current schema version is FVU 8.6as of mid-2026. Most HRMS systems handle this automatically, but verify the FVU version your file targets — using an outdated schema means rejection on upload.

Step 3 — Validate via the File Validation Utility (FVU)

Download the latest FVU from the TIN-NSDL/Protean site. Point it at your text file. FVU runs structural and PAN-syntax checks and produces:

• An .fvu file (the validated upload artefact).
• A Form 27A cover sheet (used in physical filing — most e-filing flows don't need this any longer).
• An error file if validation fails. Fix the errors at source — never patch the text file.

Step 4 — Upload to the Income Tax e-filing portal

Log in to incometax.gov.inas the deductor with TAN credentials. Navigate to e-File > Income Tax Forms > File Income Tax Forms > Form 24Q. Upload the .fvu file. Sign with DSC (Digital Signature Certificate) or EVC. Note the acknowledgement number.

Step 5 — Track processing on TRACES

Log in to TRACESas the deductor. The return moves through statuses: Uploaded → Verified → Booked. Once Booked, the TDS reflects in employees' Form 26AS. If it sits in Verified for several days, expect a Default Notice — check the justification report for what went wrong.

The five most common 24Q errors

1. Invalid PAN. Treated as "PAN not available" — TDS attracts a 20% rate, employee's 26AS shows no credit. Fix: bulk PAN verification before each quarter.
2. Challan mismatch. BSR or serial number wrong by a digit. Fix: enter challan details directly from the bank advice, never from memory.
3. Section code mismatch. Using 92A instead of 92B. Fix: HRMS default should be 92B for resident individuals.
4. Missing Annexure II in Q4. Without it, Form 16 cannot be generated. Fix: explicitly check that your Q4 file includes both Annexures.
5. Regime mismatch. The regime opted at the start of the year and used in monthly TDS computation should be the regime declared in Annexure II. Fix: lock the regime in the payroll engine, not in a spreadsheet.

If you do get a Default Notice

Defaults are common; don't panic. The justification report on TRACES tells you exactly which deductees and which challans triggered the default. Most are short-deduction (rate issue, exemption mismatch) or short-payment (interest accrued on delayed deposit). File a correction statement (C2/C3/C4/C5 depending on the field) and the default amount usually disappears.

How Texlaculture handles 24Q

• Monthly reconciliation by employee, by challan, by section code — long before the quarter closes.
• PAN bulk verification surfaces errors before they go on the 24Q.
• FVU-ready text file export, Annexure I (Q1–Q4) and Annexure II (Q4).
• Direct upload to the IT portal with status tracking on TRACES.
• Correction workflow with the conso file imported back from TRACES.

The takeaway

Form 24Q is a process problem, not a one-time filing problem. The teams that struggle each quarter are the ones reconciling at quarter-end. The teams that file smoothly reconcile monthly — PANs, challans, regime choices, structure changes — so by 31 July, 31 October, 31 January and 31 May, the file is generated, validated and uploaded in under an hour.