Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
When a TDS entry is absent from your Form 26AS despite being recorded in your books as a receivable, the most common cause is not a missing deposit — it is a challan mismatch. TDS challan mismatch resolution in India requires identifying which field was entered incorrectly in the deductor’s TDS return, then tracking the correction through TRACES until Form 26AS reflects the credit.
What a TDS Challan Mismatch Is
OLTAS (Online Tax Accounting System) maintains a record of every tax challan deposited through authorised bank branches. When a deductor files a quarterly TDS return, the system attempts to match each challan reference in the return against the OLTAS record. If any of the three identifying fields — BSR code, challan serial number, or deposit amount — do not match, the challan is flagged as unmatched. The consequence for the deductee is that the TDS entry in the return cannot be confirmed as deposited, so Form 26AS does not update.
A challan mismatch is distinct from non-deposit of TDS. The money has been paid to the government; the error is in how the transaction was identified in the TDS return.
Three Types of Challan Mismatch
Wrong BSR Code
The BSR code is the 6-digit Reserve Bank of India branch code of the bank branch where the challan was deposited. Deductors who use multiple banks or who copy challan details from a prior period sometimes transpose digits or use an outdated BSR code after a branch merger. OLTAS cannot locate the challan because the branch identifier is wrong.
Wrong Challan Serial Number
Each challan receives a unique serial number from the bank at the time of deposit. Transcription errors — particularly when challan details are entered manually into the TDS return — result in a serial number that does not exist for the given BSR code and date combination. TRACES will show the challan status as unmatched.
Amount Difference
If the challan was deposited for a consolidated amount covering multiple deductees or sections, and the return entries are split in a way that does not sum to the challan total, the system may flag one or more entries. This also occurs when a revised payment was made but the original challan amount was used in the return.
Challan Mismatch Types: Detection and Resolution
| Mismatch Type | Detection Method | Resolution Action | Estimated Correction Time |
|---|---|---|---|
| Wrong BSR code | TRACES challan status shows unmatched; OLTAS search by amount+date finds correct BSR | Deductor files C2 correction with correct BSR code | 3–7 business days after C2 processed |
| Wrong serial number | TRACES: challan serial not found for given BSR+date | C2 correction with correct serial number | 3–7 business days |
| Amount difference | Form 26AS amount differs from TDS receivable ledger | C2 correction aligning return entries to challan total | 3–7 business days |
| Wrong quarter | Challan deposited in Q3, return filed under Q4 | C2 correction moving challan to correct quarter | 3–7 business days |
Practical Resolution Process
The first step is to download Form 26AS from the TRACES portal and compare it line by line against the TDS receivable ledger, matching by deductor TAN, section code, and quarter. Where an entry is missing or the amount differs, contact the deductor with specific details: the expected amount, the quarter, and the section under which TDS was deducted.
The deductor should log into TRACES, navigate to the challan correction section, and compare the BSR code and serial number in the original return against the bank-issued challan. Once the discrepancy is identified, the deductor files a C2 correction return. The Income Tax India portal provides the updated Form 26AS after the correction is processed.
For organisations with large vendor or client bases, tracking dozens of open challan mismatches through email follow-ups and spreadsheets becomes unmanageable. TDS reconciliation software that maps Form 26AS entries against the TDS receivable ledger, flags unmatched rows by TAN and quarter, and generates follow-up records per deductor reduces the manual effort and the risk of mismatches going undetected until ITR filing. Reconciliation software India platforms that integrate TRACES data via API can further automate the detection step.