Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
What TDS Reconciliation Involves
TDS reconciliation compares two records of the same tax deduction: your company's TDS receivable ledger (what you expect to be credited) and Form 26AS from the TRACES portal (what the government has actually recorded). A match means the deductor deposited the correct amount under your PAN for the correct quarter and section. A mismatch means credit is either missing, incorrect, or delayed.
Under Indian tax law, you can only claim TDS credit against your income tax liability if the corresponding entry exists in Form 26AS. If a client deducted ₹1,00,000 from your invoice under Section 194J but deposited only ₹95,000 under your PAN, you lose ₹5,000 of credit — either by understating the deduction in your return or by paying the shortfall as advance tax.
For IT services companies, consulting firms, and any organisation that bills professional services at scale, TDS receivable can represent a meaningful portion of total tax liability. Unreconciled TDS across a fiscal year is, in practical terms, a tax loss.
Why TDS Reconciliation Fails in Practice
The structural problem is that TDS reconciliation involves three parties — your company, the deductor (your client or vendor), and the government — and errors introduced by the deductor can only be fixed by the deductor. Your finance team can identify the mismatch but cannot correct it unilaterally.
Deductor errors in TDS returns
The most common reason Form 26AS does not reflect expected TDS is a deductor error: wrong PAN, wrong quarter, or wrong TDS section in the filed return. These errors are not visible to you until you download Form 26AS and compare it entry by entry. A deductor with 500 vendors may have batch-filed a TDS return with a typographical error in your PAN — and the return was accepted by the system because the format was valid, not because the content was correct.
Timing gaps between deduction and deposit
TDS must be deposited by the 7th of the month following deduction (or 30th April for March deductions). Form 26AS is updated after the CHALLAN is processed, which can add 3 to 7 days further. If your reconciliation window closes before the deposit is processed, a legitimate deduction will appear as a mismatch. At quarter-end, this timing gap is systematically wider because deductors file in bulk.
Multi-deductor volume and branch-level complexity
An IT services company with 80 active clients may receive TDS deductions under Section 194J from each client across four quarters. If each client bills from a different branch with a different TAN (Tax Deduction Account Number), the total number of Form 26AS entries to reconcile can run into hundreds per quarter. At this volume, a VLOOKUP-based process is not slow — it is structurally incapable of producing a reliable output without significant manual review.
The TDS Reconciliation Process: Step by Step
A structured TDS reconciliation process has four stages. The output of each stage feeds the next. Skipping stages or combining them into a single spreadsheet exercise is where most errors originate.
Step 1 — Download and structure Form 26AS data
Download Form 26AS in text or Excel format from the TRACES portal for the relevant assessment year. Extract Part A (TDS on salary) and Part A1 (TDS on non-salary) into a structured format with at minimum: deductor TAN, deductor name, TDS section, transaction date, certificate number, amount paid, TDS deducted, and TDS deposited. This is your source-of-truth dataset from the government.
For organisations that have transitioned to the Annual Information Statement (AIS), the same data appears under the TDS/TCS section of AIS, which is more granular and includes transaction-level detail rather than quarterly aggregates.
Step 2 — Extract TDS receivable from your books
From your ERP or accounting system, extract the TDS receivable ledger for the same period. This should show each invoice raised, the TDS expected at the applicable rate, and the client TAN if captured at the time of invoicing. If your ERP does not capture TAN at the invoice level, this is a data quality gap that will make exact matching impossible — you will need to match by deductor name and amount instead, which introduces ambiguity.
Step 3 — Match and classify exceptions
Match each Form 26AS entry to the corresponding TDS receivable entry using TAN + quarter + section as the primary key. Where an exact match exists, mark the entry as reconciled. Where no match exists or amounts differ, classify the exception into the appropriate variance type (see table below). This classification is not optional — different variance types have different resolution paths, and resolving them all through a single "follow up with deductor" step will produce inconsistent results.
Step 4 — Raise correction requests and close the loop
For each classified exception, initiate the appropriate resolution: request a correction return from the deductor (for PAN or quarter errors), follow up on pending deposits (for not-deposited entries), or write off rounding differences within your documented tolerance. Track each exception to closure. The quarter's TDS reconciliation is complete only when every exception is resolved or documented with a management approval for the outstanding amount.
Common TDS Variance Types and Resolution Paths
| Variance Type | Description | Resolution |
|---|---|---|
| PAN_MISMATCH | Deductor quoted wrong PAN in TDS return | Deductor files correction return citing correct PAN |
| QUARTER_ERROR | TDS deposited in wrong quarter (e.g., Q1 instead of Q2) | Deductor files correction return with correct quarter |
| RATE_DIFFERENCE | Deductor applied different TDS rate than invoiced | Commercial follow-up for the shortfall amount |
| NOT_DEPOSITED | TDS deducted but CHALLAN not yet deposited with govt | Follow up with deductor to deposit and file TDS return |
| ROUNDING | Sub-₹10 difference due to rounding at deductor end | Write off if within tolerance; document with approval |
| SECTION_MISMATCH | TDS deposited under wrong section code (194C vs 194J) | Correction return required; may affect rate applied |
TransactIG assigns structured variance codes to each TDS exception automatically. See variance taxonomy →
How Automated TDS Reconciliation Works Differently
A structured TDS reconciliation engine does not simply replicate the VLOOKUP approach at higher speed. It changes the matching logic, the exception management model, and the output format.
Matching logic: Instead of matching on a single field, the engine applies a multi-signal approach — TAN, PAN, quarter, section code, and amount — with configurable tolerance on the amount field (e.g., allow matches with ≤₹10 difference for rounding). This captures legitimate matches that a strict-equality VLOOKUP would flag as mismatches.
Exception management: Unmatched entries are not presented as a raw list. Each exception is classified by variance type and assigned a resolution path. A SECTION_MISMATCH exception has a different owner and timeline than a NOT_DEPOSITED exception. Grouping them together in a single "pending" tab creates confusion and delays resolution.
Audit trail: Every match decision — including overrides and write-offs — is logged with timestamp and user identity. For tax department inquiries, this log is more valuable than the reconciliation spreadsheet, because it shows the reasoning behind each adjustment.
TransactIG's four-pass matching engine applies deterministic matching first, then fuzzy matching for entries where the deductor name or certificate number varies slightly between the ERP export and Form 26AS. In a validated test on 781 rows of TDS data, this approach improved match rates from 51% (exact match only) to 88% (multi-signal matching with tolerance).
TDS Reconciliation by Deductee Type
The complexity of TDS reconciliation varies significantly by the nature of the organisation's client base and revenue structure.
- ▸ IT Services and Consulting: High volume of Section 194J deductions from enterprise clients. Multiple TAN entries per client (branch-wise). Common issues: PAN errors in bulk TDS returns, timing gaps at quarter-end.
- ▸ Healthcare and Hospitals: TPA settlements often carry TDS on professional services. Multiple TPAs with different TAN registrations. Common issue: TDS deducted at summary level, not traceable to individual invoices.
- ▸ Staffing and Manpower: TDS on contract staffing invoices under 194C (if treated as work contract). Client interpretation of section (194C vs 194J) often differs from the staffing firm's invoicing basis, creating structural rate mismatches.
- ▸ Real Estate and Infrastructure: TDS on rent (194I) and contractor payments (194C). RERA-escrow-related TDS entries may require matching to milestone-specific invoices rather than a running ledger.
The Income Tax department's e-filing portal and TRACES provide the source data for all TDS reconciliation. Understanding the data structure and update cycles of these portals is a prerequisite for building a reliable reconciliation process, regardless of whether you use a spreadsheet or dedicated software.
For organisations processing high volumes of TDS, see how TransactIG handles TDS reconciliation for IT services and the invoice-with-TDS matching pattern in detail.
When to Consider a Dedicated TDS Reconciliation Tool
A spreadsheet-based TDS reconciliation process is adequate when the number of active deductors is below 30, all deductors use a consistent TAN and PAN, and the total TDS receivable per quarter is below ₹5 lakhs. Above these thresholds, the risk of undetected errors and the staff cost of manual matching typically justify structured tooling.
The key indicator is not volume — it is the exception rate. If your TDS reconciliation regularly produces more than 10% unmatched entries that require manual investigation, the process is producing noise faster than the team can resolve it. At that point, the bottleneck is not staff effort; it is the absence of a structured classification and resolution framework.
See the full evaluation framework in the reconciliation software guide for a seven-dimension comparison between spreadsheet and purpose-built approaches.
Form 26AS vs AIS vs TIS: Three Data Sources for TDS Verification
The Income Tax department now provides three overlapping data sources for TDS verification, each with a different scope and purpose. Understanding which source to use — and when — is essential for accurate reconciliation.
Form 26AS (Tax Credit Statement) is the original source, available from the TRACES portal. It contains TDS/TCS credits reported by deductors, advance tax and self-assessment tax payments, refund details, and high-value transaction data. For TDS credit claims in your income tax return, Form 26AS remains the authoritative source — if a TDS entry does not appear here, the credit cannot be claimed.
Annual Information Statement (AIS) is a broader dataset introduced by the Income Tax department. It includes TDS/TCS data (mirroring Form 26AS) plus additional financial information: interest income, dividend income, share transactions, mutual fund purchases, foreign remittances, and rental receipts. The AIS also includes a feedback mechanism — taxpayers can submit corrections or flag entries as inaccurate directly on the compliance portal. This feedback does not change Form 26AS but creates an audit trail of disputed entries.
Taxpayer Information Summary (TIS) is a derived summary generated from the AIS. It aggregates financial data into categories (processed value, information value, derived value) and presents a consolidated view. TIS does not contain new data — it reorganises AIS data for easier comprehension. For TDS reconciliation specifically, TIS is useful as a cross-check but not as a primary matching source.
The practical reconciliation workflow is: match your TDS receivable ledger against Form 26AS for credit confirmation, use AIS to identify additional financial transactions that may require tax treatment, and review TIS for a consolidated summary before filing. For enterprise TDS reconciliation, Form 26AS remains the primary dataset. AIS adds breadth but does not replace the credit-level precision of Form 26AS.
TDS Reconciliation as a Deductor
Most TDS reconciliation guidance focuses on the deductee side — verifying that TDS credits appear correctly in Form 26AS. But organisations that deduct TDS from payments to vendors, contractors, and professionals face an equally demanding reconciliation requirement on the deductor side.
As a deductor, reconciliation means matching three datasets: the TDS deducted per your books (recorded in Forms 24Q for salary, 26Q for non-salary, and 27Q for non-resident payments), the challans deposited with the government, and the quarterly TDS returns filed on TRACES. Each dataset must agree on PAN of the deductee, TDS section applied, amount deducted, and the quarter of deduction.
The deposit deadline is the 7th of the month following deduction (with the exception of March, where the deadline is 30th April). A missed deposit attracts interest under Section 201(1A) at 1% per month from the date of deduction to the date of deposit. Reconciliation must therefore verify not just that the correct amount was deposited, but that it was deposited by the due date.
Common deductor-side errors include: depositing TDS under the wrong section code (194C instead of 194J), using an incorrect PAN for the deductee, consolidating multiple deductees into a single challan without maintaining the individual breakup, and filing the quarterly return with amounts that do not match the challans deposited. Each error creates a downstream problem for the deductee's Form 26AS, which eventually generates follow-up requests from your vendors asking for correction returns.
A structured deductor reconciliation process runs monthly — not quarterly — to catch deposit and filing errors before they compound. Organisations with 200+ vendor payments per month typically find that monthly challan-to-ledger matching prevents 80% of the correction return requests that would otherwise arrive at quarter-end.
Penalties for TDS Non-Compliance
TDS non-compliance carries a layered penalty structure that escalates significantly with duration and intent. Understanding these penalties provides the financial context for investing in a structured reconciliation process.
| Section | Nature | Consequence |
|---|---|---|
| 201(1A) | Interest on late deduction or deposit | 1% per month (late deduction) or 1.5% per month (late deposit) from date of deduction to deposit |
| 40(a)(ia) | Disallowance of expenditure | 30% of the payment amount disallowed as a business expense if TDS was not deducted or deposited |
| 234E | Late filing fee for TDS return | ₹200 per day of delay, up to the total TDS amount for the quarter |
| 271H | Penalty for failure to file TDS return | ₹10,000 to ₹1,00,000 penalty imposed by Assessing Officer |
| 276B | Criminal prosecution for non-deposit | Rigorous imprisonment of 3 months to 7 years with fine for wilful failure to deposit TDS |
The compounding effect is significant. Consider a scenario where ₹50 lakh of TDS is deducted in Q1 but deposited 4 months late due to a reconciliation gap. Section 201(1A) interest at 1.5% per month amounts to ₹3 lakh. Section 234E late filing fee at ₹200 per day for 120 days adds ₹24,000. Section 40(a)(ia) disallowance of 30% on the underlying expense — if the payment was ₹5 crore — creates a tax impact of approximately ₹45 lakh at a 30% tax rate. The total financial exposure from a single quarter's reconciliation failure can exceed ₹48 lakh.
These penalties apply independently — an organisation can face interest, late filing fees, penalty, and disallowance simultaneously for the same default. Structured TDS reconciliation that identifies deposit delays and filing gaps within the month of occurrence eliminates the compounding risk entirely.
How much working capital is your TDS gap actually costing?
The TDS Mismatch Estimator runs entirely in your browser. Adjust four inputs — annual TDS, deductee count, gap %, resolution lag — to see the rupee exposure, interest cost, and analyst hours your 26AS gap is consuming.
Run the TDS Mismatch Estimator →