Why the return matters more than you think
A TDS challan tells the government you paid money. It is the quarterly TDS statement (commonly called the TDS return) that says whose tax it was — mapping every rupee to a deductee's PAN, a section, and a challan. Only after this statement is processed does the amount appear in the deductee's Form 26AS/AIS, and only then can TRACES generate Form 16/16A certificates.
Skip or delay the return and three people suffer: your vendor (no tax credit visible), your employee (can't file their own return cleanly), and you (late fees accruing daily). If you need a refresher on the overall deduct → deposit → file → certificate loop, start with our TDS basics guide.
24Q vs 26Q: which form is yours?
Most businesses file one or both of two statements each quarter:
| Form 24Q | Form 26Q | |
|---|---|---|
| Covers | TDS on salaries (Section 192) | TDS on non-salary payments to residents — contractors (194C), professionals (194J), rent (194I), goods purchases (194Q), etc. |
| Filed by | Employers | Any deductor making covered payments |
| Special feature | Q4 includes the full salary annexure that feeds Form 16 | Each quarter's data feeds quarterly Form 16A certificates |
| Certificate | Form 16 (annual) | Form 16A (quarterly) |
Two siblings complete the family: 27Q for payments to non-residents, and 27EQ for TCS (relevant if you collect tax under provisions like 206C(1H) — see our 194Q vs TCS comparison). A firm with employees, local vendors and TCS obligations could file three statements every quarter.
The quarterly rhythm
The financial year splits into four quarters — Apr–Jun, Jul–Sep, Oct–Dec, Jan–Mar — and each has its own filing due date, typically a month or so after the quarter ends, with the fourth quarter getting extra time because of the salary annexure. Exact due dates are prescribed in the rules and occasionally extended, so confirm the current calendar on incometax.gov.in before relying on memory.
The practical workflow each quarter looks like this:
- Reconcile — match every deduction entry in your books against deposited challans. This is where clean bookkeeping pays off; our TDS journal entries tutorial shows the ledger structure that makes this a five-minute job.
- Validate PANs — one invalid PAN can trigger a higher-rate demand after processing.
- Prepare the statement — using the return-preparation utility (RPU) with the file-validation utility (FVU), or software that produces the validated file directly.
- File — upload on the e-filing portal (or through a TIN facilitation centre) using your TAN and digital signature/EVC.
- Track processing — TRACES processes the statement and issues a justification report if it finds defaults (short deduction, short payment, late fees, interest).
- Issue certificates — download Form 16/16A from TRACES and send them to deductees within the prescribed time.
What late filing actually costs
The consequences of a delayed statement are mechanical and accumulate daily:
- Late filing fee (Section 234E concept) — a fixed fee per day of delay, capped at the amount of TDS in the statement. Even a nil-tax-impact delay costs real money: a statement carrying ₹20,000 of TDS filed 100 days late at ₹200/day would rack up ₹20,000 — the cap itself. The fee must be paid before the statement is accepted.
- Penalty exposure — beyond a longer delay, a separate penalty can apply in addition to the daily fee.
- Interest on late deduction/deposit — separate from filing delays, charged monthly if the tax itself moved late.
- Angry deductees — the unofficial penalty. Until you file, their 26AS shows nothing, and their own return filing stalls.
Rates and caps for these levies are set by statute and can change — treat the numbers above as illustrations of the mechanism and verify current figures.
Made a mistake? File a correction statement
TDS statements are correctable — you file a correction (revised) statement against the original, identified by its token number. Common fixes:
- PAN corrections — the classic. A wrong PAN means the deductee got no credit and you may face a higher-rate demand. Note that PAN corrections have restrictions on how much a PAN can be altered, so get PANs right the first time.
- Challan mismatches — wrong challan serial, date or amount linked to deductee rows; fixable by re-mapping to the correct challan.
- Adding missed deductees — a bill that surfaced after filing can be added with its deduction details.
- Amount/section corrections — a 194J payment wrongly reported under 194C, or a typo in the amount.
Corrections are filed through the same ecosystem (TRACES conso file → RPU/FVU → upload) and there is no fee for correcting per se — but any short payment or interest the correction reveals must be deposited. There is no limit on how many correction statements you can file, though each round takes processing time, so batch your fixes.
A quarter-end checklist you can steal
- All challans for the quarter deposited and CIN numbers recorded.
- TDS payable ledger balance = zero for the quarter (books ↔ challans reconciled).
- PANs verified for every new deductee.
- 24Q and/or 26Q validated through FVU with no errors.
- Filed before the due date; acknowledgement token saved.
- Form 16A downloaded and emailed to deductees after processing.
- Justification report checked; any default resolved with a correction statement.
Let the books do the heavy lifting
Nearly every filing error traces back to messy books: deductions recorded without PANs, challans not linked to entries, sections guessed at quarter-end. If your accounting software captures section, PAN and challan at the moment of entry, the quarterly return becomes an export, not a project. See how iAccounting handles this in the software guides, or go deeper on withholding rules in the TDS & TCS tutorial.