FAQs
Categories
Sub-Categories
- (Q1.) Can I edit the unmatched Challan details?
- Yes, the unmatched challan details can be edited through "Tagging the challan to the statement" .
- The challan with "Zero" amount can be replaced with a challan having available balance through "Tagging the challan to the statement" .
- Please check the CIN details (BSR Code/Date of Deposit/Challan Serial Number and Challan Amount) of the challan you are looking for. Please note that only those Challans which have available balance and which are within the range of +1/-1 financial year will be reflecting under "TAG Challan" option.
- If the challan is unmatched due to wrong Assessment Year but is within the range of +1/-1 Assessment Year, it will be available in "Tagging challan to statement option" for correction.
- Challans are unmatched if TAN or CIN details (BSR Code/Date of Deposit/Challan Serial Number and Challan Amount) quoted in the statement Do Not Match with OLTAS details.
- Yes. You have to move deductees of the excess amount to the challan with available balance. In case there is No challan available, you have to pay the challan and then move the deductees accordingly.
- This error occurs when the last correction for the relevant statement is still NOT processed. Please wait for some time till the last correction for the relevant statement gets processed.
- BIN will not reflect in "TAG challan" option if either the BIN is fully consumed or BIN is not related to the same Financial Year, Quarter, and Form Type.
- Yes. You have to move deductees of the excess amount to the BIN with available balance. In case there is No BIN available, you have to generate a new BIN and then move the deductees accordingly.
- This error occurs when Deductor bifurcates the Challan amount in different columns, the sum of which is more than the Actual amount deposited. Deductor needs to check the remaining balance for the same challan under challan status tab.
- Yes, BIN details in the statement can be corrected through "Challan Correction" option under 'Unmatched Challan' header through Tagging the challan to the statement.
- Rejection reasons pertaining to challan details are as follows:
- Challan detail record on which correction has been filed does not exist in regular / previous statement.
- In a correction statement, verification keys from challan data should match with the corresponding fields in regular statement
- Challan detail/Transfer voucher verification keys for Non Nil Statement do not match with some of the non updatable matched challan columns - Last transfer voucher number, Last Bank-Branch Code / Form 24G Receipt Number, Last date of transfer voucher / bank Challan, Last deposit amount as per challan.
- Challan detail / Transfer voucher verification keys for Nil challan do not match with that of original. - Last date of transfer voucher number / bank challan, last total deposit amount as per challan.
- If an unmatched challan is being corrected, then the sum of deposit amount of all the active deductee rows in the regular and correction statement and corrected values of claimed TDS interest and claimed TDS Others amount should be less than or equal to Total deposit amount of challan given in statement.
- If a matched challan is being corrected, then available balance amount in the challan should be sufficient for consumption of updated sum of deposit amount of all the active deductee rows in correction and corrected values of claimed TDS interest and claimed TDS Others amount
- In case of existing matched / partially matched challan, Deductor can only update Cheque / DD Number, claimed TDS Interest amount , claimed TDS Others amount and Section code
- If Deductor updates only deductee details, then claimed TDS Interest amount and claimed TDS Others amount as given in the challan should match with the corresponding values present in regular / previous return
- Challan details in correction do not match for some of the non-updatable matched challan columns
- New Challan detail record number already present in the database for adding CD record
- Deductor can select 'other' option in the challan for making the payment of late filing fee u/s 234E if column for late filing is not available.
- The fields that can be corrected by Deductor through bank are tabulated below:
- Correction through bank is applicable only for physical Challan only (TDS/TCS deposited by personally visiting bank and submitting Challan).
- If challan paid through online mode (internet challan), the above challan fields like: Financial Year, Minor Head (200 and 400), Major Head (20/21) and Section Code (Nature of Payment) except Section Code 195 can be corrected through OLTAS Challan Correction functionality available on TRACES website at Deductor login.
- For correction in TAN or PAN Field in the OLTAS Challan, submit application for correction along with relevant documents to the jurisdictional AO of the correct TAN/PAN who will create an electronic ticket over AO portal. Thereafter it will be forwarded for approval of the AO in whose jurisdiction the credit of the current challan is lying. The process of challan correction will be completed after his approval. Updated challan status can be verified at the TRACES website at the deductor's login.
- When Deductor reports Challan details in the statement which is different from the Challan Details mentioned in the Challan/OLTAS, and then Challan mentioned in the Statement will be considered as Unmatched/ Mismatch Challan. The Mismatch may be because of:
- Mismatch in CIN Details
- Mismatch in Challan Amount.
- When reported amount of deductee rows in Annexure-1 of the statement is more than OLTAS Available amount of Challan, and then Challan mentioned in the Statement will be considered as overbooked challan.
- Deductor can deposit the Short Payment default amount through ITNS Challan No. 281 by ticking minor head 400.
Deductor can receive short payment in following cases and follow the given procedure for online correction: - Short payment due to insufficient balance - Deductor needs to check that how much amount has consumed against the deductee row, then move the deductee rows to the challan with sufficient available balance through "Resolution of Overbooked Challan (Movement of Deductee Row)" option (refer E-tutorial for detail).
- Short payment due to mismatch in challan - Deductor can correct the mismatch challan through "Challan Correction" option under "Unmatched challan" header (refer E-tutorial for detail)
- Tag the challan with available balance to the nil challan. Once it is processed, then you will be able to download Conso file.
- Yes, BIN details in the statement can be corrected through "Challan Correction" option under 'Unmatched Challan' header. Refer e-tutorial Online Correction - Challan Correction for more details.
| Sr.No | Challan Field | Period for Correction Request (in days) | |
|---|---|---|---|
| Through Bank | Through Assessing Officer | ||
| 1 | PAN / TAN | Within 7 days from challan deposit date | After 7 days from challan deposit date |
| 2 | Assessment Year | Within 7 days from challan deposit date | No Assessing officer Approval required (can be done through OLTAS Challan Correction functionality available on TRACES) |
| 3 | Major Head | With 3 months from challan deposit date | No Assessing officer Approval required (can be done through OLTAS Challan Correction functionality available on TRACES) |
| 4 | Minor Head | Within 3 months form challan deposit date | No Assessing officer Approval required (can be done through OLTAS Challan Correction functionality available on TRACES) |
| 5 | Nature of Payment | Within 3 months form challan deposit date | No Assessing officer Approval required (can be done through OLTAS Challan Correction functionality available on TRACES) |
| 6 | Total Amount | Within 7 days from challan deposit date | ------Not applicable------- |
Note:
