TDS Return Filing

A short-payment default appears on TRACES when the TDS reported as deducted doesn’t fully match the challans mapped to it, usually because of incorrect challan mapping or a challan not being picked up. It’s the most common TDS return default. We resolve it by reconciling challans against OLTAS and filing a correction statement that maps the deposited challans correctly, clearing the demand. Correct mapping at filing time is how we prevent it in the first place.

A short-deduction default arises when you deducted less than the correct amount on a payment, often from applying the wrong section, the wrong rate or an outdated threshold and TRACES raises a demand for the under-deducted tax plus interest. Unlike short payment (a challan-mapping issue), short deduction is about the amount deducted being too low. We report the correct amounts, apply current rates and thresholds and file corrections where an earlier return under-deducted.

Because wrong challan mapping is the top cause of short-payment defaults. Each deduction you report has to be linked to the specific deposited challan that covers it; if the mapping is off, wrong challan, wrong amount, a challan missed, the return doesn’t reconcile and TRACES raises a demand even though you paid. It’s a myth that mapping “doesn’t matter much.” We map every deduction to the correct challan and reconcile against OLTAS, so the return ties out exactly.

The justification report is the detailed breakdown TRACES issues when your return has a default it spells out exactly what’s wrong (which challan, which deductee, what shortfall) and what’s demanded. Ignoring it means the default never gets fixed and grows with interest. We read your justification report, identify precisely what needs correcting and file the right correction statement to clear it, turning a confusing demand into a resolved matter.

No, that’s a costly myth. Unresolved defaults on TRACES grow with interest and can escalate to recovery action; they must be actively cleared by filing a correction statement. Leaving a short-payment, short-deduction or PAN default sitting there only makes it bigger and keeps your deductees from their credit. We monitor your TRACES status each quarter and clear any default promptly, so nothing snowballs.

A correction (revised) return fixes errors in an already-filed TDS return, wrong challan mapping, an incorrect deductee PAN, a missed deductee or amount errors. Because returns can’t be edited freely, corrections are filed against the original using its token number and a conso file downloaded from TRACES. Correction filing is often what clears short-payment and PAN defaults and finally gets deductees their credit. We read your justification report and file the right correction.

Because TDS returns can’t be edited freely after filing, the system requires errors to be fixed through formal correction statements filed against the original return, using its token number and a conso (consolidated) file downloaded from TRACES. This structure is exactly why corrections trip up DIY filers, who get stuck at the conso-file and justification-report stage. We handle the correction process end to end, so an error in a filed return actually gets fixed rather than lingering.

The common ones: challan corrections (fixing wrong challan details or mapping deductions to the right challan to clear short-payment defaults), PAN corrections (fixing a deductee PAN so their credit flows), amount corrections (adjusting deduction or deposit figures to fix short deduction), adding or deleting deductees (including a missed one or removing a wrong entry) and adding challans (mapping an additional deposited challan). We identify which your return needs from the justification report and file it correctly.

A conso (consolidated) file is a download from TRACES containing the full, as-filed data of your original return, it’s the base you edit to prepare a correction statement, filed against the original using its token number. You can’t file a correction without it. Getting corrections right is often where the real value is and where DIY filers get stuck. We pull the conso file, apply the fixes and file the correction so your defaults clear and deductees get their credit.

Yes, this is a common request and very fixable. We pull the justification reports and conso files for each affected quarter, identify exactly what’s wrong (remap challans, correct PANs, adjust amounts) and file correction statements to clear the defaults, restoring your vendors’ and employees’ credit in Form 26AS and giving you a clean validated process going forward. Send us your TRACES login and the affected quarters and we’ll work through the backlog.

Form 16 is the annual TDS certificate an employer issues to employees, summarising salary paid and tax deducted under Section 192. Form 16A is the quarterly certificate for non-salary TDS on contractor, professional, rent, commission and interest payments. Both are generated from TRACES after the return is processed and let the deductee claim credit. We download and issue both to your people on time, so they can file their own returns smoothly.

No, filing the return and issuing the certificate are two separate obligations. It’s a myth that Form 16 is optional once you’ve filed 24Q; you must issue Form 16 from the filed return, by the 15 June due date, so employees can claim their credit and file their own ITRs. A filed return with no certificate leaves your staff stuck. We generate Form 16 from your processed 24Q and issue it on time to every employee.

When your return is filed correctly and processed, each deduction, mapped to the right PAN and challan, flows into that deductee’s Form 26AS as tax credit they can claim against their own liability. That’s the whole point of the return: it’s how your vendor or employee actually sees the tax you deducted on their behalf. If the PAN is wrong or the challan doesn’t reconcile, the credit doesn’t reach them. We file accurately so every deductee’s credit lands where it should.

Usually it’s a PAN error, an unreconciled challan (short-payment default) or a return that hasn’t processed cleanly, any of which stops the deduction from reaching the vendor’s Form 26AS. The fix is to read the TRACES justification report, correct the PAN or challan mapping and file a correction statement. We diagnose exactly why the credit isn’t flowing and file the correction that restores it, so your vendors stop chasing you and stay on side.

If you hold a TAN and have been deducting in other quarters, it’s generally expected that you either file the return or submit a declaration of non-filing for a nil quarter to keep your deductor record clean and avoid notices for non-filing. The exact treatment depends on your situation. We advise on and handle nil-quarter filing or declarations, so your compliance stays gap-free even in a quiet quarter.

From FY 2025-26, partnership firms and LLPs must deduct 10% TDS on partner remuneration above ₹20,000 a year and report it in Form 26Q like any other non-salary deduction. The partners are added as deductees and the deductions mapped under the correct section. Many firms are reporting this for the first time, so getting the deductee setup and section right matters. We handle it cleanly from the first quarter, so partner-payment TDS is reported without a default.

Form 27Q reporting for payments to non-residents requires extra care — the correct rate under Section 195, the payee’s residential status and any DTAA relief all have to be reflected accurately and the deductee details differ from resident reporting. Mistakes here are easy and costly. We prepare 27Q with the correct rates and DTAA notes, so payments to NRIs and foreign parties are reported cleanly and the deductee’s position is right.

No. Property buyers under 194-IA and individual tenants under 194-IB file a ‘challan-cum-statement’ Form 26QB for property and 26QC for rent rather than a regular quarterly return and use their PAN instead of a TAN. It’s a different mechanism from the 24Q/26Q return cycle. We handle these challan-cum-statements too, so whether you’re a regular deductor or a one-off property buyer, the right filing is done correctly.

Yes. We regularly help businesses file overdue quarterly returns and clear the resulting defaults. We gather the deduction and challan data for each pending quarter, reconcile and validate it, file the returns and calculate the late fees and interest involved so there are no surprises. We then put you on a tracked quarterly routine so you stay current from then on. A backlog is very recoverable, the key is starting now.

Late filing attracts a fee of ₹200 per day under Section 234E, running from the due date until the return is filed, capped at the total TDS amount. Beyond that, non-filing or filing incorrect details can attract a penalty of ₹10,000 to ₹1,00,000 under Section 271H. Short-payment and short-deduction defaults bring demands plus interest and PAN errors deny credit until corrected. All are avoidable with accurate, on-time filing, which is exactly what our quarterly process ensures.

Yes. If TRACES or the department raises a demand for a short payment, short deduction, late fee or PAN error, we review the justification report, identify exactly what’s wrong, file the necessary correction statement, arrange payment of any genuine dues and respond to resolve the matter. Many demands trace back to fixable challan or PAN issues. Existing clients get this support as part of how we stand behind our work. (We also offer dedicated TDS/TCS notice handling.)

Keep the token number (provisional receipt) for each return, the conso files, your challans, the deductee data and copies of the Form 16/16A you issued. These are essential for filing corrections, defending the return if a notice arises and for audits. Income tax law requires records to be retained for several years. We maintain an organised archive of your returns, token numbers and certificates as part of the service, so your records are always ready.

For FY 2025-26 returns you continue using the familiar section numbers (194C, 194J, etc.) and current form names, so this year’s filing is unchanged. From FY 2026-27, the new Income Tax Act, 2025 moves TDS to a consolidated, code-based system and renames some forms and certificates. Using old section references for payments from 1 April 2026 will cause filing errors. We file correctly under today’s rules now and will guide your transition to the new framework next year.

Yes. TDS compliance runs on national systems, the e-filing portal and TRACES, so we can manage it for businesses anywhere in the Vasai-Virar and Palghar There’s no government fee to file. You pay our professional fee either per return or as a quarterly plan based on the number of deductees and forms plus 18% GST; correction returns carry a modest additional fee and the TDS itself is deposited to the government separately. And because returns are filed on national systems (the e-filing portal and TRACES), we serve businesses across Vasai-Virar, Palghar, the wider MMR and beyond, fully online. region, the wider Mumbai Metropolitan Region and beyond, fully online. You share your TAN and payment data digitally and we handle deduction guidance, deposits, returns, certificates and notices remotely. For local businesses we’re also happy to meet in person at our office on Mahatma Gandhi Road, near T.B. College. Distance is no barrier to clean, on-time TDS.

Because your returns simply get filed, accurately, validated, on time, quarter after quarter and your defaults get cleared. We reconcile challans against OLTAS, validate every PAN, run the FVU before upload, select the right form, issue Form 16/16A on time, save your token numbers and file correction statements when something needs fixing. We reply quickly on call and WhatsApp, keep organised records and handle TDS alongside your income tax, GST and accounting under one roof.