Home › Income Tax › TDS Return Filing
TDS STATEMENTS · TAX YEAR MAPPING · TRACES SUPPORT
File quarterly Tax Deducted at Source (TDS) statements with greater confidence. Online Tax Filings helps employers and businesses organise deductee records, reconcile TAN-wise challans, choose the correct old or new Act reporting form, prepare validated statements and resolve correction requirements.
✓ Quarterly TDS statements
✓ Challan & PAN matching
✓ TRACES corrections
ACCURATE DATA · RIGHT STATEMENT · VALIDATED UPLOAD
Review tax year, salary and non-salary payment categories.
Match TAN, challans, PAN and deductee-wise deductions.
Prepare the correct utility file and confirm portal status.
✓ Correct tax-year form
✓ Deductee-wise validation
✓ Statement correction support
EMPLOYERS · DEDUCTORS · BUSINESSES
Tell us your tax year, quarter and type of deduction—salary, resident non-salary or non-resident payment. We can identify the statement and supporting records relevant to your filing.
For privacy, do not submit OTPs, e-filing credentials, complete PAN lists or challan files in the public enquiry form. We can arrange a secure document-sharing method.
Share your deductor category, statement quarter and whether you need a regular return or a correction. Sensitive records can be reviewed separately through a secure channel.
AN IN-DEPTH GUIDE TO TDS RETURN FILING IN INDIA
This guide focuses on deductor-side quarterly TDS reporting: who files, form selection across the April 2026 change, TAN and deductee information, challan matching, validation utilities, TRACES certificates and correction statements. Income tax notices, personal ITR filing and specialised NRI remittance advice remain separate approved services.
Tax Deducted at Source (TDS) returns are deductor-side statements that report tax withheld on specified payments and the persons to whom those payments relate. A quarterly statement is distinct from depositing TDS or filing the deductee’s personal income tax return. The filed record supports the tax credit available to deductees.
A statement normally combines deductor identifiers, payment or deduction codes, deductee PAN or prescribed particulars, tax values and linked challans. A reliable return connects these components back to payroll, vendor accounts or other payment registers.
Person responsible for tax withholding.
Recipient whose tax was deducted.
Quarterly reporting of deductions.
Information that feeds taxpayer records.
Practical note: A successful tax payment does not by itself mean a matching TDS return has been filed.
For relevant non-salary payments, the earlier of the credit or payment event determines the applicable withholding law. Where that event occurred on or before 31 March 2026, the Income-tax Act, 1961 governs the deduction. From 1 April 2026, the Income-tax Act, 2025 applies to the relevant event, including its reorganised provisions and forms.
Salary deductions have a payment-based trigger. Older financial-year statements and their corrections continue under the old Act and original return formats even when amended after April 2026. Tax Year 2026–27 filings use the prescribed new forms and utilities, so the selected year matters more than the upload date.
Apply the relevant 1961 Act rules.
Check the 2025 Act and 2026 Rules.
Retain the original form framework.
Use the newly notified form and codes.
Practical note: Do not translate an old TDS section code automatically into a new-Act return without checking the official reporting table.
The form numbers changed for Tax Year 2026–27. Salary TDS that used Form 24Q is now reported in Form 138; resident non-salary TDS previously reported on Form 26Q uses Form 140; non-resident non-salary reporting formerly under Form 27Q uses Form 144. These are not interchangeable categories.
Tax Collected at Source (TCS) is legally distinct from TDS: the earlier Form 27EQ category corresponds to Form 143 under the new law. Separate challan-cum-statement transactions previously using Forms 26QB/26QC/26QD/26QE generally fall under new Form 141. Confirm the payment category before selecting any of these forms.
Old 24Q → new Form 138.
Old 26Q → new Form 140.
Old 27Q → new Form 144.
Old 27EQ → new Form 143.
Practical note: Form 141 challan-cum-statement cases are not ordinary quarterly Form 140 filings.
Employers reporting salary withholding must align payroll totals with employee-wise taxable salary, withholding and applicable deductions. For legacy periods, Form 24Q remains the recognised quarterly statement. From Tax Year 2026–27, Form 138 is the applicable new-law salary statement, with additional specified reporting uses identified in the official form manual.
Salary reporting needs a consistent employee identifier, payroll adjustments, relevant declarations and withholding reconciliation. Year-end records and employee certificates should agree with the processed salary statement rather than being prepared from an unrelated spreadsheet.
Reconcile pay and taxable components.
Validate identifying records.
Match actual payroll withholdings.
Align reporting with issued records.
Practical note: A payroll report and a quarterly salary TDS statement serve different purposes and should be independently checked.
The resident non-salary return covers eligible withholding on transactions such as professional fees, contractor payments, commission, brokerage and rent where the law requires deduction. Legacy filings use Form 26Q and relevant old provisions; from Tax Year 2026–27 the corresponding quarterly return is Form 140.
Review ledger entries, invoice character, recipient residency, deduction trigger and the relevant item of section 393 under the 2025 Act. Applying a rate or classification based solely on the vendor’s invoice description can create incorrect deduction codes and later credit mismatches.
Review actual payment character.
Check credit or payment event.
Identify relevant return category.
26Q historically; 140 from TY 2026–27.
Practical note: Resident contractor and professional payments can have different withholding classifications even when recorded in one expense ledger.
Quarterly reporting for covered non-resident non-salary payments used Form 27Q under the earlier framework. For transactions governed by the Income-tax Act, 2025, Form 144 is prescribed. The statement should reflect the payment nature, deductee details, applicable withholding information and the documentary basis for any relevant special treatment.
Residency, treaty claims, certificates and foreign-remittance reporting may require separate evaluation. This page addresses accurate TDS return reporting; a distinct approved NRI service page will explain transaction-specific cross-border deduction and remittance assistance.
Identify the income character.
Check non-resident deductee particulars.
Record applicable evidence.
Old 27Q or current Form 144.
Practical note: Do not use a resident-payment statement for a non-resident transaction merely because the payee holds an Indian PAN.
Tax Collected at Source (TCS) is a separate mechanism applying to specified collections rather than deductions from payments. Legacy TCS reporting used Form 27EQ; under the Income-tax Act, 2025 the quarterly statement is Form 143 and the consolidated new-law charging framework is section 394.
A business that has both TDS and TCS obligations should maintain separate transaction mappings, challan checks and form selection. This explanation helps prevent return misclassification but does not add TCS Return Filing as a separate website service topic.
Different from payment deduction.
Verify if TCS applies to transaction.
Form 27EQ for older periods.
Form 143 under the 2025 Act.
Practical note: TCS transactions should not be inserted as deductee rows into a TDS statement.
A valid Tax Deduction and Collection Account Number (TAN) and the correct tax-year portal registration are basic filing controls for most regular TDS statements. The deductor profile, responsible person, contact information and permitted e-verification method must match the authorised filing arrangement.
Deductee PAN accuracy is essential because invalid or mismatched identifiers may delay correct tax-credit attribution. Review name and PAN records against available official validation tools without sharing full identifiers through unsecured intake channels.
Check registered deductor account.
Confirm filing permissions.
Validate deductee identifiers.
Check contact and signing details.
Practical note: If a TAN or deductee PAN was entered incorrectly, correct the record through the recognised process rather than masking the difference.
Each applicable deduction should be reconciled with the corresponding tax payment record. Review challan details, payment date, tax head, available balance and the allocation of tax across deductee rows. Under the 2026 integrated payment system, select the correct Act for the applicable period.
An unmatched or overbooked challan may produce a statement default or incorrect tax-credit information even if the deductor believes the payment was completed. Cross-check banking confirmations and the portal challan view before validating the return file.
Retain official payment evidence.
Match statement references.
Prevent overbooking.
Old or new law for the correct year.
Practical note: A valid challan can still be incorrectly consumed if it is associated with the wrong statement or amount.
Reliable quarterly statements rely on individual transaction rows rather than only aggregate tax totals. Organise payment amounts, deductions, applicable withholding codes, relevant dates, PAN information and any permitted declaration or lower-deduction reference applicable to the chosen tax year.
Compare the return dataset with payroll or accounts ledgers. Payment reversals, duplicate vendor records, year-end adjustments and separate deduction types need careful mapping so that credits are not duplicated or omitted.
One transaction to correct deductee.
Use the notified tax-year category.
Match payment and withholding records.
Support special reporting positions.
Practical note: Do not reuse old-year section numbers automatically in Tax Year 2026–27 forms.
The official workflow uses the updated Return Preparation Utility to prepare structured statement data and validate it into a File Validation Utility (FVU) output. The applicable utility release, statement form, quarter, TAN and tax year must match the portal requirements when uploading.
File-level errors are different from tax-law errors. Resolve missing mandatory fields, invalid formats and mismatched file versions first; then review whether the underlying deductions are substantively correct. An FVU pass is a technical check, not an independent legal confirmation.
Use the current Protean release.
Generate for the selected statement.
Align utility and portal expectations.
Record and resolve validation issues.
Practical note: A statement can be technically valid yet contain wrong deductee or withholding information.
After preparing the validated file, a registered deductor uses the Income Tax e-Filing portal to choose the applicable Act, statement form, tax year, quarter and upload type. The file is uploaded and verified through the permitted method. Keep the portal acknowledgement and record the submitted filing reference.
Upload completion and final processing are distinct stages. Revisit the filed-form status to check acceptance or rejection. If rejected, inspect the specific reason—such as TAN mismatch, incorrect form selection or incompatible file version—before preparing the corrected upload.
Choose matching portal category.
Match the statement period.
Use authorised confirmation.
Check accepted or rejected result.
Practical note: Do not describe a statement as accepted solely because the portal displayed an upload confirmation.
TRACES supports post-filing deductor services including statement status, challan consumption, TDS credit and available certificate downloads. For periods governed by the old Act, salary TDS certificates are commonly known as Form 16 and non-salary certificates as Form 16A. Confirm year-specific certificate naming and generation requirements on the applicable portal.
A certificate should be supported by processed statement data and reconciled challan amounts. Where a PAN, challan or salary entry is wrong, a correction statement may be necessary before downloading or sharing the correct certificate with a deductee.
Review processing outcomes.
Check PAN-wise reported amount.
Use portal-generated records.
Retain downloads and reconciliation.
Practical note: Editing a downloaded certificate PDF is not a substitute for correcting incorrect source statement data.
Corrections may be required for deductee PAN, challan allocation, transaction values or other original statement particulars. TRACES provides a consolidated file of processed regular and correction statements for the selected TAN, year, quarter and form, helping prepare an accurate amendment.
A legacy FY 2025–26 correction continues using the earlier Act’s statement format, even if the correction is furnished in 2026. Tax Year 2026–27 corrections follow the newer form and matching statement reference requirements. The accepted correction should be followed by renewed checks of downstream tax-credit records.
Get current processed statement data.
Identify field or challan error.
Keep old/new Act year mapping.
Verify post-correction outcome.
Practical note: Always use an up-to-date consolidated file that reflects the latest processed correction, where applicable.
Before preparing the statement, assemble the TAN and authorised filer details, deductee master data, payroll/vendor payment registers, tax deduction workings, relevant challans, permitted supporting certificates and earlier statement acknowledgements for the same quarter.
Maintain a reconciled workbook or ledger extract showing exceptions reviewed, changes authorised and upload status. Store statement reference numbers and TRACES processing reports securely. The right internal control is a verifiable link between each deduction, payment deposit, filed row and deductee tax credit.
Confirm TAN and deductee details.
Reconcile salary and vendor ledgers.
Retain FVU and acceptance evidence.
Document reconciliations and corrections.
Practical note: Do not email OTPs, passwords or complete employee PAN lists through unapproved channels.
TDS payment remits withheld tax to the government, while the quarterly statement assigns that deduction to specified deductees and transactions. Both records must reconcile.
For periods governed by the Income-tax Act, 1961, including legacy corrections, Form 24Q remains relevant. Salary TDS for Tax Year 2026–27 is reported under new Form 138.
Form 140 is the quarterly statement for covered non-salary TDS paid to residents from Tax Year 2026–27. Older periods continue to use Form 26Q.
Form 27Q applies to covered old-law periods and Form 144 is the corresponding new-law quarterly form. Residency and payment type must be checked before selecting it.
No. Form 27EQ was a TCS statement, not a TDS statement. Under the 2025 Act the corresponding quarterly TCS statement is Form 143.
Not generally. Old Forms 26QB, 26QC, 26QD and 26QE represent specified challan-cum-statement categories; the new framework uses Form 141 for the applicable transactions.
A valid TAN is generally a prerequisite for regular deductor statements. Some transaction-specific challan-cum-statement mechanisms have different identifiers and should be checked separately.
Common causes include PAN or deductee detail errors, unmatched or overbooked challans, incorrect transaction reporting and an unprocessed statement. Check TRACES status and source data.
Yes, eligible statement errors can be corrected through the appropriate TRACES or return preparation workflow. The period determines whether old or new Act formats apply.
It is the processed combined statement data for a TAN, year, quarter and form type, including relevant corrections. A current file supports preparation of subsequent corrections.
No. FVU is a technical file validation step. The uploaded statement must still pass portal validation and processing, and its final status should be checked.
Yes. New-law quarterly forms include Form 138 (salary), Form 140 (resident non-salary), Form 144 (non-resident non-salary) and Form 143 (TCS), while old-year returns and corrections retain applicable old formats.
Use official form manuals for the correct tax year. Income Tax Department guidance explains the Income-tax Act, 2025 transition, current statement formats and portal upload requirements; TRACES provides statement status and correction support.
This guide distinguishes legacy statement forms for periods through 31 March 2026 from Tax Year 2026–27 reporting under the Income-tax Act, 2025. Verify the latest forms, tax codes and acceptance conditions on the official portal before any live filing.
Online Tax Filings can assist with a TDS filing review based on your deductor category, transaction types, reported quarter and available payment and deduction records. Our work can focus on the statement selection, source reconciliation and portal-filing requirements.
Discuss regular statements, corrections, mismatched challans, validation errors or the handover of TRACES reports and deductee certificates. NRI remittance advisory and individual ITR return preparation have their own approved pages.
Never share Income Tax login passwords, OTPs, complete PAN/Aadhaar numbers or employee-level confidential records through this general enquiry form.
TDS STATEMENTS · CHALLAN MATCHING · TRACES REVIEW
Discuss your quarter, Act, statement form, TAN, challans and whether a regular or correction filing is required.
Income tax consultancy, TDS return filing assistance, business registrations and practical advisory support for businesses across India.
Reliable compliance starts with informed decisions and accurate supporting records.
Online Tax Filings
Serving businesses across India
info@onlinetaxfilings.in
Request a Consultation
© 2026 Online Tax Filings. All rights reserved.