TDS returns are quarterly statements that a deductor files to report tax deducted at source, the deductee-wise details, and the tax deposited against that deduction. In practice, the return is what moves TDS credit into the reporting system used for processing and downstream documents such as deductee tax credit records. If you need a broader refresher on the withholding framework itself before focusing on the return, CA Samaaj’s guide on what TDS means and how it works is the better starting point.
Change-sensitive portal note verified on August 15, 2026: the Income Tax Department’s current e-filing portal shows the familiar TDS statement forms alongside newer portal labels under the Income-tax Act, 2025. Professionals still commonly refer to the legacy names 24Q, 26Q and 27Q, and those names remain the clearest way to discuss quarterly TDS returns in day-to-day work.
Which TDS return applies
| Common form name | Current portal label | When it is used | Core distinction |
|---|---|---|---|
| Form 24Q | Form 138 | TDS on salary | Employer salary reporting |
| Form 26Q | Form 140 | TDS on most resident non-salary payments | Resident deductee, other than salary |
| Form 27Q | Form 144 | TDS on payments to non-residents | Non-resident payment reporting |
The official tax deductor guidance separately lists Form 24Q for salary, Form 27Q for payments to non-residents, and Form 26Q for other cases. That distinction is more important than the label change on the portal, because most filing errors begin with choosing the wrong return bucket.
What is not a regular quarterly TDS return
Not every TDS compliance event is reported through a standard quarterly statement. Certain PAN-based transaction forms operate as challan-cum-statements instead of the regular quarterly return model. A useful edge case appears in the Income Tax Department’s e-Pay Tax FAQs: if a transaction such as property purchase, rent, specified contractor or professional payment, or specified VDA transfer involves a non-resident deductee, the applicable form is Form 27Q rather than the resident-only PAN-based statement route.
Another common confusion point is Form 27EQ. That is a TCS statement, not a TDS return, so it should not be mixed into a TDS return checklist.
Current quarterly filing cycle
Change-sensitive dates verified from current Income Tax Department user manuals on August 15, 2026: the due dates presently shown for Forms 24Q, 26Q and 27Q are the same quarterly cycle below.
| Quarter | Period | Due date |
|---|---|---|
| Q1 | April to June | 31 July |
| Q2 | July to September | 31 October |
| Q3 | October to December | 31 January |
| Q4 | January to March | 31 May of the following financial year |
These are return filing dates, not TDS deposit dates. In working files, that distinction matters because a quarter may have timely tax payment but still suffer return default if the statement is filed late.
How the filing process works in practice
- Identify the correct return type by deductee category and payment nature.
- Prepare the quarterly statement using the current Return Preparation Utility.
- Generate a valid FVU file and package it in the required zip format.
- Log in to the income-tax e-filing portal using TAN credentials.
- Select the TDS/TCS form filing service, choose the relevant form, quarter and upload type.
- Upload the zip file and complete e-verification.
- Track whether the upload is accepted or rejected after validation and then processed through TRACES.
The current Form 138, Form 140 and Form 144 user manuals all point to the same workflow pattern: use the updated utility set, upload the correct FVU version, and monitor whether the statement is accepted or rejected before TRACES processing. The procedural weakness in many teams is not return preparation itself but version control of the utility and quarter selection at upload stage.
Examples that resolve the usual form-selection confusion
Example 1: resident professional fee
Assumptions: ABC Pvt. Ltd. pays Rs. 2,00,000 to a resident consultant in August and deducts TDS correctly. This is a resident non-salary payment, so the reporting route is Form 26Q on the legacy naming basis, currently shown as Form 140 on the portal. Because the deduction falls in July to September, it belongs to Q2, whose current due date is 31 October.
Example 2: payment to a non-resident vendor
Assumptions: an Indian company pays royalty to a non-resident in December and deducts tax under the applicable provision. Even if the accounting team is used to filing resident vendor payments in 26Q, this case shifts to Form 27Q, currently shown as Form 144, because the deductee is non-resident. Since the deduction falls in October to December, it belongs to Q3, whose current due date is 31 January.
Correction statement basics
A correction statement is the mechanism for fixing an already filed TDS statement. Typical triggers include wrong PAN, wrong challan tagging, wrong amount breakup, wrong deductee rows, or a statement that was uploaded with the wrong utility version or quarter context.
Change-sensitive current rule verified from the official tax deductor page: the note currently states that a correction statement of TDS is to be filed within 6 years from the end of the financial year in which the TDS statement is required to be furnished, with the note marked as applicable from April 1, 2025.
For online correction through TRACES, the official CPC-TDS communication states three key prerequisites: a regular statement must already be filed and processed, all earlier corrections for that statement must have been processed, and a digital signature must be registered on TRACES. The same communication lists PAN correction and challan or BIN correction among the available online correction functions.
For utility-based correction uploads through the e-filing portal, the current form manuals for Forms 138, 140 and 144 also flag a practical validation point: if you upload a correction file, the RRR number in the FVU must match what is entered on the filing screen. A mismatch can cause rejection.
Where correction filings usually fail
- Wrong form selected for the deductee category, especially resident versus non-resident cases.
- Regular statement uploaded where correction upload was intended, or the reverse.
- FVU version mismatch between the utility output and the version expected on the e-filing portal.
- TAN in the FVU file not matching the logged-in TAN.
- Duplicate filing for the same quarter.
- RRR or prior receipt references not matching in correction uploads.
Late filing exposure
Change-sensitive current statutory points verified from the official tax portal: section 234E currently provides a fee of Rs. 200 per day for delay in furnishing the TDS or TCS statement, subject to the amount of TDS or TCS, and section 271H can apply for failure to furnish the statement or for furnishing an incorrect statement. That makes the control objective simple: do not treat return filing as a clerical afterthought once tax has been deducted and deposited.
Working checklist for finance teams and practitioners
- Confirm whether the payment belongs in salary, resident non-salary, or non-resident reporting.
- Check whether the case is a regular quarterly TDS return or a separate challan-cum-statement category.
- Reconcile challan details, deductee rows and quarter mapping before utility generation.
- Use the latest RPU and matching FVU version.
- Keep the accepted regular statement details available before starting any correction.
- For TRACES online correction, ensure the earlier statement is processed and DSC is active.
- After filing, verify acceptance or rejection status and then watch for downstream credit and certificate impacts.
If the return work is being linked to deductee documentation, CA Samaaj’s comparison of Form 16 and Form 16A helps map which certificate typically follows the underlying TDS reporting pattern.
