Section 194C TDS on contractor payments is one of the most frequently misapplied provisions in India’s TDS framework. Accounts receivable teams in IT services, staffing, and construction companies deal with rate mismatches and multi-branch TAN complexity every quarter. This article explains the rate structure, where reconciliation breaks down, and how to resolve the most common variances.
What Section 194C Is
Section 194C requires any specified entity — companies, firms, trusts, government departments — to deduct TDS when making payments to a resident contractor for carrying out any work. The rate is 1% for payments to individuals and Hindu Undivided Families (HUFs) and 2% for all other contractors, including private limited companies, LLPs, and partnership firms. The deduction threshold is ₹30,000 per payment or ₹1,00,000 in aggregate during a financial year. Sub-contractors are also covered: a main contractor paying a sub-contractor must deduct at the same rates.
Where Reconciliation Issues Arise
Rate Mismatch: Individual vs Company
The single most common 194C variance is the TAX_DEDUCTION variance caused by applying the wrong rate. A client’s accounts payable team marks a contractor as “individual” in their ERP, triggering 1% deduction, when the contractor is actually a private limited company and 2% applies. On a ₹10,00,000 payment, this creates a ₹10,000 shortfall in Form 26AS credit — a gap that the contractor’s finance team must chase through a correction return or gross-up claim at ITR filing.
Sub-Contractor TDS Chains
When a main contractor engages sub-contractors, two TDS deduction events occur on overlapping work: the client deducts from the main contractor, and the main contractor deducts from the sub-contractor. Each deduction uses a different TAN and appears as a separate row in the respective payees’ Form 26AS. Reconciling the sub-contractor’s Form 26AS requires identifying which TAN belongs to the main contractor and confirming that the challan for that deduction was deposited by the 7th of the following month.
Multi-Branch TAN Multiplicity
Enterprise clients — particularly banks, retail chains, and IT firms with registered offices in multiple states — maintain separate TANs for each branch or division. A logistics vendor serving a client with 12 regional offices may receive 12 separate TDS deductions under 12 different TANs, all for Section 194C, across a single quarter. Form 26AS lists each row individually. Manual reconciliation of these rows against 12 separate invoices takes a senior accounts executive two to three working days per quarter.
Section 194C Variance Reference Table
| Variance Type | Root Cause | Variance Code | Reconciliation Action |
|---|---|---|---|
| Rate applied 1% instead of 2% | Payee type set as individual in client ERP | TAX_DEDUCTION | Request correction return from deductor; file Form 26A if needed |
| Wrong TAN on certificate | Branch TAN used vs registered TAN | TAX_DEDUCTION | Confirm TAN via TRACES; ask deductor to refile |
| Wrong section (194J vs 194C) | Work contract misclassified as professional service | TAX_DEDUCTION | Obtain rectification from deductor; document nature of work |
| TDS deposited late | Challan filed after 7th of following month | UNEXPLAINED | Verify challan date on TRACES; credit appears next quarter |
| Rounding difference | Deductor rounds to nearest rupee, ERP rounds differently | ROUNDING | Accept if within ₹1; flag if > ₹1 |
| TDS not deposited | Deductor deducted but did not remit | UNEXPLAINED | Issue notice under Section 205; escalate to deductor’s finance team |
Reconciling 194C in Practice
For organisations with more than 20 active contractor relationships, Form 26AS reconciliation against the TDS receivable ledger typically takes three to five working days each quarter. The primary match keys are: Deductor TAN, Section code (194C), quarter, amount deducted, and certificate number. Amount alone is unreliable because multiple invoices may share the same value.
TDS reconciliation software that applies a four-pass matching engine — UTR, partial reference, counterparty TAN, and date proximity — reduces this cycle to under four hours for organisations with 50 or more active contractor deductors. TransactIG’s Test Pack 2 (781 rows) showed a match rate improvement from a 51% baseline to 88% after applying weighted signal matching, with the counterparty signal (deductor TAN) carrying a 0.15 weight in the scoring model. Tolerance tiers handle the rounding variance: any amount difference within ₹1 on a high-confidence match is auto-accepted.
Organisations using reconciliation software India-wide deployments at the group level can consolidate all branch-level TAN deductions into a single reconciliation workspace, eliminating the need to open Form 26AS for each TAN separately.
TDS rates, section applicability, and Form 26AS download instructions are published on the Income Tax India e-filing portal.