The Income Tax Department has confirmed an important update. OLTAS Challan Correction for Tax Year 26-27 will soon be available on TRACES 2.0. This news brings relief to many taxpayers and deductors. Until now, this correction facility was missing from the new portal. As a result, many people faced delays and confusion.
What Is Changing on TRACES 2.0?
TRACES 2.0 is the upgraded version of the government’s tax portal. It was launched as part of the transition to the new Income-tax Act, 2025. However, several legacy features did not carry over immediately. OLTAS Challan Correction was one of them.
Until this update rolls out, taxpayers must still use the older TRACES portal. This applies specifically to challans linked with FY26 and Tax Year 2026-27. Soon, though, this gap will close. The correction facility will move fully to TRACES 2.0.
Why This Correction Facility Matters
Mistakes in TDS challans happen more often than people expect. A wrong financial year, an incorrect section code, or a mismatched amount can create real problems. For instance, TDS credit may not reflect correctly against your records. Consequently, this could raise your tax payable during return filing. It may also cause mismatches between TDS statements and official records.
Therefore, timely correction is essential. Deductors managing TAN-based compliance rely heavily on this feature. Without it, resolving errors becomes a slow, manual process.
What Can Be Corrected Through OLTAS
Several challan fields qualify for correction without Assessing Officer approval. These include the financial year, minor head code, major head code, and section code. However, some exceptions apply. Section Code 195, for example, still requires approval from the Jurisdictional Assessing Officer.
Additionally, corrections only apply to unclaimed or matched challans. Fully consumed or partially consumed challans fall outside this scope. Deductors should verify challan status before starting the correction process.
How the Process Currently Works
For now, users must complete corrections through the legacy TRACES portal. The process involves a few clear steps. First, log in using your TAN credentials. Next, navigate to the challan correction section. Then, enter the challan details, including BSR code and deposit date. Finally, review and submit your correction request.
Processing usually takes between 24 and 48 hours. After approval, the system reflects updated challan details. However, once the new update goes live, this entire process will shift smoothly to TRACES 2.0.
What Taxpayers and Deductors Should Do
Meanwhile, caution remains important. Double-check the financial year and other details before submitting any TDS payment. Small errors can lead to bigger complications later. Also, keep monitoring official TRACES announcements for the exact rollout date.
Once TRACES 2.0 fully supports OLTAS Challan Correction, the experience should feel more streamlined. Users will likely benefit from a modernized interface and faster processing. Until then, patience and accuracy remain your best tools.
Final Thoughts
This update marks a meaningful step forward for India’s tax administration system. Although the transition has caused temporary inconvenience, the department is actively closing these gaps. Soon, OLTAS Challan Correction for TY 26-27 will be fully functional on TRACES 2.0. Taxpayers and deductors should stay alert for the official announcement and prepare accordingly.
Recent Comments