Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Recipients of large TDS deductions—IT services companies, consulting firms, and high-volume subcontractors—often find that standard TDS rates over-collect tax relative to their actual annual liability. Section 197 of the Income Tax Act provides the remedy: a tds lower deduction certificate section 197 india issued by the Assessing Officer on TRACES that authorises deductors to apply a reduced rate. Using it correctly requires discipline from both the recipient (applying early, distributing the certificate to all deductors) and the deductor (verifying on TRACES before applying any reduction).
What Section 197 Is
Section 197 permits a resident recipient to approach their Assessing Officer with a formal application demonstrating that the TDS that would be deducted at standard rates across the year would exceed their estimated total tax liability. If the AO is satisfied, a certificate is issued specifying a lower rate (or nil in some cases) for listed TDS sections. The certificate is valid for one financial year only—it must be renewed annually. It does not apply automatically to the next year. The legal basis for applying a lower rate exists only from the date the deductor receives and verifies the certificate; payments made before that date are governed by the standard rate.
Reconciliation Challenges
Certificate Date vs Payment Date Gap
A certificate issued on 15 June is furnished to the deductor on 20 June. Payments made by the deductor between 1 April and 19 June should have been deducted at the standard rate. Any payments made at the lower rate before 20 June were incorrectly processed and create a short-deduction liability. Reconciliation teams must maintain a log showing: (a) date the certificate was issued by TRACES, (b) date it was furnished to each deductor, and (c) first payment date at the lower rate per deductor. These three dates must be consistent.
Multi-Deductor Certificate Tracking
A consulting firm may issue invoices to 40 clients. It receives one Section 197 certificate but must distribute it to all 40 deductors. Each deductor verifies independently on the TRACES portal. If 5 of the 40 deductors continue deducting at the standard rate—either because they did not receive the certificate or did not process it—Form 26AS will show a mix of rates for section 194J. The recipient must identify which deductors applied the wrong rate and request revised TDS certificates (Form 16A) for affected quarters.
Lower Deduction Certificate Rate Comparison
| TDS Section | Standard Rate | Typical LDC Rate | Applicable To | Certificate Section |
|---|---|---|---|---|
| 194J (professional fees) | 10% | 1–2% | IT/consulting firms with low net margins | 197 |
| 194C (contractor payments) | 2% (companies) | 0.5–1% | Large subcontractors | 197 |
| 194H (commission) | 5% | 1–2% | Distributors and agents | 197 |
| 194I (rent) | 10% | 2–5% | Property owners with mortgages | 197 |
| 194D (insurance commission) | 5% | 2% | High-volume agents | 197 |
India-Specific Reconciliation Angle
The Section 197 certificate changes the expected TDS rate in the recipient’s TDS receivable ledger for the entire financial year from the date of furnishing. If a company expects ₹50 lakh in 194J income and holds a 2% LDC, the TDS receivable should be booked at ₹1 lakh (2%) rather than ₹5 lakh (10%). Any deductor still applying 10% generates a ₹4 lakh unexpected credit—which must be traced to that specific deductor and reconciled against Form 26AS Part A each quarter.
TDS reconciliation software configured for LDC scenarios maintains a per-deductor expected-rate table, compares it against Form 26AS entries for each quarter, and flags any deductor still applying the standard rate despite a valid certificate being on file. Reconciliation software India that supports certificate lifecycle management—tracking issue date, furnishing date per deductor, and validity expiry—eliminates the April error of applying last year’s certificate to the new financial year. Quarterly reconciliation against TRACES data, downloadable from the TRACES portal, provides the verification baseline for every rate applied during the year.
Section 395 Under the New Income Tax Act 2025
Section 197 has been renumbered as Section 395 under the Income Tax Act 2025, effective April 1, 2026. The new provision retains the core mechanism — a certificate authorising lower or nil TDS — but introduces three significant changes that affect both applicants and deductors.
Expanded scope. Under the old Section 197, lower deduction certificates were available only for specified TDS sections listed in the provision. Section 395 expands the scope to cover all TDS provisions under the new Act. This means recipients subject to TDS under sections that were previously excluded from the Section 197 list can now apply for lower deduction certificates — a material change for enterprises that were unable to obtain LDCs for certain payment categories.
AI-driven processing. The Assessing Officer review process has been replaced with a fully digitized, AI-driven assessment system. Applications filed through TRACES are now processed algorithmically, using the applicant’s tax history, advance tax record, and prior-year LDC utilisation data to determine the appropriate lower rate. This is expected to reduce processing times from the current 4-8 weeks to a significantly shorter window, though the statutory 30-day deadline remains unchanged.
Transitional validity. LDC certificates issued under the old Section 197 for FY 2025-26 remain valid for payments made through March 31, 2026. For payments from April 1, 2026 onwards, a new certificate under Section 395 is required. Enterprises holding existing LDCs should plan their renewal applications under the new framework well before the March 2026 expiry to avoid a gap period where the standard rate applies.
Deductors must update their rate tables and TRACES verification workflows to reference Section 395 certificate numbers for FY 2026-27 onwards. The certificate verification mechanism on TRACES continues to function as before — only the section reference and the underlying processing engine have changed.