NSDL Return Preparation Utility (RPU) version 2.6 released

New TDS software will alert about Unmatched challan, Invalid PAN, Challan pending amount. A new RPU version has been released in accordance to these updations.

Key features of NSDL Return Preparation Utility (RPU) version 2.6 

  • Unmatched challan: On import of consolidated file in the NSDL RPU (version 2.6), an alert messageStatement contains unmatched challan. The same has been highlighted in red colour will be provided if the consolidated file imported contains unmatched challan.
  • Deductee/ Salary details records with invalid PAN: On import of consolidated file in the NSDL RPU (version 2.6), an alert message will be provided Statement contains invalid PANs. The same has been highlighted in red colour if the statement contains invalid PAN in deductee/ salary detail records.
  • Challan pending amount: If the user attempts to over utilize the challan amount then the error message Deductee deposit amount exceeds the Challan / transfer voucher amount for Challan Serial Number(s) will be provided on validating the file and the file will not be validated.
  • Update of PAN: If for a given deductee / salary detail record. if the user attempts to update the PAN more than once then error message Further update of PAN for the deductee record is not allowed. Update of deductee PAN (valid to valid) is allowed only once will be provided.

Govt. Deductors: Change in due dates of filing eTDS returns

Income Tax Department has changed the date of TDS filing for Govt. Deductors vide notification 57/2011 dated 24.10.2011. The due date of filing eTDS returns has been extended by 15 days for first three quarters of the Financial year but remains the same for last quarter ending 31st March. The amendment is applicable from 01.11.2011 & so it is applicable from the 3rd quarter of F.Y. 2011-12.

Please Note:The changed due dates are applicable only for Government Deductors. For other Deductors there is no change in the due dates.


Sl. No.

Date of ending of the quarter

Due dates for Govt. Deductors

Due dates for Other Deductors





30th June

30th September

31st December

31st March

31st July

31st October

31st January

15th May

15th July

15th October

15th January

15th May



This notification relates to eTDS returns covered under rule 31A means for quarterly returns for Forms – 24Q (Salary), 26Q (section 193 to 196D except entries covered in 27Q) and 27Q. As the rule 31AA has not been amended so TCS (Form 27EQ) return due dates remains unchanged unless notified later.

The amendment is applicable only for Govt. Deductors




Correction in OLTAS challan

      3 Comments on Correction in OLTAS challan

NSDL receives tax collection data as uploaded by the bank.  NSDL is not authorized to carry out any changes in the data  sent by the bank to TIN.


The fields that can be corrected by the Taxpayer through Bank are tabulated below:

Sl. No.

Type of Correction on Challan Period for correction request (in days)


PAN / TAN Within 7 days from challan deposit date


Assessment Year Within 7 days from challan deposit date


Total Amount Within 7 days from challan deposit date


Major Head Within 3 months from challan deposit date


Minor Head Within 3 months from challan deposit date


Nature of Payment Within 3 months from challan deposit date

Note :

1.Above correction mechanism is applicable only for physical challans with deposit date greater than equal to September 1, 2011.
2. Any correction request initiated by the taxpayer after the time limit specified above shall be rejected by Bank.
3. For challans with challan deposit date from September 1, 2011 to September 30, 2011, the time limit for correction in TAN/PAN, Assessment Year and Amount will be within 45 days from challan deposit date.
4. The fields that can be corrected and the entity authorized to carry out corrections on challan with deposit date less than September 1, 2011 are as below:

Sl. No.

Type of Correction on Challan Performed By


PAN / TAN Assessing Officer


Assessment Year Assessing Officer


Major Head Assessing Officer / Bank


Minor Head Assessing Officer


Nature of Payment Assessing Officer


Total Amount Bank


Name Bank



Inconsistencies in the TDS / TCS statements

      No Comments on Inconsistencies in the TDS / TCS statements

When you file your TDS / TCS return, first the details  regarding deposit of TDS/TCS made by you is compared with the data given by banks. The data is uploaded by banks on the  basis of the TDS/TCS challans received by them. For this purpose, the Challan Identification Number (CIN), TAN and  TDS amount as given in your TDS/TCS return is compared with the corresponding details given in the challan details provided by the bank that has accepted the tax. (CIN consists of the BSR code of the branch where you deposited the tax, date on which you deposited tax and the challan serial number which have beenstamped on the counter foil of the challan given to you). Depending on this, different types of inconsistencies creep up in the returns.

Once these are matched, the PAN ledger of each deductee is credited with the TDS/TCS as provided in your return provided the PANs of the deductees have been given by you in the return.

The types of inconsistencies are as below: 


If all the CIN details in the TDS / TCS return match with the corresponding details provided by the banks, the challan is shown as matched as the payment claimed to have been made by you is also validated by the bank

Match Failed

In this case CIN given in your TDS / TCS return is found in the bank data. But the TAN and / or amount as given in your return against this CIN do not match with the TAN and / or amount given against this challan by the bank.

Match Pending

In this case, the CIN as given in your statement is not available in the CIN details provided by the banks.

Count of Missing deductee PAN

If you have not provided the PAN details of some of your deductees, the count of such cases is provided.

Count if deductee PAN not present in ITD database

If some of the deductee PAN provided by you are not present in Income Tax Department (ITD) database, the count of such cases is provided.

Impacts of the inconsistencies are as below:

  • In case of inconsistency, there would be no posting in the PAN ledger of the deductee with the amount of tax deducted/tax collected on his behalf. He may, therefore, have difficulty in proving the TDS /TCS claimed by him in his income tax return.
  • If challans claimed in the TDS/TCS returns could not be matched completely with the data given by the banks, you may have difficulty in proving to your TDS assessing officer that you have actually deposited the TDS/TCS deducted by you.